Revenue Tracking

Revenue tracking lets you see the financial impact of issues, measure revenue per session, and understand which traffic sources drive the most revenue. It's configured per project and supports two modes depending on how your store tracks transactions.

info

Revenue tracking is optional. Issue detection, traffic analytics, and all other features work without it. Enabling revenue tracking adds financial estimates to issues and unlocks revenue-specific analytics.

Setup

1. Go to Project Settings > Revenue
2. Enable revenue tracking
3. Choose a mode (event-based or manual)
4. Select the event that represents a conversion (e.g., purchase_completed)
5. Configure the value source

Modes

Event-Based Revenue

Best for stores where each transaction has a different value (most e-commerce).

• Event name — the custom event that represents a purchase (e.g., purchase_completed)
• Value field — the property in the event payload that contains the transaction amount (e.g., total)

// Your site sends events with actual transaction values
tracelog.event('purchase_completed', {
  total: 149.99,
  currency: 'EUR',
  orderId: 'ORD-789'
});

TraceLog reads the total field from each event to calculate actual revenue. This gives the highest accuracy.

Manual AOV (Average Order Value)

Best for subscription businesses or stores with consistent pricing.

• Event name — the custom event that represents a conversion
• AOV — a fixed average order value applied to every conversion

Instead of reading actual values from events, TraceLog multiplies conversion count by your fixed AOV. Simpler to set up, but less precise for stores with variable pricing.

What Revenue Tracking Enables

Feature	Without Revenue	With Revenue
Issue detection	Severity + affected sessions	+ estimated weekly/monthly revenue impact
Revenue per session	Not available	Revenue ÷ sessions metric
Source analytics	Traffic volume + engagement	+ revenue attribution by source
Copilot	Answers about traffic and engagement	+ answers about revenue and financial impact
Reports	Traffic and engagement analysis	+ revenue sections in AI reports

Confidence Levels

Revenue impact estimates include a confidence level based on data quality:

Level	When	Margin
High	100+ conversions in sample	±15%
Medium	20–99 conversions	±30%
Low	Under 20 conversions	±50%

When confidence is too low to produce a meaningful estimate, revenue impact is suppressed (hidden) rather than shown with an unreliable number. Suppression reasons include insufficient conversion sample, missing scoped revenue data, or unmeasured exposure.

Currency

Revenue is tracked in a single currency per project, configured in project settings. The default is EUR. TraceLog does not perform currency conversion — ensure your events send values in the configured currency.

tip

Start with manual AOV if you're unsure. You can switch to event-based revenue at any time without losing historical issue data. Only future revenue estimates will use the new configuration.