Facebook / Instagram Lead Ads

Lead ads serve as the best way to run lead generation campaigns on Facebook and Instagram. Lead ads allow people to show their interest in a product or service by filling out a form in the ad with their details and allowing a business to follow up with them (which depends on the details you have. For instance, you cannot send an email without an email address).

Possible use cases:

  • Acquisition of retargeted lead ads
  • Acquisition of look-alike audiences
  • Custom questions for actionable queries (preferred appointment slot, shoe size, etc.)
  • Retargeting to target specific customers to gather additional information about them

If you want to read more about Facebook Lead Ads, you can access the official Facebook business webpage.

Combining Exponea with Facebook Lead Ads:

The advantage of using Exponea with Facebook Lead Ads is in utilizing typical Exponea functions which otherwise would not have been supported by Facebook.

  • Advanced segmentation or prediction from Exponea‚Äôs single customer view for Facebook Lead Ads pixel or custom audiences
  • A/B testing via Facebook Lead Ads pixel or custom audiences
    In other words, Leads will allow for an advanced segmentation of audience/customers, which can be used for further targeted campaigns.

Using Facebook Leads Correctly

For correct functionality, an instance needs to have a FB app set-up with correct permissions. For private instances this might not work unless the approval process is completed.

Step-by-Step Integration Guide:

First of all, the user needs to be both Project admin in Exponea and needs to be the admin for the Facebook page which uses the Facebook Lead Ads. Once this condition is met, follow these steps:

  • Go into data & assets -> integrations
  • Create a new Facebook Lead Ads integration
  • In the integration, authenticate with a Facebook login
  • Select the page to be used for gathering leads from the dropdown
  • OPTIONAL: Select the data mapping to assign leads to the correct ID
  • Click Save

Data Mapping

Note, that if you do not select data mapping (you leave the field blank), the program will generate a new anonymous cookie. However, if you choose to map program IDs, you can do it via email, phone, work email or work phone; all gathered via your customer responses. Therefore, we suggest to make all ID-mapped fields mandatory in your lead ads.

After the integration is saved, all leads from all lead ads for the specific page will be gathered as events into the project.

One page can be integrated only into one project.

Step-by-Step Campaign Setting Guide:

If you want to learn more about how to create forms to acquire leads and integrate the lead form data with your customer system, you can access the official Facebook E-learning Course..

Event structure

  • Copy all of the standard Lead Gen Form fields as event properties of the facebook_lead event with a type of standard_form.
  • Each custom question will be its own facebook_lead event with a type of custom_question. These events will have attributes question and answer respectively.
  • Copy form_name, form_id, page_name, page_id from integration.
  • There will be lead_id for each individual lead response.
  • Timestamp will be taken from created_time of a lead.
  • Customer mapping for ID will be done in the integration
  • Event type will be facebook_lead.

Example

  • type: "standard_form",
  • form_name: "My Form",
  • form_id: "333",
  • page_name: "My Page",
  • page_id: "111",
  • lead_id: "2739831366061736",
  • full_name: "Martin Mrkvicka",
  • email: "exponeaqateam@gmail.com",
  • phone_number: "+421444444444",
  • street_address: "Street 23",
  • date_of_birth: "03/26/1998",
  • job_title: "My job title",
  • company_name: "My company name",
  • gender: "non binary"

In general terms, you are going to create one event for each question, the same way as each custom question is going to have a independent event.

Facebook / Instagram Lead Ads


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.