Google Ads Developer Blog: conversion

Upcoming Improvements to Offline Conversion Imports

2026 m. kovo 26 d., ketvirtadienis

Starting in April, 2026 the Google Ads API will benefit from a series of infrastructure changes designed to improve the Offline Conversion Import experience. These upgrades will not result in any breaking changes to the Google Ads API, however there may be minor fluctuations in attribution rates as the changes are rolled out. Here is a breakdown of the rollout and the improvements you can expect:

Improved attribution and fallback recovery (April, 2026): We will implement changes allowing us to attribute some expired GCLIDs and clicks that occurred before a conversion. Once deployed, you may receive fewer EXPIRED_EVENT and CONVERSION_PRECEDES_EVENT errors in conversion upload responses, and you may notice higher attribution rates.

Flexible import requests (April - May, 2026): We will improve the authorization structure for conversion import requests to make it easier for manager or client accounts to import conversions on behalf of a different trafficking account. Once released, users should expect a reduction in UNAUTHORIZED_CUSTOMER and INVALID_CUSTOMER_FOR_CLICK errors in conversion import responses. This may also result in an increase in attribution.

Make sure to review our guidance on how to maximize the performance of your Google Ads conversion data. And take a look at the Data Manager API, including our migration guide for Google Ads API users. Reach out to the Google Ads API support channel if you have any questions. And if you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.

- Ben Karl, on behalf of the Google Ads API Team

Changes to IP Address and Session Attribute Support in the Google Ads API

2026 m. sausio 7 d., trečiadienis

Starting on February 2, 2026, the Google Ads API will no longer accept new adopters of session attributes or IP address data as part of conversion imports. To ensure a more robust and scalable experience for handling complex data, we recommend that Google Ads API developers transition to the Data Manager API - where session attributes and IP address are accepted - as their primary conversion and user data import API. Developers who have already adopted session attributes or IP addresses in their click conversion imports can continue importing that data using the Google Ads API until they’ve moved their conversion imports over to the Data Manager API. Technical details

Developers will be allowlisted by their developer token.

Once this change is rolled out, you may notice the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE in the partial_failure responses of your conversion import requests. This error indicates that the associated conversion was rejected due to the presence of session attributes and/or IP address.

Resolve this error with these steps:

Temporarily remove session attributes and IP address from conversion import requests and continue importing conversions to the Google Ads API.
Update your code to use the Data Manager API with session attributes and IP address.
Discontinue conversion imports to the Google Ads API once you’re successfully making imports to the Data Manager API.

Reach out to the Google Ads API support or Data Manager API support channels if you have any questions. If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.

- Ben Karl, on behalf of the Google Ads API Team

Bidding enforcement for conversion environment in in-app conversions no longer planned

2025 m. spalio 8 d., trečiadienis

On June 30, 2025 we announced that we would roll out a change that would cause our bidding models to start using the presence of the ClickConversion.conversion_environment field in imported in-app conversions for campaign performance. That change, which may have caused performance degradation in certain campaigns where this is not set, will no longer be implemented. However we still recommend that users who import conversions using the Google Ads API set the conversion_environment field in order to gain the following benefits:

Accurate cross-environment attribution: Understand the full value of your campaigns across website and app sources.

Ad destination reporting: Gain insights into where the user lands after clicking your ad, and the relative performance of each segment.

Streamlined Google support: Receive faster and more effective troubleshooting.

For more details see this Help Center article. If you have any questions or need help, see the Google Ads API support page for options.

- Ben Karl, on behalf of the Google Ads API Team

Streamlined Account-Default CustomerConversionGoal Behavior in Google Ads

2025 m. rugsėjo 25 d., ketvirtadienis

