Skip to content

THE PRODUCT

Where the visit came from, what happened in the shop, and the answer. All from the same data.

Metrunio connects measured ad contacts, recorded steps in the shop, and orders or enquiries. Attribution stays a traceable model decision.

01 / ONE EXAMPLE. THREE PERSPECTIVES.

From “Where from?” to “What happened?”

A channel report shows the distribution. A journey shows the path. A question leads straight to the right analysis.

CUSTOMER PATH · SAMPLE DATASET

What happens between entry and result?

Connect the measured ad contacts with the recorded steps in the shop. A visit without a purchase has a history too.

  1. AD CONTACTPaid social

    Recorded click on the campaign “Meta Prospecting: Backvideos”.

  2. IN THE SHOPProduct → cart

    Reported shop events, no recording of the screen.

  3. RESULTPurchase or open

    Only reported completions. Missing steps are not filled in.

Three journeys in detail →

Metrunio shows what could be recorded and linked. Not a complete observation of every person and no replay of their mouse movements.

02 / ASK YOUR DATA

You ask the question. The data stays checkable.

Ask Metrunio about an order, a channel or a data gap. The answer shows the basis it used and takes you to the right analysis.

In the portal on every plan, with ten questions a month on the free one. With your own AI tool it also works outside the portal, through MCP, an interface that only reads: from Growth, by signing in through the portal or with your own read key.

EXAMPLE · PREPARED, NOT A LIVE QUERY

16 journeys added something to the cart this week and had not bought as of the data cut-off. The five most recent started via Paid social, Direct, Direct, Direct, Direct. A cart value is not revenue.

Matching journeys
16
Cart in the example, not revenue
€12.00

Week: 5 Oct 2026–11 Oct 2026 · Europe/Berlin

Sample data as of: 5 Oct 2026, 12:18

What is behind this answer
BasisIn this example
Tooljourneys · abandonedCart: true
Period5 Oct 2026–11 Oct 2026 · Europe/Berlin
As of5 Oct 2026, 12:18

A later purchase changes the result. Why someone did not buy is not in the data. The assistant names causes only with evidence.

jr_93752d1e864f · Paid social · cart as the last measured step

Open journey →

03 / TRACEABLE MEASUREMENT

A number is only as useful as its basis.

Metrunio separates measured events from attribution by a model. That helps you understand discrepancies and check open questions in a targeted way.

  1. 01

    Your own signals before the shop.

    With its own tag, Metrunio also measures delivery and viewability of ads, in ad environments that allow your own tag. Post-view, meaning ads that were seen but not clicked, is included from Pro.

  2. 02

    Rules you can compare.

    Put attribution models side by side. Different shares are a different distribution, not proof of additional sales.

  3. 03

    Gaps stay visible.

    Unattributed orders or leads, missing costs and limited coverage become visible. An unknown number does not turn into zero.

MORE ANALYSES

More than the single order.

Commerce metrics, products, goal steps, platform reconciliation and data quality complement the journey. Every view names its data basis.

See all areas in the demo ↗

FOR LEADS TOO

A completion does not have to be a purchase.

For SaaS and lead businesses, Metrunio measures sign-up, setup and further goal steps, with the same attribution as for an order.

Guide to goal steps →

04 / INCLUDED

What Metrunio does.

Eighteen things the product does itself, in three tasks. What is not listed here, Metrunio does not measure; what it deliberately does not do is further down.

Understand contacts

  • Click tracking

    Signed tracking links. No open redirect, no foreign destination.

  • Impression tracking

    Your own 1×1 pixel. You measure delivery yourself.

  • Viewability

    A separate tag: 50 percent of the area, one second. Only visible counts.

  • Journeys

    Linked deterministically, every visit step by step, purchase or not. No fingerprinting. The full visit history comes with Growth; below that, 7 or 30 days.

  • Web analytics

    Page views, visits, time on site and bounce rate per channel, page and technology, with paths and real time. On every plan, counted for visitors with consent.

  • Funnel steps

    Signed up, set up, first payment: one conversion per step, counted once per customer, with the channels per step. You set each step’s acquisition value yourself, kept apart from revenue.

Compare channels

  • Attribution

    Seven models, each with and without post-view: two compared head to head, all seven in one table, one of them data-driven. Model comparison and post-view come with Pro and above.

  • Commerce

    Contribution margin, when your shop sends margin and cart along. From Pro, also new-customer cost and margin ROAS per channel and campaign.

  • Budget

    Campaigns sorted by what is known about them: measured (by experiment, from Scale), attributed, open.

  • Post-purchase question

    “How did you hear about us?” on the thank-you page. The answers appear as self-reported next to what is measured, never in revenue and never in an attribution.

