Skip to content

Area: User guide

What each Analytics metric means

This page lists every card and tile on Analytics › Dashboard, tab by tab, with what it counts and what it is compared with. For the ideas behind the figures, read How analytics works. For a walkthrough, see Check how your store is doing.

  • Period. Every tab shares the date range in the button above the tabs. It opens on the last 14 days, including today. The presets are 1 week, 2 weeks, 1 month and 3 months; the calendar lets you pick any start and end day in the past. The range is kept while you switch tabs but not when you leave the page.
  • Previous period. A range of the same length that ends the day before your start date. Every arrow, vs previous period and Previous: value compares the period with it. A green arrow up means the figure rose, a red arrow down means it fell, a dash means it did not change.
  • Where the numbers come from. Everything is computed from the events your shop sends to Releva. A shop that does not send an event shows zeros for it. See How events get into Releva.
  • Attributed. An order is attributed to Releva when the buyer opened or clicked a Releva message within 7 days, or clicked an on-site block within 1 day, before ordering. It counts orders Releva took part in, not orders it can prove it caused.
  • Refunds. Refunds are subtracted from revenue figures, never from order counts.

The headline tab. It loads its own data, so it opens at once.

At a Glance: Attributed revenue against Total store revenue

Card or tile What it counts Compared with
Conversion metric: The event actions your shop counts as a purchase. With several actions, every one of them is counted. Not compared.
Attributed revenue Revenue of the orders attributed to Releva, with its share of total store revenue. Previous period.
Total store revenue Everything your store took, Releva involved or not. Previous period.
Share bar The attributed share against the rest of your store, with the dates and the attribution rule in the caption. Not compared.
Funnel card Your starred funnel: how many people reached each step in order within the period, and the % of previous step. It counts everyone, whether Releva reached them or not. Edit funnels opens Customer Insights › Funnels. Not compared.

At a Glance: the Attributed revenue breakdown

Card or tile What it counts Compared with
Attributed revenue breakdown The attributed figure split by campaign mode (One-off, Continuous & triggered), by channel under Sent through campaigns (one tile per channel your shop has set up) and by on-site surface under On your website (Product blocks, Banner blocks, Search as you type, Sales agent). One order can be credited to several surfaces, so the tiles overlap and do not add up to the total. Previous period, per tile.
Top performing continuous & triggered, Recent one-off campaigns, Top performing product blocks, Top performing banner blocks The campaigns, product blocks and banners that earned the most attributed revenue in the period. Not compared.
View attributed orders Opens Orders attributed to Releva for the same period: the tiles Attributed orders, Attributed revenue and Value of those orders (including the lines Releva was not credited for), and one row per order with Time, Order, Status, Profile, Attributed and Credited to. Not compared.

Traffic tab

Card or tile What it counts Compared with
Page Views All page views tracked in the period. Previous period.
Assisted Page Views Page views that followed a Releva surface, such as a product block or banner click. Previous period.
Product Block Clicks Clicks on products in a product block. Previous period.
Banner Clicks Clicks on a banner block. Previous period.
Releva Contributed vs Other Page Views The donut splits the period’s page views into Releva Contributed and Other; the lines plot Assisted Page Views and Other Page Views per day. Not compared.
Top 3 Page views by source The three UTM sources with the most page views, with Current, Previous and Change. Previous period, per row.
Top 3 Page views by medium The same for UTM media. Previous period, per row.

Engagement tab

Card or tile What it counts Compared with
Engagement How often people acted on what Releva showed them, on the site and in messages: the cart adds attributed to a Releva surface. Previous period.
By event One tile per cart-add event. It appears only when your shop maps more than one event to a cart add. Previous period, per tile.
Daily trend Engagement per day over the period. Not compared.
Where people engaged Clicks by surface, on the site and in messages, highest first: product block, banner, email, push, SMS, Viber, WhatsApp, sales agent and search clicks. A surface with no clicks in the period is not listed. Not compared.

Conversion tab

Card or tile What it counts Compared with
Conversions The events this domain counts as a conversion, however they were reached. Previous period.
By event One tile per purchase event. It appears only when your shop maps more than one event to a purchase. Previous period, per tile.
Daily trend Conversions per day over the period. Not compared.
Conversion rate The share of people in the period who converted. Previous: value of the previous period.
Conversion rate · Releva-engaged The conversion rate of the people who engaged with a Releva surface. Previous: value of the previous period.
Conversion rate · Not engaged The conversion rate of the people who did not. Previous: value of the previous period.

The two segmented rates are a correlational segmentation, not a controlled test. People who engage with Releva are also the people who were already shopping, so the gap is not a measure of lift. For a causal figure, enable a control group in your domain settings and read the A/B test results; see How A/B tests work.

Revenue tab

Card or tile What it counts Compared with
Source tiles One tile per Releva source that earned attributed revenue, such as Email, Product Block and Sales Agent. For the Sales Agent’s own figures, see Check how the Sales Agent performs. Previous period, per tile.
Releva Contributed vs Other Revenue The donut splits the period’s revenue into Releva Contributed and Other; the lines plot each Releva source per day. Not compared.

