How to create Meta (Facebook) and Brevo connection

This guide walks you through the complete process of connecting Facebook Lead Forms (Source) to Brevo (Destination) using the sysConnector platform. Once configured, leads will sync automatically in real time.

Step 1: Create a New Connection

1. Log in to the sysConnector.

2. Click Create Connection.

Step 2: Configure Facebook as the Source

• Select Facebook Lead Forms as the Source App
  From the app list, choose Facebook Lead Forms, then click Next to continue.

• Log in or Select an Existing Facebook Account

  • If this is your first connection, you will be prompted to log in to Facebook.

  • If you have connected Facebook before, select an existing account from the list.

• Choose an Existing Account or Connect a New One

  • If an account already exists, select it and click Next.

  • If not, click Connect New Account.

    • Enter an Account Name and Connect
      Enter an Account Name.
      Recommended: Use the Facebook Page name (e.g., Client 1 Marketing) for easy identification.
      Then click Connect to Facebook Lead Forms.

    • Authorize Page Access
      Click Connect to [Page Name] and approve the permissions in Facebook.

• Select the Lead Form
  Choose the Lead Form you want to sync (e.g., Marketing Survey Form).
  Each connection supports one form only, so create separate connections for additional forms.

Step 3: Configure Brevo as the Destination

• Select Brevo as the Destination App.

1. Enter a Destination Account Name
   Example: Brevo Marketing or Brevo CRM Prod.

2. Enter required credentials:

   • API Key

3. Click Connect to Brevo to verify access.

Step 4: Define Connection Settings

1. Connection Name
   Use a clear, descriptive name such as:
   Facebook Leads 2026

2. Project Selection
   Choose an existing Project (folder) or use Unassigned.

3. Sync Frequency
   Select Event Space to enable real-time syncing when a lead is submitted.

Step 5: Field Mapping and Data Transformation

This step defines exactly how data collected in Facebook is translated, formatted, and delivered into Brevo. Proper configuration here ensures clean data, accurate reporting, and successful automation.

5.1 Basic Field Mapping

This section establishes a direct relationship between Facebook fields (source) and Brevo fields (destination).

Process:

• For each data point, select the Facebook field on the left.

• Map it to the corresponding Brevo field on the right.

Example:

• Facebook field Name → Brevo field First Name

• Facebook field Email → Brevo Email

If a required Brevo field is not mapped, records may fail to sync or be rejected.

5.2 Using Custom Text

The Custom Text feature allows you to send a fixed value that does not exist in the Facebook itself.

Common Use Case:

• Create a field in Brevo called Lead Source

• Use Custom Text to automatically populate it with Facebook for every lead coming through this connection

This is especially useful for campaign tracking, reporting, and segmentation.

5.3 Custom Transformations (Merging and Formatting)

Custom transformations allow you to manipulate or enhance data before it reaches Brevo, which is useful when the data structures between systems do not align perfectly.

Merge Fields

• You can select multiple Facebook fields and combine them into a single Brevo field.

• You may apply a divider (comma, dash, pipe, etc.) between values for readability.

Example:
If your Facebook contains separate columns for First Name and Last Name, you can merge them into a single Full Name field in Brevo (e.g., John Doe).

Prefix and Postfix

You can add text before (prefix) or after (postfix) a value.

Example:

• Prefix: FB-

• Result: FB-john.doe@email.co

This is useful for tagging, internal labeling, or adding context to incoming data.

5.4 Data Type Conversion

In some cases, Facebook sends data in a format that does not match the required data type in Brevo.

Example:

• Facebook sends a value as Text

• Brevo requires an Integer

How sysConnector Handles This:

• During testing, sysConnector automatically detects mismatched data types.

• Since Brevo field types are fixed, you must adjust the Source Type in sysConnector to match the destination field.

This ensures records are accepted and processed correctly.

5.5 Mandatory Testing and Validation

Before a connection can be activated, mapping must be tested successfully.

Process:

1. Enter sample test data for every mapped field.

2. Click Test Mapping.

3. The system validates formatting (e.g., email fields must contain valid email formats).

4. After a successful test, log in to Brevo and confirm the test record appears correctly.

Activation is blocked until testing passes.

Step 6: Testing and Activation

1. Enter sample test data and click Test Mapping.
   This step is mandatory before activation.

2. Log in to Brevo and confirm the test data was received correctly.

3. Click Save and Activate to begin live syncing.

Managing Your Connection

Monitoring

Go to Reports to view:

• Successful lead transfers

• Failed sync attempts

• Logs from the last 24 hours to 30 days