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 API
• INT64 in the Google Ads API
• number or string in Google Ads scripts
• string 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?

	AdWords API	Google Ads API beta
Bidding Strategy	BiddingStrategyConfiguration.bidding_strategy_id BiddingStrategyId (multiple reports)	BiddingStrategy.id
Budget	BudgetOrder.id	AccountBudget.id BillingSetup.id
User List	UserList.id CriterionUserList.userListId CLICK_PERFORMANCE_REPORT.UserListId AUDIENCE_PERFORMANCE_REPORT.Id	UserList.id
Shopping Campaigns	ServiceLink.serviceLinkId ShoppingSetting.merchantId SHOPPING_PERFORMANCE_REPORT.MerchantId SHOPPING_PERFORMANCE_REPORT.AggregatorId	MerchantCenterLink.id ShoppingSetting.merchant_id segments.product_merchant_id segments.product_aggregator_id
Conversion Action	ConversionTracker.id ConversionTrackerId (multiple reports) ConversionTracker.originalConversionTypeId	ConversionAction.id
Account Conversion Tracking Configuration	ConversionTrackingSettings.effectiveConversionTrackingId	ConversionTrackingSetting.conversion_tracking_id ConversionTrackingSetting. cross_account_conversion_tracking_id

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.

	Google Ads scripts
Bidding Strategy	AdsApp.BiddingStrategy.getId()
Budget	AdsApp.BillingAccount.getId() AdsApp.BudgetOrder.getId()
User List	AdsApp.Audience.getId() AdsApp.ExcludedAudience.getId() AdsApp.UserList.getId() AdsApp.​ShoppingCampaignAudience.getAudienceId() AdsApp.ShoppingCampaignAudienceBuilder.withAudienceId() AdsApp.ShoppingCampaignAudienceSelector.withIds() getAudienceId() and withAudienceId() for all Targeting -> Audience Search methods.

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.

	Content API for Shopping
Merchant Center	AccountIdentifier.merchantId Order.merchantId OrdersCustomBatchRequestEntry.merchantId RegionalinventoryCustomBatchRequestEntry.merchantId ProductsCustomBatchRequestEntry.merchantId ProductstatusesCustomBatchRequestEntry.merchantId AccountsCustomBatchRequestEntry.merchantId OrderReportDisbursement.merchantId OrderReportTransaction.merchantId LocalinventoryCustomBatchRequestEntry.merchantId ReturnpolicyCustomBatchRequestEntry.merchantId
Shopping Campaign	AccountIdentifier.aggregatorId

Where can I get support?
If you have any API questions or need help, you can reach us at:

• AdWords API and Google Ads API beta forum or googleadsapi-support@google.com.
• Google Ads scripts forum.
• Content API for Shopping forum.

Nadine Wang, on behalf of the entire Google Ads Team