> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rabbitpay.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Generate Meta Pixel Access Token
> Generate the Meta Pixel ID and Conversions API Access Token required to connect Meta Pixel with RabbitPay.
## Overview
RabbitPay supports **Meta Pixel** integration for tracking customer events and improving conversion reporting through the [Meta Conversions API](https://developers.facebook.com/docs/marketing-api/conversions-api). Server-side events sent from RabbitPay to Meta help merchants recover attribution lost to browser restrictions and ad blockers, resulting in more accurate campaign performance data.
Before connecting Meta Pixel with RabbitPay, merchants must generate two credentials from their Meta account:
* **Meta Pixel ID** — identifies the Pixel that will receive events.
* **Meta Pixel Access Token** — authenticates server-side event requests sent from RabbitPay to Meta.
This setup is required **only once** during the RabbitPay onboarding process. Once configured, RabbitPay will automatically send purchase, checkout, and other conversion events to Meta on the merchant's behalf.
## Prerequisites
Before starting, ensure that:
* The merchant has an active **Meta Business Account**.
* A **Meta Pixel** has already been created in Events Manager.
* The merchant has **Administrator** access to Meta Business Manager.
* The merchant has access to **Meta Events Manager**.
## Navigation
Follow this path inside Meta Business Suite to reach the Conversions API settings:
```text theme={null}
Meta Business Suite
↓
Events Manager
↓
Select Pixel
↓
Settings
↓
Conversions API
```
## Step 1: Open Meta Events Manager
1. Log in to [Meta Business Suite](https://business.facebook.com/).
2. From the left navigation menu, open **Events Manager**.
3. Select the **Meta Pixel** that you want to integrate with RabbitPay.
Verify that the selected Pixel belongs to the correct Meta Business Account before generating the Access Token. Using the wrong Pixel may result in incorrect conversion tracking on your storefront.
## Step 2: Open Pixel Settings
1. After selecting the Pixel, open the **Settings** tab from the top navigation.
2. Scroll down until you find the **Conversions API** section.
This section allows merchants to generate an Access Token for server-side event tracking. Events sent through this API are attributed to the same Pixel that handles browser-side events, giving you a unified view of conversions.
## Step 3: Generate the Access Token
1. Under the **Conversions API** section, click **Generate Access Token**.
2. Meta will generate a new Access Token and display it once on screen.
3. **Copy the generated Access Token immediately.**
4. Store the token securely — it will be required during RabbitPay onboarding.
The Access Token authenticates every request sent from RabbitPay to Meta using the Conversions API. A sample token looks like this:
```text Access Token (example) theme={null}
EAAG5x8x0abcXYZ123...ZDZD
```
Meta displays the Access Token **only once** at the time of generation. If you navigate away without copying it, you will need to generate a new token. Save it to a secure password manager before closing the dialog.
## Step 4: Copy the Pixel ID
1. Locate the **Pixel ID** displayed at the top of the Pixel details page, next to the Pixel name.
2. Click the Pixel ID to copy it to your clipboard.
3. Store the Pixel ID securely alongside the Access Token.
RabbitPay requires **both** the Pixel ID and the Access Token to complete the Meta Pixel integration. A Pixel ID is a 15–16 digit numeric string, for example:
```text Pixel ID (example) theme={null}
123456789012345
```
## Verification
Your Meta Pixel setup is complete when:
* The **Pixel ID** has been copied successfully.
* The **Access Token** has been generated and copied successfully.
* Both credentials are stored securely and ready to be configured in RabbitPay.
## Security Notes
Keep the Access Token secure. Never expose it publicly or include it in frontend code or public repositories. If the Access Token is compromised, generate a new one from Meta Events Manager and update it in RabbitPay immediately.
Do not delete or regenerate the Access Token after it has been configured in RabbitPay **unless you also update the new token within RabbitPay**. An invalid or expired token will prevent server-side events from being sent to Meta, resulting in gaps in conversion tracking.
## Next Steps
Connect your Shopify store with RabbitPay to enable 1-Click Checkout.
Set up Razorpay API keys and webhooks for payment processing.