Starting on November 17 2025, we are changing the account-default behavior of automatically created customer conversion goals. Current behavior Currently, when you create a new conversion action using the Google Ads API, customer conversion goals are created automatically, as needed. These newly created goals are automatically set as account-default, meaning this goal will automatically be biddable in any campaign that is optimizing to account-default goals. While convenient, this sometimes leads to bidding mechanisms targeting unnecessary goals, potentially resulting in suboptimal campaign performance. This change aims to optimize bidding performance by reducing the number of unnecessary goals included in the account-default set for a given account. What’s changing? With this change, a new automatically created goal will only be set as account-default if all other goals within the same category are also account-default goals. For example, if an account has an existing, non-account-default customer conversion goal associated with a conversion action with the category PURCHASE and a conversion origin of WEBSITE, then any new conversion actions with the category PURCHASE will result in goals that are also not account-default. This approach helps us better infer user intent, and it ensures that the account-default set remains lean and effective. Technical recommendation After this change is introduced, newly created account goals will not be considered account-default automatically. If you want to set an account goal to account-default manually, set the CustomerConversionGoal.biddable field to true. This update will enhance the efficiency and effectiveness of goal management within Google Ads. We encourage you to review your applications and client workflows in light of this upcoming change. For any questions or concerns, feel free to refer to our support page. You can also discuss this post in our “Google Advertising and Measurement Community” Discord server.

- Ben Karl, on behalf of the Google Ads API Team

Introducing improved diagnostics for enhanced conversions for leads imports

2025 m. rugsėjo 23 d., antradienis

Today in the Google Ads UI, you will see updated enhanced conversions for leads diagnostics that feature a number of improvements that offer better visibility into the state of your conversion import implementation. The goal of these changes is to help you identify common problems and address them quickly. Here are some of the changes you’ll see:

New "Importing limited user-provided data" Alert: A new, high-priority alert has been introduced to detect a common implementation error, where users fail to import incremental conversions that contain user-provided data (UPD) but not a GCLID. We recommend that you import all of your conversion data that has user-provided data, regardless of whether or not it has a GCLID. Doing so helps to find cross-device or Youtube EVC conversion touchpoints, driving performance uplift. You may not see these benefits if you omit UPD-only conversions.

Improved Status for "Tagless" Implementations: A new "Good" status has been added to validate setups where advertisers import conversions with both a GCLID and user-provided data, but do not have the Google tag implemented on their website. Previously, this valid configuration could trigger confusing "Urgent" alerts. If you have not implemented the Google tag on your website, it’s important to include GCLIDs in your conversion imports whenever possible in order to get performance benefits.

Reprioritized Alert Logic: Alert priorities have been updated to be more intelligent. For users sending GCLIDs with their offline data, import-related issues will be prioritized as more critical, while tag-related issues will be downgraded in severity.

Complete Alert Visibility: The diagnostics interface has been updated to show all alerts at once, regardless of their severity tier. This allows developers to see a complete picture of all required and recommended actions upfront, rather than fixing one issue only to uncover another.

Deprecation of CLICK_NOT_FOUND: The informational CLICK_NOT_FOUND error has been removed from the Diagnostics UI and API, and, correspondingly, the debug_mode parameter in the UploadClickConversions method that triggers it in API responses has also been removed. See this related blog post for reference.

Reach out to the Google Ads API support channel if you have any questions or need support. If you want to discuss this change with us, join our “Google Advertising and Measurement Community” Discord server.

- Ben Karl, on behalf of the Google Ads API Team

Maximize the performance of your Google Ads conversion data

2025 m. rugpjūčio 20 d., trečiadienis

In today's data-driven world, the performance of your ad campaigns increasingly depends on the richness of the conversion data you import. When it comes to machine learning, the more signals you provide, the better the models can understand user behavior, predict outcomes, and deliver value. For conversion imports specifically, richer data can mean increased observed conversions, and better modelled conversions. For this reason it’s important to make sure that your application is set up to gather, and import, as much conversion data as possible to the Google Ads API. To do that, you may need to make improvements to your existing conversion import pipeline. Why upgrade? We recommend that you upgrade your conversion import pipeline by gathering and importing more than just GCLIDs.

