EZRaider USA · Lead tracking implementation

Connecting test-drive inquiries to trustworthy conversion signals.

EZRaider USA website showing its electric all-terrain vehicles and Book a Drive call to action.

Summary

Connected successful Book a Drive inquiries to GA4, Google Ads, and Meta while preserving the existing GoHighLevel contact handoff. The implementation separated lead conversions from engagement, paired browser and server signals, and gave the team a documented way to validate and read the data.

Services

Measurement strategy & event design
GTM, GA4 & advertising conversions
Consent & CRM integration
Production QA & reporting handoff

Industry: Electric all-terrain mobility
Conversion: Successful Book a Drive inquiry
Delivery: July 2026 implementation

Coverage

Measurement platforms connected: 3
Engagement event types: 6
Meta delivery paths: browser + server: 2
Successful lead definition: 1

Delivery

Lead tracking in the delivery report: Live
GoHighLevel CRM handoff: Preserved
Consent-path QA: Passed
Live test lead: Completed

Enhancements

Google Enhanced Conversions: Enabled
Meta audience events: Enabled
Meta browser/server deduplication: Shared ID
Platform reporting handoff: Documented

01 Client & Context

EZRaider USA introduces buyers to an electric all-terrain mobility platform. The website helps visitors explore models, understand the vehicles, and make contact about a test drive. For this journey, a successful inquiry is the meaningful conversion that connects website activity to a sales conversation.

The measurement work covered the lead journey across the website, advertising platforms, and existing CRM. It also made supporting actions visible: visitors viewing a model, watching a product video, tapping a phone number, or choosing Book a Drive before completing the form.

02 Challenge & Goals

Challenges

A click on Book a Drive and a successfully delivered inquiry needed distinct definitions. Counting both as the same outcome would make advertising and website reporting harder to interpret.
GA4, native Google Ads conversions, and Meta needed a consistent lead signal without duplicate optimization or browser/server double counting.
Measurement had to run alongside the existing contact workflow, preserving its fields and CRM delivery while responding to the visitor’s consent choice.
The client needed a usable handoff that explained what fired, where to find it, and why platform totals could differ from raw inquiries.

Goals

Define one primary conversion at successful form completion after the spam check.
Connect that conversion to GA4, Google Ads, and Meta with explicit counting rules.
Track useful engagement separately and preserve the GoHighLevel contact handoff.
Validate consent paths and a live test lead, then document the reporting workflow.

03 Discovery

We mapped the complete inquiry journey: the visitor reaches a model or contact page, submits the form, passes Cloudflare Turnstile, and receives a successful submission response. That success point became the conversion trigger.
We assigned each platform a clear role. GA4 receives generate_lead for analysis; Google Ads uses the native Book A Drive - Lead conversion as primary; the GA4 import remains observation-only. Meta receives matching browser and server Lead events.
We defined six supporting event types: phone clicks, email clicks, CTA clicks, outbound clicks, video plays, and model views. Form location, buyer type, model interest, unit count, and purchase timeline supplied useful non-personal lead context.
Consent was part of the event design. The handoff documented default-denied behavior, activation after acceptance, and what happens after rejection, including the effect on reported conversion coverage.

Delivery-report table defining phone, email, CTA, outbound, video, and model-view engagement events. — Original July delivery-report excerpt: six engagement signals defined separately from the primary lead conversion.

04 Solutions

Count the successful inquiry at the right moment

Journey: Book a Drive connects a visitor’s interest to the sales team. A button click shows intent; a successful form submission creates the inquiry.
Implementation: Trigger the lead signal after the successful form submission and spam check, then send the action to GA4, native Google Ads, and Meta.
CRM: Keep the GoHighLevel submission and existing contact fields in place. Tracking runs alongside the contact handoff.
Validation: The July delivery report records a live test lead and identifies the core setup as live in production.

A defined conversion point joins the advertising signal to a successfully captured inquiry, while the sales team continues receiving the contact.

