CallRail → DV360 · Conversion tracking
Connecting CallRail to Display & Video 360
CallRail knows which call came from which visit, and for phone-led businesses the call is the conversion. DV360 shares Google's identity graph with Google Ads but not its conversion plumbing, which catches out advertisers who assume a conversion set up in one is visible in the other. The join between them succeeds or fails on one thing: whether the Floodlight activity, not a click identifier reaches the CallRail call record before the conversion happens, because DV360 can only match a conversion it can tie back to a click it recognizes.
✓ 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 CallRail → DV360
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 CallRail → DV360 tracking rebuild — in their own words, on camera.
Why this join usually fails
The Floodlight activity, not a click identifier never reaches CallRail
The single most common cause. Dynamic number insertion has to run before the visitor dials. If the swap script is deferred, blocked by consent, or the visitor calls from a cached page, CallRail records the call but cannot tie it to the session, and the click identifier goes with it. Calls from the Google Business Profile or a printed number never had a session at all.
Every call counts, including the wrong numbers
Unfiltered call conversions teach the ad platform to find people who dial, not people who buy. A 12-second call is not a lead and should not be paid for as one.
Assuming Google Ads conversions appear in DV360
They do not. They are separate systems with separate configuration, and an advertiser running both frequently discovers months in that DV360 has been optimizing toward a Floodlight nobody checked, or toward nothing at all.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. Campaign Manager reports Floodlight activity counts directly. Check those, not the DV360 campaign view, and compare against your own order count for the same window.
Architecture
How CallRail and DV360 actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
CallRail holds the truth
The call record carries duration, source, the tracking number, the keyword where available, and — critically — the session CallRail stitched it to. That session is what carries the click identifier.
Step 2
Display & Video 360 needs a click to match
DV360 needs the Floodlight activity to fire, or an offline conversion uploaded against it. It also needs the counting method — counter or sales, unique or per-session — set deliberately, because the default is frequently wrong for what you are measuring.
Step 3
The identifier is the bridge
The Floodlight activity, not a click identifier, captured at the visit and carried into the CallRail call record. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send after the call completes, filtered by duration or by the qualification your team applies. Sending on call start counts wrong numbers and hang-ups as conversions.
Step 5
Deduplication at the destination
Floodlight's counting method is the deduplication rule. A counter activity set to count every fire will record repeat page views as conversions, which is the single most common misconfiguration in the product.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the DV360 dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
The Floodlight activity, not a click identifier present on the call
Visible on the record itself in CallRail, not merely captured somewhere on the site.
Sent from the CallRail post-call webhook
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
Floodlight's counting method is the deduplication rule. A counter activity set to count every fire will record repeat page views as conversions, which is the single most common misconfiguration in the product.
Reconciles with the source
DV360's count and CallRail's records agree within a few percent over a closed window.
Actually broken
The Floodlight activity, not a click identifier missing on most records
Dynamic number insertion has to run before the visitor dials. If the swap script is deferred, blocked by consent, or the visitor calls from a cached page, CallRail records the call but cannot tie it to the session, and the click identifier goes with it. Calls from the Google Business Profile or a printed number never had a session at all.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. Unfiltered call conversions teach the ad platform to find people who dial, not people who buy. A 12-second call is not a lead and should not be paid for as one.
Counted twice, or not at all
They do not. They are separate systems with separate configuration, and an advertiser running both frequently discovers months in that DV360 has been optimizing toward a Floodlight nobody checked, or toward nothing at all.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to CallRail. A wrong number that nobody checks is indistinguishable from a right one.
Diagnostic sequence
Diagnostic order
Each step rules out a class of cause. Run them in order and the last one usually has a single explanation standing.
- 1
Count calls carrying the Floodlight activity, not a click identifier
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through CallRail and into DV360.
- 3
Check what share of calls have a session attached
In CallRail, calls without a session cannot be attributed by anyone. That percentage is your real ceiling, and it is usually the number that ends the debate.
- 4
Open the Floodlight configuration and read the counting method
Counter versus sales, unique versus every fire. It takes a minute and it explains most inflated DV360 conversion counts.
- 5
Read the match rate, not the success message
Campaign Manager reports Floodlight activity counts directly. Check those, not the DV360 campaign view, and compare against your own order count for the same window.
Source-of-truth validation
How it gets proven
Against CallRail's own records, not against either platform's dashboard.
- The Floodlight activity, not a click identifier confirmed present on a live call.
- A real conversion followed from click through CallRail to DV360.
- Floodlight conversion counts reconciled against your own order records, with the counting method documented.
- The duration or qualification threshold agreed in writing before anything is sent.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later.
Straight talk
When you don't need this
Worth reading before paying anyone, including us.
- If DV360 already reports conversions that reconcile against CallRail's records within a few percent, this join is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred calls and count how many carry the Floodlight activity, not a click identifier. Ten minutes, free, and it tells you whether any of this is worth doing.
- CallRail's own native integrations are genuinely decent for straightforward setups. If you only need calls into one destination and your qualification is just a duration threshold, use theirs — we will say so.
- If you only run Google Ads, you do not need Floodlight at all and setting it up adds a second conversion system to keep in sync.
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 CallRail → DV360 (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 working looks like
The Floodlight activity, not a click identifier on every call
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in DV360
8+ EMQThe conversion is attributed under the configured Floodlight and attribution model, and becomes available for optimization.
Reconciled against the source
DedupedCallRail's own records are the reference, not either dashboard.
What gets built
Identifier capture into CallRail
Confirm the number-swap script runs early and unconditionally on every page a paid visitor can land on, and that CallRail's session capture is receiving the click identifier from the URL.
Event source: the CallRail post-call webhook
Send after the call completes, filtered by duration or by the qualification your team applies. Sending on call start counts wrong numbers and hang-ups as conversions.
Dispatch to DV360
Floodlight tags, or offline conversion upload through Campaign Manager against the Floodlight activity.
Reversals where they exist
There is nothing to reverse, but a call later marked unqualified should not have been counted — which is why the duration or qualification filter belongs before the send, not after.
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
Wires the join and verifies it on a live conversion. Honest about its ceiling where the source can only be read from the browser.
- The join built and tested end to end
- Verified on a real conversion
- Reconciled against the source's own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
The join built server-side from the source's own records, so it does not depend on a browser being present when the conversion happens.
- Events sourced from the system of record, not the browser
- Identifier captured and persisted end to end
- Deduplicated at the destination
- Reversals wired where the source supports them
- 95%+ accuracy guaranteed in writing
Full 1st-party stack
Every destination fed from one place, plus monitoring so a broken join surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- All paid destinations from one container
- CRM and offline loop
- Refunds and cancellations reversed everywhere
- Monitoring per 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.
01Why aren't my CallRail conversions showing in DV360?
Almost always because the Floodlight activity, not a click identifier never reached the CallRail call record. Dynamic number insertion has to run before the visitor dials. If the swap script is deferred, blocked by consent, or the visitor calls from a cached page, CallRail records the call but cannot tie it to the session, and the click identifier goes with it. Calls from the Google Business Profile or a printed number never had a session at all. Measure coverage before debugging the dispatch.
02What identifier does DV360 need?
DV360 attributes through Floodlight rather than through gclid. Floodlight is Campaign Manager's conversion counter, it has its own configuration and its own attribution model, and a conversion action built in Google Ads does not exist in it. Two Google products, two conversion systems, one very common and expensive assumption.
03Where should the event come from?
The CallRail post-call webhook. Send after the call completes, filtered by duration or by the qualification your team applies. Sending on call start counts wrong numbers and hang-ups as conversions.
04How do I know it worked?
Campaign Manager reports Floodlight activity counts directly. Check those, not the DV360 campaign view, and compare against your own order count for the same window.
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 yourCallRail → DV360 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 CallRail → DV360 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 CallRail and DV360 joined properly
Book a free 30-minute call. We measure your identifier coverage live on your own account, and you leave with a written plan — including the option that you don't need us.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
