Revenue

Revenue is where you see what actually made money. Because TrueMetriks tracks server-side, the revenue, ROAS, and profit here include the conversions iOS, ad-blockers, and the pixel miss - so you can judge each source on real numbers.

Set this up with AI

Copy this prompt into ChatGPT, Claude or whichever AI you use. It carries this whole guide, the pages it depends on, and a link to every video, so it can walk you through it one step at a time.

Open as text

Video guide

How the Revenue page works in TrueMetriks

What the Revenue page shows

The page has a row of headline cards, a set of attribution and audience controls, a breakdown table you can drill from channel all the way down to the exact ad, and a duration block that shows how long buyers take to convert. Everything respects the date range at the top.

app.truemetriks.com / revenue
Total Revenue
$299,000.36
Purchases
1,052
AOV
$284.22
LTV
$314.41
Attribution:First-touch ▾
Audience:New + Returning ▾
Columns: 8
Search...
5 rows⇩ Export CSV
ChannelVisits ▾UniqueLeadPurchaseRevenueSpendROASProfit
Direct67060012014$4,970$0.00--
Referral121131$470$0.00--
▾∞Meta2,0401,85025165$17,745$5,6403.15x$12,105
▾Paid2,0401,85025165$17,745$5,6403.15x$12,105
▾CAMPAIGNABO Sales Cold 85004506318$4,970$1,8202.73x$3,150
▾AD SETAdset 1 - Broad 24 - 453122804118$4,970$1,1804.21x$3,790
ADUGC video - testimonial3122804118$4,970$1,1804.21x$3,790
▸AD SETAdset 2 - Broad 24 - 45188170220$0$6400.00x-$640
▸CAMPAIGNCBO Sales Cold 25204707014$3,150$1,5002.10x$1,650
▸CAMPAIGNSummer Glow Launch - ABO5404808825$8,910$1,9004.69x$7,010
▸CAMPAIGNInstagram Stories - Retargeting480450308$715$4201.70x$295
▸GGoogle88077018062$17,350$3,4005.10x$13,950
▸tTikTok2401806019$3,470$0.00--
Total3,8423,411614161$44,005.00$9,040.004.87x$34,965.00
The Revenue page: server-side revenue and profit for the period, broken down by channel and drilled all the way down to the individual ad. Green rows make money, red rows lose it.

The top cards

  • Total Revenue - all purchase value attributed to this period.
  • Purchases - how many purchases happened.
  • AOV - average order value (Total Revenue divided by Purchases).
  • LTV - average lifetime value per buyer, so you can compare what a customer is worth against what you pay to acquire one.

Only Purchase counts as revenue. Total Revenue and ROAS add up Purchase events only. A custom event can carry a value, but that value stays with the event and is never added to Total Revenue or ROAS. If a sale should count, send it as a Purchase. You can fire your custom event as well; it does not count the money twice.

When the date range has subscription renewals, the cards show the split:

  • Total Revenue shows how much came from new sales and how much from renewals.
  • Subscription revenue appears next to it, with its share of the total and the number of renewals.
  • Purchases shows how many were new sales and how many were renewals.
  • Buyers shows how many active subscribers paid a renewal in the date range.
  • AOV uses new sales only.

With no renewals in the range, the cards look exactly as before.

When sales in the date range have refunds, the cards show them too:

  • Total Revenue is after refunds. Its bar shows the refunded part as a red hatched stripe, and the line under it shows sales and how much was refunded.
  • Refunds appears next to it, with the refunded amount, its share of sales and how many refunds there were.
  • Purchases still counts a refunded order, because the sale happened. The line under it says how many were refunded.
  • AOV is after refunds, and its line under it says so.

With no refunds in the range, the cards look exactly as before.

Attribution and audience controls

These controls decide how the numbers below are calculated. Change one and the whole table recomputes.

  • Attribution - which touch gets the credit for a conversion: First-touch (the source that first brought the visitor in), Last-touch (the most recent source before the purchase, the default), or Any-touch (every source the visitor touched, see how any-touch counts booked calls). This is how you settle "which channel gets the sale."
  • Audience - whether to count New + Returning, only new, or only returning buyers.
  • Columns - tick the columns the table shows and drag them into the order you want. Lead, Schedule and Purchase appear as columns once your site sends those events.

The breakdown table

