Meta Conversion Tracking: Datasets, Pixel, and the Conversions API in 2026

Updated July 22, 2026.

A current Meta implementation is built around an Events Manager dataset, the Meta Pixel for browser events, and—when the business can support it—the Conversions API for authoritative website, app, offline or messaging outcomes. The goal is not to maximize the number of events. It is to send consistent events with strong matching, correct values and reliable duplicate protection.

Verification boundary. This guide was checked against official Meta advertiser help, developer documentation, and release notes available on July 22, 2026. It does not rely on agency blogs, community posts, or third-party tutorials. Interface labels can differ during account-level rollouts. Where the official documentation describes a pilot, gradual rollout, regional limit, or incomplete availability, the guide says so rather than assuming access.

Meta’s developer documentation can require login or rate-limit automated access. The official URLs and field-level verification points are included, but the exact current screen labels should be checked in an authenticated Events Manager account before publication and again before implementation.

Understand datasets, pixels and event sources

Meta’s official setup article says Events Manager is gradually merging website, app and offline event data into a single dataset view. When an existing pixel becomes a dataset, the dataset ID remains the same as the pixel ID. That means older documentation may say “pixel” where a current account displays “dataset.” Treat the identifier as sensitive configuration and confirm it in the target business account.

Step 1: Create or select the dataset

1. Open Meta Events Manager under the correct business and ad account context.
2. Choose Connect data, select Web, and continue.
3. Name the pixel/dataset and create it. Record the ID shown in Events Manager.
4. Select Conversions API and Meta Pixel or Meta Pixel only.
5. If using both, select the current official path offered to the account: partner integration, Conversions API Gateway, or manual setup.
6. Assign the required people, partners and ad accounts through Meta’s data-source access controls.

Do not create a new dataset merely because a developer cannot find the old pixel. Confirm business ownership and permissions first. Duplicate data sources fragment diagnostics, audiences and event history.

Step 2: Install the Meta Pixel base code

Use the code generated inside Events Manager or the selected official partner integration. Place the base code in the global site template so PageView fires on intended pages. Do not paste a pixel ID from another environment or business.

// Illustrative event syntax after the official base code is installed.
fbq('track', 'Purchase', {
  value: ORDER_VALUE,
  currency: 'USD'
}, {
  eventID: STABLE_EVENT_ID
});

The example is not a substitute for the personalized code in Events Manager. The event ID becomes important when the same purchase is sent through the browser and server.

Step 3: Select standard events

Meta’s official Pixel reference defines standard events for common commercial actions. The current set used in this guide is:

PageView, ViewContent, Search, AddToCart, AddToWishlist, InitiateCheckout, AddPaymentInfo, Purchase, Lead, CompleteRegistration, Contact, CustomizeProduct, Donate, FindLocation, Schedule, StartTrial, SubmitApplication, Subscribe

Step 4: Add events by the right method

Event Setup Tool

Meta’s official setup flow offers a point-and-click Event Setup Tool. Use it for straightforward button or URL actions when the page structure is stable and the tool can distinguish success from intent. Document the selector or URL rule it creates. Re-test after design changes because visual tools can break when buttons, overlays or form flows change.

Manual browser code

Use manual code when values, content arrays, order IDs, event IDs, application state or precise success conditions matter. Fire the event from the application’s success callback or server-confirmed state—not from an unverified click.

Partner integration

Use an official partner integration when it sends the correct standard events, exposes values and IDs, supports Pixel/CAPI deduplication and provides a clear mapping. Disable duplicate manual integrations before enabling the partner.

Step 5: Use custom events and custom conversions deliberately

A custom event is an event name outside Meta’s standard event set. A custom conversion is a rule in Events Manager that classifies eligible received activity—often by event name, URL or parameters—into a conversion definition for reporting and optimization where supported.

Use a standard event whenever its meaning is accurate. Use a custom event for a genuinely distinct action, then create a custom conversion only when you need a rule-based subset, specific reporting definition, value rule or campaign selection. Avoid custom names that simply rename a standard event, because they make diagnostics and optimization harder to compare.

Example: qualified lead

Do not try to infer qualification from a thank-you URL. Send a server/CRM event when qualification actually occurs. Use an approved standard or custom event definition consistent with the current Meta setup available in your account, then create the corresponding custom conversion if needed. Document whether raw Lead and qualified lead are separate optimization events so both are not counted as independent customers.

Step 6: Configure Conversions API

Meta says Conversions API can send website, app, offline and messaging events. For website events, Meta recommends using CAPI alongside the Pixel rather than treating CAPI as an automatic replacement for every browser event.

