Test Facebook Conversion API Events

Browser-side tracking alone is no longer enough. Facebook expects advertisers to send server-side events through the Conversion API, and the quality of those payloads influences attribution, bidding, and compliance.

Use it when onboarding new offers, changing pixels, or debugging hashed identifiers. The response exposes warning messages about missing parameters, hashing mismatches, or rate limits so you can fix issues before the next optimization cycle.

Related tools

How this CAPI tester works

The tester sends an HTTPS request to Meta using your credentials and displays the raw JSON response.

Facebook CAPI Tester

Send test events to Facebook Conversion API and verify responses instantly.

What does this tool do?

The Facebook CAPI Tester sends sample Conversion API events and shows Meta's response so you can confirm payloads before deploying.

Why use this tool?

Validate setup

Ensure Pixel ID, access token, and events are working.

Debug server events

Inspect status codes and error messages directly from Meta.

Share proof

Provide clients with live confirmation of Conversion API hits.

Prove server-side events reach Meta

The Facebook CAPI Test tool sends structured events so you can validate hashing, payloads, and responses.

  • Post real Pixel IDs, access tokens, and test event codes.
  • See Meta's raw response plus any deduplication or validation errors.
  • Ensure email/IP hashing and event IDs are formatted correctly.

Use it when

  • •

    Rolling out a new server-side integration or migrating from browser-only tracking.

  • •

    Debugging rejected events or low match rates in Events Manager.

  • •

    Coaching partners and CRMs on the exact payload structure you require.

Practical examples

Dry-run Shopify to CAPI

Send a sample Purchase from your server script and confirm Meta accepts the hashed customer data.

Investigate duplicate events

Test with and without the pixel event ID to see when Meta flags deduplication problems.

Support an affiliate's CRM integration

Share a successful test payload so their devs mirror the same fields and hashing.

Contextual resources

Pixel Scanner

Verify browser events fire before tackling server-side sends.

→
Postback Tester

Validate the callbacks you plan to forward into CAPI.

→

FAQ

Facebook CAPI FAQ

Do test events affect reporting?

No. Use Meta's test event code to keep the payload out of production reports while you debug.

Can I include user data?

Yes, and you should. The more hashed identifiers you send, the better Meta can match the conversion to a click.

What if I see a deduplication warning?

Include the same event_id in both browser and server events so Meta can deduplicate them. The tester helps you verify that the event_id is set correctly.

Pixel cluster

Best for

  • Server-side event debugging
  • Comparing browser vs. CAPI payloads
  • Documenting Event Match Quality improvements

Use this when

Initial CAPI rollout

Send sample purchases to confirm hashing, timestamps, and IDs line up with Meta requirements.

Deduplication bugs

Test matching event_id / external_id pairs to find which side is causing duplicates.

Related resources

Facebook Pixel Checker Pixel Scanner

Need help fixing tracking or attribution?

If you're struggling with tracking issues, attribution problems, or broken postbacks, I offer professional tracking setup and audits.

Fix your tracking issues → Request free audit

Tools for Affiliate Tracking Debugging

Related tools

Related Tracking Tools

Pixel Scanner

Verify Meta, TikTok, and Google tags fire on any landing page instantly.

Open tool →

Postback Tester

Fire sample conversion callbacks and read the raw response before launch.

Open tool →

UTM Builder

Create campaign tracking URLs with UTM parameters.

Open tool →