Durability:

Improve conversion attribution, especially when GCLIDs are missing, by incorporating new data points.
Adapt to evolving privacy regulations and the deprecation of traditional tracking identifiers.

Better modeling:

Provide more data to Google's AI for better campaign optimization.
Get a more complete picture of user behavior and improve model reliability.

Steps to upgrade your conversion import pipeline

Update your Google Ads API version:

Move to Google Ads API version v20 or later. See our release notes and migration guides.

Include user-provided data:

Include hashed user-provided data (email, phone number), when available, to unlock cross-device and engaged-view conversions. See our documentation on sending user-provided data.
Important: Set up your application to import all conversions, even if they only have user-provided data and don’t have a GCLID.

Send additional signals:

Capture and import session attributes by using our JavaScript helper function to generate an encoded token (setting session_attributes_encoded), or by capturing the sub-fields individually as key-value pairs (setting session_attributes_key_value_pairs). We recommend using the JavaScript helper function to provide an encoded token; use of key-value pairs is available for users who cannot generate an encoded token in the browser. User's IP address is also available as a new field, though reporting and bidding benefits will become available in the future.
Make sure you provide users with clear and comprehensive information about the data you collect on your sites, apps, and other properties and get consent where required by law or any applicable Google policies.

Adopt Braid (gbraid & wbraid):

Capture and import these URL parameters for privacy-safe conversion reporting when GCLID and user-provided data are unavailable.
Note: We recently announced that gclid and gbraid can be imported together for a single conversion starting on Oct. 3, 2025.

Implement order ID:

Set the order_id field with a unique identifier. This helps reference conversions when adjustments or retractions are needed.

Provide conversion environment:

Set the conversion_environment field to specify whether the conversion source is APP or WEB.
Note: We recently announced that conversion environment data will start informing bidding models for in-app conversions in late September.

Consent and data sharing responsibilities:

Advertisers are responsible for ensuring they have the right to share all data uploaded to Google. Make sure you set the consent field on all imported conversions.

Reach out to the Google Ads API support channel if you have any questions.

- Ben Karl, on behalf of the Google Ads API Team

Increased flexibility for Google Ads API conversion imports

2025 m. liepos 22 d., antradienis

Starting on October 3, 2025, you will be able to set both the gclid and gbraid fields on your ClickConversion messages when importing them to the Google Ads API, by using the UploadClickConversions method. Previously, setting both of these fields resulted in the following partial failure error:

error_code: FieldError.VALUE_MUST_BE_UNSET

location.field_path_elements.field.field_name: gclid

Once this change is released, this error will no longer be returned. Instead you will see successful import responses.

- Ben Karl, on behalf of the Google Ads API Team

[Update] Add Conversion Environment to Google Ads Conversion Imports

2025 m. birželio 30 d., pirmadienis

The previously announced September 30, 2025 deadline to include the ClickConversion.conversion_environment parameter has been removed. The changes described in this blog post will not be released and no further action is required for this specific update. For more details see our Help Center article. Previously we announced that, starting on June 30, 2025, in-app conversions imported through the Google Ads API must include a value for the ClickConversion.conversion_environment field. The timing and details for this rollout have changed. Now, starting September 30, 2025, we will begin gradually rolling out a change to our bidding models so that they will start using the presence of the ClickConversion.conversion_environment field in imported in-app conversions to ensure accurate attribution for smarter bidding and optimal campaign performance. This means that if you are using the Google Ads API to measure in-app conversions, your campaign performance may degrade if the ClickConversion.conversion_environment field is not set. For developers importing in-app conversions, the following considerations still apply:

In-app conversions are defined as any conversion events that occur within an app, such as purchase, add to cart, or sign up.

Once this bidding model change is launched to a campaign, if you do not include the conversion_environment field when importing conversions, you may observe fewer in-app conversions and worse overall campaign performance.

If you do include conversion_environment data for your imported conversions, it ensures attribution accuracy and campaign effectiveness.

