Missing is not zero.
When a source hasn’t synced, its value stays unknown and named. It never quietly becomes $0 in a total.
Know reporting is complete
before anyone asks.
See which sources synced, when, and what each report leaves out, before the numbers reach a meeting. Late data gets flagged, not quietly counted as a bad day.
SourcesHealth
Google Ads4m ago
Meta6m ago
HubSpot26h ago
Stripe2m ago
weive pixelLiveSource health4 of 5HubSpot needs attentionExample states
Google AdsHealthy
MetaHealthy
HubSpotLate
StripeHealthy
weive pixelReceiving
A dip in leads might be a bad Thursday, or it might be a sync that never ran. weive tells you which one before anyone builds a theory on it.
Change the rule.Watch the credit move.
Complete data matters because every rule depends on it. Pick one and see how this order is credited once every source is in.
- Google AdsGeneric search
- MetaRetargeting ad
- EmailAbandoned cart
Direct/checkout- OrderPaid
Order · Stripe$320
Google Ads—
Meta—
Email—
Direct—
See every sourcestitch into the month.
Each thread is a source; each stitch is a day it delivered. A missing stitch is a late day, and it’s labelled on every report it touches.
- Daily delivery per source
- Late days flagged, not filled
- Every report shows what it’s missing
Source coverageLast 14 days
Google AdsHealthy
MetaHealthy
HubSpotLate 26h
StripeHealthy
weive pixelReceiving
17 Sep24 Sep30 Sep
Missing is not zero.The last two HubSpot days stay unknown until the sync lands. Nothing is filled in.
Example states
A late synclooks like a late sync.
Track records per source and day. A dip caused by a late sync looks different from a dip in demand, and weive tells you which one you’re seeing.
- Records per source per day
- Partial days marked
- Totals that say they are partial
HubSpot leadsLast 7 days
MonTueWedThuFriSatSun
SyncedPartial · late sync
Sat and Sun incomplete
Ask why it moved.Get the cause in the data.
When a number moves, ask weive whether it moved because of the market or because of the data.
- Sync issues surfaced in answers
- Changes traced to sources
- Records one click away
Why did leads drop over the weekend?
HubSpot last synced 26 hours ago, so Saturday and Sunday leads are incomplete. Google Ads clicks, Meta clicks, and pixel visits were steady. Check again once the sync completes.
HubSpot sync statusPixel visitsAd clicks
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.
How often do sources sync?
Connected sources sync on a regular schedule, and each one shows its last sync time in Connections.
Who sees source issues?
Everyone with access to the workspace sees the same coverage and sync states on every report.
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.