Data warehouse sync
Sync notification analytics data from Knock into your own data warehouse
You can bring your notification analytics from Knock into your own data warehouse so that you can analyze it alongside the rest of your data.
Connecting your data warehouse#
Please contact our support team to get started with the warehouse connection process. Your message should include the destination type of the warehouse that you'd like to connect; supported types are listed here. You should also specify which of the tables you'd like to sync from the available data listed below.
We will ask you for additional information according to the destination type that you'd like to connect. Once we have the required details, Knock will provide you with a magic link to a step-by-step wizard that will guide you through the remainder of the setup process.
Upon successful connection, your first data sync will include a backfill of historical data. You will receive up-to-date data once every 24 hours after the initial backfill.
Available data#
Messages table#
Our data warehouse connector syncs data from our messages
table. Each message
represents a notification that was executed for a single recipient. You can read more about messages as a concept here.
Below is a description of the columns included in the table and the data type of each. To see how this data type will map onto the data types of your destination table, check the destination type mapping table.
Recipient change stream table#
Our data warehouse connector syncs data from our recipients
table. Each row captures the properties and preferences of a Recipient at a given moment in time.
Each row has an event_type
indicating how the event was generated. Possible values are:
recipient.created
- indicates the first time a recipient was identifiedrecipient.snapshot
- is emitted every time a recipient's properties or preferences are updated, and contains the complete set of properties and preferences at that moment in time. This event may also be generated manually for all or a subset of recipients (by ID) by contacting support.recipient.deleted
- contains no properties or preferences, but indicates when a recipient was deleted. A recipient may be re-identified after being deleted, which will generate another recipient.created event
Events in the recipient change stream table are retained for 7 days.
Below is a description of the columns included in the table and the data type of each. To see how this data type will map onto the data types of your destination table, check the destination type mapping table.