Skip to content

Commit 6f22c93

Browse files
authored
Update index.md - remove beta refs for trait enrichment in fb additional trait matching
1 parent ad8a285 commit 6f22c93

File tree

1 file changed

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

1 file changed

+0
-3
lines changed

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

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -107,9 +107,6 @@ Once created, the audience should be available in Facebook in ten minutes unless
107107

108108
## Additional Traits Matching
109109

110-
> info ""
111-
> 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 [friends@segment.com](mailto:friends@segment.com).
112-
113110
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.
114111

115112
> success ""

0 commit comments

Comments
 (0)