Overview
This article explains what the Raiser's Edge NXT (RE NXT) integration does after setup: which constituents it syncs, how it decides they have consented to SMS, which phone number it uses, how constituent codes become tags, and how gifts are recorded and attributed as donations in Tatango.
There are two sync paths, they are both included, and they follow the same rules:
Path | When it runs | What it does |
Daily sync | Once a day | Runs your saved Tatango query in RE NXT (which must be a Dynamic query) and adds or updates every constituent it returns. |
Real-time sync | Within a few minutes of a gift being added in RE NXT | Checks the donor against your query's criteria and consent settings, then adds or updates them and records the gift as a donation. |
Constituent code changes are also synced in real time (see Constituent codes become tags below).
Who gets synced
The real-time sync mirrors the criteria of your saved RE NXT query so the two paths agree on who belongs on your list.
Always applied
The constituent must be an Individual. Organization records are never added.
If your query excludes Inactive or Deceased constituents (the checkboxes at the top of the query editor), the real-time sync excludes them too.
Taken from your query
Constituent Code criteria, whether on the constituent's primary constituency or on any of their constituencies.
Solicit Code criteria.
AND / OR connectors and parentheses are evaluated exactly as RE NXT evaluates them (AND before OR).
Criteria on other fields, such as Date Last Changed or giving totals, are used by the daily sync when RE NXT runs the query, but are not re-evaluated on the real-time path. A new donor who matches your code criteria is added immediately even if their record would not have appeared in yesterday's daily run.
Ended codes do not count. A constituent code or solicit code with an end date in the past, or marked inactive, is ignored for eligibility and for tags.
Check your parentheses. Because AND binds before OR, a query like Constituency = Donor OR Constituency = Volunteer AND Solicit Code ≠ Do Not Text only applies the Do Not Text exclusion to volunteers. Group the OR in parentheses so the exclusion applies to everyone.
SMS consent
Eligibility also depends on consent. You choose one of two models on the last step of the setup wizard (Use RE NXT Consent).
Solicit code model (box unchecked)
A constituent is eligible unless they carry the Tatango SMS Opt-Out solicit code.
When a subscriber texts STOP, Tatango adds the Tatango SMS Opt-Out solicit code to their RE NXT record.
To keep someone off your list, add this solicit code to their record in RE NXT.
RE NXT Consent model (box checked)
A constituent is eligible only if their most recent SMS consent record in RE NXT is Opt in. Consent category does not matter; the newest SMS consent entry wins.
Constituents with no SMS consent record are not eligible.
When a subscriber texts STOP, Tatango records the opt-out on their RE NXT consent.
Both models apply to the daily sync and the real-time sync.
Which phone number is used
RE NXT phone types are free text, so the integration does not rely on a phone being labeled "Mobile". Instead it ranks every active phone on the constituent and tries them in order:
Phone types that look like a mobile number (for example Mobile, Cell, Cell Phone) rank highest.
The phone type you mapped in the setup wizard ranks next. If you mapped Cell Phone to Phone Number, phones of that type are preferred.
The constituent's primary phone gets a boost.
Phone types that look like a landline rank lowest, and fax numbers are skipped entirely.
Tatango then tries the top-ranked number. If the carrier reports it as a landline or unreachable, the next candidate is tried, and so on. If no number is accepted, the constituent is not added, but any gift they made is still recorded (see Donations below).
Mapping more than one phone column in the setup wizard gives the integration more candidates to work with. You do not need to guess which column holds the mobile number.
Which fields are sent
Only the fields you mapped in the Data Mapping step are sent to Tatango, plus:
System Record ID, used to match the RE NXT record to the Tatango subscriber.
Tags, from the constituent's active constituent codes.
Phone number, chosen as described above.
Mapped columns are resolved automatically to the right RE NXT data, including standard constituent fields, preferred address fields, the triggering gift's date and amount (Last Gift Date / Last Gift Amount), and constituent custom fields. Dates that are missing a month or day in RE NXT (for example a birth year only) are left blank rather than sent as a partial date.
Constituent codes become tags
Every active constituent code on a synced constituent becomes a tag on the Tatango subscriber, using the code's name. Use these tags to segment messages, for example to text everyone tagged Monthly Donor.
Tags stay in sync in real time:
When a constituent code is added in RE NXT, the matching tag is added to the subscriber.
When a code is changed or given an end date, tags are reconciled: active codes are added, and tags whose names match a constituent code that is no longer active on the record are removed.
Tags that are not constituent code names are never touched. Tags you add manually or through other tools are safe.
Code changes never add or remove someone from your list. Eligibility is decided only at gift time and during the daily sync.
To find the subscriber, the integration uses the System Record ID custom field you mapped, and falls back to matching on phone number if needed.
Donations and message attribution
Every gift that triggers the real-time sync is recorded as a donation in Tatango.
If the donor was added or updated as a subscriber, the donation is attached to that subscriber.
If no phone number could be accepted, the donation is still recorded and attributed to the list's most recent message so it is not lost from reporting.
Attributing gifts to a specific message
With donation tracking set up (see the setup guide, Part 3), gifts can be tied back to the exact text message that produced them:
You create an Appeal in RE NXT with a unique ID for the message, for example
SMS_2026-09-15_FallCampaign.When you shorten the giving link in your Tatango message, you add
appeal_idas a parameter with that appeal ID as the value.The giving form passes the appeal onto the gift in RE NXT.
When the gift is added, the integration reads the gift's appeal ID, finds the Tatango message that used it, and attributes the donation to that message.
If a gift arrives with no appeal, or with an appeal that no Tatango message used, the donation is attached to the subscriber and attributed to their most recent message instead.
Attribution depends on the appeal being on the gift record. RE NXT online giving forms pass it automatically when the link carries appeal_id. Gifts entered manually or through third-party processors need the appeal set on the gift for attribution to work.
Timing
Gift and code events are processed in batches and usually appear in Tatango within one to five minutes.
Daily sync runs once a day.
Opt-outs are sent to RE NXT as soon as the subscriber unsubscribes.
Frequently asked questions
A donor gave but was not added to my list. Why?
Check, in order:
they are an Individual (not an Organization)
they pass your query's constituent code and solicit code criteria;
they are not inactive or deceased if your query excludes those
they pass the consent check for the model you chose
they have at least one phone number the carrier accepts as a mobile number.
Can I add a field to the sync without contacting Tatango? Yes. Add the column to your saved RE NXT query, create a matching custom field in Tatango if needed, then edit the integration from My Apps and add the mapping.
Do I need to create webhooks? No. The integration creates its RE NXT event subscriptions and the Tatango unsubscribe webhook for you when you finish the setup wizard.
What if I rename or delete a constituent code? Tags follow the code names on the constituent. If a code is ended or removed, the matching tag is removed the next time that constituent's codes change or they are synced.
Need help?
Reach out to your Tatango Customer Success Manager or contact support from the Help menu in Tatango.