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-31Lines changed: 1 addition & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ With Segment, you can use your events to fire a Google Ads conversion pixel from
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
17
> info "Consent mode"
18
-
> Google enforced consent on March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/google-ads-classic/#consent-mode) and how to set it up.
18
+
> Google enforced consent on March 6, 2024 for European Economic Area (EEA) users. Google Ads Classic won’t be updated to support Consent Mode due to its use of a Google legacy tag that, while still functional, is not actively maintained by Google and lacks support for privacy-durable solutions, including consent management. Segment recommends you to migrate to [Google Ads (Gtag) destination](/docs/connections/destinations/catalog/google-adwords-new/) for web tracking and to the [Google Firebase destination](/docs/connections/destinations/catalog/firebase/) for mobile tracking as soon as possible.
19
19
20
20
### Configure the Google Ads (Classic) destination
21
21
@@ -26,36 +26,6 @@ You can also trigger Google Ads (Classic) conversion from your mobile app using
26
26
5. On the destination Settings tab, enter the **Conversion ID** from your Google Ads (Classic) account.
27
27
6. Select the Event Mappings 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 (Classic) conversion's `google_conversion_label`.
28
28
29
-
## Consent mode
30
-
[Consent mode](https://support.google.com/analytics/answer/9976101?hl=en){:target="_blank"} is a feature provided by Google in the context of its products, particularly the Gtag library and Google Analytics. As of March 6, 2024, Google announced that consent mode must function for European Economic Area (EEA) users, otherwise data from EEA users won't process.
31
-
32
-
Consent mode in the Gtag library and Google Analytics is designed to help website owners comply with privacy regulations, such as the General Data Protection Regulation (GDPR) in the European Union. It allows website owners to adjust how these tools use and collect data based on user consent.
33
-
34
-
With consent mode, you can configure your website to dynamically adjust the tracking behavior of the Gtag library and Google Analytics based on the user's consent status. If a user provides consent to data processing, both the Gtag library and Google Analytics can collect and use that data for analysis. If a user doesn't provide consent, both tools limit data collection to essential functions, helping businesses respect user privacy preferences.
35
-
36
-
Consent mode may involve updates to your sources outside of Segment, such as incorporating a consent management system for consent functionality.
37
-
38
-
### Consent mode for mobile and server apps
39
-
To set up consent mode for Google Ads Classic mobile and server apps:
40
-
1. Update your app's SDK to a version that supports consent mode v2.
41
-
* Android apps must use [Firebase Android Analytics SDK version 21.5.0 or later](https://firebase.google.com/support/release-notes/android#analytics_v21-5-0){:target="_blank"}.
42
-
* iOS apps must use [Firebase Apple SDK version 10.17.0 or later](https://firebase.google.com/support/release-notes/ios#analytics){:target="_blank"}.
43
-
44
-
2. Set up consent mode for your app if you haven't already set it up.
45
-
* Android: [Set up consent mode for Android apps](https://developers.google.com/tag-platform/security/guides/app-consent?platform=android&consentmode=advanced){:target="_blank"}
46
-
* iOS: [Set up consent mode for iOS apps](https://developers.google.com/tag-platform/security/guides/app-consent?platform=ios&consentmode=advanced){:target="_blank"}
47
-
3. If you already set up consent mode for your app, upgrade it to consent mode v2.
48
-
* Android: [Upgrade to consent mode v2 for Android apps](https://developers.google.com/tag-platform/security/guides/app-consent?platform=android&consentmode=advanced#upgrade-consent-v2){:target="_blank"}
49
-
* iOS: [Upgrade to consent mode v2 for iOS apps](https://developers.google.com/tag-platform/security/guides/app-consent?platform=ios&consentmode=advanced#upgrade-consent-v2){:target="_blank"}
50
-
51
-
### Consent mode for web
52
-
To set up consent mode for Google Ads Classic Web, choose from these options:
53
-
* If you don't have a consent banner: [Set up a consent banner](https://support.google.com/tagmanager/answer/9976101){:target="_blank"} on your website. If you choose a banner provided by a Google-certified partner, make sure you enable consent mode in the banner settings. Learn how to [set up a consent banner](https://support.google.com/tagmanager/answer/9976101#cmp1){:target="_blank"}.
54
-
* If you have a consent banner but don't use consent mode: If you use a Google-certified consent management platform (CMP), enable consent mode in your banner settings. Learn more about [Google-certified consent management platforms](https://cmppartnerprogram.withgoogle.com/){:target="_blank"}.
55
-
* If you maintain your own consent banner but don't use consent mode: Implement consent mode for your website. Learn how to [implement consent mode for a website with your own consent solution](https://developers.google.com/tag-platform/security/guides/consent){:target="_blank"}.
56
-
* If you use a Google-certified consent management platform (CMP), your CMP provider automatically updates to the newest version of consent mode. Learn more about [Google-certified consent management platforms](https://cmppartnerprogram.withgoogle.com/){:target="_blank"}.
57
-
* If you maintain your own consent banner, [upgrade to consent mode v2](https://developers.google.com/tag-platform/security/guides/consent#upgrade-consent-v2){:target="_blank"} to collect ad measurement and ads personalization consent signals.
58
-
59
29
## Web
60
30
61
31
This section details the configuration of the Google Ads (Classic) destination with Analytics.js sources.
0 commit comments