Website and blog

Meta Pixel and Postfjord

Your Postfjord pages tell your Meta Pixel about each new signup with the Conversions API, only when the visitor ticks a box to allow it. No cookies and no pixel code on your pages.

Join the waitlistRead the help page

What it does

When someone signs up through a form on your link in bio page or a landing page and ticks the box to allow it, Postfjord sends your Meta Pixel one Lead from its own servers, with the Conversions API. Your Meta ads can then see how many signups they bring in.

Your pages set no cookies and run no scripts, and Meta's pixel code never loads on them. Visits and taps are never sent to Meta.

Connect in three steps

  1. In Meta Events Manager, copy your Pixel ID and generate a Conversions API access token.
  2. In Postfjord, go to Pages, paste both into the Meta Pixel card with the address of your privacy policy, and press Save and start.
  3. Paste the Test events code from Events Manager and press Send test event.

What moves where

  • From Postfjord to Meta: one Lead per new signup whose visitor ticked the box, with the visitor's IP address and browser, the page address and its utm tags, the time, and Meta's ad click id when the visit came from a Meta ad. Every Lead asks Meta to apply Limited Data Use.
  • From Meta to Postfjord: nothing.
  • Postfjord never sends an email address or a name, in plain text or hashed.

FAQ

Do I need Meta's pixel code on my pages?

No. Postfjord sends the Lead from its servers with the Conversions API, so your pages stay free of cookies and scripts.

Can I use it with Google Analytics?

Yes. Connect both, and the one box on your forms asks to tell Meta and Google.

Missing an app?

Tell us which one you need. We read every message. Or build your own with the API and MCP.

Tell usBuild your own with the API and MCP

All integrations

Get your workspace

Join the waitlist and we email you when your account is ready. Free plan, no card needed.

Join the waitlistSee pricing