Connector Improvement: Klaviyo Conversion and Revenue Data
Answered
Currently Klaviyo connector provides raw events table, however email conversion and revenue are key measures to stakeholders. Logic to re-create conversion and revenue from events tables is redundant since Klaviyo provides API to access calculated revenue and conversions. So in order to Klaviyo connector' schema to be really analytics ready, there should be campaign and flow performance measures either directly from the API or through a DBT package.
-
Official comment
Hi Teresa - great question! This is by design according to Fivetran's Shared Responsibility Model:
In designing a Fivetran schema, we do not try to provide an immediate answer to a specific customer's question. Instead, our goal is to provide a correct, easy-to-query schema that all of our customers can use to answer their own questions.
Klaviyo will attribute a given order to the last email someone opened/clicked within the account's conversion window; not all orders will be driven by email marketing, so there will be orders where there is no email last opened/clicked within the conversion window for attribution. So, the query is a window function looking at the last open/click on an email prior to the Placed Order metric, and then assigning the revenue to the campaign associated with that email. The conversion window is a configurable parameter in the Klaviyo interface, so use the same value in your query to get the same results.
Great idea re a dbt package - it was already on in the queue and I hope to see it built soon.
Please sign in to leave a comment.
Comments
1 comment