Skip to content

Commit 85aa50e

Browse files
authored
Merge pull request #5919 from segmentio/rvadera12-patch-1
Update Google Enhanced Conversions Docs - Legacy API Sunset
2 parents 056286e + cddc7f5 commit 85aa50e

File tree

1 file changed

+44
-19
lines changed
  • src/connections/destinations/catalog/actions-google-enhanced-conversions

1 file changed

+44
-19
lines changed

src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md

Lines changed: 44 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -18,30 +18,58 @@ The Google Ads Conversions destination enables you to upload offline conversions
1818
7. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
1919

2020
> warning "Upload Enhanced Conversion (Legacy) Action Deprecation"
21-
> Google plans to sunset the legacy API, so Segment will migrate your instance to the new API in the beginning of 2024. No action is required at this time, and Segment will reach out to communicate next steps prior to the migration.
21+
> Google plans to sunset the legacy API, leading to the discontinuation of the Upload Enhanced Conversions (Legacy) Action. New subscriptions using the sunsetting Upload Enhanced Conversion (Legacy) Action are **no longer possible**, but existing subscriptions will remain functional.
2222
>
23-
> With this change, the Upload Enhanced Conversions (Legacy) Action **will no longer be available**. Please use the "Upload Click Conversion", "Upload Call Conversion", and "Upload Conversion Adjustment" actions, which sends data to the new Google Ads API.
23+
> Segment recommends users to transition to the "Upload Click Conversion," "Upload Call Conversion," and "Upload Conversion Adjustment" actions, to send data through the new Google Ads API.
24+
>
25+
> [Use these steps](#migrate-your-upload-enhanced-conversion-legacy-action) to migrate your Upload Enhanced Conversion (Legacy) Action subscriptions.
2426
25-
> info ""
26-
> When you use the "Upload Enhanced Conversion (Legacy)" action, Segment sends data to the legacy Enhanced Conversions API. To authenticate into the legacy API and send enhancement data, Segment needs your Conversion ID and Conversion Label.
27-
>
28-
> The Conversion ID is a global setting because it's an account-level ID that's the same for all conversion actions in your Google Ads account.
29-
>
30-
> The Conversion Label is unique to each conversion action and is therefore configured per mapping. Find the Conversion ID and Conversion Label in your Google Ads account using the instructions in the article [Google Ads conversions](https://support.google.com/tagmanager/answer/6105160?hl=en){:target="_blank"}.
27+
{% include components/actions-fields.html settings="true"%}
3128

32-
> info ""
33-
> When you use the "Upload Click Conversion", "Upload Call Conversion", and "Upload Conversion Adjustment" actions, Segment sends data to the new Google Ads API.
34-
>
35-
> To authenticate into the Google Ads API, Segment needs your Customer ID and Conversion Action ID. The Customer ID is a global setting because it's an account-level ID that's the same for all conversion actions in your Google Ads account. The Conversion Action ID is unique to each conversion action and is configured per mapping. The Conversion Action ID can only be found in the browser URL of your given conversion action under the `ctId` parameter. For example, if the URL is `https://ads.google.com/aw/conversions/detail?ocid=00000000&ctId=576882000`, your Conversion Action ID is `576882000`.
29+
## Migrate your Upload Enhanced Conversion (Legacy) Action
30+
31+
To migrate from Upload Enhanced Conversion (Legacy) Action to the Upload Conversion Adjustment Action:
32+
33+
1. Fill out your Conversion ID and Customer ID settings.
34+
2. Fill out the required fields for the Upload Conversion Adjustment Action:
35+
- Conversion Action ID
36+
- Adjustment Type
37+
3. Replicate as many fields from your original mapping as possible using the table below for reference. Look at the [Upload Conversion Adjustment Action](/docs/connections/destinations/catalog/actions-google-enhanced-conversions/#upload-conversion-adjustment) for more details about each field.
38+
39+
| Upload Enhanced Conversion (Legacy)| Upload Conversion Adjustment | Default Mapping |
40+
|------------------------|----------------------------|--------------------------------------|
41+
| conversion_label | NOT AVAILABLE | `$.properties.conversion_label` |
42+
| email | email_address | `$.properties.email or $.traits.email or $.context.traits.email` |
43+
| transaction_id | order_id | `$.properties.orderId` |
44+
| user_agent | user_agent | `$.context.userAgent` |
45+
| conversion_time | conversion_timestamp | `$.timestamp ` |
46+
| value | NOT AVAILABLE |` $.properties.total ` |
47+
| currency_code | NOT AVAILABLE | `$.properties.currency ` |
48+
| is_app_incrementality | NOT AVAILABLE |` false ` |
49+
| pcc_game | NOT AVAILABLE | `false ` |
50+
| phone_number | phone_number | `$.properties.phone or $.traits.phone` |
51+
| first_name | first_name | `$.properties.firstName or $.traits.firstName` |
52+
| last_name | last_name | `$.properties.lastName or $.traits.lastName` |
53+
| street_address | street_address | `$.properties.address.street or $.traits.address.street` |
54+
| city | city | `$.properties.address.city or ​​$.traits.address.city` |
55+
| region | state | `$.properties.address.state or $.traits.address.state` |
56+
| post_code | postal_code | `$.properties.address.postalCode or $.traits.address.postalCode` |
57+
| country | country | `$.properties.address.country or $.traits.address.countr`y |
58+
| | gclid | Default Not Available |
59+
| | adjustment_timestamp | Default Not Available |
60+
| | restatement_value | Default Not Available |
61+
| | restatement_currency_code | Default Not Available |
3662

3763

38-
> info ""
39-
> Conversion ID, Conversion Label, Customer ID, and Conversion Action ID should always be different values.
40-
41-
{% include components/actions-fields.html settings="true"%}
4264

4365
## FAQ and troubleshooting
4466

67+
### Conversion ID, Customer ID, and Conversion Action ID should always be different values
68+
69+
Conversion ID and Customer ID are global settings because it’s an account-level ID that’s the same for all conversion actions in your Google Ads account.
70+
71+
The Conversion Action ID is unique to each conversion action and is configured per mapping. The Conversion Action ID can only be found in the browser URL of your given conversion action under the `ctId` parameter. For example, if the URL is `https://ads.google.com/aw/conversions/detail?ocid=00000000&ctId=576882000`, your Conversion Action ID is `576882000`.
72+
4573
### Enhanced conversions
4674

4775
[Enhanced conversions](https://support.google.com/google-ads/answer/11062876){:target="_blank"} is a feature that can improve the accuracy of your conversion measurement and unlock more powerful bidding. It supplements your existing conversion tags by sending hashed, first-party conversion data from your website to Google in a privacy safe way. You can use the "Upload Conversion Adjustment" action to send enhancements to the Google Ads API. In order to send enhanced conversions, you must record first conversions using the standard Google Ads Conversion tag (Gtag). Segment offers a [Google Ads (Gtag) destination](/docs/connections/destinations/catalog/google-ads-gtag/) so you can use your existing Segment implementation to activate Gtag. Enhancements can be sent to web conversion actions that have **Turn on enhanced conversions** by API enabled.
@@ -61,6 +89,3 @@ When you use OAuth to authenticate into the Google Ads Conversions destination,
6189

6290
Because of the duplicate API requests, you may see a warning in Google for unprocessed conversions due to incorrect or missing OAuth credentials. This warning is expected and does not indicate data loss. Google has confirmed that conversions are being processed, and OAuth retry behavior will not cause any issues for your web conversions. Whenever possible, Segment caches access tokens to reduce the total number of requests made to Google Ads Conversions.
6391

64-
### Sending app conversions for incrementality studies (legacy enhanced conversions API only)
65-
66-
The legacy Enhanced Conversions API does not offer standard reporting for app conversions. As such, Google requires that you set up a new web conversion action specifically for the purposes of app incrementality studies. To send app conversions in your incrementality study, use the "Upload Enhanced Conversion (Legacy)" action. Be sure to input the Conversion Label associated with your incrementality study **and** set the App Conversion for Incrementality Study field to `true`. You should create separate web conversion actions in Google Ads for each app event you want to send data for.

0 commit comments

Comments
 (0)