Google Ads and Meta Microconversion Setup
Implemented and QA’d the client’s Resource / Guide Download microconversion tracking across Google Ads, Meta, and GA4. The existing GTM setup depended on a stale download_report custom event, but GTM Preview showed the live resource flow emitted gtm.formSubmit on /resources/research/ pages. The fix created a resource-specific form trigger, connected it to Google Ads and Meta, updated GA4 download reporting, and added Enhanced Conversions through user-provided data extracted from HubSpot form fields. The work also separated platform scopes: Meta native lead forms belonged in Ads Manager, while MQL/SQL tracking remained blocked until Salesforce-to-HubSpot lifecycle sync was available.
The fix replaced a dead custom event with the actual live HubSpot form-submit signal.
Role: Sole GTM and paid media tracking implementer
The Problem
The client needed microconversions for Google Ads and Meta because Google Ads was only optimizing to Booked a Demo and Salesforce integration was not yet available. The team also needed Meta setup readiness for a Q3 relaunch using native lead forms and lower-funnel signals.
The existing GTM setup had an old download_report custom-event trigger that did not fire on the current resource form flow. The live form behavior emitted gtm.formSubmit on /resources/research/ pages, while some legacy CTA click logic also caused false-positive Book a Demo tracking on resource pages.
The work required reading the current GTM export, interpreting a GTM Preview trace, separating legacy events from current behavior, creating cross-platform conversion coverage, and avoiding scope creep into Meta native lead forms and future MQL/SQL lifecycle events.
Approach & Architecture
Created and validated Google Ads, Meta, and GA4 tracking for Resource / Guide Download based on the current HubSpot form submit behavior. Corrected the trigger strategy from the obsolete download_report event to a form submission trigger scoped to /resources/research/. Added enhanced conversion support using GTM User-Provided Data variables and documented that Meta Native Lead Form Submission is managed in Meta Ads Manager, not GTM. Also identified and fixed or documented false-positive Book a Demo CTA behavior on resource pages.
The GTM container GTM-XXXXXXX runs base tags and conversion tags for the client. The new conversion logic uses native GTM form submit events on resource research pages, maps them to Google Ads and Meta web events, updates GA4 download report tracking, and enriches Google Ads conversions with user-provided data extracted from HubSpot form fields.
Key Decisions & Trade-offs
Hardest Part
Diagnosing that the existing download_report event did not match the live HubSpot resource form flow and replacing it with a reliable resource-specific form submit trigger.
Technical Detail
Resource / Guide Download event mapped to GA4, Google Ads, and Meta; MQL/SQL deferred until Salesforce-to-HubSpot lifecycle stage sync.
Client-side GTM web container on client.com.
Used GTM Preview to inspect gtm.formSubmit, Page Path, Click ID, form details, and tag firing; validated Meta custom conversion data source and Google Ads Enhanced Conversions setup.
Code
function() { var form = {{Form Element}}; if (!form || !form.querySelector) { return undefined; } var field = form.querySelector('input[name="email"], input[type="email"]'); if (!field || !field.value) { return undefined; } return field.value.trim().toLowerCase();
}function() { var form = {{Form Element}}; if (!form || !form.querySelector) { return undefined; } var field = form.querySelector('input[name="firstname"], input[name="first_name"], input[name="firstName"]'); if (!field || !field.value) { return undefined; } return field.value.trim();
}function() { var form = {{Form Element}}; if (!form || !form.querySelector) { return undefined; } var field = form.querySelector('input[name="phone"], input[type="tel"], input[name="mobilephone"]'); if (!field || !field.value) { return undefined; } return field.value.trim();
}ChatGPT was used as the MarTech pair-engineer to inspect GTM exports and preview behavior, reason through trigger failures, produce exact GTM implementation steps, and draft Asana/client communications.
Measured Results
The Resource / Guide Download microconversion was created and validated across Google Ads, Meta, and GA4 using the current HubSpot form behavior. The work also clarified that Meta native lead forms and MQL/SQL events required separate platform or CRM-side setup rather than browser GTM changes.
| Metric | Value | Before | Source |
|---|---|---|---|
| Meta Q3 relaunch budget noted in request Budget context, not an implementation result. | $78K annual budget | n/a | Ticket/request context |
Every figure above was recorded during the work itself. Where no number was measured, none is claimed.