The presence or absence of the conversion_environment parameter does not impact conversion uploads. These conversions will still be consumed and reported, with no error messages.

If you have any questions or need help, see the Google Ads API support page for options.

- Ben Karl, on behalf of the Google Ads API Team

Upcoming Removal of debug_enabled in Google Ads API Offline Conversion Imports

2025 m. birželio 26 d., ketvirtadienis

In v21 of the Google Ads API, the UploadClickConversion method’s debug_enabled setting will be removed. Starting on August 6, 2025, all the previous versions (v18, v19, and v20) will ignore this setting if it’s set as part of a request. As a result of this change, Google Ads API will no longer return ConversionUploadError.CLICK_NOT_FOUND errors, because setting the debug_enabled field to true is the only way to retrieve it. This error code will be removed from the Google Ads API in a future version. Here’s a breakdown of how this change will materialize in each Google Ads API version:

v21:

The debug_enabled field will be removed from the UploadClickConversionsRequest message.
ConversionUploadError.CLICK_NOT_FOUND errors will not be returned.

v18, v19, and v20:

The debug_enabled field will be present on the UploadClickConversionsRequest message, but it will not be functional.
ConversionUploadError.CLICK_NOT_FOUND errors will not be returned.

If your application uses this field or error code, make sure you update your application to handle the new API behavior. If you have any questions or need help, check out the Google Ads API support page for options.

- Ben Karl, on behalf of the Google Ads API Team

Add Conversion Environment to Google Ads Conversion Imports

2025 m. gegužės 27 d., antradienis

Previously we announced that, starting on June 30, 2025, in-app conversions imported through the Google Ads API must include a value for the ClickConversion.conversion_environment field. The timing and details for this rollout have changed. Now, starting September 30, 2025, we will begin gradually rolling out a change to our bidding models so that they will start using the presence of the ClickConversion.conversion_environment field in imported in-app conversions to ensure accurate attribution for smarter bidding and optimal campaign performance. This means that if you are using the Google Ads API to measure in-app conversions, your campaign performance may degrade if the ClickConversion.conversion_environment field is not set. For developers importing in-app conversions, the following considerations still apply:

In-app conversions are defined as any conversion events that occur within an app, such as purchase, add to cart, or sign up.

If you do include conversion_environment data for your imported conversions, it ensures attribution accuracy and campaign effectiveness.

The presence or absence of the conversion_environment parameter does not impact conversion uploads. These conversions will still be consumed and reported, with no error messages.

If you have any questions or need help, see the Google Ads API support page for options.

- Ben Karl, on behalf of the Google Ads API Team

Improvements to conversion adjustment uploads

2024 m. rugpjūčio 12 d., pirmadienis

Starting on September 9, 2024, Google Ads API users will no longer need to wait 24 hours before uploading conversion adjustments - they can be uploaded immediately after the original conversion has been uploaded or recorded by Google tags. This means that you will no longer need to keep track of the 24-hour window before uploading conversion adjustments, and can stop checking for certain error codes and retrying those upload requests. Specifically, the following changes will take effect:

The following error codes will no longer be returned in responses from the UploadConversionAdjustments method, and will no longer be visible in diagnostic reports:

Conversion adjustments that would previously be rejected with these error codes will count towards the pending_count in diagnostics until they’re processed, at which point they’ll be counted towards either the successful_count or failed_count fields. This might take up to 24 hours.

Here is how these changes will affect older Google Ads API versions v15 and v16:

The following error codes will no longer be returned in responses from the UploadConversionAdjustments method, and will no longer be visible in diagnostic reports:

Any conversion that would have triggered these codes will, in diagnostic reports, count towards the total_event_count metric while being processed. Once processing is completed they will be counted towards either the successful_count or failed_count. This might take up to 24 hours.

What do I need to do?

Remove any logic from your application that waits before uploading adjustments, and begin uploading conversion adjustments at any time after the original conversion has been uploaded.

