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 Segment Data

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

Replicating Segment Data

Historical Data

For Standard Segment accounts, Stitch is only capable of receiving new data from the time you create the Segment integration.

If you're on the Segment Business tier, you can use Segment's Replay Historical Data feature to perform a complete historical sync.

Replication Method & Frequency

Stitch uses what is called a direct integration to integrate with Segment. This is a webhook-based method of sending your Segment data to integrations. Unlike REST or SOAP APIs, webhooks deliver data as it happens in real-time.

Because Segment data is sent to Stitch in real-time, this means that only new records are replicated to your data warehouse. In the event that our webhook service experiences downtime, you may notice some lag between an event occurring and the data appearing in your data warehouse.

Segment Tables in Your Data Warehouse

Below are the Segment tables that will be created in your data warehouse.

Each of Segment's endpoints contains a set of fields unique to that endpoint along with a set of common fields. Common fields are the same across all of Segment's endpoints.

Common fields describe user identity, timestamping, device, network, and so on. For a full list of these fields, check out Segment's Common Fields Spec.

For detailed info about each of the endpoints Stitch hits, click the table names below.

group
Primary Key: message_id

The group table contains information about groups, which is how individual users are associated with companies, accounts, projects, teams, and so on.

In addition to the common fields, this table's attributes may also include group traits and the group's ID.

identify
Primary Key: 
message_id

The identify table records all user information.

In addition to the common fields, this table's attributes may also include customer traits and the user's ID.

page
Primary Key: message_id

The page table contains information about page events, along with any data about page properties.

In addition to the common fields, this table's attributes may also include page properties and the page name.

screen
Primary Key: 
message_id

The screen table contains information about screen events, along with any data about screen properties.

In addition to the common fields, this table's attributes may also include screen properties and the screen name.

track
Primary Key: message_id

The track table contains user action information.

In addition to the common fields, this table's attributes may also include event properties and the event name. For information on semantic events - or Segment's standardized event names and properties - check out their documentation here.

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!