#1

Good day,

We own a Twitter for Developers app called Christopher. We are facing an issue where some of our Clients are doubting the data emanating from these APIs, and therefore essentially also questioning these Twitter API endpoints. They say it does not match what they see on their end.

I have logged numerous support tickets in December 2020 without a response. I am hoping someone can get back to me in this forum? It will be a great help if we can receive some form of formal confirmation from Twitter that we can share with Clients confirming our APIs with you.

These Clients are big Twitter advertisers in South Africa and these concerns pose not only a risk for us, but a risk of them pulling their general Twitter spend in South Africa as well. Please do treat this as a matter of urgency.

#2

Statistics differences between the API and UI are usually caused by a few different things:

  1. Your application will need to make requests for both placements, ALL_ON_TWITTER and PUBLISHER_NETWORK , separately and sum up the results to match the UI,
  2. date ranges in the UI are inclusive while the end_time is exclusive in the API, and
  3. the API will default to midnight in the accounts local timezone, if not specified

If these aren’t causing the discrepancy, please provide the Account ID, Entity IDs, and any campaign information in the UI that isn’t matching.