Tatango

Tatango is a powerful SMS marketing platform designed to help organizations engage supporters via text messaging. Anedot’s integration allows you to relay Action Page submissions with proper opt-in consent directly into your Tatango subscriber lists.

When configured, Anedot will send donor and subscriber data—from both financial and non-financial Action Pages—to your Tatango list. Data is only sent when users opt-in and provide a valid mobile number.

---

Table of Contents

• Connecting Anedot to Tatango
• Data Relays
• Setting Up Custom Fields in Tatango
• Finding Subscribers in Tatango
• Field Mapping
• Payload Data

---

Connecting Anedot to Tatango

Pre-Setup Requirements

To ensure successful relay, you must enable the following fields in the Form tab of the Action Page Builder:

• Communications Consent (toggle ON)

• Phone Number (set as required)

Only valid mobile numbers from verifiable carriers are accepted by Tatango. Landlines or unverified numbers are rejected without appearing as a failure in Anedot.

---

Complete Connection 

To connect Anedot to Tatango, follow the steps below:

1. Navigate to Settings > Integrations > Directory in your Anedot account.

2. Click the blue + New Connection button in the upper right corner.

3. Select Campaign Monitor from the integration directory.

4. Choose the Action Pages you’d like to sync.

   • The default is All Pages.

   • To exclude specific pages, enter their Action Page IDs as a comma-separated list.

5. (Optional) Scope the integration to only include Team-specific data.

6. Enter Tatango Credentials
   • Login Email Address

   • API Key

   • List ID (found in your Tatango list settings)

7. Configure Optional Settings
   • Bypass Opt-In Process: Prevent sending initial opt-in confirmation (default: false)
   • Bypass Opt-In Response: Prevent follow-up opt-in message (default: true)
   • Relay Donation Pages Only: Limit data sync to financial pages (default: false)
8. Click Save to complete setup.

---

Data Relays

• Supported Pages:
  Relays are supported for both financial and non-financial pages—unless filtered using the “Relay Donation Pages Only” option.

• Relay Requirements:

  • Communications Consent must be toggled on.

  • Phone number must be required and valid (mobile carrier only).

• Relay Fields:

  • Includes default fields and custom fields (must be preconfigured in Tatango).

  • Fields that are not predefined must be manually added in Tatango.

• Push Unsent Support:

  • Failed or unsent relays can be retried by date range using the Push Unsent feature.

• Failure Handling:

  • After 5 consecutive failed relay attempts, the integration is marked inactive, and no further relays are sent until reactivated.

---

Setting Up Custom Fields in Tatango

To match custom data fields from Anedot:

1. Go to your Tatango list and open the Settings > Custom Fields tab.

2. Click New Custom Field.

3. Enter:

   • A label for the field

   • The Anedot field name as the merge tag

   • The field type

4. Save your new field. All fields (predefined and custom) will appear in the list.

---

Finding Subscribers in Tatango

Tatango identifies each subscriber using their unique phone number. To find them:

• Go to your Tatango List > Subscribers tab.

• You’ll see each record created from relayed submissions.

---

Field Mapping​

Anedot Field Name	Tatango Field Name	Tatango Field Type
email	email	predefined
phone	phone_number	predefined
address {postal_code}	zip_code	predefined
firstName	first_name	predefined
lastName	last_name	predefined
"lead" or "donation"	form_type	custom - text
title	title	custom - text
middleName	middle_name	custom - text
occupation	occupation	custom - text
source_code	source_code	custom - text
date	donation_date	custom - datetime
donation_amount	donation_amount	custom - number

---

Payload Data

Request Headers

{ }

Request Body

{
  "subscriber": {
    "email": "admin@anedot.com",
    "title": "",
    "zip_code": "70113",
    "form_type": "donation",
    "last_name": "Dot",
    "first_name": "Annie",
    "occupation": "Analyst",
    "middle_name": "",
    "source_code": "EOY22",
    "phone_number": "2252501301",
    "donation_date": "2023-05-11T15:03:03.287Z",
    "donation_amount": 10.0,
    "bypass_opt_in_process": false,
    "bypass_opt_in_response": false
  }
}

Response Body (Success)

{
  "status": "Subscriber has already been sent opt-in message for this list.",
  "subscriber": {
    "tags": [],
    "email": "admin@anedot.com",
    "gender": null,
    "carrier": 77,
    "zip_code": "70506",
    "birthdate": "",
    "last_name": "Dot",
    "api_source": "Anedot/50af806d",
    "cleaned_at": null,
    "first_name": "Annie",
    "carrier_name": "Verizon",
    "clean_reason": null,
    "keyword_name": null,
    "opted_out_at": null,
    "phone_number": "2252501301",
    "opt_in_method": "api",
    "subscribed_at": "2023-05-11T07:45:33.000-07:00",
    "optin_in_progress": true
  }
}

Response Body (Failure 1)

{
  "error": "List not found",
  "status": "error"
}

Response Body (Failure 2)

{
  "error": "API key authorization failure",
  "status": "error"
}

Response Body (Failure 3)

{
  "error": "Bad phone number: landline or unreachable carrier",
  "status": "error"
}

Response Status (Success)

200

Response Status (Failure 1)

404

Response Status (Failure 2)

401