Mastering Conversion Tracking & Data Infrastructure
Marketing without accurate data is just guessing. To truly understand our Return on Investment (ROI)—and execute campaigns like our GRC Scale-Up—we had to tear down our existing tracking setup and rebuild it from the ground up.
The Imperative for Data Standardization
Our primary goal was simple: get accurate ROI across all channels. However, not all leads are created equal. To reflect this in our reporting, we standardized conversion values in CAD based on the intent and potential value of the interaction.
Here is how we valued our conversion events:
- Request Demo (Website): $200
- Request Demo (LPs): $150
- Gartner LPs: $150
- Fit Analyzer Report: $100
- Case Study Forms: $50
- Contact Form (Website): $25
- Phone Call: $25
Assigning specific monetary values to conversion actions allows us to bid more intelligently and measure the true impact of our campaigns.
Infrastructure Overhaul: Migrating to GTM
Previously, our Google Analytics implementation was hardcoded directly into the website header. This made updates slow and prone to errors.
We made the strategic decision to migrate all core tags to Google Tag Manager (GTM). This centralization allows for faster deployment, better version control, and the flexibility to add or modify tags without touching the codebase.
Debugging and Refining Conversion Triggers
During the migration, we uncovered several tracking pitfalls that were skewing our data.
The Fit Analyzer Issue
Our “Fit Analyzer” conversion goal was originally set to trigger on a page visit (/fit-analyzer/). This was a vanity metric that didn’t guarantee a lead was generated. We shifted the trigger to fire only on a successful form submission, ensuring we only counted actual leads.
The Success Page Trigger Fix
Our Google Ads conversion tag was triggering on any URL containing “success”. This was too broad and led to false positives.
We refined the trigger to use a specific Regular Expression (RegEx) that matches only the dedicated success page:
https:\/\/www\.standardfusion\.com\/request-demo\/success\/
New Goals
We also created specific Google Analytics goals to differentiate between lead sources:
- Request Demo (LPs): Category = form submission, Action = form id 2186
- Request Demo (Website): Category = form submission, Action = form id 112
Multi-Touch Lead Attribution
A single touchpoint rarely tells the whole story. We needed visibility into the entire customer journey.
Pipedrive vs. Leadboxer
We wanted marketing to own lead source details in Pipedrive. However, Pipedrive typically only records UTM parameters from the last touch.
To bridge this gap, we utilized Leadboxer. Leadboxer tracks anonymous users and records the first touch. By matching this data via email, we can pass the first-touch information into Pipedrive, giving us a fuller picture of attribution.
Combining first-touch data from Leadboxer with last-touch data in Pipedrive solves the multi-touch attribution puzzle.
Expanding Our Reach
Finally, we refined our Leadboxer segments. We removed a restrictive geography filter to ensure we were capturing lead data not just from the US, but also from key markets including Canada, UK, Germany, France, Australia, New Zealand, and Mexico.
Building a Single Source of Marketing Truth
By standardizing our data, migrating to GTM, and refining our attribution models, we now have a source of truth we can trust. This infrastructure is the backbone of our marketing strategy moving forward.
