FOR SAAS
Metrunio shows you the measured contacts before each step: signed up, set up, first payment. Each step counts once per customer and gets the same attribution as an order.
| Step | Key | Reported from | Value in the report |
|---|---|---|---|
| Signed up | signed_up | Browser, after metrunio.identify() | set: your acquisition value |
| Set up | set_up | Backend, POST /v1/server/events | set: your acquisition value |
| First payment | first_payment | Backend, with amount and currency | measured: revenue from the event |
Each step is a conversion of its own. The “Orders & goals” report shows how many customers reached it in the period and what share came there from the previous step. Anyone who reaches a step but never the one before stands apart as “skipped”.
A sign-up has no price. So that you can still hold the funnel against ad spend, you give each step an acquisition value: what a customer who reached it is worth to you. That value is set and never appears in revenue or ROAS. If the first payment carries its amount, that is measured revenue.
PLANS
Goal steps, acquisition value, the source in the form and the CRM import are available on every plan. Pro adds ad costs, so you see the cost per step, and the comparison of all seven models; Growth, at €249, adds sending conversions back to the ad platforms and the read API.
01 / WHAT YOU GET
Each step has a key and an order and counts exactly once per customer, however often your code reports it. A step without a customer ID is rejected.
From your backend you report steps and payments through POST /v1/server/events, with the server key and independently of the browser. An invalid event does not discard the whole call: the response gives the status of each event and, on failure, the reason.
Give your contact form the attribute data-metrunio-lead. With consent to analytics, Metrunio writes source, medium, campaign, click ID and a lead ID into hidden fields, and they travel with the lead into your CRM. Without consent the fields stay empty.
If the deal comes weeks later, you import it as a CSV. Through the lead ID it finds the lead’s journey and appears with its amount in the attribution. A row without a unique identifier is rejected rather than guessed.
Payments from Stripe or PayPal arrive through a webhook without programming; a payment is attributed when it carries the reference from the SDK. Renewals of a subscription appear separately in revenue and get the shares of the first payment of the same subscription, provided your server reports them with consent.
The customer cohorts under “Commerce & products” group customers by the month of their first measured purchase and show for each following month who paid again. When a customer has paid for themselves is shown under “Paid back” once ad costs are there, so from Pro.
02 / LIMIT
The click window reaches at most 90 days and applies to each step separately. If the first payment comes half a year after the click, it stays “unattributed”, even if the sign-up before it was still inside the window. With cycles of months to years, a window that long would attribute coincidences; Metrunio is not the right fit for that.
Look around in the demo first. Your own account is currently available by invitation only.