Skip to main content

Snapchat Ads Reader

Note

This adapter is in preview and is available on Striim Developer only. See Striim Developer for more information.

Snapchat Ads are full-screen vertical video advertisements lasting up to 10 seconds, displayed between friends' stories and curated content. They allow businesses to engage younger audiences (13-34 years old) with interactive, visually compelling ads that can link to websites, apps, or longer videos.

The Snapchat Ads Reader connects with the Snapchat Ads platform and reads from supported objects.

Feature summary

Feature

Supported?

Notes

Objects

Standard objects

Custom objects

Authentication

Basic authentication

Username and password

OAuth authentication

Manual configuration based

Custom authentication methods

Not all methods may be supported

Operations

Automated mode

Initial load

Pull-based incremental load

Push-based incremental load

Automated pipeline

Governance

Connection profile

Sherlock AI

Sentinel AI

Schema handling

Initial schema creation

Works with supported targets

Schema evolution

Setup

Wizard template

Flow Designer

Striim TQL

Runtime

Resilience/recovery

Parallel execution

Metrics

Standard metrics

Supported authentication method

The Snapchat Ads Reader supports OAuth authentication. Creating a connection requires creating an application in Snapchat Ads, obtaining the OAuth credentials from Snapchat Ads, and setting the Striim connection properties.

To create a connection using OAuth authentication:

  1. Create a developer account:

    1. Visit the Snapchat Developer Portal at https://developers.snap.com.

    2. Sign up and create a developer account.

  2. Set up a Business Account:

    1. Navigate to the Snap Business Manager.

    2. Create a business account if you haven't already.

    3. Ensure you have Organization Admin privileges.

  3. Generate the app credentials.

  4. In the Business Details section, set up an OAuth app.

  5. Locate your generated Client ID and Client Secret.

Sample authorization code request

curl -X GET \ "https://accounts.snapchat.com/login/oauth2/authorize" \ 
-d "client_id=YOUR_CLIENT_ID" \ -d "redirect_uri=YOUR_REDIRECT_URI" \ 
-d "response_type=code" \ -d "scope=snapchat-marketing-api"

Sample refresh token request

curl -X POST \ "https://accounts.snapchat.com/login/oauth2/access_token" \ 
-H "Content-Type: application/x-www-form-urlencoded" \ -d "client_id=YOUR_CLIENT_ID" \ 
-d "client_secret=YOUR_CLIENT_SECRET" \ -d "code=AUTHORIZATION_CODE" \ 
-d "grant_type=authorization_code" \ -d "redirect_uri=YOUR_REDIRECT_URI"

Supported objects

The following are the supported objects for reading from Snapchat Ads:

  • AccountStats

  • Accounts

  • AdSquadStats

  • AdSquads

  • AdStats

  • Ads

  • AdvancedDemographics

  • AudienceInsights

  • AudienceSegments

  • BillingCenters

  • CampaignStats

  • Campaigns

  • Creatives

  • DemographicsAgeGroups

  • DemographicsGender

  • DemographicsLanguages

  • DeviceCarriers

  • DeviceConnectionTypes

  • DeviceMakes

  • DeviceOSTypes

  • DeviceOSVersions

  • FundingSources

  • GeolocationCountries

  • GeolocationMetros

  • GeolocationRegions

  • GeolocationZipCodes

  • Invoices

  • LocationCategories

  • NielsenInterests

  • OracleDatalogixInterests

  • Organizations

  • PlacedVisitationSegmentsInterests

  • SnapLifeStyleCategoriesInterests

Snapchat Ads Reader properties

Property

Type

Default value

Notes

Client ID

String

The client ID assigned when you register your application with an OAuth authorization server.

Client secret

Password

The client secret assigned when you register your application with an OAuth authorization server.

Refresh token

Password

The OAuth refresh token for the corresponding OAuth access token.

Connection pool size

Integer

20

Specifies the maximum number of active connections.

Exclude tables

String

A list of tables excluded from read operations. Typically used to create a list of exceptions when the Tables property includes wildcards. Misconfiguration of the Tables and Exclude Tables properties can cause "Invalid table names" errors.

Incremental load marker

String

The incremental load marker is a unique incremental column in each object used for incremental load. When no marker is specified, tables are resynced at each polling interval.

Specify the name of the column that contains the start position value. This column must meet the following criteria:

  • It should have an integer or timestamp data type (for example, a creation timestamp or an employee ID).

  • The values must be unique and continuously increasing to ensure proper incremental reading.

Migrate schema

Boolean

False

Only available in Initial Load or Automated mode. Set to True to enable initial schema migration, which propagates the object schema from the source to the target.

Mode

Select list:

  • Automated mode

  • Initial load

  • Incremental load

Automated

Automated mode applies incremental updates to objects that support incremental load and performs full resyncs for objects that do not support incremental load.

Polling interval

Integer

5m

Specifies an interval as an integer followed by a unit. Supported units are days (d), hours (h), minutes (m), or seconds (s). The reader polls the source at the specified interval.

Refresh token

Password

An OAuth 2.0 refresh token.Use the value generated while creating the token.

Start Position

String

%=-1

Value of the incremental load marker that defines the initial reading position.

Tables

String

A semicolon-delimited (;) list of objects to read from the source. Supports the % wildcard. Misconfiguration of the Tables and Exclude Tables properties can cause "Invalid table names" errors. Do not modify this property when recovery is enabled for the application.

Thread pool count

Integer

10

The number of parallel running threads. The default value of zero specifies single-threaded operation.

When the value of the thread pool counter is higher than the connection pool size, large data ingestion operations can cause the app to halt. Since best performance is achieved when using one thread for each table being synced, increasing the size of the connection pool to match the number of threads in use is a performance best practice.