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
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,8 @@ id: 54521fd525e721e32a72ee92
14
14
With Segment, you can use your events to fire a Google Ads conversion pixel from your website **in client-side JavaScript.**
15
15
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.
16
16
17
-
> info ""
18
-
> Consent Mode: Segment is currently building Consent Mode functionally for all affected Google destinations. We expect this functionally to be available by March 1, 2024.
17
+
> info "Consent Mode"
18
+
> Segment is currently building Consent Mode for all affected Google destinations. This will be available before March 6, 2024.
19
19
20
20
### Configure the Google Ads (Classic) destination
0 commit comments