Trace the amount back to its source
Attriboo vs Plausible
Choose purchase-event analysis or connected payment reporting.
Plausible can track revenue through custom events. Attriboo connects supported payment-provider records with recorded visits. Consider the event you want to analyze, the later payment changes you need and the privacy tradeoffs of visitor matching.
Reviewed · By Jay Kang
Example · USD · Before fees
- Completed purchase
- $60
- Later partial refund
- −$10
- Payment less refund
- $50
A $60 purchase event and a $50 refund-adjusted amount can both be correct. Check what the report is designed to count.
Trace the records behind the totalThe short answer
Choose the Revenue Question You Need Answered
Use a report whose collection method and identity rules fit the decision you are making.
Consider Attriboo When…
- You need to inspect supported payment and refund records.
- You want to compare recorded source credit under First-Touch, Last-Touch and Linear.
- You accept the standard tracker's identifier and consent setup for linked journeys.
Consider Plausible When…
- Its approach without persistent visitor IDs is central to your requirements.
- You want to analyze purchase events within its website reporting workflow.
- You prefer its traffic dashboard after evaluating the current Business features.
Revenue tracking is a shared capability
Compare the Data Behind the Revenue Number
Check the event or record being counted, the visit it can match and the plan that includes the report.
| Your decision | Attriboo | Plausible |
|---|---|---|
| What revenue represents | Attriboo Payment-provider records and their links to recorded visits. Availability and history depend on the connection. Attriboo details | Plausible Monetary values attached to custom events, reported by the visit in which the purchase occurs. Plausible details |
| Server-side payment updates | Attriboo Supported providers send payment and refund records separately from browser pageviews. A payment may still have no matching visit. Attriboo details | Plausible Its API docs distinguish events sent during a visitor request from provider webhooks that lack the matching visitor context. Plausible details |
| Shopify checkout | Attriboo A supported order connection with provider-specific setup and matching. Earlier Shopify orders are not imported. Attriboo details | Plausible Documents a customer-event pixel for checkout and purchase revenue, using Shopify's reported amount and currency. Plausible details |
| Identity and privacy | Attriboo Standard tracking uses a persistent browser ID for linked journeys. Separate cookieless mode records daily pageview totals only. Attriboo details | Plausible Documents a cookieless approach without persistent visitor identifiers or cross-device tracking. Plausible details |
| Plan and evaluation | Attriboo 5,000 monthly pageview/custom-goal events free for one website. Reports have a 365-day window and 250,000-event complete-load guard per site. Attriboo details | Plausible Ecommerce revenue is a Business feature. The hosted service advertises a 30-day trial without a card. Plausible details |
Official documentation reviewed October 31, 2026. No controlled accuracy, speed or conversion comparison was performed.
A purchase event and a ledger answer different questions
Follow One Purchase and Its Later Refund
In the opening example, $60 less a $10 refund leaves $50 before fees. Start by deciding whether you need the purchase amount, the refund-adjusted amount or the source credit attached to recorded visits.
In Attriboo's Dashboard, open Watch visits become customers → Live activity and select Refunds to inspect today's recorded deductions. Keep this today-only view separate from the historical range above it.
Where to find itDashboard → Watch visits become customers → Live activity
Find this card below Follow the money. The overview keeps the complete globe, filter controls and Latest activity feed visible. The totals and refund row are enlarged below.
Select the overview to open the full screenshot.
Enlarged detail of the outlined area
- Filter to refunds
Select Refunds to show the recorded deductions in the activity feed. This does not change the historical reporting range above the dashboard.
- Check the net total
Read net revenue with the payment and refund counts underneath. The amount is before fees and other business costs.
- Inspect the recorded event
The refund row shows its recorded amount and available source and location. Reconcile it with the provider record before interpreting source revenue.
Use the revenue guide to reconcile payment and refund records. Then keep the dates and model consistent when reading Sources.
Check the Event Collection Path Too
Plausible's Events API guide explains when a server event can match an existing visit and why a payment webhook is different. Verify the actual collection route rather than assuming a successful HTTP request proves correct attribution.
Include the revenue feature you need
Compare the Relevant Plans and Reporting Limits
Plausible lists ecommerce revenue under Business. Check the current traffic allowance and billing term. Attriboo's calculator below quotes its own pageview and custom-goal allowance, so use each vendor's counting rules when comparing workloads.
Your recorded workload
Work Out Your Attriboo Allowance
Use pageviews and custom goals. Payments do not count as these events. Bot requests have a separate allowance. These inputs stay in your browser.
Up to 10,000 monthly events. Billed monthly.
Review all allowances and termsCompare the same measured workload with Plausible's current plans. This calculator quotes Attriboo only; it does not estimate another vendor's bill or convert visitors into events. Attriboo's report window and event-row limit still apply.
Attriboo's free allowance is ongoing for one website. Plausible advertises a 30-day hosted trial without a card. Check Attriboo's 365-day and 250,000-event complete-load guard independently of the monthly event allowance.
Make differences explainable
Test a Known Purchase Before Replacing a Report
Keep the comparison small enough to reconcile with the underlying provider record.
- Confirm the checkout and collection route.
List the completion event, amount, currency and visitor-matching method. Follow the chosen Attriboo provider instructions separately from any purchase-event setup.
- Check the amount and duplicate behavior.
Confirm that a reload or callback retry does not create an unexplained extra purchase. Keep payment identifiers and each tool's setup distinct.
- Check a later payment change.
Inspect the renewal or refund workflow your business needs. Decide which report should include that change before comparing totals.
- Choose the privacy and reporting tradeoff.
Use the implementation you can explain to your team and visitors. Keep the existing reports until the evaluation answers your reporting question.
Your remaining questions
Before You Choose Attriboo or Plausible
Use these answers to resolve the reporting, setup and switching questions that can change your decision.
Can Plausible track revenue?
Yes. Plausible supports monetary values on custom events and revenue analysis on its Business plan. Attriboo connects supported payment-provider records with recorded visits. Choose based on whether you need purchase-event analysis, provider payment and refund reporting, or both workflows alongside each other.
Which Plausible plan should I compare for revenue analytics?
Compare the Business plan, which lists ecommerce revenue attribution. Check the current billing term, traffic allowance and account limits rather than comparing Attriboo only with Plausible's Starter price. Attriboo's calculator quotes its own pageview and custom-goal allowance and does not estimate Plausible's bill.
Can a payment webhook be attributed like a browser purchase event?
Not automatically. Plausible's API guide says server events can join an existing visit only with the visitor's own headers, the same site and the required timing. Provider webhooks do not carry that browsing context. Attriboo's payment connections use their documented matching routes; check a known payment and investigate any missing visit.
Should Plausible revenue equal my complete payment ledger?
No. Plausible's revenue guide focuses on purchases completed during website visits and directs readers to billing tools for renewals, refunds and churn. In Attriboo, check which provider records are supported and how they match recorded visits. Reconcile amounts, dates and currency before expecting two reports to cover the same money.
Can Plausible track Shopify purchase revenue?
Yes. Its Shopify guide documents a custom pixel for completed checkout events and the reported purchase amount. Keep the goal currency and event setup consistent. Attriboo's Shopify workflow connects order records; check its current authorization, visitor matching and new-order scope before choosing between the two approaches.
Does Attriboo use the same cookieless approach as Plausible?
No. Plausible documents analytics without persistent visitor identifiers. Attriboo's standard tracker uses a first-party cookie and localStorage identifier to link recorded activity. Attriboo also offers a separate cookieless daily-pageview mode with no source or visitor links. Review the implementation and consent requirements for your site rather than treating both modes as interchangeable.
Can I keep Plausible while evaluating Attriboo?
Yes. Keep the installations distinct and confirm that neither sends duplicate events or overwrites a checkout identifier used by your application. Start with a known purchase and compare the same dates, currency and reporting scope. Keep existing reports until you can explain whether a difference comes from event collection, payment records or source-credit rules.
Check One Payment, Then Choose the Workflow
Start with one website and a supported checkout, or explore the payment and refund records in the demo.