Discrepancy between API and report in the revenue metric | Community
Skip to main content
A
AndresCa6
July 2, 2024
Question

Discrepancy between API and report in the revenue metric

  • July 2, 2024
  • 1 reply
  • 796 views

Hi. I am having trouble with some discrepancies between the data extracted via adobe analytics APIs 2.0 and the report extracted from the platform.
I am requesting visits, orders and revenue with the variables/lasttouchchanneldetail dimension and i have some segments filtering this dimension.
The discrepancies are not only for recent data but up to two months ago. Visits and orders have a low variance but revenue specifically is different for some specific channels, up to 1% differece in the values (considering the single channel). Considering all channels in a whole day, this difference is not greater than 0.07%.
Since the other metrics are pretty close, my question is if this is an expected behaviour and how much discrepancy should be considered normal?
Thanks in advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 3, 2024

Did you use the Workspace Debugger to get the API call?

 

Workspace reports use API 2.0 to pull the data, so there should be no reason for the data to be different, unless the API call has some minor logic differences that could be causing a slight variation.....

 

 

To see the API calls for your Workspace Reports, turn on Debugging from the Help Menu (this will add a new bug icon to your visualizations)

 

Click on this icon, and it will first ask you if you want the Freeform Table or Sparkline, choose the Table. Then it will show you timestamps of the APIs... keep in mind that complex data pulls could be using multiple requests.

 

When you click on the timestamps, a new page will open showing the API call in multiple formats.

 

I would compare your API requests for differences, this is the most likely cause of the discrepency.

Terms & ConditionsAccessibility statement

Loading footer...