Modify your application logic and business processes so that you are not tracking the two conversion adjustment errors that are being removed.

If you rely on the successful or failed event count metrics, revisit your application logic with the understanding that some uploaded events may, at times, when using v17, be represented as pending.

If you have any questions or need help, see the Google Ads API support page for options.

- Ben Karl, on behalf of the Google Ads API Team

Upcoming changes to conversion action management

2022 m. liepos 11 d., pirmadienis

August 22, 2022include_in_conversions_metricConversionActionFieldError.IMMUTABLE_FIELDWhy is this change happening?conversion goalsprimary_for_goalinclude_in_conversions_metricinclude_in_conversions_metricprimary_for_goalinclude_in_conversions_metricWhat should you do?include_in_conversions_metricsprimary_for_goalconversion_action.include_in_conversions_metricconversion goals guideprimary_for_goalforum

- Josh Radcliff, Google Ads API Team

Live Webinar: Website Conversions & Audience Remarketing

2020 m. gruodžio 1 d., antradienis

Website Conversions & Audience Remarketing with the Google Ads APIMark your calendarPrerequisitesAPI Overview documentationGoogle Ads API Overview workshopthis postAgenda

What conversion actions are

How to create and utilize conversion actions

How remarketing works in the Google Ads API

How to define different audience types

How to measure audience performance

Remindersadd the event to your calendarYouTube event pageforum

- Devin Chasanoff, on behalf of the Google Ads API Team

Automatic opt-in for cross-device conversions in the AdWords API "Conversions" column

2016 m. liepos 20 d., trečiadienis

The v201601 release of the AdWords API included a new optimizeOnEstimatedConversions attribute of Customer.conversionTrackingSettings that allowed you to opt-in to including cross-device conversions in the Conversions column. With this option set to true, AdWords includes cross-device conversions when optimizing for conversions in an automated bid strategy.

What's changing

Starting on August 16, 2016, new AdWords accounts will automatically have optimizeOnEstimatedConversions set to true.
During September, 2016, the optimizeOnEstimatedConversions setting will be changed to true on all existing AdWords accounts to give you the most complete view of performance possible.
Starting on September 6, 2016, the optimizeOnEstimatedConversions field in the AdWords API will become read-only. If your CustomerService mutate request attempts to modify this field by sending a value other than the current value, the request will fail with RequestError.INVALID_INPUT.

For more information, check out the recent Inside AdWords blog post on cross-device conversions.

What you should do
Prior to September 6, 2016, ensure that your CustomerService mutate requests do not attempt to modify the value of optimizeOnEstimatedConversions. You can also migrate your accounts before the migration by setting optimizeOnEstimatedConversions to true.

If you have any questions, please post on the forum or the Ads Developers Plus Page.

- Josh Radcliff, AdWords API Team

Changes to validation for AdWords API iTunes AppConversions

2015 m. lapkričio 3 d., antradienis

What’s new?

The validation for AppConversions will become stricter starting on November 9, 2015. If you’re using AppConversions in v201509 or v201506 with AppPlatform: ITUNES, you’ll need to make sure that you’re using the correct AppConversionType.

What was the old behavior?

When v201509 was first released, the API would not throw an error if the incorrect value was sent in a request for an iTunes AppConversion. The API automatically converted to the correct AppConversionType. For example, if the value DOWNLOAD was passed into v201509 for an iTunes AppConversion, then that value would automatically be converted to FIRST_OPEN.

What is the new behavior?

In v201509, AppConversionType DOWNLOAD changed to FIRST_OPEN for iTunes apps. Here’s what you will need to do:

For v201506 or earlier, you must pass in AppConversionType DOWNLOAD rather than FIRST_OPEN.
For v201509 or later, you must pass in FIRST_OPEN instead of DOWNLOAD.

Passing in the incorrect value will result in the error DOMAIN_EXCEPTION from the API starting on November 9.

