Heyflow · Conversion tracking
Heyflow conversion tracking without the double counts
Heyflow ships with native GA4, GTM, Meta Pixel and Meta Conversions API connections, plus its own Events API and dataLayer events, a redirect with answer variables and webhooks. So the issue is rarely a missing signal — it is too many overlapping ones, and a funnel that ends in an embedded Calendly block where the actual booking may or may not be the event you are counting.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on Heyflow
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
By the numbers
No fake testimonials.Just the math.
70+
Platforms supported
Shopify · Woo · Magento · BigCommerce · 65 more
8+ / 10
Meta EMQ guaranteed
in writing — keep working free until hit
2–4d
Build to live
accurate data flowing within 7 days
$0
Monthly fees, ever
one-time fixed price · you own the stack
400d
Cookie lifetime
max RFC 6265bis allows · 57× Safari ITP
9
Ad channels covered
Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X
95%+
Tracking accuracy
verified vs Stripe · GA4 · ad-platform reports
30 min
Free founder call
no SDR · no pitch deck · written remediation plan
Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.
Real clients · real videos · real outcomes
Don’t take our word for it. Watch the receipts.
Founders, marketers, and agency owners describing the before-and-after of their Heyflow tracking rebuild — in their own words, on camera.
Where Heyflow tracking goes wrong
Native Pixel, native CAPI and site GTM all firing
Three paths to one lead, rarely sharing an ID.
Flow completion counted as a booking
The Calendly block is a separate step inside the flow.
Embedded versus hosted flows
The same funnel behaves differently on your page and on Heyflow's.
Every lead valued the same
The flow already knows budget, location and fit.
Architecture
What Heyflow actually lets you do
A lot, which is why the work is mostly choosing.
Step 1
Native GA4, GTM, Meta Pixel and Meta CAPI
Built into the flow settings.
Step 2
Heyflow Events API and dataLayer events
Flow events your own container can listen for when embedded.
Step 3
Redirect to a URL with variables
Answers and identifiers passed to a page you control.
Step 4
Webhooks on submission
The server-side trigger for leads.
Step 5
Calendly block
Booking inside the flow; confirm what event, if any, the booking itself raises.
Diagnostic sequence
Finding the overlap in a Heyflow setup
Duplication first, then the booking.
- 1
Count Meta events per Heyflow response
More than one means native CAPI and the pixel or your GTM are both sending.
- 2
Check whether event IDs match across browser and server
Without that, Meta cannot deduplicate.
- 3
Book a test call in the Calendly block
See whether the booking is a distinct event or just part of submit.
- 4
Compare embedded and hosted versions
One may fire your site's container and the other will not.
- 5
Check which answers reach the platforms as value
Most setups send none.
Source-of-truth validation
The QA evidence
Tested on the published Heyflow flow, with a real response that books a call in the Calendly block.
- A test response arriving once at each platform, deduplicated across browser and server.
- A booking in the Calendly block confirmed tracked as its own event.
- A disqualified response confirmed excluded from bidding.
- Lead value confirmed to reflect the qualifying answers.
- Embedded and hosted versions of the flow both tested.
- A finished month of Heyflow responses compared, response for response, with what each platform logged.
- Re-run after 30 days and after every edit to the flow's steps or integrations.
Straight talk
When Heyflow's native setup is enough
Heyflow's native tools are often enough.
- If you advertise on Meta only and native Pixel plus CAPI are already deduplicating, leave them.
- If the flow ends at submission with no booking step, the native setup may cover everything.
- If every lead is worth roughly the same, answer-based values add little.
- If you are comfortable in GTM, the dataLayer events are documented well enough to wire yourself.
Who this is for
Honest about who we’re a fit for.
We don’t take every project. Here’s how to tell if we’re right for you.
You’re a great fit if…
- You run Heyflow (or are migrating to it)
- You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
- Your reported ROAS doesn’t match what your bank account is saying
- You want to own your tracking stack — no monthly SaaS fees forever
- You have 2–4 days to do this once and never think about it again
Skip us if…
- You spend less than $500/month on paid ads (browser pixel is fine)
- You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
- You need attribution modeling — we fix the data foundation, not multi-touch reports
- You want a 6-month enterprise consulting engagement (we ship in 4 days)
- You expect us to manage your ad accounts (we don’t — that’s a different service)
If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.
What changes
One deduplicated lead event
Server-sideWhichever path sends it, sharing an event ID.
The booked call as its own conversion
8+ EMQDistinct from finishing the flow.
Lead value from qualifying answers
DedupedSo bidding favors the leads sales wants.
The event map for a Heyflow funnel
Flow started
Top-of-funnel engagement from the Heyflow event stream.
Qualifying question answered
The answers that set lead value.
Flow submitted
The lead conversion.
Call booked in the Calendly block
The booking, tracked separately.
Lead disqualified
Kept out of bidding.
Pick the package that fits your ad spend
Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.
Browser-side starter
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations reversed everywhere
- Monitoring on every destination
Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.
How it works
Built in 2–4 days. Accurate data within 7.
We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.
Kickoff + audit
30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.
Build the stack
Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.
QA + go-live
Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.
Verify accuracy
Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.
Got questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01Heyflow has native Meta CAPI. Why would we need more?
Often you don't. The common problem is running native CAPI alongside a pixel in your own GTM without a shared event ID, which doubles every lead.
02Is the Calendly booking tracked automatically?
Finishing the flow and booking the call are different moments. We test on your flow whether the booking raises its own event.
03Should we use the redirect or the dataLayer events?
If the flow is embedded on your site, the dataLayer events are cleaner. For hosted flows, the redirect to your own page is the dependable option.
04Can Heyflow answers set conversion value?
Yes, the answers are available to the events and redirect. We map the ones that predict a good customer to value.
05Do we still need server-side for Google Ads?
Heyflow's native CAPI covers Meta. Google Ads still needs its own route, which is where the first-party container helps.
Still have questions?Book a 30-min call— bring them all.
The call
What happens on your free 30-min call
No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourHeyflow setup — we’ll work through it together.
Min 1–5
We get the lay of your store
What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.
Min 5–15
We audit your tracking live
Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.
Min 15–25
We map a fix
What needs rebuilding, what stays. The exact Heyflow setup we'd ship and what it would recover for you.
Min 25–30
Decide. Or don’t.
If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.
Get Heyflow tracking done once
Book a free 30-minute call. Send one response through your Heyflow while we watch Meta and Google, and leave with a written plan; sometimes that plan is to leave the native integrations alone.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
You might also need
Tracking Audit
Your current vendor isn't going to tell you what's broken — they built it. We wi…
Read more
Enhanced Conversions
Enhanced Conversions enrich the conversions that already fire. First we make sur…
Read more
Meta CAPI
A one-click CAPI integration sends thin events. That's why your Event Match Qual…
Read more
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
