#1

Good afternoon, how are you?

My application was developed in .Net Core, so we were unable to use “Twurl”. Due to this problem, for accounts with dates in Brazil, we make requests with “TOTAL” granularity
With the exception of the 18ce5511gcp and 18ce54qr491 accounts, the results match the platform’s Ads Manager. Below are the requests used:

ACCOUNT: 18ce54qr491
https://ads-api.twitter.com/7/stats/jobs/accounts/18ce54qr491?end_time=2020-04-30&entity=CAMPAIGN&entity_ids=bfl91,bfrxp,bfs17,bfsja,bspd3,bspdj,bsx6u,btbw1,btbw1, btqjt, bu95r, bulb1, buxb6, bv489, cl6ja, cl6yb, cm4nm, coc5s, cocn6, cod7i & granularity = DAY & metric_groups = BILLING, ENGAGEMENT, VIDEO & placement = ALL_ON_TWITTER & start_time = 2020-02-01

https://ads-api.twitter.com/7/stats/jobs/accounts/18ce54qr491?end_time=2020-04-30&entity=CAMPAIGN&entity_ids=cod88,cod9b,cod9r,cod9x,codab,codag,codbe,cojof,cojpc, cojvm, cz8en, cz8n7, d5sd9, de7pi, de9it, degux, degv6, dexz0, dey4w, dfaw1 & granularity = DAY & metric_groups = BILLING, ENGAGEMENT, VIDEO & placement = ALL_ON_TWITTER & start_time = 2020-02-01

https://ads-api.twitter.com/7/stats/jobs/accounts/18ce54qr491?end_time=2020-04-30&entity=CAMPAIGN&entity_ids=dfqae,dg0ba,doicc,dontq&granularity=DAY&metric_groups=BILLING,ENGAGEMENT,VIDE_STONT&T 2020-02-01

ACCOUNT: 18ce5511gcp (Date in Brazil)
https://ads-api.twitter.com/7/stats/jobs/accounts/18ce5511gcp?end_time=2020-02-02&entity=CAMPAIGN&entity_ids=dnv86,dwfd5&granularity=TOTAL&metric_groups=BILLING,ENGAGEMENT,VIDEO&placement=ALL_ON_20 01

https://ads-api.twitter.com/7/stats/jobs/accounts/18ce5511gcp?end_time=2020-02-03&entity=CAMPAIGN&entity_ids=dnv86,dwfd5&granularity=TOTAL&metric_groups=BILLING,ENGAGEMENT,VIDEO&placement=ALL_ON_20 02
.
.
.
https://ads-api.twitter.com/7/stats/jobs/accounts/18ce5511gcp?end_time=2020-04-30&entity=CAMPAIGN&entity_ids=dnv86,dwfd5&granularity=TOTAL&metric_groups=BILLING,ENGAGEMENT,VIDEO&placement=ALL_ON_20 29

The result is in the attached image.

result
result773×123 6.99 KB

Please, can you validate if the error is in the platform or in our requests?

#2

Differences between the API and UI are usually caused by a few common issues:

  1. request both placements, ALL_ON_TWITTER and PUBLISHER_NETWORK, separately via API and sum them,
  1. note that date ranges are inclusive in the UI but the end_time is exclusive in the API, and
  2. the API will default to midnight in the account’s local timezone, if not specified.

If you still believe there is a mismatch between these, please include a full URL path to Ads Manager that displays expected result and an API request that is used to retrieve this information for your application.

#3

Tom, thanks for reply.

Using the two channels, divergence only in February, as shown below:
image

Please, can you validate?

#4

Certainly. Please include a full URL path to Ads Manager that displays expected result and an API request that is used to retrieve this information for your application.

#5

Of course.

Here, there are two requests to API with both placements:
https://ads-api.twitter.com/7/stats/jobs/accounts/18ce54nwcxk?end_time=2020-02-01&entity=CAMPAIGN&entity_ids=d9j48,d9ydy,daac5,dah90,davtm,dbl8k,dbl97,dc19s,dc7g4,dcyu0,dd187,ddq9i,de7zw,dew93,dey4q,df441,df9n5,dfb87,dfgag,dfpqg&granularity=TOTAL&metric_groups=BILLING,ENGAGEMENT,VIDEO&placement=PUBLISHER_NETWORK&start_time=2020-01-31

https://ads-api.twitter.com/7/stats/jobs/accounts/18ce54nwcxk?end_time=2020-02-05&entity=CAMPAIGN&entity_ids=d9j48,d9ydy,daac5,dah90,davtm,dbl8k,dbl97,dc19s,dc7g4,dcyu0,dd187,ddq9i,de7zw,dew93,dey4q,df441,df9n5,dfb87,dfgag,dfpqg&granularity=TOTAL&metric_groups=BILLING,ENGAGEMENT,VIDEO&placement=ALL_ON_TWITTER&start_time=2020-02-04

Adress Ads Twitter:
https://ads.twitter.com/ads_manager/18ce54nwcxk/campaigns/?endDate=2020-02-29&startDate=2020-02-01

https://ads.twitter.com/ads_manager/18ce54bklau/campaigns/?columnSet=1130916069735043072&columns=9.8.47.72.70.10.11.15.41.42.38.83.84.85.39.303.86.276.89.69.82&endDate=2020-02-29&startDate=2020-02-01

Tks.

#6

It looks like the Ads API requests are returning data for a separate time period than the Ads Manager UI. The UI is returning data for February and the API seems to be returning data for either Feb 1st or the span of Feb 1 → Feb 5th. Do you find there is a discrepancy when the time periods match?

Also, is your application using the Active Entites endpoint to help identify which Campaigns to fetch for a time period?

#7

Just exemplified, the date range of requests range from 2020-01-31 to 2020-03-01, the other accounts we have access to, correctly match day by day according to Ads Manager with daily details.

Yes, I’m using asynchronous method - Asynchronous Guide | Docs | Twitter Developer Platform.

Can you simulate asynchronously, TOTAL granularity, date range of just 1 day as exemplified above? I will pass the campaign requests to these two accounts:
https://ads-api.twitter.com/7/accounts/18ce54bklau/campaigns?with_deleted=true - 366 campaigns
https://ads-api.twitter.com/7/accounts/18ce54nwcxk/campaigns?with_deleted=true - 119 campaigns

Tks.

#9

How are you, Tom?

Do you have any news?

Tks