Skip to content

Commit 94b0c65

Browse files
stayseesongrchinn1
andauthored
Apply suggestions from code review
Co-authored-by: rchinn-segment <[email protected]>
1 parent 16d11ff commit 94b0c65

File tree

1 file changed

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

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@ id: 54521fd525e721e32a72ee92
1414
With Segment, you can use your events to fire a Google Ads conversion pixel from your website **in client-side JavaScript.**
1515
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.
1616

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.
1919
2020
### Configure the Google Ads (Classic) destination
2121

0 commit comments

Comments
 (0)