diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index 0b9b0108a8..1072a02e0f 100644 --- a/src/_data/catalog/destination_categories.yml +++ b/src/_data/catalog/destination_categories.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination categories last updated 2024-08-08 +# destination categories last updated 2024-08-09 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml index 5bc0e2fa95..d543880451 100644 --- a/src/_data/catalog/destinations.yml +++ b/src/_data/catalog/destinations.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination data last updated 2024-08-08 +# destination data last updated 2024-08-09 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -30535,69 +30535,6 @@ items: convert_timestamp: true trigger: type = "page" partnerOwned: true -- id: 5c9ce8b88171a10001f9eefa - display_name: CustomerSuccessBox - name: CustomerSuccessBox - slug: customersuccessbox - hidden: false - endpoints: - - US - regions: - - us-west-2 - - eu-west-1 - url: connections/destinations/catalog/customersuccessbox - previous_names: - - CustomerSuccessBox - website: https://customersuccessbox.com - status: PUBLIC - categories: - - Customer Success - - Analytics - - Customer Success - - Performance Monitoring - - Surveys - logo: - url: https://cdn-devcenter.segment.com/e9d17e14-057b-45f9-b4b6-f68c16cbbae1.svg - mark: - url: https://cdn-devcenter.segment.com/abba03a0-aa1a-4858-8467-ee36bb1d15dc.svg - methods: - track: true - identify: true - group: true - alias: false - screen: false - page: true - platforms: - browser: true - mobile: true - server: true - warehouse: false - cloudAppObject: false - components: [] - browserUnbundlingSupported: false - browserUnbundlingPublic: true - replay: false - connection_modes: - device: - web: false - mobile: false - server: false - cloud: - web: true - mobile: true - server: true - settings: - - name: apiKey - type: string - defaultValue: '' - description: >- - Settings (Gear icon) > Developer Console > API Key > API key for POST - request - required: true - label: API Key - actions: [] - presets: [] - partnerOwned: true - id: 5e1f879beef894b09f7a0ba9 display_name: Data Lakes name: Data Lakes @@ -36584,6 +36521,365 @@ items: allowNull: false presets: [] partnerOwned: false +- id: 645d5fc12eb891cf0a93fe4b + display_name: Facebook Custom Audiences (Actions) + name: Facebook Custom Audiences (Actions) + slug: facebook-custom-audiences-actions + hidden: false + endpoints: + - US + regions: + - us-west-2 + - eu-west-1 + url: connections/destinations/catalog/facebook-custom-audiences-actions + previous_names: + - Facebook Custom Audiences (Actions) + website: >- + https://developers.facebook.com/docs/marketing-api/audiences/guides/custom-audiences + status: PUBLIC_BETA + categories: [] + logo: + url: https://cdn-devcenter.segment.com/874bb0d4-48eb-4987-b4c8-0a766fa7816b.svg + mark: + url: https://cdn-devcenter.segment.com/886257bc-9a40-4d4e-be23-016236498415.svg + methods: + track: true + identify: true + group: true + alias: true + screen: false + page: true + platforms: + browser: false + mobile: false + server: false + warehouse: true + cloudAppObject: false + components: [] + browserUnbundlingSupported: false + browserUnbundlingPublic: false + replay: false + connection_modes: + device: + web: false + mobile: false + server: false + cloud: + web: false + mobile: false + server: false + settings: + - name: retlAdAccountId + type: string + defaultValue: '' + description: >- + Your advertiser account id. Read + [more](https://www.facebook.com/business/help/1492627900875762). + required: true + label: Advertiser Account ID + actions: + - id: 99Dj24PD8pAweMvTnM8vD8 + name: Sync Reverse ETL + slug: syncRetl + description: Reverse ETL action. + platform: CLOUD + hidden: false + defaultTrigger: null + fields: + - id: 7uGwzgBjXeVgg8jDrA4NSC + sortOrder: 0 + fieldKey: placeholder + label: Placeholder + type: STRING + description: Placeholder + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + hidden: false + - id: eG6ydbfKbfJvQZ8gQpgakz + name: Sync Engage + slug: syncEngage + description: Engage action. + platform: CLOUD + hidden: false + defaultTrigger: null + fields: + - id: k6z1m4C1fJUUndC6jpapkd + sortOrder: 0 + fieldKey: placeholder + label: Placeholder + type: STRING + description: Placeholder + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + hidden: false + - id: 3JEx23g4qgFzSECyYopNA4 + name: Add + slug: add + description: This action is in charge of adding elements to your audience. + platform: CLOUD + hidden: false + defaultTrigger: null + fields: [] + - id: p74MiTEFmUUeoC7SKcT7Ri + name: Remove + slug: remove + description: This action is in charge of removing elements to your audience. + platform: CLOUD + hidden: false + defaultTrigger: null + fields: [] + - id: tudPdqMVaETyBsXoipagwm + name: Sync Audience + slug: sync + description: Sync data to Facebook Custom Audiences. + platform: CLOUD + hidden: false + defaultTrigger: null + fields: + - id: idVhSY1Mr3GbYcT9y6kjb9 + sortOrder: 0 + fieldKey: externalId + label: External ID + type: STRING + description: >- + Your company’s custom identifier for this user. This can be any unique + ID, such as loyalty membership IDs, user IDs, and external cookie IDs. + placeholder: '' + required: true + multiple: false + choices: null + dynamic: false + allowNull: false + - id: modgrBhfKSPAmL4gPMXrg6 + sortOrder: 1 + fieldKey: email + label: Email + type: STRING + description: 'User’s email (ex: foo@bar.com)' + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: qdkE5rdhsu8cszpSDPdWQr + sortOrder: 2 + fieldKey: phone + label: Phone + type: STRING + description: >- + User’s phone number, including country code. Punctuation and spaces are + ok (ex: 1-234-567-8910 or +44 844 412 4653) + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: eWMuEbVFNsowEVEKv4GuG + sortOrder: 3 + fieldKey: country + label: Country + type: STRING + description: User’s country. Use 2-letter country codes in ISO 3166-1 alpha-2 format. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: rRkVQnCeFbRdcSeczLCANw + sortOrder: 4 + fieldKey: birth + label: Date of Birth + type: OBJECT + description: >- + User’s date of birth. Include as many fields as possible for better + match rates (ex: year = YYYY, month = MM, day = DD) + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 3CKH9LVTPc34AeZx6YYwNk + sortOrder: 5 + fieldKey: name + label: Name + type: OBJECT + description: >- + User’s name. Include as many fields as possible for better match rates. + Use a-z only. No punctuation. Special characters in UTF-8 format + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: wWqSP5wwL8sUbBquR3SJUG + sortOrder: 6 + fieldKey: city + label: City + type: STRING + description: User’s city. Use a-z only. No punctuation. No special characters. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: rs2FpA71nZNskSZ9fBUkC2 + sortOrder: 7 + fieldKey: state + label: State + type: STRING + description: >- + User’s state. Use the 2-character ANSI abbreviation code, Normalize + states outside the US with no punctuation and no special characters. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: gT2vBfC9mqRSU3NAGJJDer + sortOrder: 8 + fieldKey: zip + label: Postal Code + type: STRING + description: >- + User’s postal code. For the US, use only the first 5 digits. For the UK, + use the Area/District/Sector format. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 4giu733gkMRdsKBnXLcDsD + sortOrder: 9 + fieldKey: gender + label: Gender + type: STRING + description: User’s gender (m for male, f for female) + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: p91kYAhWJwS9axfGGvmwvz + sortOrder: 10 + fieldKey: mobileAdId + label: Mobile Advertising ID + type: STRING + description: >- + User’s Apple IDFA, Android Ad ID, or Facebook app scoped ID. Keep + hyphens (ex: AB1234CD-E123-12FG-J123) + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: rGL5y5Rbzmpz57QBUhnX8 + sortOrder: 11 + fieldKey: appId + label: App ID + type: STRING + description: The app ID of the user. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 7VLJMbYczypD1XdrYHnJZ4 + sortOrder: 12 + fieldKey: pageId + label: Page ID + type: STRING + description: The page ID of the user. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: jYj1UxYzS5aJNU2Ue2gakK + sortOrder: 15 + fieldKey: operation + label: Create a new custom audience or connect to an existing one? + type: STRING + description: >- + Choose to either create a new custom audience or use an existing one. If + you opt to create a new audience, we will display the required fields + for audience creation. If you opt to use an existing audience, a + drop-down menu will appear, allowing you to select from all the custom + audiences in your ad account. + placeholder: '' + defaultValue: create + required: false + multiple: false + choices: + - label: Create New Audience + value: create + - label: Connect to Existing Audience + value: existing + dynamic: false + allowNull: false + - id: 2KMUXqzqudDytGbcBz2iwP + sortOrder: 16 + fieldKey: audienceName + label: Audience Creation Name + type: STRING + description: The name of the audience in Facebook. + placeholder: '' + defaultValue: 'TODO: Model Name by default' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 6VBmtsRbVxHVM61LtnFVwX + sortOrder: 17 + fieldKey: existingAudienceId + label: Existing Audience ID + type: STRING + description: The ID of the audience in Facebook. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: true + allowNull: false + - id: q6eYyJGaCYcPSHeZPpaK5x + sortOrder: 18 + fieldKey: retlOnMappingSave + label: Select or create an audience in Facebook + type: OBJECT + description: >- + When saving this mapping, Segment will either create a new audience in + Facebook or connect to an existing one. To create a new audience, enter + the name of the audience. To connect to an existing audience, select the + audience ID from the dropdown. + defaultValue: null + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + hidden: false + presets: [] + partnerOwned: false - id: 58ae54dc70a3e552b95415f6 display_name: Facebook Offline Conversions name: Facebook Offline Conversions @@ -91956,7 +92252,7 @@ items: hidden: false defaultTrigger: type = "identify" fields: - - id: jbBqXRtanwZYoC8QUEWkC3 + - id: oiXto9Ga3x9ZjmnVCKQg3m sortOrder: 0 fieldKey: contactKey label: Contact Key @@ -91982,7 +92278,7 @@ items: hidden: false defaultTrigger: null fields: - - id: hby2ZH7ZqfnpW2uCbNY68v + - id: aLcHAWVXuPT2m6EqqaooGd sortOrder: 0 fieldKey: eventDefinitionKey label: Event Definition Key @@ -91996,7 +92292,7 @@ items: choices: null dynamic: false allowNull: false - - id: rCD3YUG5KATQdxzHjQ3XRN + - id: ffKH5kYww6CaBjNgx2Ex8A sortOrder: 1 fieldKey: contactKey label: Contact Key @@ -92010,7 +92306,7 @@ items: choices: null dynamic: false allowNull: false - - id: js28TMXuNjJ44KcBRu3jrH + - id: xbtTMVBmWPAPHDLJEhhsfp sortOrder: 2 fieldKey: data label: Event Data @@ -92037,7 +92333,7 @@ items: hidden: false defaultTrigger: null fields: - - id: 9VhszT3D143zJvwyJMbq1h + - id: 2LSnRWWZaiixnT3yp9LhVD sortOrder: 0 fieldKey: key label: Data Extension Key @@ -92052,7 +92348,7 @@ items: choices: null dynamic: false allowNull: false - - id: 4x2dDqZKE86pcMjFCYMNi5 + - id: 2BhFd19YmCQGWdNETqaKD1 sortOrder: 1 fieldKey: id label: Data Extension ID @@ -92067,7 +92363,7 @@ items: choices: null dynamic: false allowNull: false - - id: rXNdhXufxWaxfD2bXu5keL + - id: nKnByfL5D8dYQcKksvGUBu sortOrder: 2 fieldKey: keys label: Data Extension Primary Keys @@ -92084,7 +92380,7 @@ items: choices: null dynamic: false allowNull: false - - id: tuRCxZR6DpGVQMi4ucGRnt + - id: kAhwakJxjyE5zdpAZZ7kK4 sortOrder: 3 fieldKey: values label: Data Extension Fields @@ -92102,7 +92398,7 @@ items: choices: null dynamic: false allowNull: false - - id: 9bhfGtfF6kCh91zP9reRiv + - id: 3aYydqS6fdHTQGYLEiNXAZ sortOrder: 4 fieldKey: enable_batching label: Batch data to SFMC @@ -92125,7 +92421,7 @@ items: hidden: false defaultTrigger: type = "identify" fields: - - id: 6D9UWxEDVoz64MQthmtxB5 + - id: guKt4p6edmrdqcmAdg1LCR sortOrder: 0 fieldKey: key label: Data Extension Key @@ -92140,7 +92436,7 @@ items: choices: null dynamic: false allowNull: false - - id: 2RGiTR7vywkDrKwkLc5o4J + - id: 4ZtgpCXSPTFM146NRzarz9 sortOrder: 1 fieldKey: id label: Data Extension ID @@ -92155,7 +92451,7 @@ items: choices: null dynamic: false allowNull: false - - id: wFmxVrAQmLhuaaFcb7SssK + - id: 9nWih4PiFHHY4M9qykDRan sortOrder: 2 fieldKey: keys label: Data Extension Primary Keys @@ -92175,7 +92471,7 @@ items: choices: null dynamic: false allowNull: false - - id: pRrzdDwpUDPM8352gc9LyV + - id: kxvdgvYwVJcYvw9XETmQv1 sortOrder: 3 fieldKey: values label: Contact Fields @@ -92192,7 +92488,7 @@ items: choices: null dynamic: false allowNull: false - - id: aTSh3vLTWTmXeyQNyZUvFW + - id: 5sHM4HiXoYJFF4QWrHq6Mh sortOrder: 4 fieldKey: enable_batching label: Batch data to SFMC diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml index bece77674e..ee620ce6a6 100644 --- a/src/_data/catalog/destinations_private.yml +++ b/src/_data/catalog/destinations_private.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination data last updated 2024-08-08 +# destination data last updated 2024-08-09 items: - id: 54521fd925e721e32a72eee1 display_name: Pardot diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index ae136315b4..c2c4401d85 100644 --- a/src/_data/catalog/source_categories.yml +++ b/src/_data/catalog/source_categories.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# source categories last updated 2024-08-08 +# source categories last updated 2024-08-09 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml index 71e6fd052e..c78e3930e3 100644 --- a/src/_data/catalog/sources.yml +++ b/src/_data/catalog/sources.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# sources last updated 2024-08-08 +# sources last updated 2024-08-09 items: - id: 8HWbgPTt3k display_name: .NET diff --git a/src/_data/sidenav/strat.yml b/src/_data/sidenav/strat.yml index 752c18576e..85466d40f1 100644 --- a/src/_data/sidenav/strat.yml +++ b/src/_data/sidenav/strat.yml @@ -44,6 +44,8 @@ sections: title: Facebook Ads cloud source - path: /connections/sources/catalog/cloud-apps/facebook-lead-ads title: Facebook Lead Ads cloud source + - path: /connections/destinations/catalog/actions-facebook-custom-audiences + title: Facebook Custom Audiences (Actions) destination - slug: google diff --git a/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md b/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md new file mode 100644 index 0000000000..5cbefea268 --- /dev/null +++ b/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md @@ -0,0 +1,136 @@ +--- +title: Facebook Custom Audiences (Actions) +id: 645d5fc12eb891cf0a93fe4b +beta: true +strat: facebook +hide_action: + - id: 3JEx23g4qgFzSECyYopNA4 + name: "Add" + - id: 99Dj24PD8pAweMvTnM8vD8 + name: "Sync Reverse ETL" + - id: eG6ydbfKbfJvQZ8gQpgakz + name: "Sync Engage" + - id: p74MiTEFmUUeoC7SKcT7Ri + name: "Remove" +--- + +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. + +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. + +> info "This destination only supports Reverse ETL sources" +> 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. + +## Getting started + +### Prerequisites +- 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](#destination-settings) as the primary key for your Reverse ETL model, as you'll need an External ID to remove users from your custom audiences. +- A Facebook account with [ads_management](https://developers.facebook.com/docs/permissions#ads_management){:target="_blank”} permissions for the target Facebook Ads Account(s). + +### Connect to Facebook Custom Audiences +1. From your Segment app, navigate to **Catalog > Destinations** and search for "Facebook Custom Audiences (Actions)". +2. Select the Facebook Custom Audiences (Actions) destination and click **Add destination**. +3. Select the Reverse ETL source you'd like to connect to your Facebook Custom Audiences (Actions) Destination and click **Next**. +4. Enter a name for your destination and click **Create destination**. +5. Navigate to your destination's settings page and click **Connect to...** to authenticate with Facebook. +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. +7. Save the changes you've made and **Enable** your destination. + + +### Add users to a Custom Audience + +After you've connected your Facebook Custom Audiences destination to Segment, set up a mapping that adds users to a new or existing Custom Audience. + +1. Navigate to **Connections > Sources** and select your Reverse ETL source. +2. On the Models page, select the model you'd like to use and click **Add Mapping**. +3. Select the Facebook Custom Audience (Actions) destination and the Sync Audience action, then click **Create Mapping**. +4. Enter a descriptive name for your mapping. Segment recommends a name that includes both the audience name and sync mode, for example, `Loyalty Users (Add)`. +5. Under **Select record to map and send**, select **Added or updated records**. The Added or updated records sync mode both adds new records and attempts to re-add any updated records to the custom audience. Adding updated records to your destination enables better match rates as more user identifiers are added to the source model over time. + +> warning "Added or updated records is the only supported additive sync mode" +> Selecting any other sync mode might lead to sync failures with the Facebook Custom Audiences (Actions) destination. + +
    +
  1. + Set how often your model syncs by setting the [Sync schedule](/docs/connections/reverse-etl/#step-4-create-mappings). +
    2. +
  2. + Select or create an audience in Facebook to sync your data with. Click the **Select or create audience in Facebook** button to save the audience ID to your mapping. +
    3. +
  3. + Map your model columns to the appropriate Facebook Custom Audience parameters. For more context about data formatting, see the [Sync Audience](#sync-audience) and [Data processing](#data-processing) documentation. + +
    4. +
  4. + Send a test record. If successful, you should see a 200 response in Segment and one added record to your custom audience. To verify that the record was successfully added to your custom audience, open Facebook Ads Manager and navigate to **Audiences > {Audience Name} > History**. +
    5. +
  5. + Click **Save Mapping** and enable the mapping. +
    6. +
+ +### Remove users from a Custom Audience + +1. Navigate to **Connections > Sources** and select your Reverse ETL source. +2. On the Models page, select the model you'd like to use and click **Add Mapping**. +3. Select the Facebook Custom Audience (Actions) destination and the Sync Audience action, then click **Create Mapping**. +4. Enter a descriptive name for your mapping. Segment recommends a name that includes both the audience name and sync mode, for example, `Loyalty Users (Remove)`. +5. Under **Select record to map and send**, select **Deleted records**. The Deleted records sync mode removes any records from your custom audience that you deleted from your source model. +6. Set how often your model syncs by setting the [Sync schedule](/docs/connections/reverse-etl/#step-4-create-mappings). +7. Select or create an audience in Facebook to sync your data with. Click the **Select or create audience in Facebook** button to save the audience ID to your mapping. +8. Map your model columns to the appropriate Facebook Custom Audience parameters. Only the External ID is required. When a record is deleted from your source model, only the model primary key is sent to the mapping; other columns from your source model are not sent. Segment recommends using the External ID as your primary key in your source model. +9. Send a test record. If successful, you should see a `200` response in Segment and one record removed from your custom audience. To verify that the record was successfully removed from your custom audience, open Facebook Ads Manager and navigate to **Audiences > {Audience Name} > History**. +10. Click **Save Mapping** and enable the mapping. + +{% include components/actions-fields.html %} + +## Data processing + +To improve match rates, Segment built in normalization and hashing for common fields to align with [Facebook’s recommended best practices](https://developers.facebook.com/docs/marketing-api/audiences/guides/custom-audiences/#hash){:target="_blank”}. + +### Normalization +Segment automatically strips whitespace and converts the following fields to lowercase: +* Email +* First name +* Last name +* First initial +* City +* State +* Country + +Segment normalizes the Phone field by removing any non-numeric symbols, whitespace, and leading zeroes. + +### Hashing +Facebook requires you to hash all PII before sending it to the Facebook Conversions API. + +Segment automatically hashes any of the following fields that are not already SHA256 hashed at egress: +* Email +* Phone +* First name +* Last name +* First initial +* City +* State +* Postal code +* Country +* Year of birth +* Month of birth +* Day of birth +* Gender + + +## FAQs and troubleshooting + +### Audience not creating and/or existing audience list not populating +If you’re unable to create a new audience or select existing audiences while creating a mapping, this might be due to an authentication error. Verify that you've authenticated with Facebook under Destination Settings and that the Facebook user that authenticated with Segment can access your Advertiser Account ID. + +### Audience size smaller than expected +Segment sends lists of users with the identifiers you’ve mapped from your source model. 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, like 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. + +As an example, many B2B SaaS businesses have users that sign up for their products with a work email address, like jane.doe@segment.com. However, most Facebook users sign up for Facebook with a personal email only, like janedoe@gmail.com. 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. + +### Do you support value-based lookalikes? +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.