Meta node consent data issue

Good morning,

I’m having problems with the Facebook Lead Ads trigger, as the node’s response isn’t returning the ‘consent to receive marketing communications’ data from the Meta form. Could you tell me why?

Hi Lorenzo,

Thank you for reaching out.

We checked the webhook data being received from Meta and found that the "Consent to receive marketing communications" field is not included in the payload returned by the Facebook Lead Ads API. We are currently receiving only the fields that Meta sends, such as first name, last name, email, phone number, city, province, and your custom form fields.

Since the consent field is not present in Meta's API response, Pabbly Connect is unable to retrieve or display it.

If you believe this field should be available, we recommend verifying whether Meta exposes it through the Lead Ads API for your form type or contacting Meta Support for clarification.

Please let us know if you have any further questions—we'll be happy to assist.

Hi Lorenzo,

Thank you for reaching out.

We checked the webhook data being received from Meta and found that the "Consent to receive marketing communications" field is not included in the payload returned by the Facebook Lead Ads API. We are currently receiving only the fields that Meta sends, such as first name, last name, email, phone number, city, province, and your custom form fields.

Since the consent field is not present in Meta's API response, Pabbly Connect is unable to retrieve or display it.

If you believe this field should be available, we recommend verifying whether Meta exposes it through the Lead Ads API for your form type or contacting Meta Support for clarification.

Please let us know if you have any further questions—we'll be happy to assist.

Yes, the Meta documentation states that the data can be retrieved here: GET https://graph.facebook.com/<API_VERSION>/<LEADGEN_ID>?fields=custom_disclaimer_responses. Could you implement this in the trigger on Pabbly?

Hello Lorenzo,

Thank you for sharing the endpoint with us.

Please note that this endpoint is already implemented in the backend of our Facebook Lead Ads trigger. It is used to retrieve the available fields and their corresponding values from the lead data.

However, the specific field you're referring to (consent_to_receive_marketing_communications) does not appear to exist for the Lead Gen Form currently selected in your trigger.

To verify this further, we also tested the Get Lead Gen Form Details action, which retrieves the fields available in the selected Lead Gen Form. As shown in your screenshot, the API returns the following error:

(#100) Tried accessing nonexistent field (consent_to_receive_marketing_communications)

This indicates that Meta is not exposing this field for the selected form.

Could you please share a screenshot of your Lead Gen Form from Meta, clearly showing the "Consent to receive marketing communications" field? This will help us verify whether the field is configured in the form and investigate the issue further.

We look forward to your response.

Good morning,

Yes, this is the consent section of the form; there are two tick boxes – one is mandatory and the other is optional.

Hello Lorenzo,

Thank you for your patience.

We tested your use case by adding a Get Lead Details action immediately after the Facebook Lead Ads trigger in the workflow you shared. Using the custom_disclaimer_responses field, we were able to retrieve the consent responses successfully.

As shown in the attached screenshot:

• The mandatory consent is returned with its selected value.

• The optional consent is returned as an empty value when the user has not selected it.

This indicates that the consent information is available through the custom_disclaimer_responses field. You can use this field in your workflow to access the values of the consent checkboxes.

Please refer to the attached screenshot for a better understanding. If you need any assistance mapping these values in your workflow, feel free to let us know.