Overview
Kung Pow Marketing was running campaigns across multiple channels, including Google, Meta, and LinkedIn.
The problem was not a lack of data.
The problem was that the data did not answer the questions the team actually needed answered.
They could see spend.
They could see leads.
But they could not confidently answer:
- Which channel produces the best leads?
- What is our real cost per MQL?
- What is our cost per SQL?
- Which platform is generating qualified pipeline?
- Where should budget move next?
Tracking existed.
Reporting existed.
But the system was not yet aligned around lead quality.
The work focused on bringing those pieces together.
The Situation
Cross-Channel Performance Was Hard to Compare
Google, Meta, and LinkedIn all reported performance differently.
Each platform had its own definitions, attribution logic, and conversion view.
That made comparisons difficult.
A channel could appear efficient based on cost per lead while performing poorly once lead quality was taken into account.
The team needed a more consistent way to compare performance.
Qualification Was Not Clearly Defined
Before building better reporting, there was a more fundamental question:
What actually counts as a qualified lead?
The reporting could not be meaningful until the business had clear definitions for:
- Lead
- MQL
- SQL
Without those definitions, cost-per-acquisition reporting risked comparing different types of outcomes as if they were equal.
Internal Traffic Was Polluting GA4
Internal testing and QA activity was also entering production reporting.
That meant:
- Sessions were inflated
- Behavioural data was less trustworthy
- QA activity could distort performance interpretation
The challenge was to remove internal traffic without creating a fragile setup or relying on solutions that would disrupt legitimate sessions.
Cost Metrics Stopped Too Early
The business could calculate:
Cost per Lead
But that was only the first layer.
They needed visibility into:
Cost per MQL
and
Cost per SQL
because those metrics were much closer to the commercial outcome.
The Approach
Define What “Qualified” Actually Means
The first step was not technical.
It was definitional.
Before touching the dashboard, the reporting model needed clear qualification stages.
The framework established:
- What makes a lead an MQL
- What makes an MQL an SQL
- How a contact moves from one stage to the next
- Which fields and outcomes should drive reporting
This gave the data meaning before visualisation.
Standardise Cross-Channel Tracking
Tracking across Google, Meta, and LinkedIn was reviewed and aligned around consistent business outcomes.
The work included areas such as:
- Google Ads conversion tracking
- Enhanced Conversions
- GA4 event collection
- Consistent conversion definitions
- More standardised reporting across accounts
The objective was not to make the platforms identical.
It was to create enough consistency that performance could be compared sensibly.
Clean Internal Traffic Without Breaking Production Data
A session-based internal traffic solution was implemented using:
- URL parameter handling with
?internal=true sessionStorage- GTM-based logic
- Automatic session expiration
The approach avoided persistent cookies and limited the exclusion to the active session.
This meant internal QA traffic could be removed while keeping the production environment intact.
The same approach could then be reused across multiple client setups.
Build Reporting Around Lead Quality
The reporting layer was rebuilt around qualification rather than raw conversion volume.
The dashboard included:
- Total Leads
- MQLs
- SQLs
- Cost per Lead
- Cost per MQL
- Cost per SQL
- Channel-level CPA comparison
- Cross-channel performance views
Instead of opening three ad platforms and manually trying to reconcile numbers, the team could review qualified performance in one place.
The Result
Kung Pow could now evaluate marketing based on the quality of what was being acquired, not simply the volume.
The team gained visibility into:
- Which channels generated the most qualified leads
- Which channels produced SQLs most efficiently
- Where lead volume looked strong but quality was weak
- Where budget could be reallocated
- Where funnel quality was deteriorating
Reporting became much easier to interpret.
Cross-Channel CPA Clarity
Google, Meta, and LinkedIn performance could now be compared using a more consistent qualification framework.
Highlight
One view across Google, Meta, and LinkedIn
SQL-Level Reporting
Instead of stopping at cost per lead, reporting moved further down the funnel.
The team could now monitor:
Cost per Lead
Cost per MQL
Cost per SQL
This changed the quality of budget conversations.
Cleaner GA4 Data
Internal QA sessions could be excluded without disrupting legitimate website traffic.
That made behavioural and acquisition analysis more trustworthy.
Highlight
Session-level internal traffic handling
Business Impact
The biggest shift was in the questions the team could ask.
Before:
“How much are we spending?”
and
“How many leads did we generate?”
After:
“Which channels are actually producing qualified pipeline?”
That is a much more useful conversation.
The reporting system made it easier to:
- Spot inefficiencies quickly
- Compare channels fairly
- Defend budget decisions
- Identify quality problems earlier
- Focus optimisation on outcomes closer to revenue
Tracking stopped being reactive.
It became strategic.
Why This Matters
Lead generation becomes misleading when every conversion is treated as equal.
Ten cheap leads are not necessarily better than five expensive ones.
If the five expensive leads become SQLs and the ten cheap leads do not, the cheaper channel may actually be the worse investment.
That is why qualification matters.
The closer measurement gets to the business outcome, the more useful the optimisation becomes.
This project moved reporting from:
Traffic → Lead
toward:
Traffic → Lead → MQL → SQL
That created a much stronger basis for decision-making.
Key Takeaway
The Cheapest Lead Is Not Always the Best Lead.
Cross-channel reporting becomes useful when platforms are judged against the same business outcome.
For Kung Pow, the important improvement was not collecting more data.
It was creating a reporting model that connected spend to qualification.