Suppression Scoring and Locked First-Touch Attribution for an Automotive F&I Provider
Competitor and internal traffic polluted the sales queue of an automotive F&I provider. We hardened the HubSpot architecture with a -1,000 point suppression scoring model and custom FTLS/LTLS attribution properties, so campaign ROI could be reported from source data that no longer gets overwritten.
Executive Summary
Context
A Tier 1 automotive F&I provider needed a technical overhaul of its HubSpot environment: record fragmentation had to end, and a functional lead-to-revenue attribution model had to replace it.
What We Built
We executed a programmatic record cleanup and deployed a scoring model featuring a 100-point MQL threshold and a -1,000 point negative suppression trigger.
Tech Stack
- HubSpot Marketing Hub Enterprise
- HubSpot Sales Hub Enterprise
- Google Tag Manager (GTM)
Not a fit if no one on your team will own the attribution workflows after launch. The First Touch and Last Touch source properties only hold their value while a set-if-null workflow keeps running, and if that workflow ever pauses, later form fills quietly overwrite the original source data and the ROI reporting drifts, with nothing to flag that it happened.
The Challenge
2,300+ contact records had no standardized link to their respective dealership companies, so the sales team couldn't see account-level engagement history. Attribution had the same problem: the environment lacked any framework for it, so First Touch (original source) and Last Touch (most recent conversion) data was either missing or frequently overwritten by subsequent form submissions. That left marketing ROI effectively unmeasurable, because the CRM couldn't tell a high-intent dealership prospect from a competitor doing market research.
Our Approach
Record-level cleanup came first: domain name matching bulk-associated orphaned contacts with their parent companies, and we standardized naming conventions (e.g., [Dealer Group] - [Store Name]) so duplication couldn't creep back in. For lead quality, a scoring workflow awards positive points for job titles (e.g., F&I Manager) and high-intent behavior, while a -1,000 point suppression rule hits competitor domains and internal traffic. We chose suppression over exclusion filtering deliberately, since junk leads stay hidden from sales but remain in the database, keeping aggregate reporting accurate across the full record set. The attribution gap got the same treatment: custom First Touch Lead Source (FTLS) and Last Touch Lead Source (LTLS) properties were deployed using hidden form fields and "do-not-overwrite" workflow logic.
This engagement is part of our customization + optimization work for finance & insurance organisations.
Impact
Automated Lead Qualification
The 100-point MQL threshold now automates the handoff from marketing to sales. Only prospects who meet both demographic and behavioral requirements enter the sales view. The manual vetting of every form submission is gone.
Systematic Noise Suppression
The -1,000 point suppression trigger programmatically removed internal tests and competitor inquiries from the active sales queue. Reps no longer work records that will never generate revenue.
High-Fidelity ROI Reporting
The FTLS/LTLS framework locks the original lead source the moment a record is created, while the most recent touchpoint is captured separately. So leadership can now attribute revenue to specific campaigns with accuracy and without the risk of data overwriting.
2,300+ Records Programmatically Relinked
Programmatically linking the 2,300+ records pushed all engagement data up to the company level, so sales reps now see a complete timeline of interactions across an entire dealership group, with no contact left isolated from that history.
Contacts matching competitor or internal email domains receive a -1,000 point score. Unlike a delete or filter action, suppression keeps the records indexed for reporting while technically disqualifying them from MQL status; without it, competitor activity would skew conversion rates and lead-volume metrics alike.
Custom properties capture the original source (FTLS) through a "set if null" workflow, preserving that data for life. A secondary property (LTLS) updates with every new conversion. This logic needs maintenance: if the workflows pause, subsequent form fills will overwrite the original source data and destroy ROI visibility.
A manual "Pre-qualified MQL" checkbox was added to contact records. It allows high-value manual imports (e.g., tradeshow leads) to bypass the 100-point automation. Those contacts carry no digital behavioral history. The checkbox keeps speed-to-lead for offline events from stalling on that gap.
HubSpot's domain matching rules bulk-linked orphaned contacts to company records by email domain suffix. That restored the "association integrity" account-based sales views depend on. These rules need upkeep during manual imports. Skipping them leads to record duplication and broken reporting hierarchies.
The CRM couldn't tell a high-intent dealership prospect from a competitor doing market research. First and last touch source data was also missing or overwritten by later form submissions. Now a -1,000 point suppression rule hits competitor domains and internal traffic, so junk leads stay hidden from sales but remain in the database. The "FTLS" and "LTLS" properties use hidden form fields and do-not-overwrite logic, so the original source stays locked.
FAQ
The scoring rules decay without maintenance. If new job titles or high-intent web pages aren't added to the positive rules, the system will slowly stop identifying qualified leads and MQL volume will drop. If competitor domains aren't updated, noise starts re-entering the sales queue.
Automation works for inbound traffic because behavior can be tracked over time. Manual imports are different. A tradeshow list arrives with zero digital history and would never hit 100 points. The manual override lets reps verify intent offline and "fast-track" the lead into the sales pipeline immediately.
