DFP Adserver Impression metrics discrepancy

[Thu Nguyen]

Hi there, 

We're facing an issue with Ad server impressions metric discrepancy between our API queries and DFP reporting UI. The impressions metrics from the API have double of the values compared to data from reporting UI.

Other ad sever metrics like Clicks & Revenue have no issues though.

I can send out more details on a private messages.

Best,

Thu

P.S: We're calling data from API v201702

Dimensions:

"date",
"advertiser_id",
"advertiser_name",
"order_id",
"order_name",
"line_item_id",
"line_item_name",
"line_item_type",
"creative_id",
"creative_name",
"creative_type",
"creative_size",
"ad_unit_id",
"ad_unit_name"
"advertiser_type",
"line_item_priority",
"line_item_goal_quantity",
"line_item_start_date_time",
"line_item_end_date_time",
"creative_click_through_url"

Metrics

"ad_server_active_view_eligible_impressions",
"ad_server_active_view_measurable_impressions",
"ad_server_active_view_viewable_impressions",
"ad_server_downloaded_impressions",
"ad_server_impressions"

[Nicholas Figeac (DFP API Team)]

Hello,

Can you please provide me your network code, SOAP logs and a screenshot of the UI query that shows the date range, dimensions, dimension attributes and metrics selected? You can send this information using "Reply privately to author". I ran a report in my test network and received the same results for ad server impressions. Also, I don't see any known issues on our Ads Status Dashboard.

Thanks,
Nicholas Figeac, DFP API Team

[Nicholas Figeac (DFP API Team)]

Hello Community,

Here is a brief summary of the case that was taken offline as the publisher shared private information.

Publisher was having issues with data discrepancy between UI and API reports. Turned out the UI and API reports were using different dimension and columns in the report query therefore providing different reports. The solution to this kind of problem is to make the UI and API report query match. Though documentation does not have UI -> API value mappings here are a few ways to find the API values.

1) Run the saved query via API using ReportService#getsavedqueriesbystatement
2) If the saved query is not compatible, create simple saved query i.e. no filtering, date range = Yesterday to find dimension and metric values.
3) For Ad Exchange Historical report types, use our Adx mapping tool.

If you have any issues with DFP API please post a new thread.