> ## Documentation Index
> Fetch the complete documentation index at: https://help.kajabi.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Meta Pixel enhancements
> Integrate your Kajabi site with the latest Meta Pixel enhancements.
Kajabi supports the latest Meta Pixel enhancements to help ensure your conversion events reach Meta accurately, even as privacy laws and browser tracking restrictions continue to evolve.
## Latest enhancements
As privacy laws and your site visitors' operating systems continue to evolve, they may impact how Meta receives and processes Events from tracking tools like the Meta Pixel.
If you optimize, target, or report on website Events from [Meta Pixel](https://www.facebook.com/business/help/742478679120153?id=1205376682832142) or any of Meta's other business tools, you can take steps to update your Event setup and manage these evolving changes. [Learn more about these changes](https://www.facebook.com/business/help/126789292407737?id=428636648170202).
Kajabi supports [Meta's Conversions API](https://www.facebook.com/business/help/2041148702652965?id=818859032317965) to ensure lead and purchase Events reach Meta, even when the Meta Pixel alone can't.
## Set up the Meta Conversions API
### What is the Meta Conversions API?
Changes to Meta's ability to track Events may impact Kajabi's ability to send conversion Event information that you normally track in your Ads Manager.
[Learn more about these anticipated changes](https://www.facebook.com/business/help/331612538028890?id=428636648170202).
The Conversions API allows Kajabi to send purchase and lead Events that visitors complete on your Kajabi site directly to your Meta Ads Manager instead of relying on the visitor's web browser. [Learn more about Meta's Conversions API](https://www.facebook.com/business/help/2041148702652965?id=818859032317965).
### Send lead and purchase events to Meta
To set up your Meta Conversions API and send lead and purchase events from Kajabi to Meta, you will need two items:
* [Meta Pixel ID](https://www.facebook.com/business/help/952192354843755?id=1205376682832142)
* [API Access Token](/articles/api-integrations/analytics-integrations/meta-pixel-with-kajabi)
Your Pixel ID and Access Token must be added to your Pixel integration in your Kajabi Site Settings.
#### Add Meta Pixel ID and API Access Token to Kajabi
1. From the Dashboard, click **Settings.**
2. Click **Integrations & Webhooks**.
3. Scroll down to **Meta Pixel** and click the toggle to enable it.
4. Enter your Pixel ID in the **Pixel ID** field.
5. Enter your Access Token in the **Access Token** field.
6. Click **Save.**
After setting up your integration, Kajabi can send the following Events to Meta:
* Purchases
* Leads
[Learn how to connect Meta Pixel with Kajabi](/articles/api-integrations/analytics-integrations/meta-pixel-with-kajabi).
## How does this work with existing browser events?
Your current browser events will still send in addition to the server events from the Conversions API.
Meta deduplicates identical events sent through the Meta Pixel and the Conversions API by checking the Event name and ID to determine if there are duplicates.
**Warning:** If you are using a third-party CAPI Gateway such as Stape in addition to Kajabi's API Access Token, you may experience duplicate Purchase events in Meta. This happens because the CAPI Gateway sends its own server-side events independently. Because there is no matching client-side event to pair against, Meta cannot deduplicate them, resulting in inflated Purchase counts and revenue data in your Meta Ads Manager. To avoid this, use either Kajabi's API Access Token or a third-party CAPI Gateway, but not both at the same time. If you are seeing duplicate Purchase events, removing the API Access Token from your Kajabi Pixel settings may resolve the issue.
[Read more about event deduplication](https://developers.facebook.com/docs/marketing-api/conversions-api/deduplicate-pixel-and-server-events).
## Where the purchase event fires
Kajabi sends purchase events to Meta in two ways: through the customer's browser (client-side) and directly from Kajabi's servers (server-side). When both events are sent for the same purchase, Meta automatically deduplicates them using the purchase ID.
Purchase events fire on the first post-purchase page a customer reaches, such as:
* Login page (for new or returning customers)
* Account creation page (for new customers)
* Upsell page
To provide extra reliability, the purchase event is also configured to fire on post-purchase thank-you pages, landing pages, and the member library. However, once the event has fired on one page, it will not fire again on subsequent pages.
This ensures:
* Purchases are captured as early as possible.
* Tracking is consistent, even if a customer does not continue through every step of the flow.
See the flow chart below for a visual breakdown of where the purchase event fires in [Enhanced Checkout](../../sales/checkout/enhanced-checkout-overview), depending on whether the customer is new or returning, and whether returning members are already logged in or not:
**Warning:** Using the Meta Conversions API may require additional review of your compliance obligations under data regulation laws applicable to you and your customers.
## FAQs
### Which events does Kajabi send via the Meta Conversions API?
Kajabi sends two types of events via the Meta Conversions API: **Purchases** and **Leads.** These are sent server-side directly from Kajabi to Meta, in addition to the browser-based client-side events sent through the Meta Pixel.
### Does the Meta Conversions API work with all Kajabi checkout types?
The Meta Conversions API purchase event tracking is supported with [Enhanced Checkout](https://help.kajabi.com/articles/sales/checkout/enhanced-checkout-overview#enhanced-checkout-overview). If you are using Legacy Checkout, purchase event behavior may differ. See the purchase event flow chart in this article for a detailed breakdown of where events fire depending on whether the customer is new or returning.
### How do I know if my events are being deduplicated correctly?
You can verify event deduplication in your Meta Events Manager. Look for events showing as "1 event from 2 sources" — this confirms deduplication is working correctly. If you see duplicate Purchase events, check whether you are using both a third-party CAPI Gateway and Kajabi's API Access Token at the same time. Using both simultaneously prevents Meta from deduplicating events because there is no matching client-side event\_id to pair against the server-side event. [Learn more about event deduplication](https://developers.facebook.com/docs/marketing-api/conversions-api/deduplicate-pixel-and-server-events).
### Can I use a third-party CAPI Gateway like Stape with Kajabi?
Yes, but not at the same time as Kajabi's API Access Token. Using both simultaneously sends duplicate server-side events that Meta cannot deduplicate, resulting in inflated Purchase counts and revenue data. Use either Kajabi's API Access Token or a third-party CAPI Gateway, but not both.