This integration supports Segment Mode. New users in the model will be inserted into the Twitter
Custom Audience. Users that are removed from the model will be removed from the
Custom Audience.
Hightouch allows you to sync columns from your source to the supported Twitter fields.
Twitter allows mapping to various user identifiers, such as Email, Device ID, Twitter Handle, etc. Twitter requires all fields for users
to be both normalized and hashed using SHA256 (with the exception of Partner User ID).
You can achieve this in your model with a function
by using the encode(digest(value, 'sha256'),'hex') function in Postgres, or refer to the Template Mappings Section in this documentation to learn about how Hightouch can handle hashing these records for you.
Given the correct Pixel ID, Hightouch will filter for the eligible events that allow conversion events to be synced to.
Select the event you'd like to sync to from the dropdown menu. If the ID for these events exist in your model, toggle Use Column, and select the appropriate column from the dropdown menu.
Hightouch allows you to sync columns from your source to the supported Twitter fields.
If you wish to use the Email Address as an identifier, Twitter expects it to be hashed using SHA256.
You can achieve this in your model with a function by using the encode(digest(value, 'sha256'),'hex') function in Postgres, or refer to the Template Mappings section in this documentation to learn about how Hightouch can handle hashing these records for you.
Hightouch retrieves the audience metadata from Twitter in real-time. The matched number displayed in Hightouch should reflect what you see in Twitter. Note that the matched numbers are approximated to maintain privacy thresholds. Hightouch takes the matched count to calculate a match rate for your sync, where applicable. The calculation breakdown:
matched_user_count / # of rows queried in the latest sync run
The match rate is
not
calculated when:
syncing to an existing segment because the total number of records to ever be uploaded to the segment is unknown
removed users from your model is not removed in Twitter because the matched user count would be inflated in the calculation
Common causes for low match rates:
Your audience model is too small. Most ad platforms do not display the matched number unless there's at least one thousand matched users to maintain privacy thresholds.
The upload is still processing. We recommend waiting at least
72 hours
from the first sync run for numbers to settle.
Your data isn’t cleaned or hashed properly. Hightouch normalizes and hashes your data according to destination requirements, but it’s still good to make sure that the data is as clean as possible. Note that Hightouch cannot clean your data if you opt to hash it yourself. In that case, ensure you follow the data cleaning requirements forTwitter.
{"request":[{"params":{"account_id":"01ab234cdef","custom_audience_id":"0a1b2"},"operation_type":"Update"}],"operation_errors":[[{"code":"INVALID_PARAMETER","message":"Tailored audience attribute value can not be empty.","parameter":""}]]}
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.