Skip to content

Commit 9656d19

Browse files
authored
Merge pull request #2484 from segmentio/gec-faq-add
Add another FAQ to GEC docs
2 parents 6f4848a + 2889035 commit 9656d19

File tree

1 file changed

+11
-8
lines changed
  • src/connections/destinations/catalog/actions-google-enhanced-conversions

1 file changed

+11
-8
lines changed

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

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -26,13 +26,13 @@ The Google Enhanced Conversions destination enables you to improve the accuracy
2626
2. Search for “Google Enhanced Conversions” in the Destinations Catalog, and select the destination.
2727
3. Click **Configure Google Enhanced Conversions** in the top-right corner of the screen.
2828
4. Select the source that will send data to Google Enhanced Conversions and follow the steps to name your destination.
29-
5. On the **Settings** tab, enter the Conversion ID and click **Save**. Find the Conversion ID 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"}. When you log in to Google Ads, enable [Expert Mode](https://support.google.com/google-ads/answer/9520605?hl=en){:target="_blank"}. You'll follow these same instructions to get the Conversion label, which you'll need when you set up your first Mapping, below.
29+
5. On the **Settings** tab, enter the Conversion ID and click **Save**. Find the Conversion ID 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"}. When you log in to Google Ads, enable [Expert Mode](https://support.google.com/google-ads/answer/9520605?hl=en){:target="_blank"}. You'll follow these same instructions to get the Conversion Label, which you'll need when you set up your first Mapping, below.
3030
6. On the **Settings** tab, authenticate with Google using OAuth. Click **Connect to Google Enhanced Conversions**. Follow the prompts to authenticate using OAuth, with a Google login that is a member of the Google Ads account with Enhanced Conversions enabled.
3131
7. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
3232

3333

3434
{% capture conv_label %}
35-
#### Find the Conversions label
35+
#### Find the Conversions Label
3636
Enter the Conversion Label. Find the Conversion Label using the instructions in the article [Google Ads conversions](https://support.google.com/tagmanager/answer/6105160?hl=en){:target="_blank"}.
3737
{% endcapture %}
3838

@@ -75,17 +75,20 @@ To test your mapping:
7575

7676
{% include components/actions-fields.html content1=conv_label section1="postConversion" content2=test_mapping section2="postConversion" %}
7777

78-
## Troubleshooting
79-
Follow the steps below if you have issues with Access Tokens or Conversion tracking.
78+
## FAQ & Troubleshooting
79+
80+
### Conversion Tracking with Gtag
81+
82+
To use Google Enhanced Conversions, you must record conversions using the standard Google Ads Conversion tag (Gtag). After a conversion is recorded, you can send hashed first-party data through Segment’s Google Enhanced Conversions destination for up to 24 hours after the conversion. 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.
83+
84+
Conversions tracked by other means, such as importing goals from Google Analytics, are not eligible for Google Enhanced Conversions.
8085

8186
### Refreshing Access Tokens
8287

8388
When you use OAuth to authenticate into the Google Enhanced Conversions destination, Segment stores an access token and refresh token. Access tokens for Google Enhanced Conversions expire after one hour. Once expired, Segment receives an error and then uses the refresh token to fetch a new access token. This results in two API requests to Google Enhanced Conversions, one failure and one success.
8489

8590
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 we make to Google Enhanced Conversions.
8691

87-
### Conversion Tracking with Gtag
92+
### Sending App Conversions for Incrementality Studies
8893

89-
To use Google Enhanced Conversions, you must record conversions using the standard Google Ads Conversion tag (Gtag). After a conversion is recorded, you can send hashed first-party data through Segment’s Google Enhanced Conversions destination for up to 24 hours after the conversion. 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.
90-
91-
Conversions tracked by other means, such as importing goals from Google Analytics, are not eligible for Google Enhanced Conversions.
94+
The Google Enhanced Conversions API does not offer standard reporting for app conversions at this point. 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, 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)