New vs Repeat Customers

Card or tile What it counts Compared with
New Customers Orders and revenue of buyers whose first purchase fell in the period, with their share of orders and of revenue. Not compared.
Repeat Customers Orders and revenue of buyers who had bought before. Not compared.
Revenue Distribution, Orders Distribution The same split as donuts. Not compared.
Revenue Over Time Daily revenue, stacked by new and repeat customers. With no purchases in the period the card reads No purchase data available for the selected period. Not compared.
Top 3 Store revenue by source, Top 3 Store revenue by medium The three UTM sources and media with the most store revenue, with Current, Previous and Change. Previous period, per row.
Top 3 Average order value by source, Top 3 Average order value by medium The same for average order value. Previous period, per row.
Average Order Value The average order value per UTM source (Top 10 sources) and medium (Top 10 media) over the period. Not compared.

The Top 3 and Average Order Value cards are further down the tab, under New vs Repeat Customers.

User Base tab

Card or tile What it counts Compared with
Total Registered Profiles registered with your shop. Previous period.
Total Subscribed Profiles subscribed to your messages. Previous period.
Subscribes Profiles that subscribed in the period. Previous period.
Unsubscribes Profiles that unsubscribed in the period. Previous period.
Push Notification Subscribers Profiles that allowed push notifications. Previous period.
Registered Users, Subscribers The two counts per day over the period. Not compared.
Subscribes and Unsubscribes Subscribes and unsubscribes per day. Not compared.

Only the tiles your shop has figures for are shown.

Marketing tab

Card or tile What it counts Compared with
Channel tiles One tile per sending channel with figures, such as Email Sends. Previous period, per tile.
Emails Activity, Emails Sends Email opens, clicks and other activity per day, and email sends per day. Not compared.
Email Opens by Weekday, Emails Opens by Hours When your emails are opened, by day of the week and by hour of the day. Not compared.
Email Permanent Bounces, Email Transient Bounces Hard and soft bounces per day. Not compared.
Push Notifications Activity, Push Notifications Sends The same for push notifications. Always shown. Not compared.
Webhooks Activity, Webhooks Sends The same for webhook campaigns. Always shown. Not compared.
Text Messages Activity, Text Messages Sends The same for SMS. Shown only when an SMS sender is set up. Not compared.
Viber Messages Activity, Viber Messages Sends The same for Viber. Shown only when a Viber sender is set up. Not compared.
WhatsApp Messages Activity, WhatsApp Messages Sends The same for WhatsApp. Shown only when a WhatsApp account is connected. Not compared.

The email, push and webhook charts are always shown, with flat lines when the channel sent nothing. The bounce and lower charts are below the fold.

Data Quality tab on a shop without a Meta pixel

The tab reports the health of your Meta pixel and Conversions API tracking under Facebook events. It needs a Meta pixel: without one it reads No Facebook pixel configured, as above. Add the pixel on the Facebook tab of Settings › Facebook & Whatsapp, and enable backend tracking so Releva sends purchases server-side through the Conversions API; see How Facebook Ads work.

With a pixel, the header shows a Pixel badge with its id and either Releva-managed (Releva sends the events server-side) or Customer integration (your own Meta integration sends them), and the tab shows:

Card or tile What it counts Compared with
EMQ · Purchase Meta’s Event Match Quality for purchase events, out of 10. Higher means Meta matched more events to people. Not compared.
Email match · Purchase Hashed email coverage: the share of purchase events that carried a usable hashed email address. Not compared.
Attribution divergence The gap between the purchases the pixel received and the purchases Releva extracted, as a share of Releva’s count. It reads Within tolerance or Above 20% threshold (the default threshold), No baseline yet while there is nothing to compare, or Server-side tracking off on a customer integration. The 20% threshold.
Purchases · Pixel vs Releva Pixel-received purchases against Releva-extracted ones, with the ad-attributed figure. On a customer integration the tile is Purchases · Releva-extracted instead. Not compared.
Event match quality by event type A table with Event, EMQ, Email match rate and Phone match rate. Not compared.
Event Match Quality (EMQ) trend EMQ per event type, plotted daily. A line trending down means matching is degrading for that event. Not compared.
Email match rate trend (%) Hashed email coverage per event type over time. Not compared.
Purchases: Pixel-received vs Releva-extracted vs Ad-attributed Daily purchase counts from the three views. A persistent gap between pixel-received and Releva-extracted is attribution divergence. On a customer integration the chart is Purchases: Releva-extracted vs Ad-attributed. Not compared.

The alert Customer-managed integration means server-side tracking is off, so the metrics reflect your own Meta integration. The alert No event-match data means Meta reported no event-match data for the pixel in the period.

  • AnalyticsCheck how your store is doing

    Pick a period on the Dashboard and read these metrics for your own store.

  • AnalyticsHow analytics works

    Learn what “attributed” means and how funnels, RFM and cohorts are measured.

  • AnalyticsCreate a funnel

    Define the steps you care about and see how many profiles reach each one.

  • Marketing ChannelsHow Facebook ads work

    Learn how the Meta pixel and backend tracking feed the Facebook events numbers.