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. To set up this sync, please contact our support team.
How it works
Knock leverages Prequel to integrate with your data warehouse. There is no self-service UI to connect your account to start receiving data; instead when you contact us to set up a sync we'll send you a secure link to fill in the information about your data warehouse. Once it's connected, you'll begin receiving a backfill of historical data, and will continue to receive the most up-to-date data every 24 hours.
Setup
You'll need to work with our support team to connect your data warehouse. We'll need to know the destination type of your data warehouse, and will ask you for some additional information based on which destination type you're configuring. The databases supported as destinations for Knock are listed here.
Once we have the information we need, Knock generates a magic link that you'll use to complete the setup process. The link will take you through a setup wizard that is specific to your destination.
If the connection is successful, you can save it and it will proceed with the backfill transfer.
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 in the Prequel docs.
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 in the Prequel docs.