This is the heart of the page. The first column is Channel: each top row is one channel, such as Meta, Google, TikTok or Direct, worked out from each visit's UTM tags and referrer. Each row carries the full funnel:

  • Visits and Unique - traffic volume.
  • Lead and Purchase - conversions of each type.
  • Revenue - sales attributed to that row.
  • Spend - ad spend we pulled from the connected ad platforms (Facebook, Google).
  • ROAS - revenue divided by spend. Green is profitable, red is below breakeven.
  • Profit - revenue minus spend.

Expand a row with the chevron to drill down a level at a time - channel -> paid or organic -> campaign -> ad set -> ad - so you can see the exact ad that made or lost money, not just the channel total. Meta ads get one more level: the top row is called Meta, and Meta -> Paid opens to the app each click came from - Facebook, Instagram, Messenger, or WhatsApp - each with its own visits, buyers, revenue, spend, and ROAS, before campaign, ad set, and ad. Clicks from ads whose URL parameters do not carry the app yet sit under Platform not tagged; re-paste the Facebook template from the UTM Builder on those ads. Paid rows are labelled by level with a small PLATFORM, CAMPAIGN, AD SET, or AD tag (Google and TikTok read AD GROUP instead of AD SET) so you always know how deep you are. Traffic with no campaign tags still gets a channel: Direct when there was no referrer, or the channel the referrer points to, such as Organic Search, Referral or AI, so nothing goes uncounted. Green rows are winning, red rows are bleeding spend. The Total row at the bottom sums everything in view, and the row count next to Export CSV says how many rows the table has.

Export CSV

Export CSV, at the top right of the table, downloads the table as you see it:

  • every row, plus the rows you expanded, each with a Level column (Channel, Campaign, Ad Set, Ad and so on) and a Path column naming the rows above it
  • the columns you picked in Columns
  • the Total row

It follows the date range and every control above. Each line is one row of the table, a summary, not a list of individual sales.

The people behind a campaign's sales

To see who bought from one campaign, ad set or ad:

  1. Expand the rows down to the campaign, ad set or ad.
  2. Click the number in its Purchase column, or in Lead or any other event column. A zero is not clickable.

A list opens under the row with each person, when they converted and the value. View journey opens that person's full path to the sale. The list shows 5 people at a time; use the arrows to page through it.

This list has no download. Conversions Overview has its own Export CSV, which downloads individual sales and leads, one line each, up to 5,000 per file. It names the platform each sale came from (for example Facebook Paid), not the campaign, so it cannot be cut to one campaign.

Subscription renewals

A renewal is a payment after the first on a subscription or payment plan. Stripe, Whop, ClickFunnels and WooCommerce Subscriptions label renewals on their own. GoHighLevel and receiving webhooks need a small setup, see GoHighLevel and Webhooks.

A renewal is still a sale. It counts in Revenue, Total Revenue and ROAS, so your revenue includes everything you were paid.

When the date range has renewals, the table gets three more columns. You can show, hide and move them in Columns, and they are in the CSV export.

  • Renewals - how many renewals. Purchase then counts first sales only.
  • Renewal revenue - the part of Revenue that came from renewals.
  • ROAS (new) - revenue from first sales divided by spend. It is off by default. It lines up with Ads Manager when you send renewals as a custom event or not at all.

A Revenue filter also appears with the other controls: New + Renewals, New sales only or Renewals only. It decides which payments the table counts.

Filtering by kind can lower Visits, because the visits behind the other kind's purchases are left out.

A renewal has no visit of its own, so it is credited to the channel that won the subscription: the first purchase, or the free-trial signup when there was a trial. See How are subscription renewals credited?

With no renewals in the date range none of this shows, and the page looks exactly as before.

Send renewals to ad platforms

Choose what your ad platforms receive when a subscriber is billed again. Open Settings > Integrations, click the Subscription renewals tile, pick an option and click Save. The tile shows the current choice.

The setting is one per site and covers every payment source. A first payment always goes to your ad platforms as a Purchase.

  • A custom event (recommended) - renewals go out as their own event, named Renewal unless you change it. They get their own column in Ads Manager with their value, and Purchase optimization learns only from first sales.
  • Purchase - every rebill counts as a new sale, and Meta optimizes toward people who already bought.
  • Don't send - renewals stay in TrueMetriks only.