Note: This only impacts iTunes conversions. There will be no changes to the validation for AppConversions with an AppPlatform of ANDROID.

Where can I learn more?

For more information on mobile apps and conversions, check out these guides:

Questions? Visit us on the AdWords API Forum or our Google+ page.

Nadine Sundquist, AdWords API Team

Change to the default conversion optimizer mode for new AdWords Accounts

2014 m. rugsėjo 18 d., ketvirtadienis

As announced in February, flexible conversion counting in AdWords now lets you decide how you want to count conversions for each of your accounts. As a follow up to this new feature, when new AdWords accounts are created through the UI or the API after October 1st, 2014, the default conversionOptimizerMode will be MANY_PER_CLICK instead of ONE_PER_CLICK. In addition, we'll change the conversionOptimizerMode to MANY_PER_CLICK on any existing account that is not using bidding strategies impacted by conversions.

Action required
Since the new default of MANY_PER_CLICK lets your conversion-based bidding strategies take full advantage of flexible conversion counting, we recommend keeping the default setting on new accounts. However, if you still want to use ONE_PER_CLICK for new accounts created via ManagedCustomerService, then add a second step in your account creation process that issues a CustomerService.mutate call that sets the conversionOptimizerMode on the Customer.

In addition, if you decide to utilize one of the conversion-based bidding strategies, you'll want to make sure that the conversionOptimizerMode is set to the value you'd prefer. The conversion-based bidding strategies affected by conversionOptimizerMode are:

Additional information
If you'd like to learn more about conversion tracking in AdWords, check out the Help Center article on counting conversions. In addition, the remarketing examples folder in each client library contains an AddConversionTracker example that shows how to create an AdWordsConversionTracker via the API.

Still have questions? Feel free to visit us on the AdWords API Forum or our Google+ page.

- Josh Radcliff, AdWords API Team

AdWords API - Using CONVERSION DURATION THRESHOLD feed placeholder will throw errors

2014 m. birželio 30 d., pirmadienis

The CONVERSION DURATION THRESHOLD placeholder was deprecated on April 28th, 2014. Starting July 21st, 2014, using this placeholder with the FeedMappingService will result in a FeedMappingError.INVALID_PLACEHOLDER_FIELD error for all AdWords API versions.

See this post for details on how to set your conversion duration going forward with the CONVERSION TYPE ID placeholder instead.

If you have any questions about this upcoming change or anything else related to the AdWords API, please contact us on the AdWords API forum or via the Google Ads Developers Google+ page.

- Ray Tsang, AdWords API Team

Reminder: AdWords API is sunsetting CONVERSION DURATION THRESHOLD feed placeholder

2014 m. balandžio 25 d., penktadienis

This is a reminder that the CONVERSION DURATION THRESHOLD placeholder is sunsetting starting on April 28th, 2014.

Starting on the sunset date, AdWords accounts will be migrated to use the new CONVERSION TYPE ID placeholder for a four-week time period. During this period, some AdWords accounts that you access via the AdWords API may be migrated, and some may not. Read on to find out how to determine if a feed has been migrated or not. Migration of all AdWords accounts is scheduled to complete by end of May, 2014.

How will an existing conversion duration threshold be migrated?

If you used CONVERSION DURATION THRESHOLD in a Feed Mapping prior to the sunset date, then we will automatically migrate those values after the sunset date - and they will be accessible via the AdWords API v201402 as follows:

New AdCallMetricsConversion will be automatically created for you with the existing conversion duration threshold.

Note: If you have 3 feed items with call duration threshold, where two of them are set to 120 seconds, and one of them are set to 30 seconds, then only two AdCallMetricsConversion will be created - one with AdCallMetricsConversion.phoneCallDuration set to 120 seconds, and another one set to 30 seconds.
Feed attributes using CONVERSION DURATION THRESHOLD will remain, setting and reading those values will not produce errors. However, any associated feed attribute values will not be honored.
A new feed attribute will be automatically created in your existing feed, and it will be automatically be mapped to the new CONVERSION TYPE ID placeholder type.
The new conversion type ID feed attribute will be associated to the newly created AdCallMetricsConversion.

