Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tatango

Connect Anedot to Tatango to add Action Page donors with phone consent to a Tatango list, manage your connection, and review field mapping and payload data.

The Tatango integration in Settings > Integrations adds donors and supporters who give phone communications consent on your Action Pages as subscribers to a list in Tatango, an SMS (text message) marketing platform. This page covers how to connect Anedot to Tatango, manage your connection, see what Anedot sends, find your data in Tatango, and review field mapping and payload data.

Before You Begin

  • You need Integrations: Edit permissions to add, edit, push or delete a connection. Integrations: Edit permissions also require Action Pages: View permissions and Integrations: View permissions. See Permission Sets.

  • You need a Tatango account with the list you want subscribers added to.

  • You need three values from Tatango: an API key, the email address you use to log in to Tatango, and the List ID. See Step 1: Find Your API Key and List ID.

  • Anedot only sends a record when the submission has a phone number and the donor has given phone communications consent. On each Action Page you'll send, add a Phone Number field, and make it required if you want every submission to include a number. Set up communications consent in the Page Builder under Page > Form, in the Communications consent section. See Communications Consent.

Connect Anedot to Tatango

Step 1: Find Your API Key and List ID

API keys are created in Tatango, not in Anedot. We recommend creating a dedicated API key for this connection and labeling it so you can tell it's used for Anedot.

To create an API key:

  1. Log in to your Tatango account.

  2. Go to My Account > Api Keys.

  3. Create a new API key and label it, for example "Anedot".

  4. Copy the API key.

Each connection uses one list, and List ID is required. A List ID is a number that identifies a Tatango list. Have the List ID ready for the list you want subscribers added to.

You'll enter these values in the Tatango API key, Tatango login email address and List ID fields in Anedot.

Step 2: Create the Connection in Anedot

To create the connection:

  1. Go to Settings > Integrations.

  2. Click New integration.

  3. Choose Tatango.

    Tatango appears under the SMS Marketing category with the text "Send Action Page donors to Tatango lists."

  4. Choose the Action Page scope:

    • Keep All Action Pages checked to include every Action Page, including pages you add later. (Optional) In Exclude Pages, enter a comma separated list of Action Page IDs with no spaces.

    • Uncheck All Action Pages and choose pages in Selected pages to include only the pages you pick.

  5. (Optional) In Team, choose a Team to limit the connection to that Team's Action Pages. Leave it set to All teams to include every Team. See Teams.

  6. Enter your API key in Tatango API key.

  7. Enter the email address you use to log in to Tatango in Tatango login email address.

  8. Enter your List ID in List ID.

  9. (Optional) Check Bypass opt-in process to have Tatango add the phone number without double opt-in. This box is unchecked by default.

  10. (Optional) Uncheck Bypass opt-in response if you want Tatango to send its confirmation text message. This box is checked by default, which suppresses the confirmation text message sent to subscribers.

  11. (Optional) Check Relay donation pages only to skip Lead Page submissions. Event Pages are still sent. This box is unchecked by default.

  12. Click Create integration.

The connection is created, and Anedot starts sending new qualifying records to your Tatango list.

Step 3: Create Custom Fields in Tatango

Some keys Anedot sends aren't predefined Tatango subscriber fields. To store them, create a matching custom field on your Tatango list for each of these keys: form_type, title, middle_name, occupation, source_code, donation_date and donation_amount.

To create a custom field in Tatango:

  1. Go to the list you connected and select Settings.

  2. Choose Custom Fields.

  3. Click New Custom Field.

  4. Enter a Label.

  5. Choose a Type:

    • Text for form_type, title, middle_name, occupation and source_code.

    • Date for donation_date.

    • Number for donation_amount.

  6. Enter the exact key Anedot sends, for example donation_amount, as the Merge Tag.

  7. Save the field.

Repeat these steps for each key. The fields phone_number, first_name, last_name, email and zip_code are predefined in Tatango and don't need custom fields.

Manage Your Connection

Edit Your Connection

You can change the Action Page scope, Team, Name, Enabled, Bypass opt-in process, Bypass opt-in response and Relay donation pages only on an existing connection. Provider is shown but can't be changed.

To edit your connection:

  1. Go to Settings > Integrations.

  2. Click Edit on the Tatango connection.

  3. Update the settings you want to change. The first time you edit the connection, enter a Name.

  4. Click Save integration.

New settings apply to records sent from then on. Editing doesn't resend records already sent, and unchecking Enabled stops sending.

