A party-aware contribution link sits in the composer next to the tracked link. It drops your committee’s page with the source tag baked in, on whichever rail you run. You never type the URL, and you never point money at a door that won’t open.
A campaign that types its own donation URL types it wrong once. A mistyped link is a dead ask, and a link on the wrong rail is money that never arrives. The fix is to connect the rail once and let the tool carry it.
Txtra works with the processor your committee already uses, ActBlue, WinRed, Anedot, and others. Connect it once and the composer drops your page, source tag baked in. Whichever rail you run, the tool is the same.
One field under the party picker. Every contribution link the composer drops points at your page, tagged to the send that carried it.
Lifetime given, gifts on file, last gift, and the source it read from, all on the contact. Reports leads with the total raised by text.
A campaign that types its own donation URL types it wrong once. The rail follows the party, the slug follows the committee, and the composer does the rest.
A rail that won’t onboard you still renders, grayed, marked will not take you, with the reason underneath. Hiding it leaves a campaign wondering why the option vanished.
Source-tagged gifts from a Txtra send roll into one figure at the top of Reports, broken into gifts, average gift, and the send that drove the most.
Changing the party theme repaints the app. It does not always move your money. On an any-party rail like Anedot, a switch repoints nothing, and the confirmation says so. If your committee uses a party-specific rail, the confirmation names the change before it commits. The warning matches what will actually happen.
The read side ships. Donations render on the record and the raised total leads Reports, off seeded data in this build. The write side is the spine job. Live, a gift on the rail sends a receipt, and an adapter writes it onto the record matched to the contact, so the loop closes without anyone exporting a spreadsheet. The rail is yours to choose, partisan or any-party, and the party switch only repoints money when the rail is partisan.
Left or right, Txtra is the sender your carriers trust and your lawyers approve.
The composer carries a party-aware contribution link beside the tracked link. It drops your committee's ActBlue or WinRed page with the source tag baked in, so the gift traces back to the send that asked for it.
Not on its own. Txtra connects to whichever rail your committee already uses. Anedot and similar rails take any party, and a theme switch repoints nothing. Some rails are party-specific by their own rules, and if your committee uses one, changing the party is confirmed before anything commits. The tool stays neutral. The rail is your committee's choice.
Yes. Lifetime given, gifts on file, last gift, and the source. Reports leads with the total raised by text. The read side ships today on seeded data. Live, a gift on the rail writes back to the record through an adapter.