Get started with a free trial today
Already have an account? Sign in
A high-level look at Stitch's Segment (v1) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status | Released | Supported by | |
| 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 | Supported | ||
| TRANSPARENCY | |||
| Extraction Logs | Unsupported | Loading Reports | Unsupported |
Connecting your Segment data to Stitch is a three-step process:
All data collected by Segment is sent to us by default, but if individual snippets on your site specify which integrations data should be sent to, then these settings will be overridden.
If you useselective integration snippets, you’ll need to add Stitch to the list of integrations before data will flow to your data warehouse.
Here’s an example of a snippet that sends data to Stitch, Mixpanel, and KISSMetricsonly:
},{integrations:{'All':false,'Stitch':true,// 'true' indicates if the integration receives data'Mixpanel':true,'KISSmetrics':true}});When you add Stitch to your snippet, make sure you enter Stitchexactly as it appears in the example above.
On the Stitch Dashboard page, click theAdd Integration button.
Click theSegment icon.
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 Segment” would create a schema calledstitch_segment in the destination.Note: Schema names cannot be changed after you save the integration.
Lastly, you’ll be directed to Segment’s website to complete the setup.
Stitch uses what is called adirect 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.
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.
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’sCommon Fields Spec.
Stitch's Segment integration includes these tables:
Replication Method: Incremental (Webhook)
Primary Key:message_id
Contains Nested Structures?: No
group table contains info about groups, which is how individual users are associated with companies, accounts, projects, teams, and so on.While we try to include everything Segment has here,this may not be a full list of attributes. Refer toSegment's documentation for a full list and description of each attribute.
Message ID (message_id)
Replication Method: Incremental (Webhook)
Primary Key:message_id
Contains Nested Structures?: No
identify table contains all user info.While we try to include everything Segment has here,this may not be a full list of attributes. Refer toSegment's documentation for a full list and description of each attribute.
Message ID (message_id)
Replication Method: Incremental (Webhook)
Primary Key:message_id
Contains Nested Structures?: No
page table contains info about page events, along with any data about page properties.While we try to include everything Segment has here,this may not be a full list of attributes. Refer toSegment's documentation for a full list and description of each attribute.
Message ID (message_id)
Replication Method: Incremental (Webhook)
Primary Key:message_id
Contains Nested Structures?: No
screen table contains info about screen events, along with any data about screen properties.While we try to include everything Segment has here,this may not be a full list of attributes. Refer toSegment's documentation for a full list and description of each attribute.
Message ID (message_id)
Replication Method: Incremental (Webhook)
Primary Key:message_id
Contains Nested Structures?: No
track table contains user action info.For info on semantic events - or Segment’s standardized event names and properties -check out their docs.
While we try to include everything Segment has here,this may not be a full list of attributes. Refer toSegment's documentation for a full list and description of each attribute.
Message ID (message_id)
| Related | Troubleshooting |
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.