Overview

Twitter is a social media platform where users interact with each other using tweets and messages. Twitter Ads platform allows advertisers to share various types of ads and reach their customers. Connect your Twitter Ads account with Lytics to send audiences to Twitter and target them with specific ads to increase your return.

Authorization

If you haven't already done so, you will need to set up a Twitter Account and Twitter Ads Account before you begin the process described below. Please refer to Twitter's authentication document for details on how Lytics accesses Twitter's Ads API.

If you are new to creating authorizations in Lytics, see the Authorizations documentation for more information.

  1. Select Twitter from the list of providers.
  2. Select the authorization method. Note that different methods may support different job types. Twitter supports the following authorization methods:
  3. Enter a Label to identify your authorization.
  4. (Optional) Enter a Description for further context on your authorization.
  5. Complete the configuration steps needed for your authorization. These steps will vary by method.
  6. Click Save Authorization.

Twitter Sign-In

This authorization allows Lytics to access your Twitter Ad account.

  1. Select Twitter Sign-In Oauth authorization method.
  2. From the user selection window, select the Twitter account you want to connect from the list of accounts.
  3. Click Allow.

Export Audience

Use this export job to send Lytics user to Twitter Custom audience

Integration Details

  • Implementation Type: Server-side Integration
  • Implementation Technique: REST API Integration
  • Frequency: Real-time Integration
  • Resulting data: Twitter Custom Audience matched with users from the selected Lytics audience.

This integration utilizes Twitter Ads API to send the Lytics audience users. Once the job is started, it will:

  1. Create a new Twitter Custom Audience with the name format Lytics {audience_slug} {YYYYMMDD_hhmmss} if it does not already exist.
  2. For every user entering the selected Lytics audience, the job adds the user's selected identifiers and adds them to the add queue. Similarly, for every user exiting the selected Lytics audience, the selected user's identifiers will be placed on remove queue.
  3. Both the add and remove queue are sent to Twitter using its Custom Audience Users API.
  4. The export job will run continuously. The add/remove queue of users are sent to Twitter every 5 minutes or when the batch reaches 1,000 users.

Fields

The export job gives you an option to select to send Email, Device ID, Twitter Handle and Twitter ID as part of job configuration. Please refer to Twitter documentation to learn more about each type of identifier. Identifiers already SHA-256 hashed are accepted, otherwise plain user-identifier data will be SHA-256 hashed before being exported to Twitter.

Configuration

Follow these steps to set up and configure an export job for Twitter in the Lytics platform. If you are new to creating jobs in Lytics, see the Destinations documentation for more information.

  1. Select Twitter from the list of providers.
  2. Select the Export Audience from the list.
  3. Select the Authorization you would like to use or create a new one.
  4. Enter a Label to identify this job you are creating in Lytics.
  5. (Optional) Enter a Description for further context on your job.
  6. Complete the configuration steps for your job.
    twitter-export
  7. From the Twitter Ad Account input, select the Twitter Ad Account.
  8. (Optional) From the Twitter Custom Audience input, select an existing Twitter custom audience to export Lytics users to. If no audience is selected, a new custom audience will be created with the name format Lytics {audience_slug} {YYYYMMDD_hhmmss}.
  9. From the Identifier Fields Mapping input, map the value from Lytics field to Twitter Identifier field. At least one of Email, Device ID, Twitter Handle or Twitter ID must be mapped. Identifiers already SHA-256 hashed are accepted, otherwise plain user-identifiers will be SHA-256 hashed.
  10. Click the Start job button to start the job.