Snapchat

​

Supported syncing

For more information about sync modes, refer to the sync modes docs.

​

Connect to Snapchat

Go to the Destinations overview page and click the Add destination button. Select Snapchat and click Continue. You can then authenticate Hightouch to Snapchat. For the Authentication method, select Log in to Snapchat and log into your Snapchat account. Then, authorize Hightouch to access your Snapchat account: Once successful, you will be redirected back to Hightouch. There, select the Snapchat business organization you want to sync data to. Finally enter a descriptive name for your destination to complete setup.

​

Sync configuration

Once you’ve set up your Snapchat destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Snapchat destination you want to sync to.

​

Syncing segments

You can use Hightouch to create and keep audience segments in Snapchat up-to-date using Snapchat’s Ads API. Begin by selecting the Snapchat Ad Account your audience segments should belong to.

​

Select an existing audience or create a new one

You can create a new audience segment or use an existing one. When creating a new audience, you can optionally enter a name; otherwise, Hightouch defaults to the name of the associated model. To use an existing audience, select the desired audience from the dropdown.

​

Audience member retention

You can specify a custom retention period that an audience segment should retain members. Snapchat’s default is 9,999 days. You can only set custom values when first creating an audience segment. If you want to set a new retention period, you need to create a new sync.

​

User identifiers

To identify which users to add or update in an audience, select model columns and the corresponding Snapchat fields. You can match on any of the following Snapchat fields:

• Email
• Phone
• Mobile ID

​

Syncing conversion events

Snapchat’s Conversions API requires the following event parameters:

• event name (named event_type in Snapchat’s Conversions API)
• event conversion type (event_conversion_type)
• event tag (event_tag)
• timestamp

The sync configuration form ensures all these are set and provides some additional options. For more information about Snapchat’s Conversions API and it’s prerequisites, check out Snapchat’s API help article.

​

Event name and conversion type

Providing an event name is required to send an event to the Conversions API. You can either provide a static value or select to use a column from your model. You can select your event conversion type in the same way. Snapchat’s Conversions API accepts the following values: See the Snapchat Marketing API documentation for more information about event parameters.

​

Event timestamp

You can optionally select a column that contains timestamps of when events occurred. If this field is empty, Hightouch uses the time the event arrives at the server. If you select a column, it should be in UNIX timestamp, calculated in seconds or milliseconds.

​

Field mapping

Hightouch lets you sync event properties via field mapping. You must include the event tag field that Snapchat’s Conversions API requires for each event. Event tags are custom values you create, for example, “in-store,” “weekend sales,” “back-to-school campaign,” etc. Check out Snapchat’s Conversion parameters documentation for more information about the parameters you can map. Version 3 The new version of the conversion API takes many of the same parameters as the previous version but they are split into multiple mapping groups. Checkout Snapchat’s version 3 Conversion parameters documentation for more information about the parameters you can map.

​

PII hashing

Snapchat requires identity information to be normalized and hashed using a SHA256 hash. Enable PII hashing if you wish for Hightouch to normalize and hash these values for you. If you turn off PII hashing, you must ensure your model data is hashed before sending it to Snapchat.

​

Tips and troubleshooting

To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .

​

Matched users count

Below only applies to the segment sync type. Hightouch retrieves the audience metadata from Snapchat Ads in real-time. The matched number displayed in Hightouch should reflect what you see in Snapchat Ads. 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 Snapchat Ads 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 for Snapchat Ads.