Connection with Meta

Integration via Meta Conversions API (CAPI) connects the CRM Pipeline directly to Meta's servers (Facebook and Instagram Ads).

Meta Ads

With Bolten's Meta Ads Integration, your events and conversions (such as purchases, leads, and sign-ups) are sent reliably.

If the integration is enabled, whenever a Lead is moved to the Won stage in a given sales funnel, your data will be automatically sent to Meta.

Why use this integration?

If your client runs ads via Meta, using Bolten's CAPI integration helps optimize that ad delivery for audiences with similar consumption profiles. This optimization is done by identifying Meta user access patterns from the data sent by Bolten (email, phone, etc.).

This allows:

• More accurate conversion tracking.

• Better campaign performance (ad optimization).

• More complete data for ROI analysis.

How to configure

See how you can set up your first Meta Ads integration in just a few steps.

1. Accessing Meta Ads Integrations

You can find the Meta Ads Integration settings inside a project in Bolten at Settings > Integrations > Meta Ads.

2. Creating a new Meta Ads integration

1. On the Meta Ads page, click the "+ New". 2. You will see a configuration screen where you need to fill in some fields:

• Pixel ID: this is the data tied to the Meta Ads campaign. See how to retrieve the Pixel ID.

• Access Token: Meta authentication data. See how to obtain it here.

• Meta Ads Event Type: type of event that will be signaled to the Meta Pixel. Learn more here.

• Active: indicates that the integration is active to communicate with Meta.

• Component: shows all components enabled to send information to Meta's conversions API. Check the breakdown of each component in the corresponding section.

Components

1. List of available components

To configure the Meta integration, only the components enabled to send conversion events will be available, which are the following:

• Opportunity Management with status "won": for an opportunity management component to be available to emit conversion events to Meta, it is necessary that it has a "won" status configured, which can be done in Configure → Special Fields.

• Conversions: the conversions component will be enabled to create new integrations with Meta. To select which lead sources should emit conversion events, you need to configure the "Conversion Source" item.

2. Component-specific settings

When selecting a component to emit conversion events, the form will present the fields for specific configuration of the chosen component type.

• Opportunity Management with status "won": when choosing a component of this type, it is necessary to select the list of properties sent to meta ads, which contains the same fields present in the opportunities component. Sending lead identification information (name, email, phone) is always done by default.

<figure><img src="https://1580422610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaHm1VFs056Yg2At7HGkE%2Fuploads%2FQGFtTpi6OInpNkMWSn5V%2Fmeta-ads-kanban-props.png?alt=media&#x26;token=5784905a-7135-4894-91f4-21d142634d28" alt="" width="563"><figcaption></figcaption></figure>

• Conversions: when choosing a component of this type, it is necessary to select the pipeline status that will trigger the event to Meta, as well as the conversion source. Both the lists of statuses and conversion sources are the same ones configured in the conversions component.

  • Events originating from the Conversions component will be emitted only if the Conversion Source matches the options selected for the integration. When no option is selected, all sources will be considered for sending events to Meta.

  • If you are sending an event of type "Purchase", you must also provide the purchase value. This information is extracted from the conversion mapping message itself, being the first number preceded by the dollar sign ($), but if this value is not available or identifiable in the message, the Default Value specified in the integration configuration shown in the image below will be used.

Meta Pixel

Read: What is the Meta Pixel?

To access the Meta Pixel, you must have a Facebook Business account.

• Authenticate into your Facebook Business

• At the bottom left, click Settings

• On the next page, go to Data Sources > Data Sets and Pixels. The Pixel ID will be located on the right side of the screen, next to Identification

Payload

All attributes selected in the integration configuration will be sent in the custom_data

node. The data used to identify the Lead are email (em) and phone (ph) of the contact or the opportunity in question.

The person's name is also sent if they are identified (fn and ln )

The payload follows the format described in the official Meta Conversions API documentation.

Example:

{
  "data": [
    {
      "event_id": "187cecc1-2b10-4ea6-a0cd-efa3aa1ff3ae",
      "user_data": {
        "em": "73eecced1ab3205e181a62742aa190da6c67b5c3589da75133c11936df3143cc",
        "ph": "2eb045dd514c459215c51b20dea69ac23c8de1380e3de5a55e3a489a9124b6ff"
      },
      "event_name": "Lead",
      "event_time": 1755097408,
      "custom_data": {
        "Status": "Completed",
        "Contact": {
          "Name": "John Doe",
          "Email": "[e-mail]",
          "WhatsApp": "1199999999",
          "created_at": "2025-08-07T10:08:57.955-03:00",
          "updated_at": "2025-08-07T10:08:58.396-03:00",
          "component_id": "d447a6e5-7842-4059-a0eb-9aef5b5db6fc"
        },
        "Tasks": [],
        "Priority": "High",
        "created_at": "2025-07-31T11:16:41.555-03:00",
        "updated_at": "2025-08-08T16:36:49.231-03:00",
        "component_id": "f4d195ef-4f98-4402-a8e2-3124252b53f8"
      },
      "action_source": "crm"
    }
  ],
  "access_token": "<MY_ACCESS_TOKEN>"
}

Error handling

Viewing deliveries

You can see a record of the requests made to Meta in the Executions.

tab. This page shows the most recent response for each integration request.