Attribution
See which ads and traffic sources are actually driving results
Free trial. No card, no tag manager.
See what's driving your results
Visitors, sessions, page views, leads, trials and purchases are grouped by the source that brought them: Facebook, Google, Organic, Direct or a specific campaign. One table, every channel, no spreadsheet.
Attribution
Last 30 days
Source
Visitors
Revenue
Direct
831
$549.45
Organic
1,919
$172.09
511
$318.20
147
$76.10
Totals
3,408
$1,115.84
Revenue per source
Revenue and revenue per session sit next to visitors and conversions, so a channel that brings traffic but no sales stands out immediately.
Filter and drill down
Pick a date range, an event or a source and the whole table updates. Click a row to see the sessions behind it.
Down to the campaign
Sources split into campaigns and ads using the UTM and click ID PixelFlow already captures, so you can compare creatives, not just channels.
Live events
Purchase
{…}
12:04:11
Lead
{…}
12:03:58
PageView
{…}
12:03:41
Built on the same events you send to Meta
Attribution reads from PixelFlow’s own event stream, the one that also feeds the Conversions API. There is no separate analytics script to install and no sampling. If an event reached Meta, it is in your attribution table.
Click any conversion and follow the path
Every purchase in the table opens into the full customer journey: the ad they clicked first, the pages they visited, the days between visits and the event that finally converted them.
Conversion journey
6 touches, 5 days
Facebook Ad
Spring Sale, Video 3
Day 1
Pricing page
pixelflow.so/pricing
Day 1
Direct visit
Returned from bookmark
Day 3
Free trial started
CompleteRegistration
Day 4
Purchase, $79
Growth plan
Day 6
Lead
Processed
Browser
Lead
Processed
Browser
Lead
Deduplicated
Server
Purchase
Processed
Browser
Purchase
Processed
Browser
Purchase
Deduplicated
Server
No double counting, no bots
Because the browser pixel and the server event share one event ID, each sale is counted once. Bot and crawler traffic is filtered before it reaches the table, so your source numbers reflect real people.
FAQ
Everything you need to know about how PixelFlow attributes conversions.
What attribution model does PixelFlow use?
Last touch by default, over a 90 day window. The source shown against a conversion is the last known source before that visitor converted. Journeys show every earlier touch as well.
Where does the source come from?
From the referrer, UTM parameters and click IDs (like fbclid) captured when the visitor first lands, tied to the visitor with PixelFlow’s first-party cookie.
Does this replace Meta Ads Manager reporting?
No. Ads Manager reports what Meta attributes to its own ads. PixelFlow shows every source side by side, including Google, organic and direct, using the events your site actually recorded.
Can I filter by a specific event?
Yes. Choose any event, such as Purchase or Lead, and the table shows only the sources and sessions that led to that event.
Does attribution work with Stripe or Calendly conversions?
Yes. Server-side conversions from Stripe and Calendly are matched back to the visitor’s session, so a purchase completed off-site still attributes to the right source.
Is attribution included on every plan?
Yes. Attribution and customer journeys are part of every PixelFlow plan, with no extra charge and no event caps.
Smarter, server-side tracking
Start sending accurate conversions today - no tag manager, no code, no developer required.
Compatible with
