Skip to content

Commit 5965eb7

Browse files
authored
Merge pull request #2487 from segmentio/Doc439-Google-Adwords-Remarketing-List
Doc439-Google-Adwords-Remarketing-Lists
2 parents 382212a + 284f7d7 commit 5965eb7

File tree

1 file changed

+23
-23
lines changed
  • src/connections/destinations/catalog/adwords-remarketing-lists

1 file changed

+23
-23
lines changed

src/connections/destinations/catalog/adwords-remarketing-lists/index.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -18,15 +18,14 @@ hide-boilerplate: true
1818
| [Google Ads (Gtag)](/docs/connections/destinations/catalog/google-adwords-new/) | No |
1919
| [Google Ads (Classic)](/docs/connections/destinations/catalog/google-ads-classic/) | Yes - Event Destination |
2020
| [Google Analytics](/docs/connections/destinations/catalog/google-analytics/) | Yes - Event Destination |
21-
| Google Adwords Remarketing Lists (Customer Match) | Yes - List Destination |
21+
| Google Adwords Remarketing Lists (Customer Match) | Yes - Event Destination |
2222

2323
## Details
2424

2525
- **Supports Personas**: Yes
26-
- **Personas Destination type**: List
2726
- **Must create audience_name field before Personas can update those values?**: No, Personas creates the audience for you.
2827
- **Audience appears as**: A Customer list, in the Audience Manager under Audience lists.
29-
- **Destination rate limit**: None
28+
- **Destination rate limit**: No
3029
- **Lookback window allowed**: Yes
3130
- **Identifiers required** : Email or Mobile Device ID (IDFA)
3231
- **Identifiers accepted** : Email and Mobile Device ID (IDFA)
@@ -35,23 +34,23 @@ hide-boilerplate: true
3534

3635
## Overview
3736

38-
The Google Adwords Remarketing Lists (Customer Match) Destination is one of our most popular Personas List Destinations. It has a variety of use cases related to exclusion, acquisition (using Similar Audience), re-marketing, and more.
37+
The Google Adwords Remarketing Lists (Customer Match) Destination is one of Segment's most popular Personas List Destinations. It has a variety of use cases related to exclusion, acquisition (using Similar Audience), re-marketing, and more.
3938

40-
This Destination can send *audiences* (lists of users) created in [Personas](/docs/personas/) to Google Adwords Audience Lists as a [**Customer List**](https://support.google.com/google-ads/answer/7558048) type. Once you set this up, Segment sends an [initial list](https://developers.google.com/analytics/devguides/config/mgmt/v3/remarketing#insert) of users to Google Adwords Audience lists as a “Customer list”. As users move in and out of the audience, Segment automatically [updates the list](https://developers.google.com/analytics/devguides/config/mgmt/v3/remarketing#insert) in Google every 6 hours. This allows you to run advertising campaigns without having manually update the list of users to target in Adwords campaigns.
39+
This Destination can send audiences created in [Personas](/docs/personas/) to Google Adwords Audience Lists as a [**Customer List**](https://support.google.com/google-ads/answer/7558048) type. Once you set this up, Segment sends an [initial list](https://developers.google.com/analytics/devguides/config/mgmt/v3/remarketing#insert) of users to Google Adwords Audience lists as a “Customer list”. As users move in and out of the audience, Segment automatically [updates the list](https://developers.google.com/analytics/devguides/config/mgmt/v3/remarketing#insert) in Google every hour. This allows you to run advertising campaigns without having manually update the list of users to target in Adwords campaigns.
4140

42-
Currently, you can only send either an email address or mobile id (IDFA) from Segment Personas 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/personas/identity-resolution/externalids/) for the user.
43-
If you use Segment’s mobile SDK to collect events from a mobile app, the user’s IDFA is automatically captured. If you do not use Segment’s mobile SDK, you can set the user’s IDFA by setting it within `context.device.advertisingId`.
41+
Currently, you can only send either an email address or mobile id (IDFA) from Segment Personas 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/personas/identity-resolution/externalids/) for the user.
42+
If you use Segment’s mobile SDK to collect events from a mobile app, the user’s IDFA is automatically captured. If you don't use Segment’s mobile SDK, you can set the user’s IDFA by setting it within `context.device.advertisingId`.
4443

4544
When you send an audience to Google Adwords Remarketing Lists (Customer Match), you can choose which custom matcher (email or mobile id/IDFA) to match with. If a user has multiple emails or IDFAs on their account as `external_ids`, Personas only sends Adwords the ID that was most recently added to the user profile.
4645

