Conversion Window Correction

50 views
Skip to first unread message

Ryan Blecher

unread,
May 30, 2017, 1:55:11 PM5/30/17
to AdWords API Forum

My understanding is that the Conversion Window is finalized is at a max of 90 days. Our application syncs reports nightly to account for the previous day, but we need to account for conversion correction that take place much further back than that.
  1. Are there better ways to do this than sync reports for the past 90 days nightly and check if conversion counts are different each day?
    The discrepancy is most cases is < 1% and it seems inefficient to fetch data that is unchanged.

  2. Is there any way to bulk download reports for multiple users? ie. KeywordPerformanceReport for multiple campaigns.
    or can we get all the necessary reports for an account at once?

Shwetha Vastrad (AdWords API Team)

unread,
May 30, 2017, 4:23:11 PM5/30/17
to AdWords API Forum
Hi Ryan, 

Since metrics may occasionally be updated when a conversion occurs days after the initial click, it is recommended that you update your reports to get the recent account data. You can chose the frequency at which you perform this update based on the conversion window for the conversion trackers in your account. A report request can only include data from a single AdWords account for a particular report type. You need to issue separate requests for each report type and for each account. You could consider using the AwReporting framework for large scale AdWords API reporting. You can specify the report types and fields for which you want to get data. 

Regards,
Shwetha, AdWords API Team.

Zweitze

unread,
May 31, 2017, 5:35:43 AM5/31/17
to AdWords API Forum
1. If you consider that very few conversion types actually need the 90-day window:
First call the ConversionTrackerService, request all conversion types. Then determine the largest conversion window, which is in field ctcLookbackWindow. Note: if you also synchronize ViewThrough conversions, you should also consider viewthroughLookbackWindow!
You could now use that maximum instead of 90 days. It's not perfect, because the setting may change between syncs.

Another solution is request an account report, only aggregated to individual days first, and compare the conversions in that report with the contents of your local database - you should re-sync from the oldest discrepancy again.

2. You can use multithreading or multiple machines to request multiple reports at the same time. You can also use asynchronous communication, but not all libraries support that - at least the .NET library doesn't.
Reply all
Reply to author
Forward
0 new messages