Conversion tracking for DevHub location sites
Your franchisees ask which ads brought their leads, and the DevHub site can only answer with one brand-wide number. Spam counts the same as a real quote request, and calls to the local number count as nothing. The fix is already half built: DevHub's Form builder stores the gclid, fbclid, msclkid and UTMs beside every lead in its contact log. We build the path from that log to Google Ads and Meta, per location, with spam removed, and prove it against your own lead records.
Free30 minutesNo obligation
DevHub · what breaks
What goes wrong with ads on DevHub sites
- 01
One GTM container, every location, one number
DevHub's googletagmanager plugin puts one container across a site, so a form conversion fires identically on every location page. Corporate sees a brand-wide lead total; no franchisee can say which ads produced theirs, and nobody can shift budget toward the territories that convert.
- 02
Spam gets flagged after the ad platform counted it
DevHub's filters mark a submission spam=true in the contact log and write the reason in the note, but the browser tag on the thank-you step fired seconds earlier. Bidding keeps learning from junk your own platform already labeled.
- 03
Calls to the local number never reach Google Ads
DevHub logs a link-call event on the franchisee's tel link, but that isn't a Google Ads conversion until it's wired. Call-heavy mosquito and pest campaigns get optimized as if nobody ever phoned, so the keywords that ring the office look like losers.
- 04
The gclid sits in the contact log, unused
Each form lead carries campaign_params with gclid, fbclid and msclkid. That is everything an offline upload needs, and it stays in the log while the brand bids on form fills it can't value.
DevHub · the fix
What changes — DevHub
Conversions carry the location
Form and call conversions include the DevHub location_id, so a franchisee's Google Ads account sees its own leads and corporate sees the roll-up.
Spam removed before bidding sees it
Conversions come from contact-log rows with spam=false and dispatched=true, not the thank-you page, so a flagged submission never counts.
Booked jobs close the loop
The gclid saved on the lead is matched to the estimate or job in your field software and uploaded with its value.
DevHub · architecture
What DevHub actually lets you hook into
These hooks come from DevHub's API docs and integrations page; anything unconfirmed is listed as a check.
- 1
GTM and gtag plugins
A googletagmanager plugin takes a container ID and a googleglobalsitetag plugin takes GA4 IDs, each set per site.
- 2
Per-site header and footer code
Each site has header_code and footer_code fields, plus the customtag plugin. This is where a Meta Pixel goes, since Meta is absent from DevHub's integrations list.
- 3
Contact log with click IDs
Every Form builder lead is stored with click IDs, UTMs, landing page, location_id, a spam flag and dispatch status, readable per site by API.
- 4
Lead dispatch to email, CRM or webhook
HubSpot, Salesforce, Zapier, ServiceTitan Scheduling Pro and WhatConverts are on the integrations list. We confirm which path your brand uses.
- 5
Google Enhanced Conversions, details unconfirmed
Listed under Lead capture on the integrations page; the API docs don't describe it, so we test on a live submission whether hashed email and phone reach Google.
DevHub · diagnose
Where DevHub tracking breaks, in diagnostic order
Start with the corporate container, because on a DevHub brand the usual fault is one tag setup copied to every location rather than a missing tag.
- 01
Does the form conversion carry a location?
Submit on two location pages. If each platform received identical events, no franchisee can be attributed.
- 02
Compare spam rows with reported conversions
A spam=true row that still appears as a conversion means the browser tag counted it before DevHub's filters ran.
- 03
Confirm the gclid lands in campaign_params
Submit from an ad-tagged URL and read the log. A redirect or consent tool that strips it gets fixed first.
- 04
Count what fires on a tel-link tap
DevHub logs link-call; Google Ads counts nothing unless a call partner or click-to-call conversion is wired.
- 05
Inventory plugins and code fields across sites
A GA4 ID in the gtag plugin plus the same ID inside GTM is the commonest double count here. Reverse-proxy sites carry their own header and footer code (and a gtm_id in DevHub's example), so they get checked separately.
DevHub · prove
The QA evidence — DevHub
Run on live location pages on the published domain, not the DevHub preview URL, since plugins and header code can differ.
Source of truth
DevHub contact logs filtered to spam=false, dispatched=true rows per site_id, joined to your CRM or field-software record of estimates booked and jobs sold
- One submission from an ad-tagged URL, gclid confirmed in campaign_params and on the Google Ads conversion.
- Exactly one Meta Lead event per submission, with a shared event ID between browser and server.
- A spam-flagged test submission confirmed absent from every ad platform.
- Submissions on two location pages arriving with different location values, and one tel-link tap recorded as a call conversion.
- Dispatched leads reconciled per site_id against Google Ads and Meta over a closed week.
- Repeated 30 days later and after any corporate template, plugin or header-code push.
DevHub · free audit
What we check in the free audit
- Does the form conversion carry a location?
- Compare spam rows with reported conversions
- Confirm the gclid lands in campaign_params
- Count what fires on a tel-link tap
- Inventory plugins and code fields across sites
Checked against
DevHub contact logs filtered to spam=false, dispatched=true rows per site_id, joined to your CRM or field-software record of estimates booked and jobs sold
Free30 minutesNo obligation
DevHub · when not to buy
When you don't need this on DevHub
Some DevHub brands need a short settings fix, and we say so on the call.
- If corporate runs one national Google Ads account at one value per lead and the contact-log count already matches Google, leave it alone.
- If your call-tracking partner already posts calls to Google Ads with the gclid and forms are a small share of leads, fix forms yourself through the GTM plugin.
- If franchisees don't run their own ads and never will, per-location attribution has nobody to serve.
- If the only fault is a GA4 ID set in both the gtag plugin and GTM, removing one takes ten minutes and we'll tell you which.
DevHub · what we deliver
The event map on DevHub
Quote form submitted
The Form builder submission on the location page, with location_id attached, deduplicated on one event ID.
Lead accepted
Only contact-log rows DevHub dispatched to email, CRM or webhook with spam=false. Rows in the spam or suppressed stage are excluded.
Call from a location page
A tap on the franchisee's tel link, or the tracked call from your call-tracking partner, tied to the click.
Estimate or appointment booked
From your CRM or scheduler, matched to the lead by the contact-log email and phone.
Job sold
The money event, uploaded with the saved gclid and real value.
Excluded on purpose
Franchise-development inquiries, existing-customer forms and store-locator searches are logged, never counted as sales leads.
Written guarantee
95%+ tracking accuracy
Measured against DevHub contact logs filtered to spam=false, dispatched=true rows per site_id, joined to your CRM or field-software record of estimates booked and jobs sold. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
DevHub questions, answered
Yes. DevHub documents a googletagmanager plugin that takes your container ID per site, plus a gtag plugin and header and footer code fields. The plugin puts the container on the page; it doesn't decide which location a conversion belongs to.
Yes, if the conversion carries the location. DevHub stores a location_id with each form lead, so a franchisee's Google Ads account can receive only its own conversions while corporate keeps the total.
DevHub's API docs show campaign_params on each contact log entry with gclid, gbraid, wbraid, fbclid, msclkid, UTMs and the first landing page. We still confirm it live, because a redirect or consent tool in front of the form can drop it.
Usually spam. DevHub's filters set spam=true on junk in the contact log, but a thank-you-page tag already counted it. Sending conversions only from spam=false, dispatched rows closes the gap.
Meta isn't on DevHub's integrations list. The Pixel goes in through the GTM plugin or header code, and the Conversions API side runs from your own records.
Yes. DevHub lists CallRail, CallTrackingMetrics, Marchex and Invoca as partners and logs tel-link taps itself. Either a partner posts the call with its click ID or we send a click-to-call conversion, keeping the corporate 877 number out of franchisee accounts.
More on DevHub
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside DevHub, and what their bookings feed
- EyeCareProYour EyeCarePro site books exams, but your ads can't tell a new patient from a recall
- DhaliYour Dhali site shows the schedule. The enrollment happens somewhere else.
- LinktreeYour ads say people clicked your Linktree. Did anyone book?
- InteractRVInteractRV conversion tracking for RV dealers whose ads can't tell a browser from a buyer
- YextYext shows clicks and calls by location. Your ads can't see any of them.
- happyclassYour happyclass widget shows the clicks. Your ads never see the enrollment.
- Autoshop SolutionsAutoshop Solutions conversion tracking that counts repair orders, not rings
- ShowitYour Showit inbox is full of inquiries. Google Ads says you got none.
Free · 30 min
Get DevHub tracking right across every location
Free30 minutesNo obligation
