Data & feedback
Journeys write down what happens to them. Those events are counted, laid out as a funnel and broken down by country, device or batch of codes.
One session
Reports read these events back by day, week or month.
Where it acts
Launching a video gifting programme is easy. Defending it three months later is harder: what happens between the invitation and the message someone watches tends to be argued rather than counted.
Opening, recorder, form, submission, success — each step reports itself, tagged with its flow.
Every opening of a message is a view, with a session behind it.
Steps defined for your programme, compared flow by flow rather than averaged.
Reading the figures is a permission of its own.
How it works
Each step reports itself the moment it happens — no overnight pipeline.
Funnel
Illustrative funnel.
Per step, a count with its conversion from the previous step and from the first.
Breakdowns
By platform, code group, country, device, OS, flow or status — and nothing beyond.
Good to know
Every measure here has a boundary worth knowing before the number reaches a steering committee.
A query names the programmes it covers and can narrow to code groups inside them. The finest scope is the code group, not the individual message.
Events land as they happen, so no query waits on an overnight pipeline. Results come back by day, week or month, never by the hour.
Both lists are closed. Anything beyond them is a question for us, not a filter.
The numbers are prepared with your Livstick team: the analytics section of the customer portal is not open yet. The reporting role exists, the screen does not.
Not open yet
Mobile flow
Illustrative funnel.
The funnel is read once per flow. A drop that shows only on the embedded mobile flow is a different problem from one that shows everywhere.
The scope narrows to the code groups issued for that operation — a season, a store, a channel — read against the previous period and the same weeks last year.
Example brand and figures, for illustration.
FAQ
Events are written the moment they happen and read straight from the store, so nothing waits on a nightly batch. A day is the smallest bucket a report will show.
Codes created and activated, messages recorded, views, unique sessions (sessions, not people), the message and code activation rates, and per funnel step a count with its conversion from the previous step and from the first.
By platform, code group, country, device, operating system, journey flow and message status — those seven, and no free-form segmentation on top.
Yes — any query can be narrowed to one or more code groups inside a programme, keeping only the events attached to a code.
Access is role-based, and the portal carrying programme data sits behind a second factor: a one-time code sent by email, or Google’s own second factor for Google accounts.
