Snapchat Ads
Snapchat Ads provides a platform to create, manage, and measure your ad campaigns. The Snapchat Ads connector provides a history of the settings and detailed reports of the following:
- Snapchat Ad Accounts
- Campaigns
- Ad Squads
- Media Creatives
See Snapchat's API documentation for more information.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | ||
| History mode | check | |
| Custom data | check | CAMPAIGN_HISTORY table. All fields prefixed with measurement_spec_. |
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | check | |
| Fivetran data models | check | |
| Private networking | ||
| Authorization via API | check |
Setup guide
Follow our step-by-step Snapchat Ads setup guide to connect Snapchat Ads with your destination using Fivetran connectors.
Sync overview
Snapchat takes around 48-72 hours to process finalized data. The following fields will not be available in current and previous day reports:
attachment_frequencyattachment_uniquesavg_screen_time_millisfrequencyuniquesstory_opensstory_completes
Rollback sync
A rollback sync is a sync that automatically starts once a day. Rollback syncs capture the conversions within the attribution window.
Fivetran does not automatically capture the rollback window size. You can opt to configure the rollback window in the connector setup form. To do so, set the Show advanced options toggle to ON, and set the attribution window using the Swipe Attribution Window (optional) drop-down.
Multithreading
The Snapchat Ads connector supports multithreading. Fivetran uses multiple parallel API requests to sync ads data from your Snapchat Ads account to your destination. The connector’s sync speed depends on your Snapchat Ads API quota and account metadata.
Schema information
This schema applies to all Snapchat Ads connectors.
To zoom, open ERD in new window
Report schema information
We provide two types of reports:
Limitations
We skip A/B Segment testing records in the AUDIENCE_SEGMENT_HISTORY table since they aren't created or manipulated through the API. Therefore, the AUDIENCE_SEGMENT_HISTORY table doesn't have the updated_at property, which we need as a part of our composite primary key.