Skip to content

Commit 18369b3

Browse files
authored
Update index.md
1 parent c304573 commit 18369b3

File tree

1 file changed

+3
-3
lines changed
  • src/connections/destinations/catalog/personas-facebook-custom-audiences

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ Once created, the audience should be available in Facebook in ten minutes unless
109109
> info ""
110110
> 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"}{:target="_blank"}. For access, contact your CSM or email Segment at [[email protected]](mailto:[email protected]).
111111
112-
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, Engage 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 Segment can't send it to Facebook.
112+
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, Engage 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.
113113

114114
> success ""
115115
> Visit Segment's [Trait Enrichment](/docs/engage/trait-activation/trait-enrichment/) to learn more.
@@ -145,9 +145,9 @@ For example, many B2B SaaS businesses have users that sign up for their products
145145

146146
### Why are all of my audiences connected to Facebook failing with an 'Internal Error' message?
147147

148-
Most likely, this is due to your Facebook needing to be reauthorized, sometimes due to a password change. Please reauthorize the Facebook destination connection. If the error persists, please contact Segment Support.
148+
Most likely, this is due to your Facebook account needing to be reauthorized, sometimes due to a password change. Reauthorize the Facebook destination connection. If the error persists, contact Segment Support.
149149

150-
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.
150+
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.
151151

152152
### Do you support LTV audiences?
153153
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.

0 commit comments

Comments
 (0)