Run campaigns with custom audiences, retargeting, and lookalikes in Twitter
After selecting Twitter from our Destinations catalog, you will be prompted to
initiate an OAuth flow.
You will be able to select the related Twitter Ads account when you configure your sync.
This integration supports
Segment Mode. New users will be inserted into the Twitter
Custom Audience. Users that are removed from the model will be removed from the
Hightouch supports automatically creating a new segment for your sync. You can
specify a custom name for this segment. Otherwise Hightouch will use
the name of the model as the segment's name.
Test Audience will be used as the audience name:
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
encode(digest(value, 'sha256'),'hex') in Postgres:
Access tokens are not explicitly expired. An access token will be invalidated if a user explicitly revokes an application in the their Twitter account settings, or if Twitter suspends an application.
If for whatever reason you are unable to authenticate your requests, please reauthorize your application
via the destination configuration page:
Our team is relentlessly focused on your success. We're ready to jump on a call to help unblock you.
Connection issues with your data warehouse? Confusing API responses from destination systems? Unsupported destination objects or modes? Help with complex SQL queries? Start a chat
Schedule a call
If you see something that's missing from our app, let us know and we'll work with you to build it!
We want to hear your suggestions for new sources, destinations, and other features that would help you activate your data.
Request a feature