User and preference data, now available in your warehouse
At Knock, we're always looking for more opportunities to give you access to the data that's available within your Knock account so that you can analyze it along with the rest of your product usage data.
With today's release, you can now receive a stream of user and preferences changes directly into your data warehouse. This makes it easy to build models that analyze your notification opt-out rates and how user profile information in Knock changes over time.
This feature is available to Enterprise customers who have set up a data warehouse sync. Read our documentation to learn more.
Fixes and improvements
- 👀 We've moved trigger data into the
data
property in the template editor, so you now access properties as{{ data.property_name }}
- 👀 We added a link to the billing portal for all customers to see their current daily usage quotas
- 👀 We added support for
base_logo_url
andbase_icon_url
when applying tenant branding so that the original branding properties can still be referenced - 🐛 We removed support from our editor for unsupported liquid tags like
date_to_string
- 🐛 We fixed an issue where creating a new HTML partial would not immediately appear in the blocks sidebar
- 🐛 We fixed an issue where committing a change to a partial would not be reflected in the workflows and templates that use it
- 🐛 We fixed an issue where the
member
role in the account could not upload tenant branding - 🐛 We fixed an issue with our
RadioCard
component to ensure the selected state is reflected correctly - 🐛 We fixed an issue where passing
created_at
to Segment identifies could cause an error