Amperity and Snapchat: Snapchat custom audience sync
Amperity sends first-party customer segments to Snapchat Custom Audiences through Snapchat Audience Match, replacing membership on each send. Use purchase and engagement history to define audiences, then manage eligible advertising campaigns in Snapchat.
Get a demoSee the Snapchat docsWhat teams can do with Amperity and Snapchat
Build Snapchat audiences from online and in-store customer history.
Retarget customers based on the products they have purchased.
Separate recent buyers from audiences intended for acquisition.
Refresh customer membership without preparing another manual list.
Use known customer segments to inform differentiated offers.
Connect offline purchases through a separately configured events workflow.
How Amperity and Snapchat connect
1. Define the customer segment
Select customers in Amperity using purchase, engagement, or lifecycle attributes and apply the exclusions your activation requires.
2. Send a complete audience
The Snapchat destination maps supported identifiers and sends the current membership through Snapchat Audience Match.
3. Validate the audience in Snapchat
Confirm the resulting audience before using it in a campaign; a completed send does not establish campaign eligibility or customer reach.
Identity and matching for Snapchat audiences
Amperity brings customer records together before you select an audience. Snapchat makes the downstream match against its users, so a larger source segment does not guarantee a larger reachable audience. Amperity's campaign guide specifies at least 1,000 unique customers for targeting; validate eligibility and match results in Snapchat.
What the Snapchat connection supports
Capability | Supported behavior |
|---|---|
Direction and method | Amperity → Snapchat through Snapchat Audience Match within the Snapchat Marketing API. |
Audience identifiers | email, phone, and mobile_id; automatic SHA-256 hashing for this audience destination. |
Refresh behavior | Full replacement: existing audience members are removed before the current membership is added. |
Access and configuration | OAuth authorization, ad account ID, audience name, and approval for the customer account. |
Targeting qualification | At least 1,000 unique customers in the documented campaign workflow; downstream matching still applies. |
Offline conversions | Separate Snapchat Offline Events destination through the Conversions API; distinct credentials and field requirements. |
What teams do with Amperity and Snapchat
Reconnect with customers after a first purchase
Build a segment of customers who have made their first purchase and have not returned within your chosen interval. Use product or category history to select an appropriate next offer, then send the audience to Snapchat. Keep eligibility rules in Amperity and the creative decision in Snapchat, so the audience reflects the relationship you already have with the customer. Evaluate response against a defined retention goal.
Keep acquisition messaging relevant
Identify existing customers or recent purchasers before planning an acquisition campaign. Send the appropriate segment to Snapchat and use it in the exclusion settings supported by your campaign configuration. Refresh the source criteria as purchase history changes, then verify the resulting audience before launch. This gives the media team a customer definition it can inspect rather than requiring a new spreadsheet for each promotion or product release.
Bring store purchases into campaign measurement
When the business needs to evaluate offline purchases, configure the separate Snapchat Offline Events workflow. Select recent transactions, map the required event fields, and validate a test send in Snapchat before scheduling delivery. Keep the audience and events destinations distinct in the implementation plan. The events path supplies purchase signals for Snapchat's attribution and optimization processes; it does not establish that every transaction will match an ad exposure.
Setting up the Snapchat connection
Have an authorized Snapchat account owner approve access, and work with your Amperity operator to configure the audience destination. Check the ad account, audience name, identifier mapping, and full-replacement behavior before the first production send.
For direct offline events, use the Snapchat Offline Events guide: the access token and pixel must belong to the same organization. Amperity hashes supported customer fields automatically, but sends madid unhashed and lowercased; do not reuse the audience hashing rule. Events older than 28 days are skipped. A legacy CSV workflow is a separate path.
See the Snapchat docsSnapchat integration FAQs
How do I create a Snapchat custom audience from Amperity?
Does Amperity add to or replace a Snapchat audience?
Which identifiers can I send to Snapchat?
How many customers do I need for Snapchat targeting?
Can Amperity send offline purchases to Snapchat?
Put customer context to work in Snapchat
Explore how Amperity can connect your customer data to the audience workflow your team needs.
Get a demo