Four-step lead flow: successful form, browser events, server signal, and one deduplicated Meta lead. — Original client-guide diagram showing the lead path and preserved GoHighLevel handoff.

Pair browser and server events around consent

Deduplication: Meta Pixel and Conversions API send the same Lead event with a shared event ID, allowing Meta to recognize the browser and server copies as one lead.
Before a choice: Google consent defaults keep analytics and advertising storage denied. The implementation provides first-visit consent controls.
After a choice: Acceptance activates the allowed tracking. Rejection prevents Meta lead delivery; Google receives cookieless signals according to the configured consent behavior.
Data boundaries: GA4 event parameters contain reporting context, not names, email addresses, or phone numbers. Contact matching uses the applicable hashed-data mechanisms.

The browser/server design supports one counted Meta lead, with delivery tied to the visitor’s choice and a clear explanation of expected reporting differences.

Client-guide consent diagram explaining behavior before a choice, after acceptance, and after rejection. — Original implementation guide: the three consent paths covered in the client handoff.

Reported conversions can be lower than raw inquiries when visitors decline tracking. The study does not assign a recovery rate to modeled conversions.

Make the measurement usable after launch

Google Ads: Use the native Book A Drive - Lead action as primary. Keep the GA4 lead import observation-only so the same inquiry does not become two primary optimization signals.
Reporting: Document the event names, counting logic, and reporting locations in GA4, Google Ads, and Meta, including where to run live QA.
Enhancements: The updated delivery report records Google Ads Enhanced Conversions and Meta audience events as shipped on July 27. Audience signals include model views, Book a Drive CTA clicks, and video plays.
Handoff: Explain the difference between inquiry delivery, platform reporting, and processing time so the team can investigate the correct part of the journey.

The team received a working conversion setup and a practical reporting guide, with enhancement status distinguished from future reporting work.

Delivery-report table showing GA4, Google Ads, and Meta reporting locations and the native Ads primary-conversion rule. — Original updated delivery-report excerpt explaining where each conversion appears and how Google Ads counting is configured.

A custom reporting dashboard remained a proposed next step. It is not included as a delivered outcome.

05 Implementation & Development

Site-wide orchestration: Google Tag Manager provides the shared tracking layer across the site. Consent defaults are established before tag loading so event delivery follows the configured choice state.
Successful submission: The lead flow follows form validation and the spam check, preserving the CRM request and its contact fields. Browser and server Meta events share the same lead identifier.
Platform configuration: GA4 receives the lead and engagement taxonomy; Google Ads receives its native primary conversion; Meta receives browser/server Lead events and the documented audience signals.
QA & documentation: The delivery report records consent-path QA and a live test lead. The client handoff covers counting logic, privacy boundaries, platform reporting, and the July 27 enhancement update.

06 Results & Impact

Connected measurement: GA4, Google Ads & Meta
Supporting behavior: 6 engagement event types
Meta delivery: Browser + server, shared event ID
Delivery verification: Consent-path QA & live test lead

The July delivery report records the lead-tracking setup as live in production, with the existing GoHighLevel handoff preserved. Successful inquiries and supporting engagement now have distinct definitions and reporting roles.

The updated report records Enhanced Conversions and Meta audience events as live on July 27. Together with the client guide, the delivered work establishes how the team can verify the signal and interpret it in each platform.

The outcome documented here is measurement coverage, counting integrity, and an operational handoff. The project evidence does not establish a lead-volume lift, conversion-rate uplift, or improvement in return on ad spend.

Historical delivery snapshot: July 2026. Status and QA are recorded in the project’s client delivery reports; this case study is not a claim about current account performance. The custom dashboard was proposed, not delivered.

Book a free walkthrough

Review your website with Edu in a free 30-minute session. Identify 2–3 conversion priorities and leave knowing what to tackle next.

Book a free walkthrough

The full Shopify Conversion Audit is a separate service, starting at $1,000.