Reconnect SMS Integrations

To send Reconnect SMS messages to users, you must do the following: 

• Step 1: Integrate with your SMS provider. You can integrate directly with your Twilio account, or set up a custom integration to trigger message events through any SMS provider.
• Step 2: Manage your opted-in users. Inform Dynamic Yield which users consent to receive messages.
• Step 3: Identify your users. Use any of our identification events—Login, Signup, Newsletter Subscription, or Identify User. You identify users by Phone Number, Email Address, or any custom type. Learn more about cross-channel identification.
• Step 4: Track engagement. Measure the success of your campaigns.

Step 1: Integrate a messaging provider

Step 2: Manage your opted-in users

Make sure your users have given consent to receive marketing SMSs. You can inform Dynamic Yield of their opt-in status by uploading a subscriber list or by sending real-time API events. We strongly recommend using both methods to ensure that any newly opted-in users are captured and can receive messages immediately—without waiting for the next feed sync.

Option 1: Upload a subscriber list 

The subscriber list is a CSV file that you upload to an AWS S3 bucket, and sync daily.  

Important to know before you begin:

• Each section supports one subscriber list for each channel integration, in this case, SMS. 
• You should upload a file of your current opted-in users once a day. 
• You must use the same identifier type in the subscriber list as you defined in your provider integration. So if you set the integration identifier as a custom user ID (or email address), that's the identifier value you must use in the subscriber list file.

• The identifier value you use to opt users in is passed as-is to your messaging provider in the message JSON, using the variable ${User identifier}. Learn more about user data variables

• The identifier type you use in the opt-in feed and events must match what you share in the identification events and what you send to your messaging provider. For example, if you want to pass a plain-text email value to your provider as part of the Reconnect API call, set Email as your integration’s identifier, share plain-text email addresses in the opt-in feed and events, and make sure to add the email (as a hashed value) in your identify events.

Uploading and syncing your subscriber list

1. In Reconnect › Integrations, on the relevant channel integration card, click Sync Now.
2. Click Continue. An S3 bucket is generated.
3. Click Copy Credentials and store the S3 bucket details and the credentials in a safe location so they don't get lost or exposed. 
4. Prepare your CSV file according to the following format:
   • File type: CSV
   • Encoding: UTF8 encoding
   • File name: data.csv
   • First row: "phone numbers"
   • Remaining rows: Plain text phone numbers, one per row (up to 10 million rows). Each number should consist of the country code, area code, and subscriber number with digits only, in E.164 format.

   Example:  

   

   Download a sample CSV file: data.csv

5. Upload the CSV file to the following folder in the S3 bucket with the appropriate date information:
   upload_yyyy-MM-dd_HH-mm
   For example:
   upload_2020-03-19_14-00
6. Upon file upload, synchronization to Dynamic Yield is initiated within a few minutes.

POST /v2/userdata/channels/sms/opt-in

Headers: { 
  "accept": "application/json", 
  "content-type": "application/json", 
  "dy-api-key": "your-api-key"   
}

Body: { 
  "identifier": { 
    "type": "IdentifierTypeHere (email|phoneNumber|custom)", 
    "value": "UserIdentifierValueHere" 
  } 
}

POST /v2/userdata/channels/sms/opt-out

Headers: { 
  "accept": "application/json", 
  "content-type": "application/json", 
  "dy-api-key": "your-api-key"   
}

Body: { 
  "identifier": { 
    "type": "IdentifierTypeHere (email|phoneNumber|custom)", 
    "value": "UserIdentifierValueHere" 
  } 
}