build a snapchat custom audience from hashed customer data via snap audience match
domain: developers.snap.com/api/marketing-api · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a Snap Audience Match (SAM) segment via the Ads API to hold the custom audience.
Normalize identifiers (lowercase/trim emails, E.164 phone numbers) and hash each with SHA-256 before upload.
POST batches of up to 100,000 hashed identifiers per request to the segment's users endpoint.
Check the segment's processing/match status before targeting it in an ad squad.
Refresh or replace the segment periodically to keep the audience current, since Snapchat doesn't auto-sync from your CRM.
Known gotchas
Identifiers must be normalized in the exact way Snapchat expects before hashing - inconsistent casing or phone formatting silently lowers match rate rather than erroring.
Batches are capped at 100,000 identifiers per request; larger lists must be chunked client-side.
Small audiences can be suppressed from reporting or targeting due to Snapchat's privacy thresholds even though the upload itself succeeded.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?