Automotive retailGrowth story
One bilingual campaign engine, tracked from click to sales floor.
For a new-car dealership’s seasonal sales events, we built a reusable campaign engine: bilingual English and Spanish microsites on Google Cloud, GA4 and Google Ads conversions on a dedicated thank-you route, a documented UTM matrix spanning search, social, email, QR, print and radio, and automated lead alerts that push the dealership’s general manager to call right away.
- Engagement
- Client
- Client
- Platinum Hyundai of Tracy
- Sector
- Automotive retail
- Story
- Growth
The number
The one figure we’ll stand behind.
Open the receipt for where it came from, how it was counted and when we last checked it. How we count
11
channels in one documented UTM matrix, every link in English and Spanish
Google Search and Display, Facebook, Instagram, TikTok, Yahoo, Bing, email, QR codes, print and radio.
receipt
SOURCE · Campaign repository for a new-car dealership (documented UTM link matrix)
METHOD · Count of distinct channels with pre-built tracked links in the campaign’s written attribution plan.
VERIFIED · 2026-09
CLASS · repository
✓ every number on this site opens its receipt
CLAIM · utm-matrix
How we count01 · Where they started
Sales events on a deadline
The dealership sells in events: a Halloween weekend sale, a tent sale, Black Friday, the holidays. Each has its own offer, its own countdown and a short window, and each needs a page, tracking and a fast path from an interested shopper to a salesperson, in English and in Spanish.
02 · The wall
One-off pages throw away everything they learn
An event page built from scratch rebuilds its tracking from scratch, cannot say whether the flyer, the radio spot or the Instagram post drove a lead, and drops leads into an inbox where response time is left to chance. The dealership needed a system, not another page.
03 · What we built
What we built.
Named systems, described by what they do, one part at a time.
Part 1: One engine, set up per event
The event pages share one anatomy: countdown urgency, a credit-qualification form, a thank-you route built to fire the conversion, and an English/Spanish toggle that carries through to the lead. The frontend and the lead service deploy as separate Cloud Run services through Cloud Build, Docker and nginx, and the event sites were engineered with custom backends, deployment pipelines and tracking.
- Same page anatomy; new offer and deadline per event
- Separate frontend and lead-service pipelines
- Custom backends, deployment pipelines and tracking
Part 2: Measurement wired in, then tuned live
GA4 lead events fire on every form submit with language as a parameter, the Google Ads conversion fires on a dedicated thank-you route, and Hotjar heatmaps and session recordings show what shoppers actually do on the page. The commit history shows messaging, media and tracking tuned repeatedly while campaigns were live.
- GA4 lead events carrying language preference
- Google Ads conversion on a dedicated thank-you route
- Hotjar heatmaps and recordings for on-page behavior
Part 3: A UTM matrix for every channel, in two languages
A written attribution plan pre-builds tracked links for Google Search and Display, Facebook, Instagram, TikTok, Yahoo, Bing, email, QR codes, print flyers and radio, each in an English and a Spanish variant so performance can be split by language, with instructions for reading them in GA4.
- Print, radio and QR attributed the same way as paid clicks
- English and Spanish variants for split-testing by language
- Spanish social captions written into the plan
Part 4: Leads on the sales floor, fast
A lead-alert microservice sends a designed HTML email to the dealership’s general manager and partners the moment a form lands: the shopper’s details, language preference, what they are shopping for and a timestamp, with reply-to set straight to the shopper and a highlighted banner carrying the call-back target. The next iteration of the engine is designed to store leads in an access-controlled Postgres table (public insert, staff-only read) with ZIP, credit tier and down payment on every submission.
- Reply-to set to the shopper, not a no-reply box
- A call-back target on every alert
- Lead storage designed with row-level security
Part 5: Local search built in
The live event pages carry Event and dealership structured data (the Tent Sale adds FAQPage markup), hreflang alternates for the Spanish version, geo meta tags, social cards and preload tuning, aimed at the high-intent local searches shoppers make during a sale.
04 · Up close
The work, up close.
Real screens and real product photography, uncropped. Select any image to enlarge it.
05 · More receipts
The supporting figures.
Same rule as the headline number: each one opens to its source, its method and the month we checked it.
60 sec
follow-up target printed on every lead alert the engine sends
Each alert reaches the dealership’s sales leadership with the shopper’s language, what they want, and a reply-to straight to the shopper.
receipt
SOURCE · Lead-alert service in the campaign repositories for a new-car dealership
METHOD · The response-time prompt is part of the alert template itself. It is a target on every lead, not a measured average.
VERIFIED · 2026-09
CLASS · repository
✓ every number on this site opens its receipt
CLAIM · lead-sla
How we count2
sales events launched on the engine with live GA4 and Google Ads conversion tracking
The same engine was set up for two more events. We count only launches with production tracking on record.
receipt
SOURCE · Campaign repositories for a new-car dealership (tracking configuration in each event page’s code)
METHOD · Counted only event pages whose code carries live, non-placeholder GA4 and Google Ads conversion IDs.
VERIFIED · 2026-09
CLASS · repository
✓ every number on this site opens its receipt
CLAIM · campaign-engine
How we count