Analytics and reporting across Arino One
Arino One does not have a single central "Analytics" module — instead, each feature area carries its own analytics tab, scoped to the data that area produces, and reachable from the same subnav as the settings and records for that feature. This guide is a map of every one of those screens: what it shows, who can see it, and when to check it.
Campaigns and links (Marketing)
Campaign analytics, link analytics and commerce analytics share one tab bar under Marketing, because they describe stages of the same journey: a campaign goes out, a contact clicks a tracked short link inside it, and that click can turn into an order.
Link analytics (/links/analytics) reports total tracked links, total clicks, unique clicks and unique contacts reached, with a day-by-day click series over a 7/30/90-day window you can toggle. If the URL shortener add-on is switched off, new outbound links are sent as-is and only historic click data is shown — a banner on the page says so and links through to the setting. This is the screen to check when you want to know whether a campaign's call to action actually got clicked, as distinct from whether the message was delivered.
Contacts
Contact analytics (/contacts/analytics) is a single-page view of database health: total contacts, a breakdown by consent state (opted in, pending, unknown, opted out), a 30-day new-contact growth chart, and — depending on your build — a tag or locale spread. This is the first screen to check before sending a broadcast: a high proportion of "pending" or "unknown" consent is a sign your opt-in flow needs attention before you increase send volume, not after.
Templates
Templates carry two distinct analytics screens, and the difference between them matters:
- Template analytics (
/templates/analytics) reports library composition — how many templates you hold by status (approved, pending, draft, rejected, paused, disabled), by category and by language. It answers "what does our template library look like as a whole". - Template health (
/templates/health) is a live table of every template with its current status, Meta quality rating (green, yellow, red) and the most recent lifecycle event — submitted, approved, rejected, paused, quality downgraded — with a timestamp, clicking through to the template itself. It answers "is anything about to break".
Run template health as a weekly check, not just after a rejection notification, since a quality rating can slide from green to yellow between events you'd otherwise notice. See Template health and quality for how to act on what you find there.
Commerce
Commerce analytics (/commerce/analytics) is gated behind the Commerce add-on and hidden from agents entirely — only Admin, Super Admin and Manager roles see it, the same gate that controls catalogue and payment settings. It reports:
| Metric | What it tells you |
|---|---|
| Orders created vs paid | Volume and how much of it converts to settled payment |
| Revenue by currency | Ordered value and paid value, split by the currency each order was placed in |
| Product message → order → payment funnel | Where the drop-off is: are people not adding to cart, or adding to cart and not paying |
| By-channel breakdown | Whether WhatsApp or Instagram commerce is performing differently |
| Orders over time | A stacked daily view of product messages sent, orders created and orders paid |
Because a basket takes the currency of its first item, revenue is reported per currency rather than converted to one number — check each currency row rather than looking for a single total. See Commerce orders and checkout for the order lifecycle behind these figures.
Verification (OTP)
OTP analytics (/verification/analytics) reports one-time PINs sent, verified and failed over a selectable 7/30/90-day window, split by channel (WhatsApp, SMS and others where enabled). A rising failure rate here, especially concentrated on one channel, usually points to a delivery problem on that channel or an OTP expiry set too short for how the message actually lands — check it before assuming users are entering the wrong code.
Resources
Resources analytics (/resources/analytics) reports total assets, storage used and shared link count, with an asset-kind breakdown (image, video, audio, document, other). Its main use is spotting storage growth from unused uploads before it becomes a billing or housekeeping issue, and confirming your media library is weighted toward the formats your channels actually need — templates and RCS cards both draw images from this same library.
Reading analytics together, not in isolation
Because each screen is scoped narrowly, the more useful reads usually combine two: a jump in campaign sends with flat link clicks suggests a targeting or content problem, not a delivery one; strong link clicks with weak commerce conversion points at the checkout step rather than the campaign; a spike in OTP failures on one channel with no change in verification volume points at that channel's delivery, not your OTP flow. Treat each analytics tab as an instrument, not a full diagnosis, and cross-check the adjacent ones before changing anything.
Frequently asked
Is there one dashboard that covers everything?
No, and that is deliberate. Each analytics screen sits next to the feature it measures — commerce analytics is a tab inside Commerce, template analytics is a tab inside Templates — so the numbers are always one click from the setting or record that produced them, rather than living in a separate reporting module you have to cross-reference.
Which roles can see analytics?
Contact, template, link, resource and OTP analytics are visible to any signed-in staff member, since they are operational rather than commercially sensitive. Commerce analytics is the exception: it is gated behind the Commerce add-on and hidden entirely from agents, consistent with agents not seeing catalogue or payment settings either.
Can I export the underlying data?
The analytics screens are built for at-a-glance monitoring rather than exporting. For a full data pull — for finance reconciliation or a board report, for instance — use the record-level lists behind each screen (Orders, Contacts, Templates) with their filters, or ask support for a data extract.
Why do the campaign and link click screens share a tab bar?
Campaigns, link clicks and commerce are three views of the same customer journey — a campaign message contains a short link, the link is clicked, and the click can lead to an order — so they're grouped under one Marketing analytics tab bar to make that journey easy to trace end to end.
How far back does analytics data go?
Time-series screens such as commerce and link analytics offer 7, 30 and 90-day windows. Point-in-time screens — template analytics, resources analytics, contact consent breakdown — show the current state of the library or database rather than a historical trend, since composition is what matters there, not velocity.
Does viewing analytics cost anything?
No. All analytics screens are included in the $50/month instance connection and management fee. They read data you are already generating; they do not consume message credits or AI tokens.
Apply this to your own deployment
This guide describes decisions we make on live instances. Tell us your channels, systems and region and we will map it to an architecture outline, a provisioning plan and an indicative commercial model — usually within one business day.