Share
Snapchat Ads Setup Guide

Snapchat Ads is Snapchat’s advertising platform that enables you to retrieve statistics about the ads, ad squads, and campaigns running on Snapchat.

Hevo uses the Snapchat Marketing APIs to replicate your Snapchat Ads data into the desired Destination database or data warehouses for scalable analysis. For this, you must authorize Hevo to access data from your Snapchat Ads account.

Prerequisites

Configuring Snapchat Ads as a Source

Perform the following steps to configure Snapchat Ads as the Source in your Pipeline:

  1. Click PIPELINES in the Navigation Bar.

  2. Click + CREATE PIPELINE in the Pipelines List View.

  3. On the Select Source Type page, select Snapchat Ads.

  4. On the Configure your Snapchat Ads account page, do one of the following:

    • Select a previously configured account and click CONTINUE.

    • Click + ADD SNAPCHAT ADS ACCOUNT and perform the following steps to configure an account:

      Snapchat Ads Source settings

      1. Sign in using your Snapchat Ads account.

        Snapchat Ads Account

      2. Click Continue to authorize Hevo to access your Snapchat Ads data.

        Authorize Hevo

  5. On the Configure your Snapchat Ads Source page, specify the following:

    Configure Snapchat

    • Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.

    • Select Organizations: The Snapchat organization whose data you would like to ingest. You can select multiple organizations.

    • Select Ad Accounts: The Snapchat Ads account whose data you would like to ingest. You can select multiple Ad Accounts.

    • Historical Sync Duration: The duration for which you want to ingest the existing data from the Source. Default duration: 1 Year.

    • Advanced Settings:

      • Attribution Windows: The number of days between a user’s responses on an ad. You can specify either one or both of the following:

        • View Attribution Window: The number of days between a person viewing your ad and taking an action such as visiting a page. Default value: 1_Day.

        • Swipe Attribution Window: The number of days between a person swiping up on an ad and taking an action such as tapping a story tile or sharing a lens with a friend. Default value: 28_Day.

  6. Click TEST & CONTINUE.

  7. Proceed to configuring the data ingestion and setting up the Destination.

Data Replication

For Teams Created Default Ingestion Frequency Minimum Ingestion Frequency Maximum Ingestion Frequency Custom Frequency Range (in Hrs)
Before Release 2.21 3 Hrs 1 Hr 24 Hrs 1-24
After Release 2.21 6 Hrs 30 Mins 24 Hrs 1-24

Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3 but not 1.5 or 1.75.

  • Historical Data: The first run of the Pipeline ingests historical data for the selected reports and objects on the basis of the historical sync duration specified at the time of creating the Pipeline and loads it to the Destination. Default duration: 1 Year.

  • Incremental Data: Once the historical load is complete, all new and updated records are ingested as per the ingestion frequency.

    • For objects, Hevo performs full load to capture any data changes.

    • For reports, Hevo incrementally fetches data up to the previous day (as per the Snapchat Ads account’s timezone).

  • Refresher Data: Daily Reports are refreshed once a day, and hourly reports are refreshed once every 6 hours. The refresher window depends on the attribution window you select. For example, if you select a 28 day window, Hevo refreshes the daily report data once a day, and the hourly report data once every 6 hours for the past 28 days.

Handling Deleted Objects

Snapchat Ads APIs allow performing a soft delete of records. For the deleted records, Hevo sets the deleted column to True in the ingested data and the Destination.

Hevo tracks the deleted Events through the metadata column, deleted and replicates that information for the following objects:

Object Name Event Type Tracked
ADS updated
AD SQUADS deleted
CAMPAIGNS deleted

Note: As Hevo also replicates the deleted data, you might see more Events in your Destination than in the Source.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination:

Data Model

Hevo fetches both objects and reports from your specified ads account. Reports provide metrics around your users, their interaction related details, and the performance of your Ads.

Objects

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

Object Description
Account Contains the details of the Snapchat Ads account.
Ads Contains information required to display an ad per ads squad.
Ad Squads Contains information of ad squads associated with an ad campaign.
Audience Segments Contains the list of created audience segments.
Campaigns Contains the details of the ad campaigns per ad account.
Creatives Contains the details of creatives owned by an ad account.
Funding Sources Contains information about the configured funding sources responsible to pay for the ad activity within an ad account of an organization.
Media Contains the list of created audience segments.
Organizations Contains the organization details of the user associated with the Snapchat Ads account.
Snap Pixels Contains the details of snap pixels associated with the Snapchat ads account.

Reports

The following reports are replicated as tables in the Destination when you run the Pipeline:

Ad Reports

The Ad reports include the following reports:

  • AD_HOURLY_REPORT

  • AD_DAILY_REPORT

  • AD_GEO_COUNTRY_DAILY_REPORT

  • AD_GEO_REGION_DAILY_REPORT

  • AD_GEO_DMA_DAILY_REPORT

  • AD_INTEREST_DAILY_REPORT

  • AD_DEVICE_OS_DAILY_REPORT

  • AD_DEVICE_MAKE_DAILY_REPORT

  • AD_DEMOGRAPHIC_DAILY_REPORT

  • AD_UNIQUE_IMPRESSION_DAILY_REPORT

Ad Squad Reports

The Ad Squad reports include the following reports:

  • AD_SQUAD_HOURLY_REPORT

  • AD_SQUAD_DAILY_REPORT

  • AD_SQUAD_GEO_COUNTRY_DAILY_REPORT

  • AD_SQUAD_GEO_REGION_DAILY_REPORT

  • AD_SQUAD_GEO_DMA_DAILY_REPORT

  • AD_SQUAD_DEVICE_OS_DAILY_REPORT

  • AD_SQUAD_DEVICE_MAKE_DAILY_REPORT

  • AD_SQUAD_DEMOGRAPHIC_DAILY_REPORT

  • AD_SQUAD_UNIQUE_IMPRESSION_DAILY_REPORT

Campaign Reports

The Campaign reports include the following reports:

  • CAMPAIGN_DAILY_REPORT

  • CAMPAIGN_HOURLY_REPORT

  • CAMPAIGN_GEO_COUNTRY_DAILY_REPORT

  • CAMPAIGN_GEO_REGION_DAILY_REPORT

  • CAMPAIGN_GEO_DMA_DAILY_REPORT

  • CAMPAIGN_INTEREST_DAILY_REPORT

  • CAMPAIGN_DEVICE_OS_DAILY_REPORT

  • CAMPAIGN_DEVICE_MAKE_DAILY_REPORT

  • CAMPAIGN_DEMOGRAPHIC_DAILY_REPORT

  • CAMPAIGN_UNIQUE_IMPRESSION_DAILY_REPORT

Limitations

  • Hevo does not load an Event into the Destination table if its size exceeds 128 MB, which may lead to discrepancies between your Source and Destination data. To avoid such a scenario, ensure that each row in your Source objects contains less than 100 MB of data.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Jan-07-2025 NA Added a limitation about Event size.
Nov-05-2024 NA Updated sub-section, Custom frequency for Full Load objects as per the latest Hevo UI.
Mar-05-2024 2.21 - Updated the ingestion frequency table in the Data Replication section.
- Updated the Custom frequency for Full Load objects section with suggested frequencies for teams before and after Release 2.21.
Dec-07-2022 NA Updated section, Data Replication to reorganize the content for better understanding and coherence.
Sep-21-2022 1.98 Added section, Custom frequency for Full Load objects to inform users about the option to change ingestion frequency for Full Load objects.
May-10-2022 1.88 New document.
Last updated on Jan 07, 2025

Tell us what went wrong

Skip to the section