Skip to content

Commit 38755bb

Browse files
kdaswanimarkzegarelli
andauthored
Add Troubleshooting section to GEC docs (#2434)
* add Troubleshooting section to GEC docs * style edits Co-authored-by: markzegarelli <[email protected]>
1 parent f58636f commit 38755bb

File tree

2 files changed

+15
-4
lines changed

2 files changed

+15
-4
lines changed

.vscode/yml.code-snippets

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,4 @@
2121
"body":["- name: ${1:name}\r\tdescription: ${2:description}\r\tdefault: ${3}"],
2222
"description": "Yaml settings"
2323
},
24-
"ext_link":{
25-
"prefix": ["{:}"],
26-
"body":["{:target='${1:_blank}'}"]
27-
},
2824
}

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

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,3 +74,18 @@ To test your mapping:
7474
{% endcapture %}
7575

7676
{% include components/actions-fields.html content1=conv_label section1="postConversion" content2=test_mapping section2="postConversion" %}
77+
78+
## Troubleshooting
79+
Follow the steps below if you have issues with Access Tokens or Conversion tracking.
80+
81+
### Refreshing Access Tokens
82+
83+
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.
84+
85+
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.
86+
87+
### Conversion Tracking with Gtag
88+
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.

0 commit comments

Comments
 (0)