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 1051eb0650..aee0501122 100644 --- a/src/connections/destinations/catalog/actions-display-video-360/index.md +++ b/src/connections/destinations/catalog/actions-display-video-360/index.md @@ -3,7 +3,6 @@ title: Display and Video 360 (Actions) Destination strat: google hide-settings: true id: 65302a3acb309a8a3d5593f2 -beta: true engage: true --- diff --git a/src/connections/destinations/catalog/actions-linkedin-conversions/index.md b/src/connections/destinations/catalog/actions-linkedin-conversions/index.md index 9c15b0e465..699679051e 100644 --- a/src/connections/destinations/catalog/actions-linkedin-conversions/index.md +++ b/src/connections/destinations/catalog/actions-linkedin-conversions/index.md @@ -1,7 +1,6 @@ --- title: LinkedIn Conversions API Destination id: 652e765dbea0a2319209d193 -beta: true --- The LinkedIn Conversions API (CAPI) is a conversion tracking tool that creates a direct connection between marketing data from an advertiser’s server and LinkedIn. This integration enables advertisers to measure the performance of their LinkedIn marketing campaigns no matter where the conversion happens and use this data to power campaign optimization. The Conversions API can help strengthen performance and decrease cost per action with more complete attribution, improved reliability, and optimized delivery. diff --git a/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-create-new-role.png b/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-create-new-role.png deleted file mode 100644 index e9b750f347..0000000000 Binary files a/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-create-new-role.png and /dev/null differ diff --git a/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-leads.png b/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-leads.png deleted file mode 100644 index 7aa403a8db..0000000000 Binary files a/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-leads.png and /dev/null differ diff --git a/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-newfolder.png b/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-newfolder.png deleted file mode 100644 index 19d5cfea20..0000000000 Binary files a/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-newfolder.png and /dev/null differ diff --git a/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-newservice.png b/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-newservice.png deleted file mode 100644 index b9f49701ff..0000000000 Binary files a/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-newservice.png and /dev/null differ diff --git a/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-perms.png b/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-perms.png deleted file mode 100644 index e008491890..0000000000 Binary files a/src/connections/destinations/catalog/marketo-static-lists/images/marketosl-perms.png and /dev/null differ diff --git a/src/connections/destinations/catalog/marketo-static-lists/images/personas-add-emailtrait.png b/src/connections/destinations/catalog/marketo-static-lists/images/personas-add-emailtrait.png deleted file mode 100644 index f626fce2a7..0000000000 Binary files a/src/connections/destinations/catalog/marketo-static-lists/images/personas-add-emailtrait.png and /dev/null differ diff --git a/src/connections/destinations/catalog/marketo-static-lists/index.md b/src/connections/destinations/catalog/marketo-static-lists/index.md deleted file mode 100644 index 5888cd85d9..0000000000 --- a/src/connections/destinations/catalog/marketo-static-lists/index.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -title: Marketo Static Lists Destination -hide-boilerplate: true -strat: adobe -id: 5b73515e6170785a5e62978c ---- - -> warning "Deprecation Notice" -> This destination has been deprecated. Segment created an instance of the [Marketo Static Lists (Actions)](/docs/connections/destinations/catalog/actions-marketo-static-lists/) destination for each properly configured version of the Personas Marketo Static Lists classic destination in your workspace. Settings and configurations have been migrated automatically. If your Personas Marketo Static List destination is connected to a Journey, [create a new version of your Journey](/docs/engage/journeys/build-journey/#working-with-a-published-journey) to replace the Personas destination with the new Actions destination. -> -> Segment disabled all existing Personas Marketo Static List destinations, except those connected to a Journey instance. You can still access your existing configuration, but you will not be able to make changes to it. You will also no longer be able to create new instances of Personas Marketo Static Lists. Please refer to [Marketo Static Lists (Actions)](/docs/connections/destinations/catalog/actions-marketo-static-lists/) to set up a new instance of Marketo Static Lists. -> -> For questions or issues contact [friends@segment.com](mailto:friends@segment.com). - -> info "Marketo vs Marketo Static Lists Destinations" -> This page is about the **Marketo Static Lists** destination developed specifically for use with Engage. Marketo has strict API usage limits on the [main Marketo destination](/docs/connections/destinations/catalog/marketo-v2/), so although the main destination can receive events from Engage, use the Marketo *Static Lists* destination with Engage instead. - -## Overview - -The Marketo Static Lists destination lets you sync audiences created using [Engage](/docs/engage) into Marketo as a **List**. Once you create the audience, Segment sends that list of users to Marketo, and keeps it up to date as users enter and exit the audience specification. - -This allows you to run email campaigns in Marketo without having to manually find and upload a refreshed csv of users. This documentation explains how to set up Marketo in Segment, and what to expect in your Marketo UI. - - -## Details - -- **Supports Engage**: Yes -- **Engage Destination type**: List -- **Must create audience_name field before Engage can update those values?**: No. You don't need to create the _list_ in Marketo, however you do need to create the folder Segment will create the list in. -- **Audience appears as**: A list in the folder you created, in the Marketo Lead Database under Group Lists. -- **Destination rate limit**: 100 calls per 20 seconds, which is shared among all third-party API services -- **Lookback window allowed**: Yes -- **Identifiers required**: Email -- **Identifiers accepted**: Email -- **Client or Server-Side Connection**: Server-side - - -## How it works - -Every time you create an audience in Engage and connect it to Marketo Static Lists, Segment does the following: - -1. Creates a list with the same name as the Engage audience in the folder designated for Engage. -2. Adds any users to that list who both fit the audience definition and have an email address. -3. If a user has multiple email addresses on their identity graph, each email address becomes a unique entry on the list. -4. After the audience is configured, Segment evaluates which users meet the audience criteria, updating the audience and list, by adding or removing users accordingly. - -{% include content/sync-frequency-note.md %} - -## Configuring Marketo Static Lists - -> success "Good to know:" -> To set up Marketo to receive Engage data, you need Marketo administrator access. If you don't have that access, work with the administrator for your organization. - -### Step 1: Create an API-Only Marketo user - -In this step, you'll create an API-Only Marketo user with both Access API and Lead Database access. - -1. You can use an existing role with these permissions, or create a new role that has both Access API and Access Lead Database permissions. (Do this in Marketo by going to **Admin**→ **Users & Roles** → **Roles**). - - ![A screenshot of the Marketo Create New Role popup.](images/marketosl-create-new-role.png) - -2. Go to **Admin**→ **Users & Roles** → **Users** → **Invite New User** and create a new **API Only user** with the role that has both Access API and Lead Database permissions. **Be sure to check the API Only box.** - - ![A screenshot of the Marketo Invite New User page, with the roles Marketo Static List and API only selected.](images/marketosl-perms.png) - - -### Step 2: Create a Marketo Launchpoint Service for Engage - -1. Go to **Admin** → **Integration**→ **LaunchPoint** → **New** -2. Create a new service. In the Service field, select `Custom`, and in the **API Only User** field, select the user you created in step 1. -3. Write down the **Client Id** and **Client Secret** for this service, as you will need it in Step 4. - -![A screenshot of the New Service popup in Marketo.](images/marketosl-newservice.png) - - - -### Step 3: Create a Marketo Lead Database folder and get your Marketo Endpoint - -1. Go to your Marketo Lead Database and create a new folder under Group Lists. Once connected, each Engage audience shows up as a list in this folder. - - - ![A screenshot of the Marketo Lead Database, with a New Folder menu item selected.](images/marketosl-newfolder.png) - -2. Before you continue to the next step, in Marketo, go to **Admin → Web Services**, and copy or write down the REST API Endpoint. **Be sure to copy the REST endpoint and not the SOAP endpoint.** You'll need that in the next step. - -> warning "Warning:" -> Do not create a list in the folder for the audience. Segment creates the list for you! - -### Step 4: Set up the Marketo Static Lists destination in Engage - -1. From your Segment workspace, go to **Engage → Engage Settings → Destinations→ Add Destination** and then Search for Marketo Static Lists. -2. In the destination settings, enter the **Client Id**, **Client Secret**, **Endpoint** and **Folder Name** from the LaunchPoint service and folder you created in Steps 2 and 3. For **Endpoint**, note the Endpoint from Step 3. -3. Click the toggle to enable the Marketo Static Lists destination. - -### Step 5: Create Engage audiences and add Marketo Static Lists as a destination - -1. Navigate to the Engage Audiences tab and create a new audience. -2. Give your audience a name, some event and trait criteria, then click **Preview**. -3. Select Marketo Static Lists as a destination for the Audience. - -> info "" -> Only users with an email address appear in the list in Marketo. Users with multiple email addresses as external ids appear in the list once for each email address. - -![A screenshot of the Marketo Lead Database Audience page.](images/marketosl-leads.png) - -You can view the audience in Marketo by going to **Lead Database→ Group Lists→Name of folder you created in Step 3 → Audience name** - - -## Troubleshooting - -#### Not seeing an audience in Marketo - -Check that you followed all of the set-up steps. - -Wait six or more hours after setup for your audience to start appearing in Marketo. - -Check that you didn't create a list in the folder for the audience - Segment creates the list for you, and an existing one can conflict. - -Check that the audience members you expect have an email address on their profile. - -#### Audience size is smaller than expected -Only users in the audience who also have an email address are uploaded to the list. - -You might need to adjust your query to filter out users without an email so you can get a better estimate of how many users will appear on the list. In the example below, we added an AND condition where users have a Custom trait of `email` which `exists`. - -![A screenshot of the Audiences page in Segment.](images/personas-add-emailtrait.png) - -If a user has multiple email addresses, each address appears once in the Marketo lists. diff --git a/src/connections/destinations/catalog/personas-display-video-360/images/dv360-1-select-destination.png b/src/connections/destinations/catalog/personas-display-video-360/images/dv360-1-select-destination.png deleted file mode 100644 index 54143b94c1..0000000000 Binary files a/src/connections/destinations/catalog/personas-display-video-360/images/dv360-1-select-destination.png and /dev/null differ diff --git a/src/connections/destinations/catalog/personas-display-video-360/index.md b/src/connections/destinations/catalog/personas-display-video-360/index.md deleted file mode 100644 index c203f4f2c2..0000000000 --- a/src/connections/destinations/catalog/personas-display-video-360/index.md +++ /dev/null @@ -1,338 +0,0 @@ ---- -title: Personas Google Display & Video 360 Destination -strat: google -hide-settings: true -id: 5d4dd5b989eda01a09b5cdb1 -engage: true ---- - -> warning "Deprecation Notice" -> Due to Google retiring certain APIs on March 6, 2024, Segment deprecated this destination. Segment created an instance of the [Display and Video (Actions)](/docs/connections/destinations/catalog/actions-display-video-360/) destination for each properly configured version of the Personas Google Display and Video 360 classic destination in your workspace. -> -> Segment automatically migrated destination settings and configurations, but you must take additional action to ensure your migrated destination functions as intended. 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) -> -> Segment disabled all existing Personas Display and Video 360 destinations. You can still access your existing configuration, but do not enable the destination, as it has been deprecated. You will no longer be able to create new instances of Personas Display and Video 360. Check out the [Display and Video (Actions)](/docs/connections/destinations/catalog/actions-display-video-360/) documentation if you want to set up a new instance of Google Display and Video 360. -> -> For questions or issues contact [friends@segment.com](mailto:friends@segment.com). - - -Google's [Display & Video (DV360)](https://marketingplatform.google.com/about/display-video-360/){:target="_blank"} service is an end-to-end campaign management tool that enables enterprise customers to plan, measure, and run display and video advertisements. - -> info "" -> **Note**: You can connect to a Google Ad Manager account. For more information, see [4. Create an audience and finish DV360 configuration](#4-create-an-audience-and-finish-dv360-configuration) below. - -Segment's integration with DV360 enables Segment customers to sync audiences created in Engage with DV360 to enable centralized audience management and improved retargeting. - -> warning "" -> **Important**: You must meet certain implementation criteria to use the DV360 integration: -> - For web traffic, you must have a client-side `analytics.js` source. -> - For mobile app traffic, you must have a mobile source. - -> 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 enforced consent on 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 %} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-**Requirements** - - - Business tier Segment customers with Engage - - One of the following sources, depending on type: - - For web: analytics.js - - For mobile app: a mobile source that passes an advertising identifier - - A Google Marketing Platform account -
-**Audience appears as** - -An audience list with the name of your Engage Audience on the DV360 **All Audiences** screen -
-**Destination rate limit** - -None -
-**Lookback window allowed** - -30 days -
-**Historical backfill supported** - -No -
-**Identifiers required** - -One of: -- `idfa` (iOS) -- `advertisingId` (Android) -- `anonymousId` (Web) -
-**Connection type** - -- Client-side (DoubleClick Floodlight) -- Server-side (DV360) -
-**Aliasing supported** - -No -
-{% endcomment %} - -- **Requirements**: - - Business tier Segment customers with Engage - - One of the following sources, depending on type: - - For web: analytics.js - - For mobile app: a mobile source that passes an advertising identifier - - A Google Marketing Platform account -- **Audience appears as**: An audience list with the name of your Engage Audience on the **DV360 All Audiences** screen -- **Destination rate limit**: None -- **Lookback window allowed**: 30 days -- **Historical backfill supported**: No -- **Identifiers required (one of the following)**: - - `idfa` (iOS) - - `advertisingId` (Android) - - `anonymousId` (Web) -- **Connection type**: - - Client-side (DoubleClick Floodlight) - - Server-side (DV360) -- **Aliasing supported**: No - -## Components - -The Segment DV360 integration uses two components, the [DoubleClick Floodlight tag](/docs/connections/destinations/catalog/doubleclick-floodlight/) and Personas Display & Video 360 integration - -### DoubleClick Floodlight tag - -Segment users must add this tag to their web properties. The tag performs several functions, but when enabled for the DV360 integration, it allows Segment to send information about users directly to Google client-side. - -> info "" -> **Note**: This component is required only if you want to sync audiences based on web traffic. - -### DV360 destination - -The DV360 destination syncs audience data between Segment and Google Display & Video 360. For more information about enabling the DV360 destination, see [Set up](#set-up) below. - -## Set up - -Configuring this integration requires action by both you in your Segment workspace, and Google in your Google Marketing Platform account. As a result, the time required to finish configuration and set up can vary. - -### 1. Enable Segment to create user lists in DV360 - -Before you begin the integration steps, Google must provide permission for Segment to push user lists to your organization's DV360 account on your behalf. Once requested, Google provides an email form to sign and finalize the permission grant. - -You can use this template to draft an email to your account representative. - -``` - Hi there, - - I'd like to request access for Segment (account id 262932431) to push user lists into DV360 for our ad account [insert your account id]. - - Could you please provide guidance on which permission level should be granted to Segment for our case? (`invite_partner` or `invite_advertiser`). - - Thanks. -``` - -Your Google account representative will suggest one of the following permission levels: - -| Permission | Business type | Audience list availability | -| ------------------- | ------------------------------------------------------------------------------ | --------------------------------------------- | -| `invite_partner` | An agency, trading desk, or large individual advertiser (with many sub-brands) | Any advertiser within your organization. | -| `invite_advertiser` | A single business that runs its own advertising campaigns | The single advertiser linked to your account. | - -Your selection here depends on the type of business you plan to support with the DV360 destination. - -> info "" -> **Note**: The permission level and numeric connectionID are required in later steps. Be sure to have these available before you continue. - -### 2. Configure client integration for web traffic - -> info "" -> **Note**: This step is necessary only if you want ot use Google User IDs to build audiences based on website traffic. If you plan to use mobile identifiers only, continue to [3. Enable and configure the DV360 destination](#3-enable-and-configure-the-dv360-destination). - -Segment requires the [DoubleClick Floodlight](/docs/connections/destinations/catalog/doubleclick-floodlight/) tag on your website to enable the creation of audiences based on website traffic. This allows Segment to send Google the appropriate identifier (typically `anonymousId`) for users that are in an audience. Google stores these identifiers on its servers and matches them against `google_id`. - -To configure DoubleClick Floodlight: - -> warning "" -> **Prerequisite**: Create a [JavaScript Website](/docs/connections/sources/catalog/libraries/website/javascript/) source in your Segment workspace if one does not exist. Ensure that this source is configured to track visitors to your website. For more information about configuring Javascript sources, see the [Analytics.js Quickstart guide](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/). - -1. In your workspace, visit the **Catalog** and search for the **DoubleClick Floodlight** destination. -2. Connect your JavaScript Website source to the DoubleClick Floodlight destination, and configure the following settings: - 1. **Get DoubleClickID**: `On` - 2. **Google Network Id**: `segment` - 3. Your [Segment Write Key](/docs/connections/find-writekey/). You can retrieve your write key from the Settings tab on the Source. - 4. **DoubleClick Advertiser ID** - - If you use DoubleClick Floodlight for DV360 only, enter `DV360`. - - If you use DoubleClick Floodlight for other use cases in addition to DV360, enter the Advertiser ID from your Doubleclick Floodlight account. -3. Switch the toggle to enable the destination. - -### 3. Enable and configure the DV360 destination - -Connect the DV360 destination to the Engage source from which you'll send data to DV360. - -To enable the DV360 destination: - -1. Search for and select **Personas Display & Video 360** in the destinations catalog. -2. Select the Space you want to connect to the destination. -3. Switch the toggle to enable the destination. - -> info "" -> **Note**: The destination does not have configurable settings until you create an audience, described [here](#4-create-an-audience-and-finish-dv360-configuration) - -### 4. Create an audience and finish DV360 configuration - -Create an [Audience](/docs/personas/audiences) in a new or existing Engage space. After you create the audience, you can select the Personas Display & Video 360 destination. - -![Select the destination](images/dv360-1-select-destination.png) - -> info "" -> **Note**: These settings are tied to a single audience. Each additional audience you send to DV360 requires you to input these values. - -When you select the destination, you're prompted to complete the destination settings. The settings you enter must match the information you shared when you [requested access](#1-enable-segment-to-create-user-lists-in-dv360) for Segment to post to your DV360 account: - -| Setting | Description | -| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| User Role Granted | The permission you requested from Google. Either `Advertiser`, `Partner`, or `Publisher`. **Note:** Select `Publisher` only if you plan to connect to Google Ad Manager. | -| Account ID | The ID of your DV360 or Ad Manager account. For help finding your Account ID, see [Display & Video 360 Help](https://support.google.com/displayvideo/answer/3423704?hl=en#zippy=){:target="_blank"}. | - -On Step 3: Review & Create, **deselect** the Historical Backfill option to ensure that audience sizes between Engage and DV360 align more closely. - -> info "" -> **Note**: When you create a new audience based on a web source, and select the Historical Backfill option, Segment computes the audience based on data already received, and sends that computed audience data to the destination, regardless of when a user actually joined the audience. -> -> In the case of the DV360 destination, due to DV360's reliance on browser cookies from Doubleclick Floodlight, only users who visited the site *after* Doubleclick Floodlight was added to the site are eligible to sync to the DV360 destination. -> -> As a result, if you select Historical Backfill for the DV360 Engage audience, the audience you first send to DV360 might be significantly smaller than the size displayed in Engage. - -After you complete the set up process, allow up to 24 hours for Google to create the new audience list. Once the list is created, Segment can begin to sync users to that list. Google may require additional time to process the initial audience additions. The entire first sync to DV360 may require 24-48 hours to complete. As a result, the first few audience syncs after you create the audience may fail. - -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? - -Google considers Segment to be a DMP or Data Onboarder. Audience information pushed from Segment to your DV360 account is considered to be **First-Party** data. - - -### When will my data appear in DV360? - -When you complete the connection between Segment and DV360, it can take from 24 to 48 hours for Google to create the user list. This must complete before Segment can begin to sync users into that list. - - -### What identifiers are needed to enable this integration? - -Google's [documentation](https://developers.google.com/authorized-buyers/rtb/downloads/cookie-bulk-upload-proto){:target="_blank"} provides information about the accepted identifiers for this integration. - - -- To use DV360 with web traffic, you must collect `anonymous_id` through the client-side `analytics.js` Source. -- To use DV360 with mobile traffic, you must collect `IDFA`s through Segment's mobile sources. - - -### Why is my audience in DV360 smaller than the audience that I see in Engage? What affects match rates? - -Match rates may differ between Engage and DV360 for the following reasons: - -#### Go-forward data - -When you first preview and create an audience in Engage, the audience may contain many audience members. This is more likely if you select the **Historical Backfill** option. This does not reflect the audience that syncs to DV360 for the following reasons: - - -1. During an audience sync, Segment sends a list of `anon_id` values to Google. Google attempts to match those values in their match table, to find an associated `google_user_id`. -2. To complete this lookup, Google must have both the `anon_id` and have it store along side a matched `google_user_id`. This occurs when a user visits your website with both the Doubleclick Floodlight tag installed, and the DV360 integration completed. - -As a result, you must have Doubleclick Floodlight and the DV360 integration in place before Google can match users and make them available for retargeting. - -To help reduce the difference between Engage and DV360 audience sizes, Segment recommends that you deselect the `Historical Backfill` option when you create the audience that syncs to DV360. - -#### Impact to third-party cookies: Browser Policies - -The DV360 integration for web traffic relies on Doubleclick Floodlight, which itself relies on a `google_user_id` cookie. While this cookie is “yours”, browsers treat this as a third-party cookie because it is served from Google's servers, and not the same domain as your website. As browsers become more privacy-oriented, they block third-party cookies by default. - -Users who visit your website in Firefox and Safari, and who do not specifically allow third-party cookies, are not identifiable by Doubleclick Floodlight (`google_user_id`). This prevents Google from identifying a match between an `anon_id` sent from Segment, and results in lower match rates. - -#### Impact to third-party cookies: Adblockers - -All browser-based adblocking software intentionally blocks most third-party cookies, including the Doubleclick Floodlight cookie necessary for identification. As a result, Google cannot match users who employ adblocking software in their browsers. - -#### IDFA impact: Recent Apple announcements - -Apple has announced an updated privacy policy that, while not rolled out yet, impacts the way businesses collect IDFA data. When enacted, this privacy policy will significantly reduce the percentage of users for which IDFA data is collected. This change will result in lower match rates, as both Segment and Google will see a decline in the number of IDFA values sent by Segment, and matched by Google. - -#### Invalid Google IDs - -Sometimes, Google denies IDFA or `google_user_id` values when they consider them to be invalid or inactive. - -#### Modifying Lists Configuration in DV360 - -Any changes to a DV360 list's configuration (for example, modifying the membership expiration from 540 days to a value that matches the time window on the audience) is **very risky** and **will likely** cause mismatches between Engage audiences and the lists in Google. Segment ensures that the integration works successfully only if there are no changes made to the configurations in DV360. DV360 lists are created with parameters that are known to be compatible with Engage. Configurations that differ from Segment's can cause mismatches by removing more users than intended, or by not accepting valid uploads. - - -### Why is the audience size larger in DV360 than in Engage? - -Engage syncs every IDFA or `anonymous_id` value for each user in an audience. When DV360 receives this data, it does not de-duplicate in the event that multiple identifiers map to the same unique user. This may result in a larger audience list in Google compared to Engage. - - -### Why don't I see matches in DV360? - -The most common cause of matches not appearing in DV360 is an error with Doubleclick Floodlight. From the website where tracking is enabled, open the Network inspector, and confirm that outgoing requests to `idsync.segment.com` appear. - - -### How does third-party cookie eradication impact the DV360 Destination? - -Google Chrome has committed to replacing third-party cookies with an alternative, but has not announced a timeframe for that alternative. Segment will not update this integration until these updates from Google are announced. - - -### Can I use Engage audiences to target YouTube ads with this integration? - -No. YouTube (through DV360) does not support the type of lists that Segment provides. - -### Why do I see destination settings after I add my audience, but not when I first enable the destination? - -The DV360 Destination works on a per-audience basis. This enables you to: - -- Send data from different audiences to different DV360 accounts. -- Send data to Google Ad Manager with the same destination.