Missing is not zero.
When a source hasn’t synced, its value stays unknown and named. It never quietly becomes $0 in a total.
See which visits turn
into revenue.
The weive pixel records every visit with its source. When a visit leads to a lead or a payment, weive ties the two together and shows you the path in between.
Recorded visitsOutcome
Google Ads/pricingOrganic search/blog
NewsletterTagged link
Direct/checkout
Stripe · Payment$199Checkout · 4 visits in 6 daysGoogle Ads18%
Organic search21%
Newsletter29%
Direct32%
Most visits never buy, and that’s fine. weive keeps them as visits, and only connects a visit to revenue when a real payment follows it.
Change the rule.Watch the credit move.
Four visits over six days, then a payment. Pick a rule to see how the same $199 is shared across the path.
- Google AdsSearch · /pricing
- Organic search/blog/attribution
- Newsletterutm_source=newsletter
- Direct/checkout
- PaymentCheckout completed
Payment · Stripe$199
Google Ads—
Organic search—
Newsletter—
Direct—
From thousands of visitsto the few that pay.
Watch traffic narrow from every recorded visit to the payments at the end. Each step is a count you can open, and nothing unmatched is quietly promoted to a sale.
- Every visit recorded with page, referrer, and tags
- Leads and payments matched to the visits before them
- Unmatched visits kept as visits, never conversions
18,400Recorded visits
11,900Carried a source65%
1,240Became a lead10%
412Paid in Stripe33%
SeptemberWidths to scale
Follow the pathfrom landing page to payment.
Open any credited payment to see the visits that came before it: the landing page, the article, the return visit, and the session that ended at checkout.
- Ordered visits with page and source
- Time between every step
- The payment waiting at the end
Payment #22074 visits · 6 days
- Google Ads · /pricingutm_campaign=brand
- Organic search · /blogReferrer: google.com
- Newsletter · /pricingutm_source=newsletter
- Stripe · PaymentCheckout completed$199
One snippet.Every visit, with its source.
Install the pixel once. weive records the page, the referrer, and the campaign tags on every visit, and shows you that it’s working.
- Live status in Connections
- Campaign tags captured on arrival
- Visits without a source labelled direct
weive pixelLive
StatusLast event 2 minutes agoReceivingPages seen this month184 distinct paths184
Visits with campaign tagsUTM or click ID present65%Visits without a sourceKept and labelled direct35%Example pixel status
Three promisesbehind every number.
Credit is not cause.
Attribution shows how a rule shares credit across recorded touches. It never claims an ad caused the sale.
One order, counted once.
Two platforms can claim the same sale. weive credits the payment once, and keeps each claim visible beside it.
Three stepsfrom scattered data to a decision.
Connect your sources.
Google Ads, Meta, HubSpot, and Stripe connect in a few clicks. One snippet adds the pixel to your site.
Choose your rule.
Linear, first touch, last touch, last non-direct, time decay, or U-shaped. Switch whenever you like; the outcomes never change.
Decide with the gaps in view.
Every number carries its sources, its rule, and its coverage, so the next budget move starts from evidence.
Worth askingbefore you start.
Where does the pixel run?
On the pages where you add the snippet. It records visits and campaign tags and sends them to your weive workspace.
What happens to visits that never convert?
They stay in the journey data as visits. They are never counted as leads or revenue.
Does attribution prove a campaign caused the sale?
No. Attribution shows how credit is shared across recorded touches. weive keeps that separate from causal lift, so credit is never presented as proof.