In the
AdWords API, the
Google Ads API beta,
Google Ads scripts, and the
Content API for Shopping, all entity IDs are 64-bit signed integers. They are of type:
xsd:long in the AdWords APIINT64 in the Google Ads APInumber or string in Google Ads scriptsstring in REST and as INT64 for client libraries in Content API for Shopping
Applications that integrate with the API should handle ID values in that range.
Historically, the following IDs were within the maximum value of 32-bit signed integer, but will soon be exceeding this range. Over the years, all of you have been so productive that we need to make sure 64-bit signed integers are available to allow the creation of more entities with unique IDs. This was
announced starting in July 2019. To avoid any issues, please make sure your applications handle these IDs within a range of 64-bit signed integer values. Also make sure that your application is ready to support a 64-bit signed integer for any other entity IDs not listed below.
Which IDs are affected in the AdWords API and the Google Ads API beta?
Which IDs are affected in Google Ads scripts?
JavaScript can only accurately represent integers up to 53 bits, so it's strongly advised that you begin treating all IDs in Google Ads scripts as
string to avoid any possible future errors with high ID numbers.
Which IDs are affected in the Content API for Shopping?
All IDs are returned as
string in REST and as
INT64 in the client libraries. If you convert IDs to a number in your application, please make sure the application can handle 64-bit signed integers. An example of this is merchant ID that is set in the client library’s configuration or in the REST URL.
Where can I get support?
If you have any API questions or need help, you can reach us at:
Nadine Wang, on behalf of the entire Google Ads Team