Note that in order to get the name and field attribute ID of the newly created conversion type ID field attribute, you should use the FeedMappingService to determine the feed attribute ID that is associated with the CONVERSION TYPE ID placeholder type.

How do I know if a Feed has been migrated?

If a feed has been migrated, you will be able to see that the Feed has an attribute associated to the CONVERSION TYPE ID placeholder type. You can use the FeedMappingService to determine this.

How do I set conversion duration threshold on a migrated Feed?

If you’d like to continue using conversion duration threshold, then you must upgrade to the AdWords API v201402.

In a migrated feed, the CONVERSION TYPE ID feed item attribute value refers to an AdCallMetricsConversion object by ID. To set the conversion duration threshold, you must update the associated AdCallMetricsConversion object’s phoneCallDuration field. Please note that doing this will impact other feed items that are associated to the same AdCallMetricsConversion object.

Alternatively, you can also associate the CONVERSION TYPE ID feed item attribute value to a different AdCallMetricsConversion:

Re-use an existing AdCallMetricsConversion that has the right phone call duration
Use the ConversionTrackerService to create new AdCallMetricsConversion with the phoneCallDuration field set

In a migrated feed, if you continue to set the attribute value associated with the CONVERSION DURATION THRESHOLD placeholder, then those values will be ignored.

Can I start using the new placeholder before the Feed gets migrated?

Yes. Starting from the sunset date, you will be able to use the new CONVERSION TYPE ID placeholder in your feed. If you are using the placeholder in your feed and set the attribute value to a valid AdCallMetricsConversion ID, then the CONVERSION TYPE ID value will be used, and the CONVERSION DURATION THRESHOLD value will be ignored.

If you choose to do this prior to the automatic migration - don’t worry. The automatic migration process will not overwrite your existing CONVERSION TYPE ID values with CONVERSION DURATION THRESHOLD values.

We are here to help

If you have any questions about this upcoming change or anything else related to the AdWords API, please contact us on the AdWords API forum or via the Google Ads Developers Google+ page.

- Ray Tsang, AdWords API Team

Sunsetting CONVERSION DURATION THRESHOLD feed placeholder in AdWords API

2014 m. kovo 10 d., pirmadienis

Update: The sunset date was changed from April 7th, 2014 to April 28th, 2014. --Stan Grinberg

If you use AdWords call extensions, you know that you can count phone calls as conversions based on the duration of the call (e.g., 60 seconds). When using AdWords API feeds, this duration threshold is specified as the CONVERSION DURATION THRESHOLD placeholder. This placeholder is sunsetting on April 7th, 2014. You will not receive errors if you continue to read and set values associated with this placeholder. However, these values will not be honored past the sunset date.

How do I set conversion duration threshold in the future?
After the sunset date, if you’d like to continue using conversion duration threshold, then you must upgrade to the AdWords API v201402:

Note: CONVERSION TYPE placeholder is not available for use at the time of this post. We will make a separate announcement when it’s ready.

What will happen to my existing conversion duration threshold values?
If you used CONVERSION DURATION THRESHOLD in a Feed Mapping prior to the sunset date, then we will automatically migrate those values after the sunset date - and they will be accessible via the AdWords API v201402 as follows:

New AdCallMetricsConversion will be automatically created for you with the existing conversion duration threshold.

Note: If you have 3 feed items with call duration threshold, where two of them are set to 120 seconds, and one of them are set to 30 seconds, then only two AdCallMetricsConversion will be created - one with AdCallMetricsConversion.phoneCallDuration set to 120 seconds, and another one set to 30 seconds.
Feed attributes using CONVERSION DURATION THRESHOLD will remain, setting and reading those values will not throw errors. However, any associated feed attribute values will not be honored.
A new feed attribute will be automatically created in your existing feed, and it will be automatically be mapped to the new CONVERSION TYPE placeholder type
The new conversion type feed attribute will be associated to the newly created AdCallMetricsConversion

