Improve event tracking accuracy by sending events directly from your server to Meta using the Conversions API. This helps reduce data loss caused by browser restrictions, cookie limitations, and ad blockers while improving attribution and campaign reporting.

TABLE OF CONTENTS

What is Meta Conversions API?

Meta Conversions API allows events to be sent directly from your server to Meta instead of relying only on browser-based tracking.

Unlike browser-only tracking, Conversions API helps improve event reliability by reducing the impact of:

  • Browser privacy restrictions

  • Cookie limitations

  • Ad blockers

  • Network interruptions

  • Tracking prevention technologies

When used alongside browser tracking, Conversions API provides a more complete view of customer activity and conversion performance.

Why Use Conversions API?

Using both browser events and server-side events creates a stronger and more reliable tracking setup.

Key Benefits

  • Improved Event Accuracy: Capture events that may otherwise be blocked by browser restrictions.

  • Better Attribution: Provide Meta with more complete conversion data for reporting and optimization.

  • Reduced Data Loss: Continue tracking important events even when browser tracking is limited.

  • Enhanced Campaign Optimization: Give Meta more reliable signals to improve ad delivery and performance.

  • Future-Proof Tracking: Maintain event tracking as privacy requirements and browser restrictions continue evolving.

Updated Meta Events Manager Navigation

Meta has updated the Events Manager interface and the location of Pixel settings.

Current Navigation Path

Navigate to:

Events Manager → Data Sources → Select Pixel → Settings → Conversions API

If you manage multiple Pixels, first select the correct Pixel from the Data Sources area before opening Settings.

Previous Navigation vs Current Navigation

Previous Interface

Current Interface

Events Manager

Events Manager

Select Pixel

Data Sources → Select Pixel

Settings

Settings

Server-Side API for Web

Conversions API

How to Generate a Conversions API Access Token

Generating an access token allows your platform to securely send server-side events to Meta.

Open Events Manager

Log in to your Meta account and open Events Manager.

Navigate to the Data Sources section and select the Pixel you want to configure.

Open Pixel Settings

After selecting the Pixel:

  • Open the Settings tab.

  • Scroll down until you find the Conversions API section.

Note: Older versions of Meta may still reference this section as Server-Side API for Web.

Generate the Access Token

Inside the Conversions API section:

  • Click Generate Access Token or Create Access Token.

  • Complete any authorization prompts.

  • Select the appropriate application if requested.

  • Generate the token.

  • Copy the token for use in your integration.

Save the Token Securely

Store the token securely and use it when configuring Conversions API connections.

The token acts as the authentication key that allows events to be sent to Meta.

Understanding the New Meta Interface

Depending on your Meta account setup, you may encounter different screens during setup.

You may be prompted to:

  • Select a Pixel

  • Select an application

  • Create an application

  • Assign permissions

  • Verify business access

These variations are normal and depend on your account permissions and business setup.

Once completed, the generated access token functions the same regardless of which interface variation you see.

Troubleshooting Conversions API Access Token Issues

If you cannot find the Conversions API section or generate an access token, review the following items.

Verify Pixel Access

Confirm that:

  • You are logged into the correct Meta account.

  • The Pixel belongs to the Business Manager account you are managing.

  • You have administrator permissions for the Pixel.

Refresh Events Manager

If recent permission changes were made:

  • Refresh the page.

  • Log out and back in.

  • Reopen Events Manager.

Check Data Source Selection

Many users accidentally select the wrong Data Source when managing multiple Pixels.

Confirm that the correct Pixel is selected before opening Settings.

Verify Business Permissions

If the Conversions API section is missing:

  • Verify administrator access.

  • Confirm business verification requirements have been completed if applicable.

Frequently Asked Questions

Q: Why do my screens look different from the screenshots?

Meta regularly updates the Events Manager interface. The location of settings may change, but the Conversions API section remains available through the Pixel Settings area.

Q: Is Server-Side API for Web the same as Conversions API?

Yes. Meta renamed portions of the interface, but the feature serves the same purpose of sending server-side events.

Q: Why can’t I generate an access token?

Most access token issues are caused by insufficient permissions on the Pixel or Business Manager account.

Q: Do I need both browser tracking and Conversions API?

Using both together provides the most complete event tracking and attribution.

Q: Can I regenerate an access token later?

Yes. New tokens can be generated from the Conversions API section whenever needed.

Q: What happens if my token becomes compromised?

Generate a new token immediately and update your integration configuration.

Need Help?

If you’re having trouble locating your Pixel settings, generating an access token, or configuring Conversions API tracking, start by verifying that you have the correct permissions for the Pixel and Business Manager account. Meta periodically updates its interface, so some settings may appear in different locations than older documentation or screenshots.

Before troubleshooting further, confirm that:

  • You are logged into the correct Meta account.

  • You have administrator access to the Pixel.

  • The correct Data Source (Pixel) is selected.

  • Your access token was generated successfully.

  • Any recent permission or configuration changes have had time to update.

If events are not being received after setup, review your integration settings, verify that the access token was copied correctly, and confirm that server-side event tracking has been enabled in your configuration.

If you continue to experience issues, contact support and provide:

  • Screenshots of your Pixel settings page.

  • Screenshots of any error messages you receive.

  • The steps you have already completed.

  • Details about whether events are failing to send, not appearing in reporting, or not being received by your integration.

Providing this information upfront will help speed up troubleshooting and resolution.