Target your existing followers and customers in Twitter and create relevant re-marketing campaigns by activating your audiences built within Adobe Experience Platform.
Before you configure your Twitter Custom Audiences destination, make sure to review the following Twitter prerequisites that you need to meet.
Twitter Custom Audiences supports the activation of identities described in the table below. Learn more about identities.
|device_id||IDFA/AdID/Android ID||Google Advertising ID (GAID) and Apple ID for Advertisers (IDFA) are supported in Adobe Experience Platform. Please map these namespaces and/or attributes from your source schema accordingly in the mapping step of the destination activation workflow.|
|Email address(es) for the user||Please map your plain text email addresses and your SHA256-hashed email addresses to this field. When your source field contains unhashed attributes, check the Apply transformation option, to have Platform automatically hash the data on activation. If you hash your customer email addresses before uploading them to Adobe Experience Platform, please note these identities must be hashed using SHA256, without a salt.|
Refer to the table below for information about the destination export type and frequency.
|Export type||Segment export||You are exporting all members of a segment (audience) with the identifiers used in the Twitter Custom Audiences destination.|
|Export frequency||Streaming||Streaming destinations are “always on” API-based connections. As soon as a profile is updated in Experience Platform based on segment evaluation, the connector sends the update downstream to the destination platform. Read more about streaming destinations.|
To help you better understand how and when you should use the Twitter Custom Audiences destination, here are sample use cases that Adobe Experience Platform customers can solve by using this destination.
Target your existing followers and customers in Twitter and create relevant re-marketing campaigns by activating your audiences built within Adobe Experience Platform as List Custom Audiences in Twitter.
To connect to the destination, you need the Manage Destinations access control permission. Read the access control overview or contact your product administrator to obtain the required permissions.
To connect to this destination, follow the steps described in the destination configuration tutorial. In the configure destination workflow, fill in the fields listed in the two sections below.
To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.
You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.
When you are finished providing details for your destination connection, select Next.
To activate data, you need the Manage Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
Read Activate profiles and segments to streaming segment export destinations for instructions on activating audience segments to this destination.
All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, see the Data Governance overview.
When mapping audience segments to Twitter, make sure to meet the following segment naming requirements:
More information about List Custom Audiences in Twitter can be found in the Twitter documentation.