Sites that existed before this setting started on Purchase, so nothing changes for them until they pick another option. Sites created after launch start on a custom event named Renewal.

When renewals go out as a custom event or are not sent, they are not uploaded to Google Ads.

Whatever you pick, TrueMetriks counts every renewal on this page and credits it to the ad that won the subscription.

Refunds

A refund is taken off the sale it belongs to. The sale keeps its date, channel, campaign and ad, so its revenue, ROAS and profit go down where the sale was made.

A refund counts on the sale's date. A September sale refunded in October lowers September's revenue, not October's. A month you already reviewed can change when a late refund arrives.

Every revenue number in TrueMetriks is after refunds: this page and its table, ROAS and profit, Overview, Conversions, Products, the buyer profile, the Chrome extension, Creatives, Metriko and the API. The pages always agree.

A refund only takes a sale down to zero, never below.

A refunded order still counts in Purchases and Buyers, because the order happened. The Refunds card says how many were refunded. In a buyer's profile the purchase reads Refunded or Partly refunded.

Refunds never go to your ad platforms. Ads Manager keeps the original sale, so after a refund the revenue TrueMetriks shows for an ad can be lower than the ad platform's.

Where refunds come from. Stripe, Whop, ClickFunnels 2.0, WooCommerce and GoHighLevel send them. PayPal, ClickFunnels Classic and any other tool can send them to a receiving webhook with the original sale's order ID.

A refund is matched to its sale by order ID. A refund whose order ID matches no sale changes nothing.

Refunds count from the day this feature went live. A sale brought in through an import already had its refunds taken off.

Average first-conversion duration

Below the breakdown table is the duration block: it tells you how long it typically takes for someone to convert after they first find you, so you can see which channels close fast and which run a long sales cycle.

Average First Purchase Duration time from first click to first purchase
Purchase Lead Book a Call
Platforms Campaigns Ad Sets Ads
Name Total Sales Median Duration ROAS
▸fFacebook Ads 44
19h 13mavg 1d 4h
0.52x
▸GGoogle Ads 37
11h 02mavg 16h 40m
2.14x
fFacebook Organic 2
- -
✉Email 19
2d 6havg 3d 1h
-
▸▶YouTube 6
1d 9havg 2d 2h
1.03x
Total 108 16h 44mavg 1d 6h 1.31x
Median shown as the headline (outlier-safe); the average is the lighter number beneath. "-" means no attributable conversions at this level (e.g. organic has no ad set / ad). Conversions whose first tracked event is the conversion itself (no preceding click, e.g. imported or server-side conversions) are not counted in the durations.
The first-conversion duration block: median and average time from a buyer's first click to their first conversion, for Purchase, Lead, or Book a Call, split by platform and drillable to campaign, ad set, and ad.

Read the median as the headline number and the lighter avg beneath it as the average. The median is the outlier-safe one to trust, since a single buyer who took months to convert can drag the average up without moving the median. Each buyer contributes exactly one data point: the time from their first tracked visit (their first click) to their first conversion of the selected type. A customer who buys again next month is still one point, measured to that first purchase, so this is your true first-conversion cycle, not a repeat-purchase gap.

Some conversions never had a preceding click - imported, server-side, or webhook events whose first tracked event is the conversion. Those are excluded from the duration math, which is why a row can show sales but a - in the duration column. Durations under a minute display as <1m.

The segmented toggle at the top switches the conversion type: Purchase, Lead, or Book a Call. "Book a Call" counts the standard Schedule event plus any custom event you have mapped to Schedule (Calendly, GHL, webhooks). The count column relabels itself to match - Total Sales, Total Leads, or Total Booked Calls.

The Platforms, Campaigns, Ad Sets, and Ads tabs choose how the rows are grouped. On Platforms each ad platform splits into paid and organic rows - Google Ads versus Google Organic, and the same for TikTok. Meta paid traffic splits one step further, one row per app (Meta Ads - Instagram, Meta Ads - Facebook, and so on), beside Meta Organic. Everything you bought through Google Ads sits under the Google Ads row and breaks out by campaign, ad set, and ad in the deeper tabs; the standalone YouTube row is organic YouTube traffic, not Google Ads video.

