Feature · Revenue attribution
Revenue attribution: see which source, page and country makes you money.
Send a purchase with one call. Pieowl credits it to the visit where it happened, so every source, campaign, landing page, country and device shows the money it brings, not just the visits.
- Every purchase credited to its visit
- Revenue in every overview list
- One call from browser or server
$8,420
↑ 18%
172
2.4%
- Instagram$3.1K37%
- Google$2.4K29%
- Newsletter$1.8K21%
- Direct$1.1K13%
The basics
What is revenue attribution?
- 01Send each purchase
- 02Pieowl credits it to the visit
- 03Switch any list to Revenue
Your payment dashboard tells you how much you made. Your analytics tells you where visits came from. Revenue attribution joins the two, so you can see where the money came from.
In Pieowl, every purchase is credited to the visit where it happened. That visit's source, UTM campaign, entry page, country, device, browser and OS become the purchase's too.
An example: a visitor finds your blog through Google on Monday and leaves. On Thursday they come back from Instagram, land on /products and buy for $49. The $49 goes to Instagram and to /products. The Google visit still counts as a visit, but not as revenue.
Sending a purchase takes one call:
pieowl.purchase({ id: 'A-1001', amount: 49, currency: 'USD', plan: 'pro' });
Send it from your server when the payment is confirmed, or from the browser after checkout. Then switch any list in the overview to Revenue: sources, entry pages, viewed pages, countries, devices and events. People show their lifetime revenue.
Pieowl sets no cookies and doesn't store IP addresses. You don't need to send personal data, just the amount.
Revenue attribution on every plan
Revenue everywhere you look
Switch any list to Revenue and see which part of your traffic pays.
Sources and campaigns
Revenue for every referrer, UTM source, medium and campaign. Put your budget where the paying visits come from.
Entry pages
Revenue by the page each visit started on. Each purchase belongs to one entry page, so the shares add up to 100%.
Viewed pages
Revenue of the visits that viewed each page. See which pricing, product or blog pages show up in buying visits.
Countries and devices
Revenue on the map and per country, device, browser and OS. Spot the markets and platforms that pay.
Events that lead to sales
Revenue of the visits that had each event, like a demo request or a coupon click.
Lifetime revenue per person
Each person's profile shows what they spent across all their visits. Groups and cohorts show revenue too.
Paying visits, conversion, revenue per visitor
Next to revenue, see how many visits paid, what share of visits that is, and what each visitor is worth.
Bought filter
Filter to visits that bought, or didn't. See where buyers come from and what they look at.
Reports and formulas
Use revenue as a metric for any event, break it down by entry page or UTM, and divide it in a formula.
Set up
How revenue attribution works
Three steps from a payment to revenue by source.
- 1
Send each purchase
Call purchase() with your order number, the amount and the currency. From your server, when the payment went through, with the deviceId of the visitor who paid. Or from the browser, after checkout.
- 2
Pieowl credits it to the visit
The purchase gets the source, campaign, entry page, country and device of the visit where it happened.
- 3
Switch any list to Revenue
Sources, pages, countries, devices and events show revenue next to visits. Add the Bought filter to see only buying visits.
Use cases
Who uses revenue attribution
Anyone who wants to know which traffic pays, not just which traffic comes.
Online shops
See order revenue by source, campaign and landing page, and the countries and devices that buy.
SaaS teams
Send each payment from your webhook. See which channels and pages bring paying customers, not just signups.
Marketers and agencies
Compare UTM campaigns by revenue and revenue per visitor. Move budget to the ones that pay off.
Related features
Works well with
FAQ
Frequently asked questions
Common questions about revenue attribution in Pieowl.
How do I send a purchase?
Call pieowl.purchase({ id, amount, currency }) with your order number and the amount in normal units, like 49.99. The same order sent twice counts once. From your server, use the SDK with your client secret and pass the visitor's deviceId from pieowl.getDeviceId() in the browser. From the browser, call purchase() on your success page or where your code learns the payment went through. Or connect your payment provider's webhooks, with no code.
Which visit gets the credit?
The visit where the purchase happened. Its source, campaign, entry page, country and device get the revenue. Earlier visits by the same person keep their visits but get no revenue.
Can Pieowl import my payments from Stripe?
Yes. Connect Stripe, Paddle, Lemon Squeezy or Polar in Settings → Site → Revenue, with no code. You paste one webhook address into your provider and every payment, renewal and refund arrives by itself. Past payments from before the connection aren't imported.
Which currency is used?
Your site currency, which you pick in Settings. It's USD until you change it. Send each purchase in the currency the customer paid. Pieowl converts it at the European Central Bank rate of the payment's day and keeps the original amount.
Can I record refunds?
Yes. Call refund() with the order number, and Pieowl subtracts the order from your revenue. Pass an amount for a partial refund.
Do I need to send personal data?
No. Send the amount and, from a server, a profileId, which can be your internal user ID. Pieowl sets no cookies and doesn't store IP addresses.
Your first dashboard in five minutes.
14-day free trial, no card needed. Cloud in the EU. No cookies.