1. Choose the official setup method: partner, Gateway or direct integration.
2. Use the correct dataset/pixel ID and generate credentials through Meta’s authorized flow.
3. For every event, send the official required fields for the action source. Direct website events generally require the event name, event time, action source, user data, and the source URL where applicable.
4. Send consented match data in the format required by the current parameter documentation. Hash fields only when the official field specification requires client-side hashing; do not double-hash already normalized values.
5. Send custom data such as value, currency, content IDs and order ID where relevant.
6. Use Events Manager’s test and diagnostics tools before moving to production.

Step 7: Deduplicate browser and server events

When Pixel and CAPI report the same business event, use the same event name and the same stable event ID on both copies. The event ID should represent the business action, such as the order or accepted lead, and should not change between browser and server delivery.

1. Generate or retrieve the event ID when the business action is created.
2. Pass it to the browser event as the Pixel eventID option.
3. Pass the same value in the server event’s event_id field.
4. Keep the event_name identical on both copies.
5. Confirm in Events Manager diagnostics that browser/server events are being deduplicated rather than counted twice.

Do not rely on timing alone. Two events sent seconds apart without matching deduplication fields can remain two conversions.

Step 8: Offline, app and messaging outcomes

Offline and CRM

Use the dataset and Conversions API path for in-store purchases, qualified leads, phone outcomes and CRM sales. The old Offline Conversions API to offline event sets was discontinued in May 2025. Capture permitted first-party identifiers and the relevant event time; send updates promptly; and reconcile events with the POS or CRM.

App

Use the Facebook SDK, App Events API or current CAPI app path. Separate installs, registrations, trials, purchases and subscriptions. Test platform privacy controls and mobile attribution behavior rather than copying website assumptions into the app.

Messaging

Conversions API can receive eligible business-messaging events from Messenger, Instagram or WhatsApp workflows. Meta’s official page notes that optimization availability can be event- and surface-specific—for example, purchase optimization for certain Messenger campaigns—so verify objective support in the current account.

Step 9: Choose events for campaign optimization

In campaign/ad-set setup, select the dataset and conversion event that represent the desired outcome. Keep enough event volume for the system to learn, but do not solve low volume by optimizing to a meaningless click. A two-stage plan can begin with a high-quality lead event and move toward purchase or qualified-lead value when volume and match coverage are sufficient.

QA checklist

• The correct dataset/pixel ID is installed once on production and excluded from staging where appropriate.
• PageView does not fire twice through manual code and a partner.
• Each standard event matches the actual completed action.
• Purchase value, currency and content IDs match the order and catalog.
• No URL, event parameter or customer field contains prohibited or sensitive data.
• Browser and CAPI copies share event_name and event_id and appear deduplicated.
• Event match quality and diagnostics are reviewed, not merely the event count.
• Offline/CRM events use datasets/CAPI, not a retired offline-event-set integration.
• The chosen campaign event is the intended optimization event.
• Platform totals are reconciled against the source order, CRM, app or messaging system.

Common failures

Implementation blueprints

Commerce dataset

The browser copy can preserve page and browser context; the server copy can confirm payment. Both copies use the same event name and event ID. Catalog identifiers must match the catalog exactly.

B2B lead dataset

Use a written event dictionary because Meta’s standard/custom choices may not mirror the CRM’s stage names. Do not infer qualification from a URL.

Data-policy review

Before launch, review page URLs, product names, form labels and event parameters for health, financial, identity or other sensitive information. Meta’s tools are not a permission to send every field available in the application. Keep raw personal data out of URLs and custom data fields; use only current permitted matching parameters and hashing requirements.

Release acceptance criteria

• One dataset/pixel ID is governed across the site.
• Partner, manual and Gateway paths do not overlap unexpectedly.
• All important events have a written source and success condition.
• Browser/CAPI Purchase and Lead duplicates are deduplicated.
• Event match diagnostics are reviewed alongside source-system accuracy.
• Offline events target datasets/CAPI rather than retired offline event sets.

Verification record

Technically verified: July 22, 2026

Official-source rule: Every platform-specific instruction and feature statement in this article is grounded in an official Meta source. The implementation recommendations are editorial guidance from The Ad Spend and are labeled as such.

Known limits at publication

• Events Manager labels and dataset migration status can differ during gradual rollout.
• Developer documentation may require an authenticated Meta account and can rate-limit automated access; recheck parameter pages in-browser before publishing.
• Optimization availability for app, offline and messaging events depends on objective, event and account eligibility.
• This guide does not infer permission to share sensitive or regulated data.

Official sources consulted

• Set up and install the Meta Pixel
• About Conversions API
• Meta Pixel event reference
• Conversions API parameters
• Deduplicate Pixel and server events

Related conversion tracking references

• conversion tracking library
• event match quality
• event deduplication
• event ID