Google Ads Developer Blog: google

Entity IDs as 64-bit in AdWords API, Google Ads API beta, Google Ads scripts, and Content API for Shopping

Monday, June 15, 2020

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

Google Ads conversion reporting issues starting April 9

Friday, April 10, 2020

Update (April 10, 2020 19:35 PST): Conversion data in all reports has been fixed.

An issue that impacted Google Ads reporting for Search and Shopping conversions occurring between April 9 and April 10 (Pacific Time) for advertisers using non-last click attribution models has been fixed and the data is now correct in all reports.
If you downloaded any of the fields in the table below or any derivative custom columns using the AdWords API, Google Ads API and Google Ads scripts between April 9th 8:00 PM PST and April 10th 7:20 PM PST, you may have incorrect data in your systems. Please re-download the affected fields to ensure accurate conversions reporting.
We appreciate your patience as we worked to resolve this issue as quickly as possible.

AdWords API

Google Ads API beta

Conversions
ConversionValue
ConversionRate
ValuePerConversion
CostPerConversion
AllConversions
AllConversionValue
AllConversionRate
ValuePerAllConversion
CostPerAllConversion
CurrentModelAttributedConversions
CurrentModelAttributedConversionValue
ValuePerCurrentModelAttributedConversion
CostPerCurrentModelAttributedConversion

metrics.all_conversions
metrics.all_conversions_from_click_to_call
metrics.all_conversions_from_interactions_rate
metrics.all_conversions_from_interactions_value_per_interaction
metrics.all_conversions_value
metrics.all_conversions_value_per_cost
metrics.conversions
metrics.conversions_from_interactions_rate
metrics.conversions_from_interactions_value_per_interaction
metrics.conversions_value
metrics.conversions_value_per_cost
metrics.cost_per_all_conversions
metrics.cost_per_conversion
metrics.cost_per_current_model_attributed_conversion
metrics.cross_device_conversions
metrics.current_model_attributed_conversions
metrics.current_model_attributed_conversions_from_interactions_rate
metrics.current_model_attributed_conversions_from_interactions_value_per_interaction
metrics.current_model_attributed_conversions_value
metrics.current_model_attributed_conversions_value_per_cost
metrics.value_per_all_conversions
metrics.value_per_conversion
metrics.value_per_current_model_attributed_conversion

On April 9, 2020 at approximately 8pm PST, a bug caused Google Ads Search and Shopping conversions occurring between April 9 12:01 AM PST onwards to be underreported for advertisers using non-last click attribution models. This bug impacts reports in all Google Ads interfaces, including any report data downloaded via the AdWords API, Google Ads API and Google Ads scripts. Google Ads bid strategies are not impacted by this issue.
We are actively working on fixing the bug and correcting the conversion data.

- Josh Radcliff, Google Ads API Team

Campaign IDs and Budget IDs as 64-bit in Google Ads

Monday, July 22, 2019

Update (Aug 5, 2019): Please also include SharedSet ID in your verification for 64-bit compliance. Update (Jul 26, 2019): Please also include Asset ID in your verification for 64-bit compliance.

In the AdWords API and Google Ads API, Campaign IDs and Budget IDs are 64-bit signed integers and are of type xsd:long in the AdWords API and INT64 in the Google Ads API. Applications that integrate with the API should handle ID values in that range.

Historically, Campaign and Budget IDs in Google Ads were within the maximum value of 32-bit signed integer, but will soon be exceeding this range. In order to avoid any issues, please make sure your applications are fully compliant with IDs within a range of 64-bit signed integer values.

If you have any questions or concerns, please don't hesitate to contact us via the forum.
--Stan Grinberg, Google Ads API Team

Register now for the upcoming Google Ads API Workshops!

Tuesday, February 5, 2019

We're excited to announce that a new series of Google Ads API Workshops are coming this March and April! The technical sessions focus on migration from the current AdWords API so you can migrate quickly and efficiently. New users are welcome and will benefit as well.

The workshops will be presented in English, except for those in Taipei, Tokyo, and Shanghai. Details are listed below. Note that location names link to the registration websites:

Workshops in all locations will cover the same topics, so choose a location that works best for you. Once you register, we'll send you an email confirmation.

Stay tuned for more detailed agenda on the workshop websites!

If you have any questions about the workshops, you can post them on our forum.

- Thanet Knack Praneenararat, Google Ads API Team

Ads Developer Blog

Entity IDs as 64-bit in AdWords API, Google Ads API beta, Google Ads scripts, and Content API for Shopping

Google Ads conversion reporting issues starting April 9

Campaign IDs and Budget IDs as 64-bit in Google Ads

Register now for the upcoming Google Ads API Workshops!

Labels

Archive

Feeds

Google Ads API [+]

AdWords API [+]

Google Ads scripts [+]

Content API for Shopping [+]

Google Ad Manager API [+]

DCM API [+]

Mobile Ads [+]

IMA SDK [+]