Hello, we are reporting the revenue per campaign and per flow via api integration (we are building a dashboard). we are using "Placed Order" metric to get the value of total orders per campaign and per flow
this works very well with campaigns however, for flows the api is returning a value that is greater than klaviyo dashboard UI.
Working example to get "Placed Order" for 1 campaign: https://a.klaviyo.com/api/v1/metric/WE4kdT/export?unit=day&measurement=value&api_key=123&start_date=2022-07-23&end_date=2022-07-23&where=[["$attributed_message","=","123"]]
Not working example to get "Placed Order" for 1 flow (api reports more than klv dashboard): https://a.klaviyo.com/api/v1/metric/WE4kdT/export?unit=day&measurement=value&api_key=123&start_date=2022-07-23&end_date=2022-07-23&where=[["$attributed_flow","=","456"]]
I believe the discrepancy you’re seeing can be explained due to how the API and the Performance Dashboard calculate and attribute revenue. For starters, the Performance Dashboard does not sort data by attributed message send date. This means that if someone receives a flow email in January and made a purchase in February, that revenue will not get counted for January in the Performance Dashboard. The same would apply when you’re looking at individual dates since by default, the attribution model would span 5-days based on a last interaction model. Whereas, the results from the API does not have this restriction.
Additionally, you can also use custom reports to generate a report on revenue attributed to a flow/flow message that would more closely match your API results.
I believe the discrepancy you’re seeing can be explained due to how the API and the Performance Dashboard calculate and attribute revenue. For starters, the Performance Dashboard does not sort data by attributed message send date. This means that if someone receives a flow email in January and made a purchase in February, that revenue will not get counted for January in the Performance Dashboard. The same would apply when you’re looking at individual dates since by default, the attribution model would span 5-days based on a last interaction model. Whereas, the results from the API does not have this restriction.
Additionally, you can also use custom reports to generate a report on revenue attributed to a flow/flow message that would more closely match your API results.
@David To I have tried and yes as you mentored, custom reports are matching the api response exactly, i guess the dashboard home is the one that is calculating differently for some reason.