You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/google-ads-classic/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ cmode-override: true
14
14
> info ""
15
15
> 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.
16
16
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.**
18
18
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.
19
19
20
20
### Configure the Google Ads (Classic) destination
0 commit comments