Visit our new documentation site! This documentation page is no longer updated.

Writing Job Results into Twitter Tailored Audience

You can write job results directly to your Twitter Tailored Audience.

Table of Contents

Prerequisites

  • Basic knowledge of Treasure Data, including the toolbelt.
  • A Twitter Ads Account or an account with Ads Manager role.
  • Authorized Treasure Data Twitter app access to your Twitter Ads Account

Step 1: Create a new connection

Go to Treasure Data Connections. Locate and select Twitter Tailored Audience.



The following dialog will open.



Select an existing OAuth connection for Twitter, or click the link under OAuth connection to create a new connection.



Create a new OAuth connection

Log into your Twitter account (if you haven’t logged in previously) and grant access:



Or grant access to Treasure Data app when you are already logged in.



You will be redirected back to Treasure Data Connections. Repeat the first step (Create a new connection) and choose your new OAuth connection.



You can give a name to your newly created connection and save it for later use.



Step 2: Configure to output results to Twitter Tailored Audience connection

Check Output results at top of your query editor and select your Twitter Tailored Audience connection as follows:

There are several parameters to define:

  • Twitter Ad Account ID (required): This is your Twitter Ad Account ID. See appendix C for getting account id.
  • Tailored Audience Name (required): Name of Tailored Audience list to create.
    • Important note: If you have many Tailored Audience lists with similar names as this input, the latest Tailored Audience Name will be used. We recommend that you give your Tailored Audience list a unique name.
  • Audience type (require): Type of entry in the list. It is one of email, id, device id or handle.
  • No need to normalize and hash records (default false): Indicates whether the data has already been normalized and hashed. If not, TD automatically normalizes and hashes the records.
  • Retry limit (optional, default 6): Number of retries before it gives up.
  • Initial intervals in milliseconds between retries (optional, default 10000): Interval to retry if a recoverable error happens (in millisecond).
  • Maximum intervals in milliseconds between retries (optional, default to 32000) : Maximum time in milliseconds between retrying attempts.

Here is a sample configuration:

Step 3: Write the Query to populate a tailored audience list

For the initial release, we are supporting create new Tailored Audience list

On Treasure Data console, run the following query with Output results into a connection of Twitter Tailored Audience (see Appendix A for more details of column naming):

SELECT email FROM (
  VALUES ('demo1@example.com'),
         ('demo2@example.com'),
         ('demo3@example.com')
)  tbl (email)

The above query will not match any real users, it’s for demo purpose only. Also, the query requires no source table (for the ease of testing out this feature), but you still must choose a database, so pick “sample_datasets” or any other arbitrary table.

The query should complete in a few seconds. After that, check the Twitter Audience Manager for your new list:

Twitter takes up to 24 hours to validate your newly created list. Therefore, the list will have the status: “Processing”.

Status changes to “Ready” (or an error if the list is not valid) within 6 to 8 hours.

Appendix A: Tailored Audience data

Output result needs to follow Twitter Tailored List data specification here. We are currently supporting single column, single type

  • TWITTER_ID: Twitter user IDs
  • DEVICE_ID: IDFA, AdID or Android ID of Twitter users
  • EMAIL: Email addresses
  • TWITTER_HANDLE: Twitter users name aka. Screen names

Appendix B: Data Normalization

Treasure Data result output normalizes your values automatically to follow Twitter’s normalizing rules, see here.

All values, uploaded to Twitter for matching, must be normalized with the normalizing rules of Twitter. The values will narrowly miss chances to match if they are not normalized. If you need to normalize values by yourselves, apply your own normalization before attempting to output results.

The following conversion behavior is applied according to data type during result output for normalization.

  • Email Addresses : Lowercase, remove leading and trailing spaces; ex: support@twitter.com
  • Twitter User Name : No @, lowercased and leading and trailing spaces trimmed; ex: jack
  • Twitter User IDs : Standard integer; ex: 143567
  • Device IDs : Lower-cased with dashes (IDFA), original format on device, not capitalized with dashes (AdID) and original format on device, not capitalized without dashes or spaces (Android ID); ex: 4b61639e-47cc-4056-a16a-c8217e02946 and af3802a465767e36

Appendix C: Twitter Ads Account info

An access to Ads Account is the pre-requisite to create the Tailored Audience List. The account ID can be retrieved from the Account Settings Page


Last modified: Mar 09 2018 17:36:43 UTC

If this article is incorrect or outdated, or omits critical information, let us know. For all other issues, access our support channels.