diff --git a/src/connections/destinations/catalog/actions-display-video-360/index.md b/src/connections/destinations/catalog/actions-display-video-360/index.md index e54ddf0f5b..ee663fcc1a 100644 --- a/src/connections/destinations/catalog/actions-display-video-360/index.md +++ b/src/connections/destinations/catalog/actions-display-video-360/index.md @@ -24,6 +24,9 @@ Segment's integration with DV360 enables Segment customers to sync audiences cre > info "" > Since the release of `analytics-ios` version 4, Segment no longer collects IDFA automatically. To collect and pass IDFA to your DV360 integration, follow the steps for Ad Tracking and IDFA in the [Analytics-iOS mobile source](/docs/connections/sources/catalog/libraries/mobile/ios#ad-tracking-and-idfa) documentation. +> info "Consent mode" +> Google is enforcing consent starting March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/actions-display-video-360/#consent-mode) and how to set it up. + ## Details > info "" @@ -137,6 +140,15 @@ Segment is disabling all existing Personas Display and Video 360 destinations. Y image +## Consent mode +[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. + +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. + +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. + +Segment automatically sends consent as `TRUE` for this destination. Segment uses the [bulk-uploader workflow](https://developers.google.com/authorized-buyers/rtb/bulk-uploader#workflow){:target="_blank"} which requires consented data. Ensure all audiences and journeys are connected to consented audiences. + ## FAQ ### What is Segment's relationship with Google DV360 and is the data that Segment sends considered to be First or Third party? diff --git a/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md b/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md index 343f6da4a6..e303885852 100644 --- a/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md +++ b/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md @@ -15,9 +15,8 @@ versions: When you have Segment installed, you can use your existing tracking implementation to fulfill your data collection needs with Google Analytics 4. When you enable the Google Analytics 4 Web destination, Segment loads the [gtag.js library](https://support.google.com/analytics/answer/9310895?hl=en#zippy=%2Cin-this-article){:target="_blank"} for you. To avoid duplicate data, remove the native gtag.js script from your page. -> info "Consent Mode" -> Segment is currently building Consent Mode for all affected Google destinations. This will be available before March 6, 2024. - +> info "Consent mode" +> Google is enforcing consent starting March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/actions-google-analytics-4-web/#consent-mode) and how to set it up. ## Getting started @@ -65,7 +64,63 @@ The automatically collected and enhanced measurement events include parameters b ### Conversion events -Some of Segment's prebuilt [Available Actions](https://segment-docs.netlify.app/docs/connections/destinations/catalog/actions-google-analytics-4-web/#available-actions) which map to Google's recommended events are automatically marked as a conversion in your Analytics dashboard. For example, when you add a "Order Completed" event, it will show up in your Analytics dashboard as "purchase" with the **Mark as conversion** toggle toggled on by default. However, for other events, such as "Add to Cart", you will need to manually toggle the **Mark as conversion** setting on in your Analytics dashboard. If you don't mark the event as a conversion, it will not show up as a conversion in your built-in reports. You can read more [about conversion events](https://support.google.com/analytics/answer/9267568?sjid=1275909514202748631-NA){:target="_blank"} in Google's docs. +Some of Segment's prebuilt [Available Actions](/docs/connections/destinations/catalog/actions-google-analytics-4-web/#available-actions) which map to Google's recommended events are automatically marked as a conversion in your Analytics dashboard. For example, when you add a "Order Completed" event, it will show up in your Analytics dashboard as "purchase" with the **Mark as conversion** toggle toggled on by default. However, for other events, such as "Add to Cart", you will need to manually toggle the **Mark as conversion** setting on in your Analytics dashboard. If you don't mark the event as a conversion, it will not show up as a conversion in your built-in reports. You can read more [about conversion events](https://support.google.com/analytics/answer/9267568?sjid=1275909514202748631-NA){:target="_blank"} in Google's docs. + +## Consent mode +[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. + +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. + +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. + +Consent mode may involve updates to your sources outside of Segment, such as incorporating a consent management system for consent functionality. + +See [set up consent mode on websites](https://developers.google.com/tag-platform/security/guides/consent?consentmode=advanced#update_consent_state){:target="_blank"} for more information. + +### Set up consent mode + +To enable consent mode for your Google Analytics 4 Web destination: +1. Navigate to **Connections > Destinations** and select your Google Analytics 4 Web** destination. +2. Go to the **Settings** tab of the destination. +3. Click the toggle on for **Enable Consent Mode**. +4. Set the following fields with these values: + + Field | Value + ----- | ------ + Default Ad Storage Consent State | Granted + Default Analytics Storage Consent State | Granted + Ad User Data Consent State | Granted + Ad Personalization Consent State | Granted + +5. Use your consent management platform to prompt the visitor. Ask the visitor to grant or deny consent for the applicable types. +6. Pass the updated state as properties in the `page()` event after the next page load if you decide to change the consent defaults. For example, + + ``` + analytics.page('Consent Update', { + 'Ads Storage Consent State': 'false', + 'Analytics Storage Consent State': 'false' + }); + ``` +7. As soon as the page loads and the set configuration fires to the Google Analytics SDK, Segment issues a consent mode update command. Map the properties you defined to collect consent state changes to the Set Configurations Fields mapping. You can choose to do this from 1 of 2 options in steps 4 and 5. + 1. Navigate to **Connections > Destinations** and select your Google Analytics 4 Web destination. + 2. Go to the **mappings** tab of the destination. + 3. Select the mapping you want to edit.' + 4. *(Option 1)* Under the **Select mappings** section, select `Granted` for these fields: + * Ads Storage Consent State + * Analytics Storage Consent State + * Ad User Data Consent State + * Ad Personalization Consent State + You can manually select `Granted` or `Denied` from the dropdown menu for Advanced consent mode settings, and type in `granted` or `denied` for basic consent mode settings. + 5. *(Option 2)* Under the **Select mappings** section, create an event variable to directly grab the value from the payload (for example, `properties.adStorageConsentState`). Ensure it translates to `granted` or `denied`. You can use an insert function to translate to `granted` or `denied`. Use the replace function if it's a string. Do this for these fields: + * Ads Storage Consent State + * Analytics Storage Consent State + * Ad User Data Consent State + * Ad Personalization Consent State + +When these properties are available, they send to the `update` command. + +If you have any questions setting up consent mode, reach out to [friends@segment.com](mailto:friends@segment.com). + {% include components/actions-fields.html settings="true"%} diff --git a/src/connections/destinations/catalog/actions-google-analytics-4/index.md b/src/connections/destinations/catalog/actions-google-analytics-4/index.md index 86936680d5..25627161a0 100644 --- a/src/connections/destinations/catalog/actions-google-analytics-4/index.md +++ b/src/connections/destinations/catalog/actions-google-analytics-4/index.md @@ -18,6 +18,9 @@ When you have Segment installed, you can use your existing tracking implementati > warning "" > Google Analytics 4 doesn't officially support a pure server-to-server integration. However, Segment monitors the capabilities of the Measurement Protocol API and updates the cloud integration accordingly to achieve a reasonable level of reporting for mutual customers. For full functionality, please see the [Google Analytics 4 Web destination](/docs/connections/destinations/catalog/actions-google-analytics-4-web/). +> info "Consent mode" +> Google is enforcing consent starting March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/actions-google-analytics-4/#consent-mode) and how to set it up. + ## Benefits of Google Analytics 4 Cloud The Google Analytics 4 Cloud destination provides the following benefits: @@ -40,8 +43,44 @@ To add the Google Analytics 4 Cloud destination: 5. On the **Settings** tab, enter in the [Measurement ID](https://support.google.com/analytics/answer/9539598){:target='_blank'} for web streams or the [Firebase App ID](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference?client_type=firebase#payload_query_parameters){:target='_blank'} for mobile streams. Next, enter in the API Secret associated with your GA4 stream and click **Save**. To create a new API Secret, navigate in the Google Analytics UI to Admin > Data Streams > choose your stream > Measurement Protocol > Create. 6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings). + {% include components/actions-fields.html %} +## Consent mode +[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. + +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. + +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. + +Consent mode may involve updates to your sources outside of Segment, such as incorporating a consent management system for consent functionality. + +### Set up consent mode +To enable consent mode for your Google Analytics 4 Cloud destination, you must update the **Ad User Data Consent State** and **Ad Personalization Consent State** for all mappings you want to send with consent. Consent mode supports all actions with Google Analytics 4 Cloud. You can choose from 2 options to enable consent mode for your Google Analytics 4 Cloud destination. + +* **Option 1** + + To enable consent mode for Google Analytics 4 Cloud destination: + 1. Navigate to **Connections > Destinations** and select your Google Analytics 4 Cloud destination. + 2. Go to the **Mappings** tab of the destination. + 3. Select the mapping you want to edit. + 4. Under the **Select mappings** section, find **Ad User Data Consent State**. + 5. Select `GRANTED` in the dropdown that corresponds to **Ad User Data Consent State**. + 6. Select `GRANTED` in the dropdown that corresponds to **Ad Personalization Consent State**. + +* **Option 2** + + Create an event variable to directly grab the value from the payload. To do this: + 1. Navigate to **Connections > Destinations** and select your Google Analytics 4 Cloud destination. + 2. Go to the **Mappings** tab of the destination. + 3. Select the mapping you want to edit. + 4. Under the **Select mappings** section, find **Ad User Data Consent State**. + 5. Select the **Event Variables** tab and create an event variable to directly grab the value from the payload. Ensure it translates to `GRANTED` or `DENIED`. You can use an insert function to translate to `GRANTED`or `DENIED` if your consent values are booleans. You can use the replace function if it's a string. + 6. Repeat step 5 for **Ad Personalization Consent State**. + + +If you have any questions setting up consent mode, reach out to [friends@segment.com](mailto:friends@segment.com). + ## Universal Analytics and Google Analytics 4 ### Differences between Universal Analytics and Google Analytics 4 diff --git a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md index 18a3b90ce1..73b02df69f 100644 --- a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md +++ b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md @@ -8,6 +8,9 @@ id: 60ae8b97dcb6cc52d5d0d5ab The Google Ads Conversions destination enables you to upload offline conversions and conversion adjustments to Google Ads in a privacy safe way. With this server-side destination, you can upload conversions to the [Google Ads API](https://developers.google.com/google-ads/api/docs/conversions/overview){:target="_blank"} and tie them to a user's online click or phone call. In addition, you can improve the accuracy of your conversion measurement by sending conversion enhancements, restatements, and retractions. +> info "Consent mode" +> Google is enforcing consent starting March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/actions-google-enhanced-conversions/#consent-mode) and how to set it up. + ## Getting started 1. From the Segment web app, click **Catalog**, then click **Destinations**. 2. Search for “Google Ads Conversions” in the Destinations Catalog, and select the destination. @@ -17,9 +20,6 @@ The Google Ads Conversions destination enables you to upload offline conversions 6. On the **Settings** tab, authenticate with Google using OAuth. Click **Connect to Google Ads Conversions**. Follow the prompts to authenticate using OAuth, with a Google account that is a member of your Google Ads account. 7. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings). -> info "Consent Mode" -> Segment is currently building Consent Mode for all affected Google destinations. This will be available before March 6, 2024. - > warning "Upload Enhanced Conversion (Legacy) Action Deprecation" > Google plans to sunset the legacy API, leading to the discontinuation of the Upload Enhanced Conversions (Legacy) Action. New subscriptions using the sunsetting Upload Enhanced Conversion (Legacy) Action are **no longer possible**, but existing subscriptions will remain functional. > @@ -64,6 +64,35 @@ To migrate from Upload Enhanced Conversion (Legacy) Action to the Upload Convers | | restatement_currency_code | Default Not Available | +## Consent mode +[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. + +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. + +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. + +Consent mode may involve updates to your sources outside of Segment, such as incorporating a consent management system for consent functionality. + +### Set up consent mode + +To enable consent mode for your Google Ads Conversions destination, you must update the **Ad User Data Consent State** and **Ad Personalization Consent State** for all of your Upload Call Conversion and Upload Click Conversion actions. You can do this in 1 of 2 ways: + +* **Option 1:** + 1. Navigate to **Connections > Destinations** and select your Google Ads Conversion destination. + 2. Go to the **Mappings** tab of the destination. + 3. Select the mapping you want to edit. + 4. In the **Select mappings** section, select `GRANTED` from the dropdown menu for **Ad User Data Consent State** and **Ad Personalization Consent State**. + +* **Option 2:** + 1. Navigate to **Connections > Destinations** and select your Google Ads Conversion destination. + 2. Go to the **Mappings** tab of the destination. + 3. Select the mapping you want to edit. + 4. In the **Select mappings** section, for **Ad User Data Consent State** and **Ad Personalization Consent State**, select the **Event Variables** tab and create an event variable to directly grab the value from the payload. Ensure it translates to `GRANTED`, `DENIED`, or `UNSPECIFIED`. You can use an insert function to translate to `GRANTED`, `DENIED`, or `UNSPECIFIED` if your consent values are booleans. You can use the replace function if it's a string. + +If you send `DENIED` for any of the two consent states, it results in an error and the data won't send to Google. For more information, see [FAQ about the EU user consent policy for Customer Match upload partners](https://support.google.com/google-ads/answer/14310715?hl=en){:target="_blank"}. + +If you have any questions setting up consent mode, reach out to [friends@segment.com](mailto:friends@segment.com). + ## FAQ and troubleshooting diff --git a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md index 919217c003..b6748a8b50 100644 --- a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md +++ b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md @@ -9,12 +9,8 @@ id: 5a6b50f1c900fa00011858fd The Google Ads Remarketing Lists destination is one of Segment's most popular Engage List destinations. It has a variety of use cases related to exclusion, acquisition (using Similar Audience), remarketing, and more. -> info "Consent Mode" -> Segment is currently building Consent Mode for all affected Google destinations. This will be available before March 6, 2024. - This destination can send audiences created in [Engage](/docs/engage/) to Google Ads as a [Customer List](https://support.google.com/google-ads/answer/6276125){:target="_blank"}. Once you set this destination up, Segment sends an initial user list of users to the [Google Ads API](https://developers.google.com/google-ads/api/docs/remarketing/overview){:target="_blank"}. As users move in and out of the audience, Segment automatically updates the list in Google every hour. This allows you to run advertising campaigns without having manually update the list of users to target in your Google Ads campaigns. - You can send either an email address or mobile device ID (IDFA) from Engage to Google as custom matchers. You can set an email address on the user profile by including `email` as a trait on an [`identify` call](/docs/connections/spec/identify/), as a property on a [`track` call](/docs/connections/spec/track/), or as an [external id](/docs/unify/identity-resolution/externalids/) for the user. If you use Segment’s mobile SDKs to collect events from a mobile app, the user’s IDFA is automatically captured. If you don't use Segment’s mobile SDKs, you can set the user’s IDFA by setting it within `context.device.advertisingId`. You are also required to collect `context.device.type` and `context.device.adTrackingEnabled` on the event payload. Additionally, ensure `android.idfa` and `ios.idfa` are enabled as identifiers in your [Identity Resolution settings](/docs/unify/identity-resolution/identity-resolution-settings/) in Engage. When you send an audience to Google Ads Remarketing Lists, you can choose which custom matcher (email or mobile device ID/IDFA) to match with. If a user has multiple emails or IDFAs on their account as `external_ids`, Engage sends the ID that was most recently added to the user profile to Google Ads. @@ -24,6 +20,9 @@ These audience lists can be used to serve content on Google Search, YouTube, and > info "" > You must have access to Engage as part of your Segment plan to use this destination. [Contact Segment's sales team](https://segment.com/demo/){:target="_blank”} to try this out. +> info "Consent mode" +> Google is enforcing consent starting March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/adwords-remarketing-lists/#consent-mode) and how to set it up. + ## Details - **Supports Engage**: Yes @@ -107,6 +106,29 @@ In Google Ads, go to **Tools & Settings** > **Shared Library** > **Audience mana > info "" > **Note**: Google Ads can take 24+ hours to fully process initial audience uploads before they can be used for a campaign. If the audience is still processing, the list status appears as “Populating”. +## Consent mode +[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. + +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. + +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. + +Consent mode may involve updates to your sources outside of Segment, such as incorporating a consent management system for consent functionality. + +### Set up consent mode + +To enable consent mode for Google Adwords Remarketing Lists destination: +1. Navigate to **Connections > Destinations** and select your Google Ads Remarketing Lists destination. +2. Go to the **Settings** tab of the destination. +3. Under the **Connection Settings** section, select **Ad Personalization**. +4. Select `GRANTED` in the dropdown and click **Save**. +5. Under the **Connection Settings** section, select **Ad User Data**. +6. Select `GRANTED` in the dropdown and click **Save**. + +The consent fields apply universally to all audiences linked to the instance. The consent fields are intended for application across all audiences. If it's not intended for all audiences, you should create a new instance of the destination and associated non-consent audiences with the new instance. For more information, see [FAQ about the EU user consent policy for Customer Match upload partners](https://support.google.com/google-ads/answer/14310715?hl=en){:target="_blank"}. + +If you have any questions setting up consent mode, reach out to [friends@segment.com](mailto:friends@segment.com). + ## Troubleshooting ### Not seeing an audience in Google Ads Audience manager diff --git a/src/connections/destinations/catalog/firebase/index.md b/src/connections/destinations/catalog/firebase/index.md index 313fb314c3..d259f779d9 100644 --- a/src/connections/destinations/catalog/firebase/index.md +++ b/src/connections/destinations/catalog/firebase/index.md @@ -14,6 +14,9 @@ Segment's Firebase destination code is open source and available on GitHub. You - [Kotlin](https://github.com/segment-integrations/analytics-kotlin-firebase){:target="_blank"} - [Swift](https://github.com/segment-integrations/analytics-swift-firebase){:target="_blank"} +> info "Consent mode" +> Google is enforcing consent starting March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/firebase/#consent-mode) and how to set it up. + ## Getting Started on Android To start sending data to Firebase Analytics from your Android project, you'll need to follow a few simple steps: @@ -106,6 +109,27 @@ By default, Segment bundles only `Firebase/Core` which is [Firebase's mobile ana By default, Segment only bundles `Firebase/Core` which is [Firebase's Analytics offering](https://firebase.google.com/docs/analytics/){:target="_blank"}. You can see the other available [Firebase pods and features here](https://firebase.google.com/docs/ios/setup){:target="_blank"}. +## Consent mode +[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. + +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. + +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. + +Consent mode may involve updates to your sources outside of Segment, such as incorporating a consent management system for consent functionality. + +To set up consent mode for Google Firebase: +1. Update your app's SDK to a version that supports consent mode v2. + * Android apps must use F[irebase Android Analytics SDK version 21.5.0 or later](https://firebase.google.com/support/release-notes/android#analytics_v21-5-0){:target="_blank"}. + * iOS apps must use [Firebase Apple SDK version 10.17.0 or later](https://firebase.google.com/support/release-notes/ios#analytics){:target="_blank"}. + +2. Set up consent mode for your app if you haven't already set it up. + * Android: [Set up consent mode for Android apps](https://developers.google.com/tag-platform/security/guides/app-consent?platform=android&consentmode=advanced){:target="_blank"} + * iOS: [Set up consent mode for iOS apps](https://developers.google.com/tag-platform/security/guides/app-consent?platform=ios&consentmode=advanced){:target="_blank"} +3. If you already set up consent mode for your app, upgrade it to consent mode v2. + * 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"} + * 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"} + ## Setting up Firebase with Analytics-React-Native If you use Segment's older React Native source library, you must explicitly bundle the mobile SDKs for both iOS and Android with your project. diff --git a/src/connections/destinations/catalog/google-ads-classic/index.md b/src/connections/destinations/catalog/google-ads-classic/index.md index e4dcf73489..731f6b5d00 100644 --- a/src/connections/destinations/catalog/google-ads-classic/index.md +++ b/src/connections/destinations/catalog/google-ads-classic/index.md @@ -14,8 +14,8 @@ id: 54521fd525e721e32a72ee92 With Segment, you can use your events to fire a Google Ads conversion pixel from your website **in client-side JavaScript.** 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. -> info "Consent Mode" -> Segment is currently building Consent Mode for all affected Google destinations. This will be available before March 6, 2024. +> info "Consent mode" +> Google is enforcing consent starting 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. ### Configure the Google Ads (Classic) destination @@ -26,6 +26,36 @@ You can also trigger Google Ads (Classic) conversion from your mobile app using 5. On the destination Settings tab, enter the **Conversion ID** from your Google Ads (Classic) account. 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`. +## Consent mode +[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. + +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. + +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. + +Consent mode may involve updates to your sources outside of Segment, such as incorporating a consent management system for consent functionality. + +### Consent mode for mobile and server apps +To set up consent mode for Google Ads Classic mobile and server apps: +1. Update your app's SDK to a version that supports consent mode v2. + * 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"}. + * iOS apps must use [Firebase Apple SDK version 10.17.0 or later](https://firebase.google.com/support/release-notes/ios#analytics){:target="_blank"}. + +2. Set up consent mode for your app if you haven't already set it up. + * Android: [Set up consent mode for Android apps](https://developers.google.com/tag-platform/security/guides/app-consent?platform=android&consentmode=advanced){:target="_blank"} + * iOS: [Set up consent mode for iOS apps](https://developers.google.com/tag-platform/security/guides/app-consent?platform=ios&consentmode=advanced){:target="_blank"} +3. If you already set up consent mode for your app, upgrade it to consent mode v2. + * 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"} + * 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"} + +### Consent mode for web +To set up consent mode for Google Ads Classic Web, choose from these options: +* 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"}. +* 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"}. +* 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"}. +* 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"}. +* 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. + ## Web This section details the configuration of the Google Ads (Classic) destination with Analytics.js sources. diff --git a/src/connections/destinations/catalog/google-ads-gtag/index.md b/src/connections/destinations/catalog/google-ads-gtag/index.md index 64cad7f78e..212a5afce9 100644 --- a/src/connections/destinations/catalog/google-ads-gtag/index.md +++ b/src/connections/destinations/catalog/google-ads-gtag/index.md @@ -15,6 +15,9 @@ The [Google global site tag (gtag.js)](https://support.google.com/google-ads/ans > info "" > If you're sending [enhancement data to Google Ads](/docs/connections/destinations/catalog/actions-google-enhanced-conversions/) in parallel with Gtag, you must include the same Order ID (Transaction ID) on both sets of data. This is required to properly deduplicate conversions between Gtag conversions and enhanced conversions. To send Order ID (Transaction ID) to Gtag, include `order_id` as a property on your web events. +> info "Consent mode" +> Google is enforcing consent starting March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/google-ads-gtag/#consent-mode) and how to set it up. + ## Getting Started You can use this destination to map your `.page()` calls to **Page Load Conversions** or `.track()` calls to **Click Conversions**. Currently this is only supported on the browser. @@ -28,9 +31,52 @@ You can use this destination to map your `.page()` calls to **Page Load Conversi 5. On the destination Settings tab, enter the **Conversion ID** from your Google Ads (Gtag) account. 6. Select the 'Click Conversion' 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 (Gtag) conversion label. -> info "Consent Mode" -> Segment is currently building Consent Mode for all affected Google destinations. This will be available before March 6, 2024. +## Consent mode +[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. + +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. + +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. + +Consent mode may involve updates to your sources outside of Segment, such as incorporating a consent management system for consent functionality. + +### Set up consent mode + +To enable consent mode for your Google Ads (Gtag) destination, you can choose from 2 implementation options. + +* **Option 1:** + 1. Set the consent defaults by implementing the `ready()` method to set consent defaults. + + ``` + analytics.ready(function() { + window.gtag('consent', 'default', { + 'ad_storage': 'granted', + 'ad_user_data': 'granted', + 'ad_personalization': 'granted', + 'analytics_storage': 'granted' + }); + }); + ``` + + 2. Use your Consent Management Platform to prompt the visitor. Ask the visitor to grant or deny consent for the applicable types (for example, analytics, advertising). + + 3. Pass the information to Gtag.js by calling `gtag` inside the Segment `ready`() method. + + ``` + analytics.ready(function() { + window.gtag('consent', 'update', { + 'ad_storage': 'denied', + 'ad_user_data': 'granted', + 'ad_personalization': 'denied', + 'analytics_storage': 'granted' + }); + }); + ``` + +* **Option 2:** Create an instance of the [Google Analytics 4 Web destination](/docs/connections/destinations/catalog/actions-google-analytics-4-web/), to set up [consent in your GA4 Web destination](/docs/connections/destinations/catalog/actions-google-analytics-4-web/#consent-mode), which loads a gtag with consent preferences. If you're already using Google Analytics 4 Web on the same page, you just need to configure the consent mode settings once. There's no need to create another instance of GA4 Web. + +If you have any questions setting up consent mode, reach out to [friends@segment.com](mailto:friends@segment.com). ## Page diff --git a/src/connections/destinations/catalog/google-tag-manager/index.md b/src/connections/destinations/catalog/google-tag-manager/index.md index d56280cc6a..ed117a1aea 100644 --- a/src/connections/destinations/catalog/google-tag-manager/index.md +++ b/src/connections/destinations/catalog/google-tag-manager/index.md @@ -9,17 +9,16 @@ id: 54521fd625e721e32a72eeb9 > info "" > The Google Tag Manager destination is for web only. The destination isn't compatible with iOS or other mobile sources. For mobile tracking, Segment recommends using the [Firebase Destination](/docs/connections/destinations/catalog/firebase/). -## Getting Started +> info "Consent mode" +> Google is enforcing consent starting March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/google-tag-manager/#consent-mode) and how to set it up. +## Getting Started 1. From the Segment web app, click **Catalog**. 2. Search for "Google Tag Manager" in the Catalog, select it, and choose which of your sources to connect the destination to. 3. In your Segment UI's destination settings, enter your Container ID (note: it should start with "GTM-"). You can find this in the Admin section of your [GTM dashboard](https://tagmanager.google.com/#/admin/){:target="_blank"}. 4. GTM loads on any pages where your Segment snippet is initialized and `analytics.page` is called in client-side JavaScript. Once you've turned on GTM through Segment, you can use Segment `track` events to populate the GTM `dataLayer`, and remove the GTML snippet from your page. -> info "Consent Mode" -> Segment is currently building Consent Mode for all affected Google destinations. This will be available before March 6, 2024. For Google Tag Manager, please note that consent mode settings need to be managed directly [within your GTM account](https://support.google.com/tagmanager/answer/10718549?hl=en#tag-settings){:target="_blank"}. There's no direct update from Segment for the GTM destination regarding consent mode, as it's managed within GTM tags themselves. - > info "" > Segment recommends that you load GTM through Segment rather than loading Segment inside of GTM. When you load Segment through GTM, it limits Segment's ability to help troubleshoot. @@ -97,3 +96,10 @@ By default Segment pushes the `anonymousId` and `userId`(if exists) into the `da ### Environments If you're using an 'environment' variable for `gtm_preview` in your tag's query string, you can set that string in the **Environment** of your Optional Settings. IMPORTANT: Make sure the string includes the `gtm_auth` variable. For example, your string should look like: `env-xx>m_auth=xxxxx`. + +### Consent mode +[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. + +For Google Tag Manager, consent mode settings need to be managed directly [within your GTM account](https://support.google.com/tagmanager/answer/10718549?hl=en#tag-settings){:target="_blank"}. There's no direct update from Segment for the GTM destination regarding consent mode, as it's managed within GTM tags themselves. + +Segment recommeds you to install a consent management platform that uses the current [consent-tools wrapper](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools){:target="_blank"} that's outside of Google Tag Manager such as [One Trust](https://tanelytics.com/integrate-onetrust-with-google-tag-manager/){:target="_blank"}. \ No newline at end of file diff --git a/src/connections/destinations/catalog/personas-display-video-360/index.md b/src/connections/destinations/catalog/personas-display-video-360/index.md index b875d6ae7c..3aa10ea5c0 100644 --- a/src/connections/destinations/catalog/personas-display-video-360/index.md +++ b/src/connections/destinations/catalog/personas-display-video-360/index.md @@ -10,7 +10,7 @@ id: 5d4dd5b989eda01a09b5cdb1 > > Settings and configurations will be migrated automatically, but you must take additional action to ensure the destination is properly functioning. For more information, see [Migrate from Personas Google Display & Video 360 Destination ](/docs/connections/destinations/catalog/actions-display-video-360/#migrate-from-personas-google-display-&-video-360-destination) > -> We are disabling all existing Personas Display and Video 360 destinations. You can still access your existing configuration, but please refrain from enabling the destination, as it is set to be deprecated. You will no longer be able to create new instances of Personas Display and Video 360. Please check out [Display and Video (Actions)](/docs/connections/destinations/catalog/actions-display-video-360/) to set up a new instance of Google Display and Video 360. +> Segment is disabling all existing Personas Display and Video 360 destinations. You can still access your existing configuration, but please refrain from enabling the destination, as it is set to be deprecated. You will no longer be able to create new instances of Personas Display and Video 360. Please check out [Display and Video (Actions)](/docs/connections/destinations/catalog/actions-display-video-360/) to set up a new instance of Google Display and Video 360. > > For questions or issues contact [friends@segment.com](mailto:friends@segment.com). @@ -30,6 +30,9 @@ Segment's integration with DV360 enables Segment customers to sync audiences cre > info "" > **Note**: Since the release of `analytics-ios` version 4, Segment no longer collects IDFA automatically. To collect and pass IDFA to your DV360 integration, follow the steps for Ad Tracking and IDFA in the [Analytics-iOS mobile source](/docs/connections/sources/catalog/libraries/mobile/ios#ad-tracking-and-idfa) documentation. +> info "Consent mode" +> Google is enforcing consent starting March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/personas-display-video-360/#consent-mode) and how to set it up. + ## Details {% comment %} @@ -239,6 +242,15 @@ After you complete the set up process, allow up to 24 hours for Google to create Extra information from the API (settings, connection modes, etc.) are automatically pulled in here. {% include content/sync-frequency-note.md %} +## Consent mode +[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. + +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. + +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. + +Segment automatically sends consent as `TRUE` for this destination. Segment uses the [bulk-uploader workflow](https://developers.google.com/authorized-buyers/rtb/bulk-uploader#workflow){:target="_blank"} which requires consented data. Ensure all audiences and journeys are connected to consented audiences. + ## FAQ ### What is Segment's relationship with Google DV360 and is the data that Segment sends considered to be First or Third party?