The Tatango API key, Tatango login email address and List ID aren't shown in the Edit form. To change any of them, delete the connection and connect again with the new values. See Delete Your Connection.

Push Unsent Records

Push unsent is on the connection's row in Settings > Integrations. It sends submissions, including Lead Page and Event Page submissions, and successful recurring charges in the date range you enter.

  • Enter a Start date and End date. The dates default to the last 30 days in your account's time zone.

  • The range can be up to 31 days.

  • The start date must be within the last 12 months.

  • Wait about five minutes between pushes.

  • The connection's Action Page scope, Team and Relay donation pages only settings still apply. Incomplete donations and failed charges aren't sent.

  • If the phone number is already on the Tatango list, Anedot doesn't add it again.

For full steps, see Push Unsent in Webhooks (API).

Delete Your Connection

To delete your connection:

  1. Go to Settings > Integrations.

  2. Click Delete on the Tatango connection.

  3. Confirm the prompt "Delete this integration?".

Anedot stops sending to Tatango.

To reconnect, follow the steps in Connect Anedot to Tatango again.

Data Relays

What Anedot Sends

Anedot sends the person as a subscriber to the Tatango list in List ID, as a JSON POST to /api/v2/lists/{List ID}/subscribers on https://app.tatango.com. Before sending, Anedot checks whether the phone number is already on the list.

  • Donation Pages and Event Pages: After a successful payment, Anedot adds the person to the list with the fields in Field Mapping. Event Page registrations with no charge are sent when the registration is submitted.

  • Lead Pages: Anedot sends the submission when it's created, unless Relay donation pages only is checked.

  • Recurring donation payments: A successful recurring charge is sent with the same fields, including donation_amount and donation_date when the total is more than one cent. If that phone number is already on the list, for example from the original donation, Anedot doesn't send it again and doesn't update the subscriber.

Anedot sends the last 10 characters of the phone number as phone_number. Tatango expects a continuous string of ten digits, with no dashes and no country code, for example "2065551111".

Each connection sends to one List ID. To send to another list, create another connection.

Anedot doesn't send refunds, chargebacks, commitment changes such as a cancellation, Abandoned Actions, or later edits to a submission. See Commitments.

Records Anedot Skips

Anedot doesn't send these records, and they don't show a row in Settings > Integrations > Integration Requests:

  • A submission with no phone number.

  • A submission where the donor hasn't given phone communications consent.

  • A record whose phone number is already on that Tatango list.

  • A Lead Page submission when Relay donation pages only is checked.

  • Submissions from Action Pages outside the connection's Action Page scope, including a Team-scoped connection's pages outside that Team.

  • Any submission while Enabled is unchecked.

  • Incomplete Donation Page submissions with no completed donation.

A missing email address doesn't stop a record from being sent. The email is sent as null.

Delivery Statuses

Each send that goes out shows a row in Settings > Integrations > Integration Requests with its status (Success, Failure or Error), the request and the response. The stored request is the JSON body, and the API key isn't stored. See Integration Requests.

  • Success: Tatango accepted the request with an HTTP 2xx response, including HTTP 200. Tatango's success messages include "Subscriber added".

  • Failure: Tatango returned any other HTTP status, including HTTP 401, 404 or 422. These rows aren't tried again automatically. Use Push Unsent Records to try them again.

  • Error: Anedot couldn't complete the request, for example because of a connection problem. Anedot tries again automatically.

Anedot doesn't check whether a number is a landline before sending. Tatango rejects a home phone (non-cellular number) with the message "Bad phone number: landline or unreachable carrier" and status code 422, and the row shows Failure.

Repeated authorization errors (HTTP 401 or 403) turn the connection off. A successful send resets this. To send again after the connection is turned off, check Enabled and click Save integration.

Users with the Integration sync failed notification turned on get an email when a row shows Failure. See Notifications.

Find Your Data in Tatango

To view the subscribers Anedot sent:

  1. In Tatango, open the list you connected.

  2. Select the Subscribers tab.

The person appears on that list. Values for keys that aren't predefined Tatango fields are stored only if you created matching custom fields. See Step 3: Create Custom Fields in Tatango.

Field Mapping

Anedot Source
Tatango Key

Email, sent in lowercase. A missing email is sent as null.

email

First name

first_name

Middle name

middle_name

Last name

last_name

Title

title

Occupation

occupation

Address postal code

zip_code

Phone number, sent as the last 10 characters

phone_number

Action Page type: "donation", "event", or "lead"

form_type

Source code

source_code

Total in dollars, as a decimal number, only when the total is more than one cent

donation_amount

