Tag Archives: adwords_scripts

Changes to GCLID field length in AdWords API

In AdWords API v201309 we released a new Google Click ID field (GCLID) in the Click Performance report. Originally, this field value was limited to 26 characters. We will be extending the maximum length of this field in order to support improvements to our advertising system. Starting March 31st 2014, the value of GCLID can be up to 100 characters long.

Since this value is used in many client systems, we’re giving you advance warning of this change. Make sure your log, storage and redirecting systems can handle the extended size of the GCLID value.

Note: as a result of this change, the Click Performance report will only be available for dates up to 90 days before the time of a request. If you need the older click data, download and store these details before March 31st, 2014.

If you have any questions about the change, reach out to us on the forum or via the Google+ page.

Ensuring reliable performance with new filter limits for AWQL and reports

To ensure reliable performance for all developers and advertisers, AdWords API and AdWords scripts will start enforcing a limit of 10,000 matching values as arguments for the IN and NOT_IN operators starting March 31, 2014.

You may be affected by this change if you construct large queries that have thousands of matching values using these operators in one of these use cases: Once this change goes into effect, our servers will start throwing a SelectorError if your queries contains more than 10,000 matching values for IN and NOT_IN operators. For AdWords API v201309, the error reason would be set to SELECTOR_ERROR. In newer versions, the error reason would be set to TOO_MANY_PREDICATE_VALUES.

To make sure your applications and scripts work properly, check any code that constructs queries for reports and AWQL and add necessary limit checks before March 31, 2014.

If you have any questions about this change, you can post them on AdWords API or Scripts developer forums.