Columbus, OH // Better Analytics & Digital
Columbus Marketing Infrastructure — B.A.D.
B.A.D. Marketing. On Purpose.
measure everything. own everything.
We build the marketing machine, then we run it. Not a service you rent.
We build the stack, the data pipeline, and the attribution — then we run campaigns on top of it. Not a service you rent.
You're spending money on marketing you can't measure. We fix that first.
Here's what usually happens: you hire someone to run your marketing, they send you a report full of impressions and clicks, and everyone nods like that means something. Meanwhile, you can't connect a single dollar you spent to a single dollar you earned.
We start where everyone else stops — at the infrastructure. Tracking that actually works. Data that actually connects. Reporting that actually tells you what happened and why.
Then we run your campaigns on top of it. And you see everything.
This isn't theory. The person who builds it does exactly this, in-house, for a four-dealership auto group — every day, with a six-figure monthly budget on the line.
The usual stack is a client-side GA4 tag, a few platform pixels, and a dashboard of impressions and clicks. Browser-side prevention — ITP, ad blockers, consent gaps — strips a chunk of your events before they're ever counted, and last-click hands the credit to whoever showed up last. You're optimizing against numbers that are both incomplete and misattributed.
We start at the data layer: a first-party, server-side endpoint that captures what the browser blocks, identity stitched across the funnel, and a clean warehouse export you can actually query.
Then we run campaigns on top of it — and every decision traces back to revenue you can audit.
This isn't theory. The person who builds it runs this exact stack in-house for a four-rooftop dealer group — click to closed sale, every day, on a live P&L.
What this means in practice
Server-side tracking that captures what browsers block and client-side scripts miss.
First-party sGTM endpoint capturing events client-side prevention strips: ITP-truncated cookies, blocked pixels, consent-mode gaps. Built to run at 100% event coverage with Event Match Quality in the 9s — scores client-side setups don't see.
Real attribution — from the first click to the closed deal, not vanity metrics dressed up as results.
Click IDs persisted to the CRM, offline conversions fed back to ad platforms via API, full-funnel join from gclid to closed revenue. Attribution you can audit — not a dashboard widget you have to trust.
Dashboards you'll actually open. Built for business owners, not analysts.
Custom dashboards built for your business — not 40 default GA4 reports. The five numbers that matter, joined to revenue on a clean BigQuery export, refreshed daily.
Three phases. Zero handoffs.
Most agencies split strategy, execution, and measurement across three different teams. Information dies at every handoff. We don't. The person who builds your tracking is the same person running your ads and reading the data.
Most agencies split strategy, execution, and measurement across three teams, and context leaks at every handoff — a spec gets written, translated, re-translated, until no one owns the whole picture. We don't. The person writing the tags is the same person modeling attribution, running the accounts, and querying the warehouse. Nothing is lost in translation because nothing gets translated.
Phase 01
Tear it apart.
Take the stack apart.
We audit everything — your tracking, your analytics, your campaigns, your vendor relationships. You get an honest, uncomfortable picture of where you actually stand. Most businesses have never had someone do this, and the findings are rarely fun.
We inspect the whole pipeline — tag firing and sequencing, Event Match Quality, event dedup, consent-mode configuration, attribution windows, and data-layer integrity. You get an honest read on what's actually being captured versus what your reports claim is happening. Most stacks have never been audited at this level, and the findings are rarely comfortable.
You'll know exactly what's broken and what it's costing you.
You'll know exactly where the pipeline leaks — and what those dropped events are costing you.
Phase 02
Build the machine.
Build the data layer.
Before we spend a dollar on ads, we build the infrastructure underneath your marketing — the tracking, the pipelines, the attribution, the dashboards. It's yours when it's built. This is the part most agencies skip entirely — because they can't do it, and because it's harder to bill for infrastructure than it is for ads.
Before a dollar moves through the ad accounts, we stand up the infrastructure underneath your marketing: a first-party, server-side GTM endpoint, a clean warehouse pipeline, an attribution model that survives an audit, and custom dashboards joined to revenue. Built to be handed over, not rented back to you. This is the layer most agencies skip entirely — because they can't build it, and because infrastructure is harder to bill than ad spend.
Your marketing becomes measurable for the first time.
Every event is captured at the source and traceable end to end — measurable for the first time.
Phase 03
Run it and prove it.
Run it against the warehouse.
We run your campaigns — SEM, SEO, paid social — on top of that infrastructure. Every dollar is tracked. Every result is visible. Every decision is backed by evidence, not guesswork. And because we built the measurement layer, we can actually prove what's working.
We run your campaigns — SEM, SEO, paid social — optimized against clean, joined-to-revenue data instead of platform-reported vanity numbers. Bids move on what actually closed, not on what a pixel guessed. And because we built the measurement layer, every decision traces back to a row in the warehouse you can query yourself.
You'll never wonder where your money went again.
Every dollar of spend reconciles to a conversion you can trace to revenue.
Why zero handoffs matter
There's no account manager relaying your questions to a team you've never met. No telephone game. The strategy, the build, the analysis, and the debugging all happen at the same desk — so when something breaks at 10 PM, the person who built it is the person who fixes it.
When a tag stops firing or a conversion import silently breaks, diagnosing it takes the same context as the campaign decision riding on that data — and that context lives in one head, not scattered across a ticket queue. No account manager relaying your questions to a team you've never met. When something breaks at 10 PM, the person who built it is the person who fixes it.
Everything on this page is measured. Including you.
Here's what it's picked up since you got here. It keeps going while you read.
Real dataLayer entries and real network hits, each tagged with where it came from. The tape itself sends nothing anywhere.
- dataLayer
- 0
- network
- 0
- this page only
- 0
watching
Waiting for this page's analytics to fire.
Listening for a ga4 collect hit on the wire.
counted · google route refused · first-party
Your browser blocked Google's tag manager — and this page counted you anyway, through its own domain. Most sites would have lost you right there. That's what we build.
googletagmanager.com was refused client-side. The gateway served the container first-party and the ga4 hit landed on this domain with a 2xx. Same visit, recovered. That's the build.
counted · first-party
Your visit was counted — and the data left through this site's own address, not Google's. Plenty of browsers block the usual route, and most businesses never see those visitors at all.
ga4 hit landed on this domain with a 2xx — first-party via the tag gateway, not google-analytics.com. The route most blocklists key on is not in the path.
google route refused · sent first-party
Your browser blocked Google's tag manager — and this page still sent your visit out through its own domain. Your browser keeps the final receipt private, so that's as far as the page will claim.
googletagmanager.com was refused client-side; the gateway served the container first-party and a ga4 hit left for this domain. This engine doesn't expose the hit's status, so landing is unconfirmed — not assumed.
sent · first-party
Your visit left through this site's own address, not Google's — the route blockers are least likely to cut. Your browser keeps the final receipt private, so that's as far as the page will claim.
ga4 hit dispatched to this domain — first-party via the tag gateway. This engine doesn't expose the hit's status, so landing is unconfirmed here — not assumed.
sent · third-party
Your visit was sent to Google's servers. Plenty of browsers block that route — and most businesses' reports just quietly count fewer people.
ga4 hit dispatched cross-origin, so this page can't confirm it landed. That's the route blockers cut first.
loaded · no hit yet
The tag manager loaded, but no analytics hit has left this page yet. The tape will update the moment one does.
Container present, zero ga4 hits observed so far — consent, a blocked collect endpoint, or timing. Still listening.
not counted · blocked
Your browser blocked this page's analytics. You're one of the visitors most businesses never see — their reports just have fewer of you in them. That gap is the job.
No container, no hit — client-side refusal. This visit does not exist in GA4. Multiply by every blocker session: that's the gap in most reporting, and it's the job.
inconclusive
Couldn't confirm either way — the page hasn't finished loading.
Couldn't confirm either way — the load event never fired.
What this page runs
- Google Tag Manager → Google Analytics 4
- Vercel Web Analytics · Speed Insights
That's what this page can see from inside your browser. It doesn't know your name, your email, or who you are — that's the part you'd tell us. Want to see this for your own customers? That's Phase 01.
That's the full inventory. No identity, no fingerprinting — and the tape itself stores and sends nothing. Want this level of visibility on your own funnel — server-side, joined to revenue? That's Phase 01.
Talk to usGianni Young
The kind of marketer agencies warn you about.
Most marketers configure a stack someone else built. He builds the stack.
Director of Marketing running the entire digital operation — and a six-figure monthly ad budget — for a four-dealership automotive group in Central Ohio. Built the department from scratch. Server-side tracking that captures what most setups quietly lose. Closed-loop attribution from ad click to vehicle sale — something most of the automotive industry operates without. Two production web applications shipped and running.
B.A.D. Marketing is what happens when that same operator builds for you. Same infrastructure-first approach. Same obsessive measurement. Same refusal to hand you a report full of vanity metrics and call it a win.
Director of Marketing for a four-rooftop automotive group in Central Ohio — the entire digital operation, built from zero. First-party server-side GTM feeding a BigQuery warehouse, with Meta CAPI holding EMQ in the 9s. Closed-loop attribution that ties a gclid to a signed buyer's order — a join most dealer groups, and most of their agencies, have never stood up. Two production web apps shipped, deployed, and live.
B.A.D. Marketing is that same architecture pointed at your business. Infrastructure first. Measurement that survives an audit. No report engineered to look good in a meeting.
Operator profile
Built for businesses that want the strategy, the build, and the reporting coming from the same desk — and everything that gets built is yours to keep.
Built for teams that need the person modeling attribution to be the same person writing the tags, running the accounts, and querying the warehouse — on a stack you own when it's done.
You know you want to.
If your tracking is broken, your reporting is decorative, or your current agency can't explain where your money went — we should talk.
If your Event Match Quality is sliding, consent mode is quietly dropping events, your attribution never moved off last-click, or there's no warehouse behind any of it — we should talk.
Open channel
Tell us what's broken, what you're trying to build, or what you suspect your current setup is hiding.
Short brief or long rant. Both work.
Send the symptom or the spec — a tracking gap you can't close, a pipeline you want built, or the events you suspect your current setup is quietly dropping.
Short brief or long teardown. Both work.