Skip to content

Commit 973b489

Browse files
authored
Update index.md
1 parent 8f07812 commit 973b489

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/google-ads-classic

1 file changed

+1
-1
lines changed

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ cmode-override: true
1414
> info ""
1515
> Google released a new version of Google Ads that uses [a Global Site Tag (or Gtag)](https://support.google.com/adwords/answer/7548399?hl=en). Segment supports this using a different version of the destination - see the documentation for [Google Ads (Gtag)](/docs/connections/destinations/catalog/google-adwords-new/) for more details.
1616
17-
With Segment, you can use your events to fire a Google Ads conversion pixel from your website **in client-side javascript.**
17+
With Segment, you can use your events to fire a Google Ads conversion pixel from your website **in client-side JavaScript.**
1818
You can also trigger Google Ads (Classic) conversion from your mobile app using the **Server to Server** destination, so you don't need to include the SDK in your app. The server to server connection requires mobile device specific details to forward the events to Google Ads (Classic). Google Ads (Classic) **does not work with any server-side libraries**. Make sure when you're setting up your Google Ads (Classic) conversions that you choose the appropriate tracking method.
1919

2020
### Configure the Google Ads (Classic) destination

0 commit comments

Comments
 (0)