---
title: "Meta Pixel and Conversion API Tracking"
description: "Install a Meta Pixel on your funnels and websites and set up the Facebook Conversions API so your practice can track events and measure ad performance accurately."
url: https://help.aesthetixcrm.com/en/articles/1912-meta-pixel-and-conversion-api-tracking
collection: "Domains, SEO & Analytics"
updated: 2026-08-07
language: en
---

# Meta Pixel and Conversion API Tracking

Install a Meta Pixel on your funnels and websites and set up the Facebook Conversions API so your practice can track events and measure ad performance accurately.

Accurate tracking is what lets your practice see which ads actually drive consultation requests and bookings. Aesthetix CRM lets you add a Meta Pixel to your funnels and websites for browser-side event tracking, and set up the Facebook Conversions API (CAPI) for server-side tracking that holds up even when browser tracking is blocked. This guide covers finding or creating your Pixel ID, installing the pixel on a page, and connecting the Conversions API through a workflow.

Note that Ads Manager also documents the Conversions API from the ad-account side. This guide focuses on the funnel and website tracking setup, so use the two together when you configure attribution for a campaign.

## The Difference Between the Meta Pixel and the Conversions API

-   **Meta Pixel:** A piece of code that lives in the header of your funnel or website. It tracks events in the visitor's browser, such as page views and form submissions.
    
-   **Conversions API (CAPI):** Sends events to Facebook directly from the server rather than the browser. This preserves attribution when browser-based tracking is limited by privacy settings or ad blockers, keeping your reporting more complete.
    

Most practices use both together: the pixel for browser events and the Conversions API for reliable server-side confirmation.

## Finding or Creating Your Pixel ID

Your Pixel ID is the identifier that ties tracking on your site to your Facebook ad account. To create a new pixel:

1.  Open your Facebook Events Manager inside Meta Business Suite (Business Manager).
    
2.  Confirm you are connected to the correct ad account with the required access to the Facebook Page.
    
3.  In the left sidebar, click **Connect Data Sources**.
    
4.  Choose **Web**, then click **Connect**.
    
5.  If you already have pixels, choose an existing one or create a new pixel. Enter a name and continue.
    
6.  Once created, your Pixel ID is available in the pixel's settings, ready to install on your funnels and websites.
    

## Setting Up the Facebook Conversions API for a Funnel Event

Setting up CAPI has three parts: create and configure the pixel in Events Manager, add the pixel code to your funnel or website, and build a workflow that sends events to Facebook.

### Step 1: Create and Configure the Pixel in Events Manager

1.  In Events Manager, start connecting a **Web** data source and create a new pixel (or use an existing one).
    
2.  When prompted, enter the domain of the funnel or website where you will add the pixel code, then click **Check**. A green checkmark means the domain is eligible. Click **Next**.
    
3.  On **Choose how to connect your website**, choose **Conversions API and Meta Pixel**.
    
4.  When asked how to set up the Conversions API, choose **Set up Manually**.
    
5.  Read the manual implementation overview, then click **Continue**.
    
6.  On **Select Events**, choose the industry most relevant to your practice, select the events you want to send to Facebook, and click **Continue**.
    
7.  On **Select Parameters**, keep the recommended event detail parameters and add **Event ID**.
    
8.  Under customer information parameters, keep **Client User Agent** and also check **Client IP Address**, **First Name**, **Client ID**, **Email**, **Business ID**, and **Last Name**. Apply these same selections to every event you added.
    
9.  Review the setup, confirm the parameters for each event, and click **Continue**.
    
10.  Click **Continue Pixel Setup**, then choose **Install Code Manually** and click **Copy Code**.
     

### Step 2: Apply the Pixel Code to Your Funnel or Website

1.  Keeping the Events Manager tab open, switch to your Aesthetix CRM account.
    
2.  Go to **Sites** in the left sidebar, then **Funnels** or **Websites**, depending on where the page tied to that domain was built.
    
3.  Click **Edit** on the page you want to track. Opening it in a new tab is often easiest.
    
4.  In the builder, go to **Settings**, then **Tracking Code**.
    
5.  Paste the copied pixel code into the **Header Code**, then click **Yes, Save**.
    
6.  Save the funnel or website so the change goes live.
    

### Step 3: Build a Conversions API Workflow

1.  Exit the builder and go to **Automation**, then **Workflows**, then **Create Workflow**.
    
2.  Choose **Start from Scratch** and create a new workflow.
    
3.  Click **Add New Workflow Trigger** and select the **Facebook Lead Form Submitted** trigger. If you want it to fire for one specific form, add a filter for the Facebook Lead Form. Save the trigger.
    
4.  Click **Add your first Action**, then search for and select the **Facebook Conversion API** action.
    
5.  Optionally name the action. In the **Event Type** dropdown, choose **Funnel Event**.
    
6.  In Events Manager, open the pixel you set up and click **Complete Setup**. Under the Conversions API tab, click **Get Started**, then **Generate Access Token**, and copy the token.
    
7.  Paste the token into the **Access Token** field in the Facebook Conversion API action.
    
8.  Back in Events Manager, finish the implementation, then copy the **Pixel ID** from the pixel settings.
    
9.  Paste the Pixel ID into the **Pixel ID** field in the action.
    
10.  Save the action, then save and publish the workflow.
     

> **Tip:** For lead value, use an assumed value such as 1000 or 2000 so you can gauge what each new lead contributes to your pipeline.

Before the workflow can fire, confirm in **Settings > Integrations** that your Facebook account is connected with admin permissions, that the correct Facebook Page is integrated, and that the correct Facebook Lead Form is mapped under **Settings > Integrations > Facebook Form Field Mapping** with the mapping enabled.

## Frequently Asked Questions

**What is the difference between the Meta Pixel and the Conversions API?** The Meta Pixel tracks events in the visitor's browser. The Conversions API sends events to Facebook from the server, which keeps your attribution more complete when browser tracking is blocked. Most practices use both.

**Where do I put the pixel code in Aesthetix CRM?** In the funnel or website builder, go to **Settings > Tracking Code** and paste the code into the **Header Code**, then save the page.

**Do I need a workflow for the Conversions API?** Yes. The Conversions API is connected through a workflow using the **Facebook Lead Form Submitted** trigger and the **Facebook Conversion API** action.

**Where do I find my Pixel ID?** In Facebook Events Manager, open your pixel and copy the Pixel ID from the pixel settings.

**Does Ads Manager also cover the Conversions API?** Yes. Ads Manager documents the Conversions API from the ad-account side. Use it together with this funnel and website setup when configuring campaign attribution.

**Do I add the pixel to every page I want to track?** Add the header code to the pages or funnel steps you want to track. If a domain covers several pages, install it where the events you care about occur, such as the consultation request page.

**Why should I add Event ID and customer information parameters?** These parameters help Facebook match browser and server events and improve the accuracy of your conversion reporting. Apply the same parameters across every event you send.

**My workflow is not firing. What should I check?** Confirm your Facebook account is connected with admin permissions in **Settings > Integrations**, the correct Page is integrated, and the correct Facebook Lead Form is mapped and enabled under Facebook Form Field Mapping.