Note that in order to get the name and field attribute ID of the newly created conversion type field attribute, you should use the FeedMappingService to determine the feed attribute ID that is associated with the CONVERSION TYPE placeholder type.

If you have any questions about this upcoming change or anything else related to the AdWords API, please contact us on the AdWords API forum or via the Google Ads Developers Google+ page.

- Ray Tsang, AdWords API Team

Important updates for flexible conversion counting options in v201402 of AdWords API

2014 m. kovo 6 d., ketvirtadienis

We recently announced a new flexible conversion counting option feature in AdWords that may affect AdWords API v201309 users. There are a couple of additional changes in the AdWords API v201402 that we want to bring to your attention so you can take full advantage of this offering:

Record conversion values in conversion report columns based on the flexible conversion counting option
Retrieve and set flexible conversion counting options in the ConversionTracker
Adopt new conversion-related column names in the reports

Flexible conversion counting option

Since February 25th, 2014, AdWords users have been able to change the conversion counting option between All Conversions and Unique Conversions. The conversion counting option is defaulted to All Conversions - when left as the default option, your conversion related values in the reports will not change.

If the conversion counting option is changed from All Conversions to Unique Conversions, then the following conversion-related report columns will reflect the counting option selected across all reports:

ConversionsManyPerClick
ConversionRateManyPerClick
CostPerConversionManyPerClick
ValuePerConvManyPerClick
ValuePerConversionManyPerClick
ConversionManyPerClickSignificance
ConversionRateManyPerClickSignificance
CostPerConversionManyPerClickSignificance

Please see the help center article for specific examples of how counting Unique Conversions differs from counting All Conversions.

Retrieve and set flexible conversion counting options

In the AdWords API v201402, you will be able to retrieve and set the flexible conversion counting option. Please review the ConversionTracker API documentation to see the new flexible conversion counting options field named countingType.

New conversion-related column names

Conversion-related columns will have new names in reports. In AdWords API v201402:

The selector field names will remain the same
The display names and XML attribute names will be renamed

If you are downloading XML reports, you will need to update your client application to read the new column names.

Please see the migration guide for a mapping between old and new display names and XML attribute names.

If you have any questions about this upcoming change or anything else related to the AdWords API, please contact us on the AdWords API forum or via the Google Ads Developers Google+ page.

- Ray Tsang, AdWords API Team

Ads Developer Blog

Upcoming Improvements to Offline Conversion Imports

Changes to IP Address and Session Attribute Support in the Google Ads API

Bidding enforcement for conversion environment in in-app conversions no longer planned

Streamlined Account-Default CustomerConversionGoal Behavior in Google Ads

Introducing improved diagnostics for enhanced conversions for leads imports

Maximize the performance of your Google Ads conversion data

Increased flexibility for Google Ads API conversion imports

[Update] Add Conversion Environment to Google Ads Conversion Imports

Upcoming Removal of debug_enabled in Google Ads API Offline Conversion Imports

Add Conversion Environment to Google Ads Conversion Imports

Improvements to conversion adjustment uploads

Upcoming changes to conversion action management

Live Webinar: Website Conversions & Audience Remarketing

Automatic opt-in for cross-device conversions in the AdWords API "Conversions" column

Changes to validation for AdWords API iTunes AppConversions

Change to the default conversion optimizer mode for new AdWords Accounts

AdWords API - Using CONVERSION DURATION THRESHOLD feed placeholder will throw errors

Reminder: AdWords API is sunsetting CONVERSION DURATION THRESHOLD feed placeholder

Sunsetting CONVERSION DURATION THRESHOLD feed placeholder in AdWords API

Important updates for flexible conversion counting options in v201402 of AdWords API

Etiketės

Archive