Secure data quality and hand-over

  • Website and conversion

    App or plugin for Shopify, Shopware and WordPress, tag manager, snippet or server API. One data model, reports per website; several websites from Growth.

  • Data quality

    Every finding names cause, effect and the next step.

  • Custom measurement domain

    Measurement over your own address. Ad blockers then cut less often.

  • Export

    CSV at raw-data level. Recalculate every figure yourself.

  • Report delivery

    Weekly or monthly by email, with the breakdown as a CSV you can pass on.

  • Figures in words

    Every key figure as a sentence too, with the way to the raw data behind it.

  • Progress

    What has happened in your data, with no points, rank or streak.

  • Four interface languages

    Website and portal in German, English, Spanish and French, per login and with number formats. Help and emails in German and English; Spanish and French readers get them in English.

    What comes in which language

The seven models in detail, with and without post-view

05 / EVERY VIEW

Six views, from a running dataset.

Not a mock-up: these views are generated automatically from a live account, with generated but complete journeys and no customer data. Anything awkward stays in.

SAMPLE DATASET · GENERATED DATA

Screenshot of the overview: large figures for measured and attributed revenue, ad spend and ROAS, below them smaller ones for attributed conversions, CPA, CAC, post-view share, post-view coverage, unattributed conversions and attribution rate; above them period, model and a line with period, environment, model and as-of time.
Answers the question: which conversions and how much revenue can be attributed to advertising in this period, and how solid is the figure?
  1. 1Period, environment and model appear once above all tiles. Every figure below applies to exactly that.
  2. 2Attributed, not measured: the revenue is distributed across channels according to the chosen model.
  3. 3The post-view share under the default model “Click before view”: a viewable impression only counts where there was no click. Under “Last non-direct click” it would get nothing.
  4. 4Measured: the share of viewable impressions where the later purchase can be linked at all. The rest stays a gap, not a zero.

View the screenshot at full size

SAMPLE DATASET · GENERATED DATA

Screenshot of the model comparison: two models side by side (“Click before view” and “Last non-direct click”) with the share per channel and the change in percentage points; below, all seven models can be expanded.
Answers the question: which channel gets the revenue, and how much does the answer depend on the model?
  1. 1Period, conversion type and both models sit in one line. Every figure in the table applies to exactly that.
  2. 2The change is shown in percentage points. It comes from the distribution rule and is no evidence of additional advertising effect.
  3. 3Display receives more under “Click before view” than under “Last non-direct click”: the same conversions, a different rule.

View the screenshot at full size

SAMPLE DATASET · GENERATED DATA

Screenshot of an order with its journey: the timeline of measured contacts with channel, campaign and share under the default model, the direct visit expanded with its share in every model; beside it the attribution of the order, the conversion and what was recorded, with the deterministic identity signals.
Answers the question: what preceded this particular conversion, contact by contact?
  1. 1Each contact shows its share under the default model; the other models are under “More about this touchpoint”.
  2. 2Linking happens only through deterministic signals: click ID, impression ID, session, order number. No fingerprinting.
  3. 3Expanded on the direct visit: under “Click before view” it gets nothing, because there was a viewable impression. What the other models assign to it is listed below.

View the screenshot at full size

SAMPLE DATASET · GENERATED DATA

Screenshot of the data status: the data content with invalid format, events blocked by consent, attribution rate, late events, conversions without a journey and unknown campaigns, with the milestones below.
Answers the question: how complete is the data I am basing this on?
  1. 1Events blocked by consent are counted but not stored.
  2. 2The attribution rate says what share of conversions has at least one measured contact that a model could attribute. The rest is counted and not distributed.
  3. 3Almost every event here is late because this sample dataset was generated retroactively. With live measurement this is a small number.

View the screenshot at full size

SAMPLE DATASET · GENERATED DATA

Screenshot of “Setup”: the setup health centre with the verdict “All in order”, counters for events, test events, queue and last event, and below it the section on your own measurement domain.
Answers the question: is measurement running, and what is the reason when it is not?
  1. 1The verdict is at the top. Where there is a finding, it states cause, impact, error code and the steps.
  2. 2The counters show whether measurement is running right now: events, test events, queue, last event.
  3. 3On your own measurement address, ad blockers and tracking protection cut the data less often. Here it is not set up, and that is stated.

View the screenshot at full size

SAMPLE DATASET · GENERATED DATA

Screenshot of the events view: a list of received events with arrival time, type, state, consent, origin and order number, with a filter by state above it.
Answers the question: where does this figure come from? Every metric leads here.
  1. 1Filter by state: received, processed, rejected, repeat.
  2. 2Every row carries its consent and its origin: from the browser, from your server or from an offline import.

View the screenshot at full size

What access to these views costs

06 / DELIBERATELY OUTSIDE

What Metrunio does not do.

Metrunio measures, connects and attributes. Probabilistic cross-device matching and fingerprinting, session recording (session replay), heatmaps, media mix modelling, automated budget allocation and ad serving are not part of it. Tools built for those exist, and the interfaces to them are open. What Metrunio deliberately does not do

PRINCIPLE

Where a signal is missing, we do not invent one. The conversion stays visibly “unattributed”.

See what your data tells you.

Look around in the demo first. Your own account is currently available by invitation only.

Open the demoRequest access