Skip to main content Skip to complementary content
Already have an account? Sign in

AdRoll (v20-07-2020)

Last updated: 9/15/2026

AdRoll integration summary

Stitch’s AdRoll integration replicates data using the AdRoll CRUD API. Refer to the Schema section for a list of objects available for replication.

AdRoll feature snapshot

A high-level look at Stitch's AdRoll (v20-07-2017) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Deprecated on July 24, 2020

Supported by

Stitch

Stitch plan

Standard

API availability

Not available

Singer GitHub repository

Not applicable

REPLICATION SETTINGS
Anchor Scheduling

Unsupported

Advanced Scheduling

Unsupported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Unsupported

Column selection

Unsupported

Select all

Unsupported

TRANSPARENCY
Extraction Logs

Unsupported

Loading Reports

Supported

Connecting AdRoll

Step 1: Create an AdRoll User for Stitch

While you can use your own credentials to connect AdRoll to Stitch, we recommend creating a separate user for us. This will make it easier for you to manage users and audit events in your AdRoll account.

We require a General User role - which is the default - to be able to replicate your AdRoll data. Note that Stitch does not need billing access. If you need help creating an AdRoll user, you can find instructions here in AdRoll’s support docs.

Step 2: Add AdRoll as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the AdRoll icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch AdRoll” would create a schema called stitch_adroll in the destination. Note: Schema names cannot be changed after you save the integration.

  5. Enter the email address and username for the Stitch AdRoll user.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your AdRoll integration. This means that:

  • For tables using Key-based Incremental Replication, data equal to or newer than this date will be replicated to your destination.
  • For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your destination.

Change this setting if you want to replicate data beyond AdRoll’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

AdRoll integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Initial and historical replication jobs

After you finish setting up AdRoll, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

AdRoll table reference


Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!