The date and time the submission or recurring charge was created, only when the total is more than one cent

donation_date

The Bypass opt-in process setting (true or false). When true, Tatango adds the phone number without double opt-in.

bypass_opt_in_process

The Bypass opt-in response setting (true or false). When true, Tatango suppresses the confirmation message.

bypass_opt_in_response

  • Blank values: Blank name or address parts are still included in the request. They may appear as null or as an empty string.

  • Lead Pages: Lead Page submissions have a total of 0, so they never include donation_amount or donation_date.

  • Hidden fields: Hidden field values from the Action Page aren't sent. A hidden field that uses one of these key names doesn't change the value Anedot sends. See Hidden Fields.

  • Not sent: Custom field answers from the Action Page, UTM fields, referrer, fund, country, street address, city and state aren't sent.

  • Custom fields in Tatango: form_type, title, middle_name, occupation, source_code, donation_date and donation_amount need matching custom fields on the list, with the Merge Tag set to that exact key. phone_number, first_name, last_name, email and zip_code are predefined Tatango subscriber fields.

Payload Data

These are the request and response bodies shown in Settings > Integrations > Integration Requests.

Request Body

Response Body (Success)

Response Status (Success)

Response Body (Failure)

Response Status (Failure)

Troubleshooting

Rows Show Failure

Open the row in Settings > Integrations > Integration Requests and read Tatango's response.

  • HTTP 422 with "Bad phone number: landline or unreachable carrier" means the number is a home phone or can't be reached by text message.

  • HTTP 401 is an authorization error. Check that the Tatango API key and Tatango login email address match your Tatango account.

  • For other statuses, check that the API key, login email and List ID match your Tatango account and list.

Fix the cause, then use Push Unsent Records. If the API key, login email or List ID was wrong, delete the connection and connect again with the right values first.

Rows Show Error

An Error row means Anedot couldn't complete the request, for example because of a connection problem. Anedot tries again automatically.

A Donor Doesn't Appear in Tatango

If there's no row in Settings > Integrations > Integration Requests for the submission, Anedot skipped it. Check that:

  • The submission includes a phone number.

  • The donor gave phone communications consent. See Communications Consent.

  • The phone number isn't already on the Tatango list.

  • The Action Page is in the connection's Action Page scope and Team.

  • Enabled is checked.

  • The page isn't a Lead Page while Relay donation pages only is checked.

If a row shows Success but a value is missing in Tatango, check that the list has a custom field with a Merge Tag that matches the key. See Step 3: Create Custom Fields in Tatango.

The Connection Is Turned Off

Repeated authorization errors (HTTP 401 or 403) turn the connection off. To send again, go to Settings > Integrations, click Edit on the Tatango connection, check Enabled, and click Save integration.

Change Your API Key, Login Email or List ID

The Tatango API key, Tatango login email address and List ID can't be changed in the Edit form. Delete the connection and connect again with the new values. See Delete Your Connection.

If the issue continues, contact our Support team at help@anedot.com.

Frequently Asked Questions

What Does Anedot Send to Tatango?

Anedot adds the donor or supporter from each qualifying Action Page submission and successful recurring charge to your Tatango list, with their phone number, name, email, postal code, page type, source code and, for donations, the amount and date. Only records with a phone number and phone communications consent are sent. See Field Mapping.

Where Do I Find My API Key and List ID?

In Tatango, go to My Account > Api Keys to create and manage API keys. A List ID is a number that identifies a Tatango list. Enter the List ID for the list you want subscribers added to.

Can I Change the API Key, Login Email, or List ID Later?

Not in the Edit form. Delete the connection and connect again with the new values.

What Happens If the Donor Is Already on the List?

If the phone number is already on the Tatango list, Anedot doesn't send that record. This includes later gifts and recurring charges from the same number. Anedot doesn't update the existing subscriber.

Which Action Pages Are Sent?

Donation Pages, Event Pages and Lead Pages in the connection's Action Page scope are sent. You choose the scope with All Action Pages, Exclude Pages, Selected pages and Team. When Relay donation pages only is checked, Lead Pages are skipped and Event Pages are still sent.

How Do I Stop Sending to Tatango?

Uncheck Enabled in the Edit form and click Save integration, or delete the connection in Settings > Integrations.

Why Did a Row Show Failure?

Tatango returned an HTTP status other than 2xx, such as HTTP 422 for a landline or HTTP 401 for an authorization error. Open the row in Settings > Integrations > Integration Requests to read the response, fix the cause, then use Push unsent.

Was this helpful?