Snapchat Ads JSON integration is the use of JSON to export Snapchat advertising data, manage ads, or send conversion events. Most setups cover 3 tasks:
| Objective | Correct Snapchat Integration | Best For |
|---|---|---|
| Export campaign performance to JSON | Snapchat Ads API reporting endpoints or a connector | Dashboards, data warehouses and custom reports |
| Create and manage campaigns programmatically | Snapchat Ads API | Ad automation and campaign management |
| Send purchases, leads or app events | Snapchat Conversions API, or CAPI | Attribution, optimization and server-side tracking |
| Create a scheduled, no-code JSON feed | Third-party connector | Marketing and operations teams without engineering resources |
Snapchat's Marketing API includes the Ads API for campaigns, creatives, audiences and reporting. It also includes the Conversions API for server-to-server event tracking.
Use the Snapchat Ads API when you need control over reporting or campaign management. Use a connector for scheduled JSON exports. Use the Conversions API when the goal is conversion tracking rather than ad reporting.
A setup that covers both advertising data and conversion tracking can include:
The Snapchat Ads API returns JSON reports for ad accounts, campaigns, ad squads, ads and media. Reports can use total, daily or hourly granularity. Snapchat says statistics are updated approximately every fifteen minutes.
A basic reporting request looks like this:
curl "https://adsapi.snapchat.com/v1/adaccounts/{{ad_account_id}}/stats?granularity=DAY&start_time={{period_start}}&end_time={{period_end}}" \
-H "Authorization: Bearer {{access_token}}"
The response uses a JSON structure containing fields such as:
{
"request_status": "success",
"request_id": "{{request_id}}",
"timeseries_stats": [
{
"timeseries_stat": {
"id": "{{ad_account_id}}",
"type": "AD_ACCOUNT",
"granularity": "DAY",
"timeseries": [
{
"start_time": "{{period_start}}",
"end_time": "{{period_end}}",
"stats": {
"impressions": 0,
"swipes": 0,
"spend": 0,
"conversion_purchases": 0
}
}
]
}
}
]
}
Replace each placeholder before sending the request. Available metrics depend on the report type and Snapchat API schema.
Common performance fields include:
impressionsswipesspendswipe_up_percentvideo_viewsview_completionconversion_purchasesconversion_sign_upspaid_impressionsuniquesThe API can also return breakdowns by campaign, ad squad, ad, location, device and demographic dimensions. Snapchat describes demographic and delivery insights as estimated data for directional analysis.
The Ads API uses OAuth 2.0. Each request needs an access token in the Authorization header:
Authorization: Bearer {{access_token}}
You need an OAuth app in Snap Business Manager, a client ID, a client secret, an approved redirect URI, and access to the relevant organization and ad account.
Keep the client secret on the server. Do not expose it in browser-side code.
A standard export process is:
A connector is usually faster than custom development when the requirement is to move Snapchat Ads data into JSON.
A connector workflow usually lets you:
Coupler.io advertises a Snapchat Ads to JSON integration with campaign, ad group and ad performance reports, selectable metrics and dimensions, filters, scheduled refreshes and a JSON URL. Treat any generated URL that contains an access token as a password.
| Requirement | Connector | Custom Snapchat Ads API |
|---|---|---|
| Fast setup | Strong | Weak |
| No-code workflow | Strong | Weak |
| Custom transformations | Limited | Strong |
| Control over authentication | Limited | Strong |
| Campaign creation and updates | Usually unavailable | Strong |
| Scheduled JSON output | Strong | Requires development |
| Maintenance | Lower | Higher |
| Best for | Reporting and exports | Engineering and automation |
For a dashboard feed, a connector is usually the faster option. For automated bidding, campaign creation, custom data models or internal applications, use the official Ads API.
The Snapchat Ads API accepts JSON bodies for many campaign-management requests. Its advertising hierarchy includes organizations, ad accounts, campaigns, ad squads, creatives, media and ads.
A creative request can use a body like this:
{
"creatives": [
{
"ad_account_id": "{{ad_account_id}}",
"name": "Product launch creative",
"type": "SNAP_AD",
"top_snap_media_id": "{{media_id}}",
"headline": "Explore the new collection",
"profile_properties": {
"profile_id": "{{public_profile_id}}"
}
}
]
}
Send the request with a JSON content type:
curl -X POST \
-H "Content-Type: application/json" \
-H "Authorization: Bearer {{access_token}}" \
-d @creative.json \
"https://adsapi.snapchat.com/v1/adaccounts/{{ad_account_id}}/creatives"
A Snapchat Ads integration is not entirely JSON-based. Media metadata can be created through JSON, but the actual video upload uses multipart/form-data.
Snapchat's quick-start process creates media, uploads the asset, creates a creative, creates a campaign and ad squad, and then creates the ad.
Use the Snapchat Conversions API when you need to report purchases, leads or other conversion events. Campaign reporting endpoints are not a substitute for event tracking.
For web events, the CAPI v3 endpoint is:
POST https://tr.snapchat.com/v3/{{pixel_id}}/events?access_token={{access_token}}
The request body contains a data array. A purchase payload can use this structure:
{
"data": [
{
"event_name": "PURCHASE",
"event_time": {{unix_timestamp_seconds}},
"event_id": "{{unique_event_id}}",
"action_source": "WEB",
"event_source_url": "{{full_event_url}}",
"user_data": {
"em": "{{sha256_normalized_email}}",
"sc_click_id": "{{ScCid_value}}",
"sc_cookie1": "{{scid_cookie_value}}",
"client_user_agent": "{{client_user_agent}}"
},
"custom_data": {
"value": {{order_value}},
"currency": "USD",
"order_id": "{{order_id}}"
}
}
]
}
For a PURCHASE event, Snapchat requires value and currency. At least one matching signal is also required, such as:
Snapchat recommends sending sc_click_id and sc_cookie1 when they are available.
Snapchat appends the ScCid click identifier to a destination URL when someone clicks or swipes up on an ad. You can extract that value and send it as sc_click_id, or send the full URL in event_source_url so Snapchat can extract the identifier.
Use the CAPI validation endpoint before deploying production events:
POST https://tr.snapchat.com/v3/{{pixel_id}}/events/validate?access_token={{access_token}}
A successful validation response uses a status such as:
{
"status": "VALID",
"reason": "Events have been processed successfully."
}
Validation checks whether the event is constructed correctly. It does not replace testing the browser, server and attribution flow together.
If the same conversion is sent through Snap Pixel and the Conversions API, both integrations need the same deduplication identifier.
For web events:
client_dedup_id.event_id.For purchases:
transaction_id.order_id inside custom_data.Each conversion needs its own unique identifier. Do not reuse one session ID for multiple events or leave template values such as {{order.id}} unresolved.
Snapchat documents a 48-hour cross-channel deduplication window for matching event identifiers. It also documents a longer purchase matching window when transaction and order identifiers are used.
Choose the setup based on what the JSON needs to do.
Use:
Snapchat Ads API or connector
↓
JSON
↓
Data warehouse, spreadsheet or BI dashboard
A connector is the faster choice when you need scheduled campaign data without building OAuth handling, pagination, retries and schema management.
Use:
Internal application
↓ OAuth
Snapchat Ads API
↓ JSON responses
Campaign database and automation system
Add separate handling for media uploads because those requests use file uploads rather than JSON alone.
Use:
Snap Pixel + server-side order system
↓
Snapchat Conversions API
↓
Purchase, lead and optimization signals
Send the same event identifiers through the browser and server integrations to prevent duplicate reporting.