Skip to content

Commit 8e085dd

Browse files
varadarajan-twvaradarajan-tw
committed
Facebook Custom Audiences update
1 parent 7a8d785 commit 8e085dd

File tree

1 file changed

+34
-6
lines changed
  • src/connections/destinations/catalog/actions-facebook-custom-audiences

1 file changed

+34
-6
lines changed

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

Lines changed: 34 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -16,22 +16,23 @@ hide_action:
1616

1717
Deliver effective Facebook Ads campaigns by defining and syncing [custom audiences](https://developers.facebook.com/docs/marketing-api/audiences/guides/custom-audiences){:target="_blank”} to power ad suppression, acquisition (using lookalikes), retargeting, and more.
1818

19-
This destination sends audiences, or lists of users, from your data warehouse to Facebook Custom Audiences using Reverse ETL. Syncs can add or remove users from your Facebook Custom Audiences as records are created, updated, or deleted in your warehouse.
20-
21-
> info "This destination only supports Reverse ETL sources"
22-
> This destination only supports [Reverse ETL sources](/docs/connections/reverse-etl/#what-warehouse-data-sources-does-segment-support). To connect Facebook Custom Audiences to Twilio Engage, use the [Facebook Custom Audiences](/docs/connections/destinations/catalog/personas-facebook-custom-audiences/) destination.
19+
This destination sends audiences, or lists of users, to Facebook Custom Audiences. You can connect this destination to Reverse ETL sources to sync data from your warehouse, or to Engage Audiences to sync computed audiences.
2320

2421
## Getting started
2522

2623
### Prerequisites
27-
- A Reverse ETL source already set up. If you don't yet have a Reverse ETL source, follow the instructions in Segment's [Reverse ETL documentation](/docs/connections/reverse-etl/#getting-started). Segment recommends setting an [External ID](#sync-audience) as the primary key for your Reverse ETL model, as you'll need an External ID to remove users from your custom audiences.
24+
25+
- A source already set up:
26+
- For Reverse ETL: If you don't yet have a Reverse ETL source, follow the instructions in Segment's [Reverse ETL documentation](/docs/connections/reverse-etl/#getting-started). Segment recommends setting an [External ID](#sync-audience) as the primary key for your Reverse ETL model, as you'll need an External ID to remove users from your custom audiences.
27+
- For Engage Audiences: An [Engage Audience](/docs/engage/audiences/) configured which you can connect to this destination.
2828
- A Facebook account with [ads_management](https://developers.facebook.com/docs/permissions#ads_management){:target="_blank”} permissions for the target Facebook Ad Account(s). The Facebook Ad Account(s) must also be associated with a [Facebook Business Account](https://www.facebook.com/business/help/407323696966570?id=649869995454285){:target="_blank”}.
2929
- Ensure that the user connecting to the destination using OAuth has at least an *Advertiser* or *Admin* role on the ad account. To manage permissions and roles for an ad account, reference [Facebook's documentation](https://www.facebook.com/business/help/186007118118684?id=829106167281625){:target="_blank"}.
3030

3131
### Connect to Facebook Custom Audiences
32+
3233
1. From your Segment app, navigate to **Catalog > Destinations** and search for "Facebook Custom Audiences (Actions)".
3334
2. Select the Facebook Custom Audiences (Actions) destination and click **Add destination**.
34-
3. Select the Reverse ETL source you'd like to connect to your Facebook Custom Audiences (Actions) Destination and click **Next**.
35+
3. Select the source you'd like to connect to your Facebook Custom Audiences (Actions) Destination and click **Next**.
3536
4. Enter a name for your destination and click **Create destination**.
3637
5. Navigate to your destination's settings page and click **Connect to...** to authenticate with Facebook.
3738
6. Return to the Segment app and enter your Advertiser Account ID. See Facebook's [Find your Facebook ad account ID number](https://www.facebook.com/business/help/1492627900875762){:target="_blank”} documentation for more information.
@@ -123,6 +124,33 @@ Segment automatically hashes any of the following fields that are not already SH
123124
* Gender
124125

125126

127+
## Additional Traits Matching
128+
129+
> info ""
130+
> 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]).
131+
132+
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 data points to match to their user profiles. If you have this feature enabled and implemented any of these traits in your Segment tracking, the Facebook Custom Audiences (Actions) 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.) Note that the trait data implemented in your Segment tracking must match the naming convention and format specified in the table below, otherwise Segment can't send it to Facebook.
133+
134+
> success ""
135+
> Visit Segment's [Trait Enrichment](/docs/engage/trait-activation/trait-enrichment/) to learn more.
136+
137+
138+
| **Name** | **Trait Key formats supported** | **Facebook Keys** | **FB Hashing Required** | **FB Guidelines** |
139+
| Email | email | EMAIL | Yes (Segment does the hashing for you. In case you are *already* hashing emails, emails will get sent to Facebook double-hashed. Facebook will still match on double-hashed emails, but this is *not* recommended.) | Trim leading, trail whitespace, and convert all characters to lowercase. |
140+
| Mobile ID | mobile_id | MADID | No | Use all lowercase, keep hyphens. |
141+
| First Name | first_name<br>firstname<br>firstName<br>first | FN | Yes | Use `a`-`z` only. Lowercase only, no punctuation. Special characters in UTF8 format. |
142+
| Last Name | last_name<br>lastname<br>lastName<br>last | LN | Yes | Use `a`-`z` only. Lowercase only, no punctuation. Special characters in UTF8 format. |
143+
| Phone | phone<br>phone_number<br>phonenumber<br>phoneNumber | PHONE (+12023095976) | Yes | Remove symbols, letters, and any leading zeroes. You should prefix the country code if `COUNTRY` field is not specified. |
144+
| Gender | gender<br>gen | GEN | Yes | Use these values: `m` for male and `f` for female. |
145+
| Birth Year | birth_year | DOBY | Yes | Use the YYYY format from 1900 to current year. |
146+
| Birth Month | birth_month | DOBM | Yes | Use the MM format: `01` to `12`. |
147+
| Birth Day | birthday<br>birth_day<br>date_of_birth<br>DOB<br>dateOfBirth | DOBD | Yes | Use the DD format: `01` to `31`. |
148+
| State | state<br>address_state | ST | Yes | Use the 2-character ANSI abbreviation code, lowercase. Normalize states outside U.S. in lowercase, no punctuation, no special characters, no white space. |
149+
| City | city<br>address_city | CT | Yes | Use `a`-`z` only. Lowercase only, no punctuation, no special characters, no white space. |
150+
| Zipcode | zip<br>zip_code<br>zipCode | ZIP | Yes | Use lowercase, no white space. Use only the first 5 digits for U.S. Use Area/District/Sector format for the UK. |
151+
| Country | country_code<br>countryCode | COUNTRY | Yes | Use 2-letter country codes (lowercase) in ISO 3166-1 alpha-2. |
152+
153+
126154
## FAQs and troubleshooting
127155

128156
### Audience not creating and/or existing audience list not populating

0 commit comments

Comments
 (0)