Skip to content

Commit f78780e

Browse files
Merge pull request #7192 from segmentio/joeynmq-patch-2
Add info about Customer Disclaimer Responses
2 parents 50bb5b3 + b90cc27 commit f78780e

File tree

2 files changed

+9
-1
lines changed

2 files changed

+9
-1
lines changed

src/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,15 @@ See the example below:
9696
}
9797
```
9898

99+
## Customer Disclaimer Responses
100+
101+
If you've selected any checkboxes on Facebook's Custom Disclaimer form, the `custom_disclaimer_responses` field is included in the data request sent to Segment. For more information, please refer to Facebook's [Retrieving Leads documentation](https://developers.facebook.com/docs/marketing-api/guides/lead-ads/retrieving#reading-custom-disclaimer-responses){:target="_blank”}.
102+
103+
Segment recommends updating the `checkbox_key` in your Facebook Lead Ads source settings to ensure that Segment accurately checks custom disclaimer responses. If no custom disclaimer checkboxes are selected, Segment does not forward lead information to the source.
104+
105+
If no `checkbox_key` is added to Segment's source settings, Segment sends lead information by default, regardless of your custom disclaimer selections.
106+
![A screenshot of the settings page for a Facebook Lead Ads source, with a red box around the Customer Disclaimer Responses setting.](images/customer-disclaimer-settings.png)
107+
99108
## Adding Destinations
100109

101110
Now that your Source is set up, you can connect it with destinations. 
@@ -140,7 +149,6 @@ Destinations that can be used with the Facebook Lead Ads Source:
140149

141150
Log into your downstream tools and check that your events are populating, and contain all of the properties you expect. If all your events and properties are not showing up, refer to the [Destination docs](/docs/connections/destinations/) for troubleshooting.
142151

143-
144152
## Troubleshooting
145153

146154
### No Data After Updating Credentials

0 commit comments

Comments
 (0)