Skip to content

Commit a4657b1

Browse files
authored
Merge pull request #432 from segmentio/repo-sync
repo sync
2 parents c4a8eaa + 63647ef commit a4657b1

File tree

2 files changed

+107
-33
lines changed
  • src/connections
    • destinations/catalog/personas-facebook-custom-audiences
    • sources/catalog/cloud-apps/workramp

2 files changed

+107
-33
lines changed

src/connections/destinations/catalog/personas-facebook-custom-audiences/index.md

Lines changed: 13 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -38,24 +38,10 @@ This page is about the **Facebook Custom Audiences** destination developed speci
3838
- **Destination rate limit**: None
3939
- **Lookback window allowed**: Yes
4040
- **Identifiers required** : Email or Mobile Device ID (IDFA)
41-
- **Identifiers accepted** : Email and Mobile Device ID (IDFA). Other identifiers can be sent through [Additional Traits Matching](#public-preview-feature-additional-traits-matching)
41+
- **Identifiers accepted** : Email and Mobile Device ID (IDFA). Other identifiers can be sent through [Additional Traits Matching](#public-preview-feature-additional-traits-matching).
4242
- **Client or Server-Side Connection**: Server-side
4343
- **Minimum audience size required**: 100
4444

45-
<!-- commenting out until we can do better with formatting
46-
---
47-
| **Support for Personas** | Yes |
48-
| **Personas Destination Method** | List |
49-
| **Must create audience_name field in the tool before Personas can update those values** | No, we create the audience for you. Note: if you change the name of the audience in Segment, it will not be reflected in Facebook |
50-
| **How does the audience appear within the destination?** | As a Facebook Custom Audience |
51-
| **Are there rate limits?** | No |
52-
| **Lookback window allowed by Destination** | Yes |
53-
| **Identifiers Required** | email or IDFA |
54-
| **Identifiers Accepted** | See [Facebook developer docs](https://developers.facebook.com/docs/marketing-api/audiences/guides/custom-audiences/) for full list |
55-
| **Client vs. Server-Side Connection** | Server-side |
56-
| **Minimum audience size required to send data to this Destination** | 100 | -->
57-
58-
5945
## Use Cases: Known Users
6046

6147
Facebook Custom Audiences 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, name, phone number, etc. Facebook takes the data that you send to Facebook Custom Audiences and matches it to the users that are on Facebook to enable these use cases.
@@ -66,14 +52,11 @@ Facebook Custom Audiences allows you to efficiently run several marketing and ad
6652

6753
3. **Re-targeting Audiences.** 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.
6854

69-
> note ""
70-
> **Note**: Re-targeting can also mean targeting anonymous visitors (those with no known personally identifiable information, such as email). The Personas Facebook Custom Audiences Integration feature for this use case is currently in beta. See below.
71-
7255
## Use Cases - Anonymous Users (Facebook Pixel support only)
7356

7457
Sometimes, users visit your website and perform high-intent activities such as looking at a product or pricing page multiple times, but they don't convert (buy), and they don't provide any personally identifiable information so you can contact them.
7558

76-
Facebook offers the Facebook Pixel, which allows you to retarget these types of anonymous users with advertising. This works by identifying users based on a cookie set in their browser. You can create a Website Custom Audience in Facebook for this use case. Segment today does not provide a way to sync audiences of anonymous users from Personas to Facebook to automatically create one of these Website Custom Audiences, though this feature is currently under development.
59+
Facebook offers the Facebook Pixel, which allows you to retarget these types of anonymous users with advertising. This works by identifying users based on a cookie set in their browser. You can create a Website Custom Audience in Facebook for this use case.
7760

7861
## How it works
7962

@@ -97,17 +80,17 @@ Facebook offers the Facebook Pixel, which allows you to retarget these types of
9780
- Go to your Personas Space in your Segment Workspace.
9881
- Go to the Destinations tab and click “Add Destination”.
9982
- Select the Personas Facebook Custom Audiences option, and click **Configure Personas Facebook Custom Audiences**.
100-
- Authorize Facebook Ads and select a Facebook account id to sync to.
83+
- Authorize Facebook Ads and select a Facebook account ID to sync to.
10184

102-
### 2. Create an audience in Segment & connect to Facebook
85+
### 2. Create an audience in Segment Personas & connect to Facebook
10386

10487
- Go to the Audience Builder in Personas and create a new Audience with your desired event and trait criteria.
10588
- Go to your Personas space, and select the Facebook destination you added to connect the audience to Facebook.
10689
- Give the audience a name and description, and click **Create**.
10790
- Your audience starts syncing from Personas to Facebook Ads.
10891

10992
> note ""
110-
> **Note**: if you change the name of the audience in Segment, it will not be reflected in Facebook
93+
> **Note**: If you change the name of the audience in Personas, it will not be reflected in Facebook.
11194
11295
### 3. Verify that the audience appears in Facebook
11396

@@ -119,13 +102,12 @@ Once created, the audience should be available in Facebook in ten minutes unless
119102
![](images/fb_ca_final.png)
120103

121104

122-
123-
## Public Preview Feature: Additional traits matching
105+
## Additional Traits Matching
124106

125107
> note ""
126-
> This feature is in Public Preview and usage is subject to the terms contained in the [First Access and Beta Preview Terms](https://segment.com/legal/first-access-beta-preview/). If you would like access, contact your CSM or email us at [[email protected]](mailto:[email protected]).
108+
> This feature is in Public Preview and usage is subject to the terms contained in the [First Access and Beta Preview Terms](https://segment.com/legal/first-access-beta-preview/){:target="_blank"}. For access, contact your CSM or email Segment at [[email protected]](mailto:[email protected]).
127109
128-
Previously, Segment only sent email and mobile ids to Facebook. A new beta feature can send an expanded list of identifiers or traits to Facebook, so that Facebook can try to use these additional datapoints to match to their user profiles. If you have this feature enabled and implemented any of these traits in your Segment tracking, Personas can send this data to Facebook. Segment can now also sync multiple emails if the profile contains more than one. Additionally as part of this feature, Segment hashes fields before sending them downstream to Facebook, if required. (See the table below for hashing requirements.) Please note that the trait data implemented in your Segment tracking must match the naming convention and format specified in the table below, otherwise we are not able to send it to Facebook.
110+
Previously, Segment only sent email and mobile IDs to Facebook. A new beta feature can send an expanded list of identifiers or traits to Facebook, so that Facebook can try to use these additional datapoints to match to their user profiles. If you have this feature enabled and implemented any of these traits in your Segment tracking, Personas can send this data to Facebook. Segment can now also sync multiple emails if the profile contains more than one. Additionally as part of this feature, Segment hashes fields before sending them downstream to Facebook, if required. (See the table below for hashing requirements.) Please note that the trait data implemented in your Segment tracking must match the naming convention and format specified in the table below, otherwise we are not able to send it to Facebook.
129111

130112

131113
| **Name** | **Trait Key formats supported** | **Facebook Keys** | **FB Hashing Required** | **FB Guidelines** |
@@ -148,17 +130,15 @@ Previously, Segment only sent email and mobile ids to Facebook. A new beta featu
148130

149131
### Not seeing an audience in Facebook
150132

151-
Make sure you authorized Facebook and selected the correct account id.
133+
Make sure you authorized Facebook and selected the correct account ID.
152134

153135
### Audience size smaller than expected
154136

155-
Segment sends lists of users with identifiers that Facebook supports to Facebook. The matching logic itself occurs within Facebook. Facebook is more likely to be able to match a user profile if you track as many identifiers as possible, including email, mobile advertising identifiers (IDFA, Google advertising id), and others. If Facebook is unable to identify users based on the data that you provide, then the match rate will be low.
137+
Segment sends lists of users with identifiers that Facebook supports to Facebook. The matching logic itself occurs within Facebook. Facebook is more likely to be able to match a user profile if you track as many identifiers as possible, including email, mobile advertising identifiers (IDFA, Google advertising ID), and others. If Facebook is unable to identify users based on the data that you provide, then the match rate will be low.
156138

157-
Note that emails must be in a plaintext format. Facebook also provides these guidelines for the emails that you send to them: Trim leading, trail whitespace, and convert all characters to lowercase.
139+
For example, many B2B SaaS businesses have users that sign up for their products with a work email address, like `[email protected]`. However, most Facebook users sign up for Facebook with a personal email only, like `[email protected]`. If you only provide the work email address, and no other identifiers, then Facebook can't match your user to the Jane Doe Facebook profile. This is the case for all identifiers - Facebook must have the identifier somewhere in a user's profile, or else they can't match on it.
158140

159-
For example: many B2B SaaS business have users that sign up for their products with a work email address, like `[email protected]`. However, most Facebook users sign up for Facebook with a personal email only, like `[email protected]`. If you only provide the work email address, and no other identifiers, then Facebook can't match your user to the Jane Doe Facebook profile. This is the case for all identifiers: Facebook must have the identifier somewhere in a user's profile, or else they can't match on it.
141+
Please note, emails must be in a plain text format. Facebook also provides these guidelines for the emails that you send to them: trim leading, trail whitespace, and convert all characters to lowercase.
160142

161143
### Do you support LTV audiences?
162-
Facebook has a feature called [value-based audiences](https://developers.facebook.com/docs/marketing-api/audiences/guides/value-based-lookalike-audiences/) where you can send an additional field like LTV, to tell Facebook how to optimize their advertising based on a customer's value.
163-
164-
Personas does not currently support this feature. If this is important to you, let us know at [[email protected]](mailto:[email protected]).
144+
Facebook has a feature called [value-based audiences](https://developers.facebook.com/docs/marketing-api/audiences/guides/value-based-lookalike-audiences/){:target="_blank"} where you can send an additional field like LTV, to tell Facebook how to optimize their advertising based on a customer's value. Personas does not currently support this feature.

0 commit comments

Comments
 (0)