Why Pipeline On numbers differ from GA, Facebook, and Google Ads

Pipeline On numbers will not match Google Analytics, Facebook, Google Ads, or your CRM exactly. That is expected.

Each system measures a different thing, uses different rules, and loses different data.

What Pipeline On measures

Pipeline On focuses on eligible website visits that can be connected to a recovered homeowner profile.

It is not a replacement for:

Google Analytics traffic reporting.
Facebook Ads click reporting.
Google Ads conversion reporting.
Your CRM booked-job reporting.

Pipeline On is meant to show recovered homeowner opportunities that would otherwise remain anonymous.

Why Pipeline On is lower than website traffic

Most website visitors will not become recovered leads.

Reasons include:

The visitor cannot be matched with enough confidence.
The visit happens outside the available identity graph.
The visitor uses browser privacy tools.
The visit is from a bot, crawler, agency tool, or internal team member.
The visitor is outside your service area.
The tag did not fire because of consent settings.
The visit happens on a page where the tag is not installed.
The audit or account is not active.

Lower recovered lead volume does not automatically mean the tag is broken.

Why Pipeline On differs from Google Analytics

Google Analytics is session and event analytics. Pipeline On is recovered profile and lead intelligence.

Common differences:

GA can count anonymous sessions that Pipeline On cannot identify.
GA may use modeled or thresholded data.
GA event counts can include repeat visits from the same person.
GA can include internal traffic, bots, and low-intent pageviews if not filtered.
Pipeline On only shows recovered leads that pass matching and product rules.
Cookie consent settings can affect each tool differently.

Use GA to understand site traffic. Use Pipeline On to work recovered homeowners.

Why Pipeline On differs from Facebook Ads

Facebook reports ad delivery, clicks, landing-page views, and conversions based on Meta's attribution rules.

Pipeline On reports recovered profiles from your website activity.

Numbers can differ because:

Facebook can count clicks that never fully load your website.
Facebook attribution windows can include later conversions.
A visitor may click an ad but not be recoverable.
A visitor may arrive from another channel and still be recovered by Pipeline On.
Browser and consent settings affect Meta Pixel and Pipeline On differently.
Facebook can report aggregated or modeled events.

Do not expect Facebook click totals to equal Pipeline On recovered leads.

Why Pipeline On differs from Google Ads

Google Ads reports paid-click and conversion activity inside Google's attribution model.

Pipeline On can recover homeowners from paid, organic, direct, referral, and other website traffic if the site activity is eligible.

Numbers can differ because:

Google Ads counts ad clicks, not recovered homeowner profiles.
Some clicks bounce before the Pipeline On tag loads.
Some visits are not matchable.
Google's conversion windows are different from Pipeline On recovered-at timing.
Consent mode and privacy settings can affect each tool differently.
Google Ads can deduplicate conversions differently from Pipeline On leads.

Use Google Ads for campaign performance. Use Pipeline On to find people worth follow-up.

Why Pipeline On differs from your CRM

Your CRM usually shows people who called, submitted a form, booked, or were manually entered.

Pipeline On can show recovered homeowners who visited but did not convert.

Differences are normal because:

Pipeline On may recover people before they contact you.
Your CRM may require a phone call, form, or booking.
CRM records may be merged, assigned, or deleted by office staff.
Some Pipeline On profiles should be reviewed before becoming CRM contacts.
Some CRM contacts were not generated by website traffic.

When using Zapier, map Pipeline On into a clear source, tag, campaign, or note so your team can tell these leads apart from form fills and phone calls.

Use the right comparison

Good comparisons:

Pipeline On recovered leads vs. website traffic trend.
Recovered leads by source page.
Recovered leads by high-intent page.
Recovered leads by service area.
Recovered leads that become contacted, booked, or sold.

Weak comparisons:

Pipeline On leads vs. total GA users.
Pipeline On leads vs. Facebook impressions.
Pipeline On leads vs. Google Ads clicks.
One personal test visit vs. expected lead volume.

If the gap looks too large

Check:

The tag is installed on every public page.
The tag is not blocked by a consent manager unless that is intentional.
Google Tag Manager changes were published.
The domain in Pipeline On matches the live site.
The site is receiving real homeowner traffic.
Internal traffic, bots, and agency testing are not being treated as expected lead volume.
Your audit or account is active.

If tracking is live but volume is still lower than expected, send support the domain, date range, and the traffic numbers you are comparing against.