Stitch Documentation
has moved!

Please update your bookmarks to https://www.stitchdata.com/docs

If you're not automatically redirected after 5 seconds, click here.

Expected Autopilot Data

We’re currently doing some private testing on our Autopilot integration. Want to be a part of it? Get in touch with us.

Now that Autopilot is successfully connected to your Stitch account, what comes next? In this article, we'll cover:

Replicating Autopilot Data

Historical Sync

By default, a historical sync of Autopilot data goes back one year from the Stitch connection date.

Frequency

Stitch will replicate Autopilot data based on the frequency you define. The default setting is every 30 minutes, but you can change it to better suit your needs.

Replication Method

Autopilot data is replicated using Full Table Replication. This means that every time Autopilot data is queued for replication, all rows in a table - including existing, new, and updated - will be replicated.

Autopilot Tables in Your Data Warehouse

Below is a list of the main and subtables that will be created in your data warehouse. Because Autopilot uses nested arrays to structure data in some of its API's endpoints, Stitch will de-nest these arrays and create subtables. Refer to the Handling of Nested Data Structures doc for more info.

Click a table name to view detailed info about the corresponding API endpoint in Autopilot’s documentation.

autopilot_contacts
Primary Key: contact_id

The autopilot_contacts table contains information about the contacts in your Autopilot account.

Attributes include the contact ID, first & last name, company, company priority, email address, employee range (min/max), first conversion time, first visit time, industry, lead source, mailing address, phone number, status, title, type, unsubscribe details, website, and created and updated at timestamps.

  • autopilot_contacts__lists - This subtable contains details about the lists your contacts are members of. The value column in this table contains the list ID.

    The composite key - made up of the contact ID and table row ID - can be used to tie this table back to its parent, autopilot_contacts: _sdc_source_key_contact_id:_sdc_level_0_id

autopilot_lists
Primary Key: list_id

The autopilot_lists table contains information about the available lists in your Autopilot account.

Attributes include the list ID and title.

autopilot_smart_segments
Primary Key: segment_id

The autopilot_smart_segments table contains information about the smart segments in your Autopilot account.

Attributes include the segment ID and title.

autopilot_smart_segments_contacts
Primary Key: segment_id:contact_id

The autopilot_smart_segments_contacts table details which segments your contacts are associated with.

Attributes include the segment ID and contact ID.

Related

Was this article helpful?
0 out of 0 found this helpful

Comments

Questions or suggestions? If something in our documentation is unclear, let us know in the comments!