To connect to the destination, you need the Manage Destinations access control permission. As soon as a profile is updated in Experience Platform based on segment evaluation, the connector sends the update downstream to the destination platform. Streaming destinations are “always on” API-based connections. You are exporting all members of a segment (audience) with the identifiers (name, phone number, or others) used in the YOURDESTINATION destination. Refer to the table below for information about the destination export type and frequency. Map Apple Advertising IDs into the target identity field idfa. Map Google Advertising IDs into the target identity field gaid. Map email addresses into the target identity field phoneNumber.
Map email addresses into the target identity field emailAddress. The Snap Inc destination does not support multiple identities.
To hash plain text identifiers before sending them to the destination, check the Apply transformation option when mapping target identifiers for the destination. Learn more about identities.Īll identifiers sent to the Snap Inc destination must be hashed in SHA-256 format. The Snap Inc destination supports the activation of identities described in the table below. All members have lifetime retention and will be in the segment until they are removed. It is not possible to define a retention period for an audience segment’s members.To rename a segment, you must deactivate, rename it, and then activate it. Snap Inc does not support renaming segments.Please map only one identity when activating a segment.
Snap Inc does not support multiple identities for a given audience segment.Get Started with Snapchat Advertising Limitations Please refer to this documentation for information about how to create one: To use this destination, you must have a Snapchat Ads account. This destination allows marketers to import user segments created in Experience Platform into Snapchat Ads and use them to target their ads. For any inquiries or update requests, please contact them directly at Use cases This documentation page was created by the Snap Inc team.
0 kommentar(er)
