Skip to content

Commit fd4b286

Browse files
Add configuration steps for Google Ads gtag (#4553)
* Add configuration steps for Google Ads gtag * Fix typo in configuration steps
1 parent 195b9d3 commit fd4b286

File tree

1 file changed

+9
-0
lines changed
  • src/connections/destinations/catalog/google-ads-gtag

1 file changed

+9
-0
lines changed

src/connections/destinations/catalog/google-ads-gtag/index.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,15 @@ The [Google global site tag (gtag.js)](https://support.google.com/google-ads/ans
1919

2020
You can use this destination to map your `.page()` calls to **Page Load Conversions** or `.track()` calls to **Click Conversions**. Currently this is only supported on the browser.
2121

22+
### Configure the Google Ads (Gtag) destination
23+
24+
1. From the Segment Destinations Catalog find and select Google Ads (Gtag).
25+
2. Click **Configure Google Ads (Gtag)**.
26+
3. Select the source you will use to send data to Google Ads (Gtag).
27+
4. Provide a meaningful name to this instance of the destination.
28+
5. On the destination Settings tab, enter the **Conversion ID** from your Google Ads (Gtag) account.
29+
6. Select the 'Click Conversion' setting. Enter the name of the event as it appears in the [`track`](/docs/connections/spec/track) call and map it to your Google Ads (Gtag) conversion label.
30+
2231
## Page
2332

2433
If you want to map all your unnamed `.page()` calls to a default Page Load Conversion, you can enter the Conversion ID in **Settings > Default Page Conversion**. However, if you created specific Page Load Conversions in Google Ads that you'd like to map your named `.page()` calls in Segment, you can map the events in **Settings > Page Load Conversions**.

0 commit comments

Comments
 (0)