A complete, end-to-end setup guide for installing the browser pixel, server-side Conversions API, and Lead event tracking on a Tilda site — with verification steps and a fix for every common issue.
Post-iOS 14, ad blockers, ITP, and consent banners silently drop a fifth to a third of pixel events. Meta still optimizes off whatever signal it gets — so you're paying full price for a half-blind algorithm. The fix is a server-side parallel feed: Conversions API (CAPI). Tilda has a native CAPI integration, which makes this much easier than people think.
Create the pixel in Events Manager, install on Tilda via the native Analytics field. Verify with Pixel Helper.
Track form submits and CTA clicks via Tilda's Forms service or Meta's Event Setup Tool — no code.
Generate access token, paste into Tilda's native CAPI integration, connect to all forms. Server-side dedup is automatic.
If you already have a pixel for this domain, skip to Part 2 — just grab the Pixel ID from the data sources screen.
Go to business.facebook.com/events_manager.
Business Manager → All tools → Events ManagerLeft sidebar → Data Sources → green Connect Data button.
Choose Web → Meta Pixel → Connect.
Use a descriptive internal name — e.g. SF Agency — Main Site. You may end up with several; name now, save pain later.
Meta will offer install options on the next screen. Skip them — we'll install through Tilda's native field, not Meta's installer.
It's a 15–16 digit number at the top of the pixel page. No letters, no prefix — just digits. You'll need this twice (once for the browser pixel, once for CAPI).
Method A is the default and works for 95% of cases. Use Method B only if you need custom init parameters (e.g. hashed Advanced Matching values).
Tilda has a built-in Facebook Pixel field that auto-injects the base snippet on every published page.
fbq(), no quotes, no "ID:" prefixPaste the full pixel <script> block into Tilda's HEAD insert. Use only if Method A's automatic init isn't enough.
<script> blockVisit your live Tilda site in Chrome → click the Pixel Helper extension icon. You should see a green check, your Pixel ID, and a PageView event firing.
Events Manager → your Pixel → Test Events tab → enter your site URL → reload the page. Events should appear in real-time.
Cmd+Shift+R), confirm the page is published, confirm the Tilda plan supports the Analytics field.PageView alone isn't enough — Meta needs to know which page-views are leads to optimize for them. Two no-code paths.
Tilda's built-in Facebook Pixel form-service fires fbq('track', 'Lead') automatically on every successful submit. Zero code.
Point-and-click overlay that lets you tag any button or URL as a Lead. Useful for tracking clicks before submit, or thank-you-page hits.
/thanks, OR if you want to track CTA clicks before submit. You can run both side-by-side as long as you don't double-fire on the same action.Submit the form / click the CTA on a live page. Pixel Helper should now show 2 events: PageView + Lead.
Events Manager → Test Events → trigger again → Lead appears in the live feed within a few seconds.
This is the part that recovers the 20–30% of leads the browser pixel loses. Tilda has a native CAPI integration that handles everything — including event_id deduplication — automatically.
Events Manager → your Pixel → Settings tab.
Scroll to Conversions API → click Set up manually (or Generate access token, depending on UI version).
Click Generate access token → copy it immediately. Long string starting with EAA…
Meta only shows the token once. Store it in 1Password — if you lose it you can regenerate, but old integrations break.
Site Settings → Forms → Services (same screen as the form-service Pixel from Part 3).
Scroll the list to the bottom → Facebook (this is the CAPI receiver, distinct from the browser-pixel form service).
Pixel ID — the same numeric ID from Part 1.
Access Token — the EAA… string from 4a.
Name — anything memorable (e.g. SF Agency CAPI).
Click Connect to all forms on the site. Save. Republish all pages.
Tilda now POSTs server-side Lead events to Meta's /events endpoint on every form submit, including hashed name + phone for matching.
After 2–3 real (or test) form submits:
Events Manager → Pixel → Overview. Find the Lead event row — it should now show two source columns: 🌐 Browser + 🖥 Server.
Click the event → Event Match Quality (EMQ) score. Aim for 6+/10. Source transcript reported EMQ 64 on Tilda's native integration with name + phone alone — a decent baseline.
The Deduplication tab should show events being matched between Browser and Server. Tilda's native integration passes the same event_id on both sides automatically.
If any of these aren't true, don't launch a Lead campaign at meaningful budget — the data will be garbage and you'll burn money optimizing on noise.
Symptom → likely cause → fix. The first row is the one we hit on the original advertorial.
| Symptom | Likely cause | Fix |
|---|---|---|
| Pixel Helper shows nothing in incognito but works in normal browser | Cookie consent gating script holding the pixel until consent | Non-EU traffic: relax the consent gate. EU traffic: implement consent-aware loading via custom HTML block. |
| Pixel firing twice | Both Method A (Tilda field) and Method B (HTML block) installed | Remove one. |
| Test Events shows nothing | Page not republished, Pixel ID typo, or ad blocker active | Republish; verify ID is digits-only; disable uBlock / Brave Shields for the test. |
| CAPI events not appearing | Wrong access token or service not connected to forms | Regenerate token; reconnect; republish. |
| EMQ score under 5 | Not enough user_data in CAPI payload | Tilda passes name + phone by default — add an email field to the form to boost match quality. |
| Browser Lead = 100, Server Lead = 30 | Server-side firing missing some submits | Confirm Tilda CAPI service is connected to all forms; check the form for JS errors. |
| iOS Safari traffic shows almost no pixel events | ITP blocking — expected behaviour | This is exactly what CAPI fixes. Confirm CAPI is firing for iOS submits via Test Events filtering. |
Once Pixel + CAPI are live and EMQ is healthy, you can run website-based Lead campaigns at scale instead of being locked into Meta Instant Forms. To actually graduate:
To exit learning phase. At ~65 AED CPL, that's roughly 465 AED/day per ad set, or consolidate into Advantage+/CBO so the threshold is shared.
Dedup working, no major iOS gap, both Browser and Server showing in Overview consistently for 7+ days.
Instant Form + Website Lead side-by-side. Compare not just CPL but lead quality — show rate, close rate. Website leads usually cost more but close better.