All case studies
Meta Ads Manager leads next to HubSpot contacts for the same two ad sets 1Meta: 30 + 12 leads 2HubSpot: 11 + 10 contacts
  1. Meta: 30 + 12 leads
  2. HubSpot: 11 + 10 contacts
View full size
The gap Meta counted 30 and 12 website leads. HubSpot found only 11 and 10 contacts from the same ads.

One Click Contractor

Fixing Meta conversion tracking

  • B2B SaaS
  • Marketing operations
  • Paid media

The brand

One Click Contractor makes sales software for home improvement contractors, from estimates to signed proposals.

Why

Meta was reporting far more website leads than HubSpot could find. Meta was learning from bad data, and the team could not trust the numbers.

How

  1. I audited every Meta event on the client side and the server side.
  2. I removed 9 legacy Lead events that fired on page visits, button clicks, emails and phone links, and counted the same lead more than once.
  3. I found an old Signals Gateway trial that copied every Pixel event to the server, on top of HubSpot’s Conversions API. I disconnected it with no loss of tracking.
  4. Now the Meta Pixel in Google Tag Manager handles page views, and HubSpot’s Conversions API sends MQLs, SQLs and opportunities back to Meta.

What I learned

  • When ad platform numbers look too good, check for duplicate events first.
  • Optimising for MQLs and opportunities, not form fills, tells Meta to find leads that become customers.

Want something like this for your team?

Let’s talk

Let’s connect

Let’s work together

I’m open to full-time roles and consulting. Tell me about your mission and who you want to reach. I’ll reply with honest next steps.

Sound like you? Tick the boxes 0/4 ticked

Don’t use a mail app? Open the email in Gmail or Outlook.

LinkedIn