Issue regarding Revenue data pulled through Twitter's API

[DatoramaDev]

Hey Twitter Dev community,

We got a complaint from a client of ours that the revenue data being pulled by our Twitter API does not match the data in their Twitter UI.
We’ve investigated the issue and noticed that this data was being originally pulled from the Twitter API connector, we’ve built, with different numbers.

The client mentioned that they don’t have the standard Attribution Windows (1 day post impression and 30 day post click), but rather 100% of 7 day click and 33% of 7 day view. As our other clients, that have the standard attribution windows, do not suffer from this issue, our theory is that this is the main cause of the discrepancies.

Is there something we may be missing in our API calls to your platform, regarding the Attribution Windows, that will correct these numbers? If there’s anything you think may be useful on top of the answer, please share so we can come to a resolution for our client as soon as possible.

Thanks in advance,
the Datorama Dev support team.

[JBabichJapan]

Hi @DatoramaDev The data we return via our Analytics API should match any data you see on the Ads UI, and when it differs there should be a way to find out why. If the data with attribution windows is being displayed via something like a 3rd party tool, we cannot guarantee how that data is being generated so that could be the cause of discrepancies as you say. The only way to change the data returned related to conversions (for either web site tags or app events) is to change the web event tags or app event tags associated with the account, which can be done either from API or UI. Once they are changed, you can re-fetch data, but as I said the data from our UI should line up either way so the issue might be related to something outside of scope of this support forum.

Thanks

John