Authenticate to the Snap Marketing API using the OAuth 2.0 authorization code flow and obtain an access token with the snapchat-marketing-api scope
POST to the /v1/adaccounts/{ad_account_id}/audiences endpoint to create an audience of type SAM_RETARGETING (Mobile App Custom Audience), specifying the retention_in_days and source_type as APP_EVENTS
Configure the audience rules by specifying the app ID (from Snap App ID registered in Snap Ads Manager), event name (e.g. PURCHASE or ADD_TO_CART), and any event property filters
Retrieve the audience ID and check audience status via a GET request until status shows ACTIVE and the size estimate is populated
Include the audience ID in the targeting specification of an ad set by adding it to the audience object when POSTing to the /v1/adsquads endpoint for a new ad squad
Set up audience exclusions by adding exclude audience IDs to the targeting spec to suppress existing converters from the retargeting campaign
Known gotchas
Snap Mobile App Custom Audiences require the Snap Pixel or Snap App Ads SDK to be firing app events for the registered app ID; if event signals are absent or below threshold, the audience will remain empty
Snap enforces a minimum audience size for ad delivery eligibility; audiences below this threshold will show as ACTIVE in the API but the ad squad will not serve, making it appear to be a bidding or budget issue
The retention_in_days value cannot be modified after audience creation; to change the lookback window you must create a new audience, which restarts the population process from scratch
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp