Skip to content

Commit 83a0763

Browse files
committed
[netlify-build]
1 parent 6fa6def commit 83a0763

File tree

1 file changed

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

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,4 +125,4 @@ Segment sends lists of users with the identifiers you’ve mapped from your sour
125125
As an 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 Facebook with 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 they can’t match on it.
126126

127127
### Do you support value-based lookalikes?
128-
While Facebook has a feature called value-based lookalikes, where you can send an additional field like LTV to optimize campaigns based on a customer’s value, there is currently no way to sync LTV data to a value-based lookalike using the Facebook Custom Audiences (Actions) destination.
128+
While Facebook has a feature called value-based lookalikes, where you can send an additional field like LTV to optimize campaigns based on a customer’s value, there is currently no way to sync LTV data to a value-based lookalike using the Facebook Custom Audiences (Actions) destination.

0 commit comments

Comments
 (0)