Configuring Facebook Conversions Connector

Problem Statement #

Customers may face issues while configuring the Facebook Conversions Connector in LeadSquared, resulting in Meta not receiving conversion or custom event data correctly. These issues are usually caused by incorrect connector setup, missing credentials, improper entity mapping, or formatting errors in automations.

This article outlines the correct configuration steps, highlights common issues, and provides solutions to ensure successful data sync with Meta.

---

#

Common Issues Observed #

1. Pixel ID or Access Token not provided or incorrectly configured.
2. Entity options not enabled or mapped as required.
3. Incorrect sync behavior selected for Lead/Contact or Activity entities.
4. Webhook not copied or used in automations.
5. Automation rules not created correctly or mapped with wrong event data.
6. Formatting errors in custom_data or note fields (extra spaces, line breaks, or incorrect JSON).
7. Lead stage–based events not syncing as expected with Meta.

---

#

Solution / Configuration Steps #

Step 1: Complete Basic Connector Setup #

• Follow all steps up to pointer 7.1 as mentioned in the official help documentation.
• This covers the basic installation and initial connector settings.
• Help article reference: Integrate Facebook Conversions with LeadSquared.

---

#

Step 2: Provide Required Credentials #

• Ensure the customer shares the following:

  • Pixel ID
  • Access Token
• These values are mandatory and must be generated from the customer’s Meta account.
• Use reference screenshots (if available) to guide customers on how to retrieve these details.

---

#

Step 3: Authentication and Entity Configuration #

• Once authentication is completed, proceed to configure the Entity Options within the connector.

---

#

Step 4: Configure Entity Options #

a. Lead/Contact Entity

• Enable Lead/Contact Entity.
• Set Sync Behaviour to Do Nothing.

#

b. Facebook Conversions Entity

• Enable Facebook Conversions.

• Click Edit Mapping and update mapping keys for:

  • lead_id
  • event_name
  • custom_data
  • timestamp

• Important:

  • Mapping keys must remain unchanged (example: mx_Custom_2).
  • Only the values should be updated as per the required format.

#

c. Activity Entity

• Enable Activity Entity.
• Set Sync Behaviour to Capture and click Edit Mapping.

• In the Default Mapping for Activity pop-up:

  • Click Add Custom and enter:

    • System Field: Meta Activity
    • Activity Type: Chat conversation
    • Activity Fields: Note
    • Required: Disabled
  • Under Actions, click the Tick mark.
  • Click Save & Close.

#

d. Activity Type(s) Definition

• Enable Activity Type(s) Definition.
• Click Create Activity.

---

#

Step 5: Copy Webhook #

• Copy the generated Webhook URL.
• This webhook will be required while configuring automations.

---

#

Step 6: Create Required Automations #

A total of three automations must be created:

1. Automation 1:
   Identifies leads captured via the Facebook Lead Ads Connector.
2. Automation 2:
   Sends lead data from LeadSquared to the Meta account.
3. Automation 3:
   Captures custom events (for example, Lead Stage changes) during the lead lifecycle.

---

#

Step 7: Configure Automation 1 (Important Formatting Update) #

• Follow all steps from the help document.
• Modify only the following fields:

Custom_Data

{"event_source":"crm","lead_event_source":"LeadSquared"}

Note

{"event_source":"crm","lead_event_source":"LeadSquared"}

Important Guidelines:

• Do not add spaces or line breaks.
• Use the format exactly as shown above.
• The format mentioned in the help article may contain errors—use this corrected version.

---

#

Step 8: Configure Automation 2 #

• Follow the help documentation exactly.
• No additional changes are required.

---

#

Step 9: Configure Automation 3 (Custom Event Data) #

• Follow all steps from the help document.
• Update only the custom_data and note