{"__v":4,"_id":"567b4416b56bac0d0019d8ec","category":{"__v":33,"_id":"55566892150ba30d00f4e206","pages":["567b42903241c20d00b73091","567b429b17368a0d009a6e64","567b42a717368a0d009a6e66","567b42b24cde0321001e117f","567b4312ee052b1700dbd9e9","567b4322b56bac0d0019d8e8","567b43334cde0321001e1182","567b434b3241c20d00b73094","567b43594cde0321001e1184","567b4369ee052b1700dbd9eb","567b43774cde0321001e1186","567b438793919f0d00c97ae1","567b439693919f0d00c97ae3","567b43a3b56bac0d0019d8ea","567b43c13241c20d00b73096","567b43d4ee052b1700dbd9ed","567b43e5ee052b1700dbd9ef","567b43f317368a0d009a6e69","567b44053241c20d00b73098","567b4416b56bac0d0019d8ec","567b442893919f0d00c97ae6","567b49494cde0321001e118e","567b49584cde0321001e1190","567b49713241c20d00b7309f","567b498693919f0d00c97aea","567b49984cde0321001e1192","567b49a817368a0d009a6e71","567b49ca7c40060d00560436","5681b7a4aad86d0d00b9f276","5682d73a6d21130d00a705db","5682dfb77af9120d007ac2b4","568ee501bdb9260d00149d6c","56d0c60b1ecc471500f179ef"],"project":"555627c4ea5e120d001884fb","version":"555627c4ea5e120d001884fe","reference":false,"createdAt":"2015-05-15T21:43:46.368Z","from_sync":false,"order":5,"slug":"ad-ops","title":"Ad Ops"},"project":"555627c4ea5e120d001884fb","user":"55562799ea5e120d001884f8","version":{"__v":10,"_id":"555627c4ea5e120d001884fe","project":"555627c4ea5e120d001884fb","hasDoc":true,"hasReference":true,"createdAt":"2015-05-15T17:07:16.918Z","releaseDate":"2015-05-15T17:07:16.918Z","categories":["555627c5ea5e120d001884ff","55562a5526e9bc0d0044ea47","555653821026001900d72a3c","5556685c1026001900d72a85","5556687626e9bc0d0044ec04","555668821026001900d72a87","55566892150ba30d00f4e206","555668b826e9bc0d0044ec05","55e0fb6026f51b0d009b1746","567b3b3017368a0d009a6e54"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"createdAt":"2015-12-24T01:02:14.212Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"examples":{"codes":[]},"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":21,"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Certification Reporting Required\"\n}\n[/block]\nIf the Publisher/Network requires impression and reporting comparison follow the steps below:\n  * Request an Ad Server report from the Publisher/Network Ad Ops team.\n  * Enter the Flite Console and click to the *MEASURE* stage within the console.\n  * Make sure that the placement you need to generate a report for has been selected in the left-hand *Placements* panel. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/NnUMhE02TtuO0T0lmT6h\",\n        \"Measure.png\",\n        \"700\",\n        \"400\",\n        \"#7796a4\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n  * Next select the export button in the upper left of the left-hand side *Placements* pane and choose “Export Daily Metrics (.csv)” from the dropdown menu. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/wVhvSwTmRLQ3wbbQeFUQ\",\n        \"Export.png\",\n        \"700\",\n        \"153\",\n        \"#7b9aa2\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nYour report will then generate and download to your local machine.\n\n  * Compare impression numbers from both ad servers side-by-side and calculate the discrepancy percentage per daily line item.\nIf there is no discrepancy concerns following the reporting comparison [click here](doc:ad-ops-certification-finalization).\n\nIf there is a discrepancy that is outside of the standard discrepancy of 10% then add the Flite Ad Operations email alias into the email thread for further assistance (adopssupport:::at:::flite.com).\n\n## TIPS\nThere are many resources that can be found in each ad servers support system that will provide more insight to the expected discrepancies when trafficking third-party tags. An example link of these resources is found below: \n\n  * URL for DFP Premium reference:\n[Investigate discrepancies with other systems](https://support.google.com/dfp_premium/answer/177507?hl=en)\n\n> When an ad server delivers line items that are hosted by a third party, reporting discrepancies between the two systems will occur, and it is common to see campaign variances of up to 20%. Check the lists in \"More about third-party discrepancies,\" below, to learn why discrepancies may occur and what you can do to prevent them.\n\n> The best practice is to always traffic DFA/DCM tags using the \"DoubleClick tag\" creative type, which reduces discrepancies in impression numbers. Please note that if you are working on DFP Premium and DFA/DCM, you could see a discrepancy greater than 2% for both impressions and clicks. This occurs because of different invalid activity filters. You should treat DFA/DCM as any other third-party product and should expect up to 20% in counting discrepancy.\n\nAdditionally, it may be useful to debug the ad unit on the test page to monitor what calls are being made as well as request a larger test sample size to see if the discrepancy reduces based on a longer test flight.\n\nFor discrepancy resolution assistance:\n\n[adopssupport@flite.com](mailto:adopssupport@flite.com)","excerpt":"","slug":"ad-ops-certification-reporting-process","type":"basic","title":"Certification Reporting Process"}

Design Studio

Campaign Studio

Report Studio

Metrics

Flite Console

Ad Ops

Component Studio

Certification Reporting Process

[block:api-header] { "type": "basic", "title": "Certification Reporting Required" } [/block] If the Publisher/Network requires impression and reporting comparison follow the steps below: * Request an Ad Server report from the Publisher/Network Ad Ops team. * Enter the Flite Console and click to the *MEASURE* stage within the console. * Make sure that the placement you need to generate a report for has been selected in the left-hand *Placements* panel. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/NnUMhE02TtuO0T0lmT6h", "Measure.png", "700", "400", "#7796a4", "" ] } ] } [/block] * Next select the export button in the upper left of the left-hand side *Placements* pane and choose “Export Daily Metrics (.csv)” from the dropdown menu. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/wVhvSwTmRLQ3wbbQeFUQ", "Export.png", "700", "153", "#7b9aa2", "" ] } ] } [/block] Your report will then generate and download to your local machine. * Compare impression numbers from both ad servers side-by-side and calculate the discrepancy percentage per daily line item. If there is no discrepancy concerns following the reporting comparison [click here](doc:ad-ops-certification-finalization). If there is a discrepancy that is outside of the standard discrepancy of 10% then add the Flite Ad Operations email alias into the email thread for further assistance (adopssupport@flite.com). ## TIPS There are many resources that can be found in each ad servers support system that will provide more insight to the expected discrepancies when trafficking third-party tags. An example link of these resources is found below: * URL for DFP Premium reference: [Investigate discrepancies with other systems](https://support.google.com/dfp_premium/answer/177507?hl=en) > When an ad server delivers line items that are hosted by a third party, reporting discrepancies between the two systems will occur, and it is common to see campaign variances of up to 20%. Check the lists in "More about third-party discrepancies," below, to learn why discrepancies may occur and what you can do to prevent them. > The best practice is to always traffic DFA/DCM tags using the "DoubleClick tag" creative type, which reduces discrepancies in impression numbers. Please note that if you are working on DFP Premium and DFA/DCM, you could see a discrepancy greater than 2% for both impressions and clicks. This occurs because of different invalid activity filters. You should treat DFA/DCM as any other third-party product and should expect up to 20% in counting discrepancy. Additionally, it may be useful to debug the ad unit on the test page to monitor what calls are being made as well as request a larger test sample size to see if the discrepancy reduces based on a longer test flight. For discrepancy resolution assistance: [adopssupport@flite.com](mailto:adopssupport@flite.com)