47-
These audience lists can be used serve content on Google Search, YouTube, and Gmail. You can only target users with email addresses that are associated with a Google account, and you can target users in Gmail only if they have an `@gmail.com` address. <!--For Personas audiences that are compatible with Google Display Network, see our documentation for DV360. -->
46+
These audience lists can be used to serve content on Google Search, YouTube, and Gmail. You can only target users with email addresses that are associated with a Google account, and you can target users in Gmail only if they have an `@gmail.com` address. <!--For Personas audiences that are compatible with Google Display Network, see our documentation for DV360. -->
4847

4948
> info ""
50-
> **Note**: You must have access to Personas as part of your Segment plan to use this destination. [Contact our sales team](https://segment.com/demo/) to try this out.
49+
> **Note**: You must have access to Personas as part of your Segment plan to use this destination. [Contact Segment's sales team](https://segment.com/demo/) to try this out.
5150
5251
## Use Cases: Known Users
5352

54-
Google Adwords Remarketing Lists (Customer Match) allows you to efficiently run several marketing and advertising operations. The list below contains the most popular use cases when you know personally identifiable information (PII) about your users, such as email address or mobile device id (IDFA). When you send a Personas audience to Google Adwords Remarketing Lists (Customer Match) with email addresses or mobile device ids (IDFA), Segment hashes the PII values before sending them to Google. Google then uses these identifiers to match with users on their ad network to allow the following use cases.
53+
Google Adwords Remarketing Lists (Customer Match) allows you to efficiently run several marketing and advertising operations. The list below contains the most popular use cases when you know personally identifiable information (PII) about your users, such as email addresses or mobile device ids (IDFA). When you send a Personas audience to Google Adwords Remarketing Lists (Customer Match) with email addresses or mobile device ids (IDFA), Segment hashes the PII values before sending them to Google. Google then uses these identifiers to match with users on their ad network to allow the following use cases.
5554

5655

5756
### Exclusion audiences (Suppression audiences)
@@ -69,11 +68,11 @@ You can use Personas to create a detailed profile of your most loyal customers (
6968

7069
### Re-marketing audiences
7170

72-
You can use Personas to target users who completed some initial action, but didn’t follow through on a purchase or other conversion event. You can create audiences to re-target these individuals and remind them to complete the purchase or other process. For example, you might send an email to someone who didn’t complete a sign-up form, or who didn’t complete a shopping cart checkout.
71+
You can use Personas to target users who completed some initial action, but didn’t follow through on a purchase or other conversion event. You can create audiences to re-target these individuals and remind them to complete the purchase or other process. For example, you might send an email to someone who didn’t complete a sign-up form or who didn’t complete a shopping cart checkout.
7372

7473
## How it works
7574

76-
When you create an audience in Personas and connect it to Google Adwords Remarketing Lists (Customer Match), Segment does the following:
75+
When you create an audience in Personas and connect it to Google Adwords Remarketing Lists (Customer Match), Segment performs the following actions:
7776

7877
1. Creates an Adwords Audience list (type Customer List) with the name you entered in Personas.
7978
2. Adds any users that fit the audience definition based on Email or Mobile ID (IDFA). Google uses these identifiers to match users in your list to users in the Google system who can be served ads.
@@ -101,15 +100,16 @@ Before you start, make sure you have administrative access to the Adwords accoun
101100

102101
2. Search for “Adwords Remarketing Lists (Customer Match)” and click **Configure**.
103102

104-
3. Click **Connect to Adwords Remarketing Lists (Customer Match)**. You are prompted to sign in to your Google Adwords account. (Make sure you sign in to the account that has administrator access!)
103+
3. Click **Connect to Adwords Remarketing Lists (Customer Match)**. You're prompted to sign in to your Google Adwords account. (Make sure you sign in to the account that has administrator access!)
105104

106105
4. When prompted, click **Allow**. This is required for Segment to update your Google Adwords Remarketing Lists (Customer Match).
107106
![](images/garl-auth-google.png)
108107

109108
5. Select the Adwords account or sub-account to connect with Personas.
110109

111-
**What are sub-accounts?** Because the Google My Client Center (MCC) account allows a user to access multiple Google Ads accounts through a single user account. Segment has updated the selector to include these additional "sub-accounts." By default, Segment syncs the "primary" Google Ads account connected to your Google account, but when using Google MCC, you can select any of the Google Ads accounts managed by your primary Google Ads account. If you are not using MCC, your primary Google Ads account is connected. MCC is typically used by advertisers or agencies who are managing multiple client accounts.
110+
**What are sub-accounts?** Because the Google My Client Center (MCC) account allows a user to access multiple Google Ads accounts through a single user account, Segment has updated the selector to include these additional "sub-accounts." By default, Segment syncs the "primary" Google Ads account connected to your Google account, but when using Google MCC, you can select any of the Google Ads accounts managed by your primary Google Ads account. If you're not using MCC, your primary Google Ads account is connected. MCC is typically used by advertisers or agencies that manage multiple client accounts.
112111

112+
Here's an example of sub-accounts in the selector:
113113
![Example of Sub-accounts in Selector](images/adwords_subaccounts.png)
114114

115115
### 2. Create an audience in Segment and connect it to Google Adwords Remarketing Lists (Customer Match)
@@ -123,31 +123,31 @@ Before you start, make sure you have administrative access to the Adwords accoun
123123
5. Give your audience a name, and click **Create**.
124124

125125
> warning ""
126-
> **Warning**: If you change the audience name in Personas, the change is not reflected in Google Adwords Audience lists.
126+
> **Warning**: If you change the audience name in Personas, the change isn't reflected in Google Adwords Audience lists.
127127
128128
### 3. Confirm that the Audience is building in Google Adwords Audience Manager
129129

130130
> info ""
131131
> **Note**: Adwords can take 6-12 hours to process initial audience uploads before they can be used for a campaign. If the audience is still processing, the list status appears as “Populating”.
132132
133-
In Google Adwords go to **Tools & Settings** > **Shared Library**> **Audience manager** > **Audience lists**
133+
In Google Adwords go to **Tools & Settings** > **Shared Library**> **Audience manager** > **Audience lists**.
134134

135135
![](images/garl-audience_mgr.png)
136136

137-
137+
138138
## Troubleshooting
139139

140140
#### Not seeing an audience in Google Adwords Audience Manager
141141

142-
Make sure you authorized Google Adwords, and selected the correct account.
142+
Make sure you authorized Google Adwords and selected the correct account.
143143

144-
Make sure you have administrator access for your Google Adwords account. You can check that your Adwords credentials are correct by navigating the the Adwords Remarketing Lists (Customer Match) destination in Personas→ Destinations, and viewing the settings.
144+
Make sure you have administrator access for your Google Adwords account. You can check that your Adwords credentials are correct by navigating the Adwords Remarketing Lists (Customer Match) destination in Personas→ Destinations, and viewing the settings.
145145

146146
![](images/garl-configure_dest.png)
147147

148148
### Audience size smaller than expected
149149

150-
Personas matches users in your audience using email and Mobile Device ID (IDFA) values. Make sure you are tracking these with Segment to have as high a match rate as possible.
150+
Personas matches users in your audience using email and Mobile Device ID (IDFA) values. Make sure you're tracking these with Segment to have as high a match rate as possible.
151151

152152
You can set an email on the user profile by including `email` as a trait, as a property on an event, or as an external id for the user. If you use Segment’s mobile SDKs to collect events from a mobile app, IDFA is automatically captured for the user. You can also set a user’s IDFA on a mobile app by setting it within `context.device.advertisingId`.
153153

@@ -157,9 +157,9 @@ If a user has more than one email address or IDFA on their account as `external_
157157

158158
#### What Google campaigns does Personas support?
159159

160-
Personas audiences can only send to Google Adwords Remarketing Lists (Customer Match) for Google Search, YouTube and Gmail campaigns. Gmail campaigns can only target users with a `@gmail` address.
160+
Personas audiences can only send to Google Adwords Remarketing Lists (Customer Match) for Google Search, YouTube, and Gmail campaigns. Gmail campaigns can only target users with an `@gmail.com` address.
161161

162-
#### How many users must be in an audience be to use Google Adwords Campaigns?
162+
#### How many users must be in an audience to use Google Adwords Campaigns?
163163

164164
100
165165

@@ -169,7 +169,7 @@ Currently, Personas sends either email or mobile device id (IDFA) to Google Adwo
169169

170170
#### If a user has multiple emails or IDFAs on their account, which ids get sent to Google Adwords?
171171

172-
Personas sends the most recent id that was added to the user profile to Google Adwords.
172+
Personas sends the most recent id added to the user profile to Google Adwords.
173173

174174
#### How do I enter multiple Mobile App IDs when exporting mobile IDs to Google Adwords?
175175

0 commit comments

Comments
 (0)