Connect Meta Pixel + CAPI

Abitlink forwards page views and block clicks to Meta through the Conversions API (CAPI), server-side from the Cloudflare Worker. Same story as GA4: no browser Pixel script on your bio page, ad blockers can’t interfere, and events arrive within seconds.

Prerequisites

• A Pro (or Early Bird) Abitlink account.
• A Meta Business account with Events Manager access. Free at business.facebook.com.
• A Pixel (aka “dataset” in newer UI versions). You can reuse one you already own.

1. Create a Pixel in Events Manager (skip if you have one)

1. Go to Events Manager.

2. Click Connect data → Web → Connect.

3. Pick Meta Pixel, give it a name (“Abitlink — maya” is fine), enter https://abitlink.co as your website, and click Create.

4. On the setup screen, skip the code/partner integration options — you’ll connect server-side via Abitlink’s CAPI flow instead.

2. Get your Pixel ID

In Events Manager, pick the Pixel you just created (or an existing one). The Pixel ID is a 15–16 digit number displayed at the top of the page, e.g.:

1234567890123456

Tip

Newer UI labels this “Dataset ID” — same number, same purpose. Either works in Abitlink’s input field.

3. Get your Conversions API access token

1. With the Pixel selected, open the Settings tab.

2. Scroll to Conversions API and click Generate access token.

3. Copy the token that appears. It’s a long string — starts with EAAx… and can be a couple hundred characters long. Save it somewhere safe for the next step.

Caution

The CAPI access token acts like a password for sending events to your Pixel. Don’t commit it to a public repo or paste it into chat. Abitlink encrypts it at rest and never sends it to the browser.

4. Paste into Abitlink

1. Log in to abitlink.co and open your dashboard.

2. Go to Settings → Analytics.

3. Paste your Pixel ID into the Meta Pixel ID field.

4. Paste the access token into the Meta CAPI Access Token field.

5. Click Save.

5. Verify with Test Events

1. In Events Manager, open your Pixel and click the Test events tab.

2. In a fresh incognito window, visit your bio page at abitlink.co/yourname and click a block.

3. Within 10–30 seconds, the Test events view shows the inbound events:

   • PageView (from your visit)
   • ViewContent / Lead / Contact depending on the block type clicked

Tip

If you add a Test event code in the Events Manager Test events view, Abitlink does not forward that code — we send production events directly. Use a separate, unused Pixel for testing if you need isolation.

Troubleshooting

Test events shows nothing. The most common cause is a typo in the Pixel ID (it’s all digits — check for copied whitespace). Second most common: the CAPI token was regenerated in Meta and the old one is now revoked. Regenerate and paste again.

Events arrive but some parameters are missing. CAPI requires customer information parameters (email, phone, IP) to match conversions to Facebook users. Abitlink sends the IP and user agent by design. Email/phone aren’t collected on bio pages — that’s expected.

My ad-match quality score is low. Meta’s match score rewards richer customer info. For a link-in-bio page (anonymous visitors), low match quality is normal — it’s not a sign of broken tracking. Use these events for retargeting audiences, not for cost-per-conversion optimization.

I want to forward to both Meta and GA4. You can. Fill in both pairs of credentials under Settings → Analytics. Every event is sent to both destinations in parallel.