Each row carries four columns: Name, Total {Sales / Leads / Booked Calls}, Median Duration (bold median plus avg beneath), and ROAS (green at 1x or above, red below, - where there is no spend to compare against). A thin magnitude bar sits under each number, scaled to that column's own largest value - count bars are blue, duration bars orange, and ROAS bars green or red - so you can eyeball the leaders down a column at a glance. Vertical separators divide the columns, and the bar-less Total row at the bottom rolls up everything in view. A - anywhere means there are no attributable conversions at that level (organic platforms have no ad set or ad rows).

The block honors the same date range, attribution (first, last, or any touch), audience (new, returning, or both), and traffic (all, paid, or organic) controls as the breakdown table above, so changing a control recomputes the durations the same way it recomputes the table.

Buyers

Buyers Page 1
BuyerFirst touchLast touchVisitsRevenueDays first to purchase
[email protected]DirectDirect9$29,772.150
[email protected]DirectDirect2$11,761.000
[email protected]DirectDirect1$8,779.000
id_b685a55a55d60225GoogleGoogle11$793.00257
id_94dbf6cf6a7fe1fdGoogleGoogle12$787.00130
[email protected]DirectDirect2$749.950
id_1ec8f8f7b6befd0cGoogleGoogle11$696.00254
id_3e564c972b0d427cGoogleGoogle10$668.0044
id_679fa6bb8d39762dGoogleGoogle11$654.00307
id_ce18e11c57bd8695GoogleGoogle10$623.00301
PrevNext
Buyers: every individual purchaser, with the source that first and last touched them, how many visits they took, total revenue, and how many days passed from first visit to purchase.

Below the breakdown is the per-buyer table - one row per customer who purchased:

  • Buyer - the customer's email, or an anonymous id if we never captured one.
  • First touch and Last touch - the source that first and last brought them in.
  • Visits - how many visits they took before buying.
  • Revenue - how much they spent in the date range.
  • Days first to purchase - how long from their first visit to their purchase, which tells you how long your sales cycle really is.

When a buyer on the page made a renewal or a labelled subscription payment in the date range, the table adds a Type column and a Payments column. Type shows Subscriber for those buyers and One-time for the rest.

Payments counts each buyer's payments in the date range.

Use the Prev and Next controls to page through the full list.

Frequently asked questions

How do I see which exact ad made or lost money?

Expand a row with the chevron to drill down a level at a time, from channel to campaign to ad set to ad, so you can see the exact ad rather than just the channel total.

What does the Attribution control do?

It decides which touch gets credit for a conversion: first-touch, last-touch, or a linear split. Changing it recomputes the whole breakdown table.

How is ROAS calculated and what do the colors mean?

ROAS is revenue divided by spend pulled from your connected ad platforms. Green is profitable, red is below breakeven.

Does a custom event's value count in Total Revenue?

No. Total Revenue and ROAS add up Purchase events only. A custom event sent with tmFireEvent or a receiving webhook can carry a value, but it stays with that event. Send a sale as a Purchase if it should count in revenue and ROAS.

How does the Revenue page show subscription renewals?

When the date range has renewals, Total Revenue splits into new sales and renewals, a Subscription revenue card appears, and the table gains Renewals and Renewal revenue columns plus a Revenue filter. A ROAS (new) column is off by default and can be ticked in Columns. With no renewals in the range, the page looks exactly as before.

How do I stop renewals going to Meta as a Purchase?

Open Settings > Integrations, click the Subscription renewals tile, pick A custom event (named Renewal unless you change it) or Don't send, and click Save. Sites that existed before the setting start on Purchase, so renewals keep going as a Purchase until you change it. First payments always go as a Purchase.

How do I see the sales of one campaign?

Expand the rows down to the campaign and click the number in its Purchase column. A list of the people who bought opens under the row, with when they bought, the value and View journey. The list has no download, and Export CSV on this page downloads the table's rows, not individual sales.

Are refunds taken off my revenue?

Yes. Each refund is taken off the sale it belongs to, so Total Revenue, ROAS and profit are after refunds on every page. When sales in the date range have refunds, a Refunds card shows how much was refunded and how many orders. Refunds are never sent to your ad platforms.

Why did last month's revenue go down?

Most likely a refund. A refund counts on the sale's date, so a September sale refunded in October lowers September. The Refunds card for that month shows it.

Need help with this?

Reach us instantly on WhatsApp, or send us a message and we will get back to you. On workdays we usually respond in less than 24 hours.

or send us a message