How to Set Up Hiro Analytics: Attribution, Filters and Reporting You Can Trust
By Trayan Hristov · Thrivelia · Published 15 November 2026

The first job in Hiro is to define which numbers the team is agreeing to use. Connecting an account and exporting a branded report comes later. If one dashboard includes subscription renewals and another excludes them, a revenue comparison can change before a single customer does anything differently.
I would set up Hiro in two passes. First, make a small reporting view reconcile. Then add the analysis that changes decisions: subscriber quality, customer progression, flow efficiency and product-specific repeat behaviour. This guide covers both passes without treating attributed revenue as proof of incremental profit.
The feature references were checked against Hiro's and Alia's documentation on 15 November 2026. Some Hiro help pages require sign-in; use the linked documentation from your account when following the interface. The acceptance checks and worked example are our recommended process.
1. Write the measurement brief
Before importing another account, fill in this short specification. Keep it with the report so a colleague can reproduce the result later.
Decision | What to record |
|---|---|
Business and account | Brand, store, email platform and SMS platform |
Period | Exact start/end dates and reporting timezone |
Money | Display currency, revenue definition and refund treatment |
Order population | Included stores, order sources and exclusions |
Attribution | Channels, interaction types, windows and transactional-message treatment |
Comparison | Prior period, prior year or equal-age cohort |
Owner | Person who approves changes and investigates differences |
This is a measurement brief, not a promise that Hiro exposes a separate toggle for every row. Where a definition is not configurable, record the platform's actual behaviour and reconcile to it. Do not label a gross revenue measure as net profit because it appears beside a cost figure.
2. Connect the right client and keep the account identifiable
Hiro's 2.0 onboarding guide starts with Manage Accounts, then client settings. It documents Klaviyo OAuth as the recommended connection route, with a read-only private-key option. Follow the current authorisation flow for the intended brand and allow historical data to populate.
Name the client so its purpose is obvious. If you maintain more than one reporting view for the same brand, record which view is approved for monthly reporting and why the other exists. Two views with different attribution settings are not interchangeable evidence.
Keep user access appropriate to responsibilities. A report reviewer does not automatically need agency-wide settings access. Confirm that a client-facing dashboard exposes the intended brand only. Configure branding after identity, data and permissions are correct.
3. Match attribution before comparing dashboards
For a Klaviyo-based view, open the client's attribution settings in Hiro and compare them with the actual Klaviyo attribution configuration. Check every interaction window and option, including treatment of transactional messages. Save the configuration and record when it changed.
Hiro's discrepancy guide documents intentional differences as well as mistakes: historical deleted-message revenue can remain in Hiro, and cross-platform last-touch deduplication can reduce overlap between email and SMS claims. It also notes that Postscript opt-in-message revenue is outside its campaign/flow reporting coverage. Do not force totals to match by changing settings until you understand the difference.
Use a fixed, completed comparison period. Allow the documented processing time after an attribution change and avoid repeatedly editing the settings while data is rebuilding. Never present a change in attribution methodology as a change in marketing performance.
4. Choose order filters for the business question
A subscription business may need an all-orders commercial view and an acquisition-focused view excluding scheduled renewals. A retailer may need to distinguish web, POS, draft and third-party orders. The right population depends on the question; excluding a source does not establish that marketing had no influence on it.
Hiro's recurring-order filter guide describes the Default Filters controls. In the documented Recharge examples, recurring orders can use both subscription_contract and subscription_contract_checkout_one. Verify the source values in your own store before applying exclusions, rather than assuming every subscription app uses the same pattern.
Review the filter preview, save the change and wait for completion. Keep the inclusion/exclusion direction visible in your notes. Accidentally including only the order type you meant to exclude can produce a perfectly formatted but misleading report.
After a filter change, recheck a first subscription purchase, a scheduled renewal, a normal one-time web order and any POS or draft order relevant to the brand. Reconcile the historical comparison under the same rules.
5. Check the platform's actual reporting coverage
Hiro's platform availability reference distinguishes the full Klaviyo-based feature set from smaller sets available for other email platforms. Adding Attentive or Postscript SMS alongside Klaviyo is different from using another platform as the email source.
One consequential distinction: the reference says Omnisend campaign and flow revenue comes from Omnisend, and Hiro's attribution settings and order filters do not apply to it. Do not promise the same recalculated attribution view across every platform. A hidden cohort or segment page may reflect API coverage rather than a broken installation.
Write unsupported analyses into the measurement brief. Obtain an appropriate source export where needed, or leave the result unavailable. An honest blank is more useful than an estimate presented as a measured metric.
6. Connect Alia and reconcile a full month first
For Alia, its Hiro integration instructions describe creating an Alia API key with read:merchant, read:events and read:segments permissions, then connecting it in Hiro's client settings. Match the Alia reporting timezone to Alia's dashboard timezone.
Start reconciliation with a complete calendar month. The same instructions explain that partial-range unique-user counts can differ because of how Alia and Hiro handle the reporting range. Also separate email submits from SMS submits. Hiro documents its combined Alia submit-rate calculation as the larger submit count divided by views, rather than adding both channels together.
For a hypothetical 1,000 views, 100 email submits and 60 SMS submits, that calculation produces 10%, not 16%. It is not a count of confirmed new subscribers or a complete union of unique email and SMS people. Inspect those downstream statuses separately.
If a popup has variants, compare the parent and child rows correctly. Do not add the parent to its variants as though they were different traffic. Save the exact date range, metric and granularity in the reconciliation note.
7. Track useful events beyond orders
Choose one or two events that represent a real customer milestone, such as starting a subscription or submitting a review. In Client Settings, select them under Tracked Metrics and save. Hiro's tracked-metrics guide distinguishes underlying Klaviyo events from Klaviyo's separately defined filtered Custom Metrics.
Do not give a click the label “activation” unless the click is the actual milestone. Confirm the event's identity, deduplication and value field. A count can be useful without a monetary value; do not manufacture a revenue value to make the chart look more commercial.
Where a Klaviyo Custom Metric is a filtered version of Placed Order, recreate the intended reporting population with the supported Hiro filters rather than expecting that custom definition to appear as another raw event. Check its result against a small known set of orders.
8. Perform a reconciliation before sharing the dashboard
Choose one closed month, one campaign, one flow and several known orders. Compare identity, period, currency, order population and attribution rules. Start with the simplest total and add complexity one layer at a time.
If you see this | Investigate first | Evidence to keep |
|---|---|---|
Store revenue differs | Order population, date boundary, refunds and currency definition | Included order IDs and period |
Email plus SMS looks too large | Overlapping platform claims and deduplication | One order's eligible touches |
Form rate differs | Unique-user scope, channel submits and variants | Same full month and granularity |
A metric is absent | Raw event availability and platform support | Event example and selected metric |
Historical totals changed | Settings, filters, deleted messages or reprocessing | Change date and prior configuration |
Classify each gap as a configuration error, timing issue, documented definition difference or unresolved variance. Quantify it. Do not hide an unresolved gap inside an AI-written explanation. Escalate with the dates, settings and a few examples, rather than a screenshot saying the numbers look wrong.
Advanced analysis: move from total revenue to customer progression
Once the baseline reconciles, ask where the next customer transition fails. Subscriber-to-first-purchase analysis can distinguish a weak acquisition offer from a weak welcome. First-to-second purchase can expose a gap after the first order. Product paths can suggest a complementary purchase worth testing.
Use equal observation windows. A customer acquired last week has not had the same opportunity to repurchase as someone acquired six months ago. Keep product, acquisition source, offer and subscription status visible where the sample supports those comparisons. A product path is an association and a test idea, not proof that buying one item causes loyalty.
For flow efficiency, compare delivered volume and attributed revenue per delivery under the same definition, then inspect customer outcomes. A rise in per-message yield can coexist with fewer entrants or weaker total store sales. The arithmetic helps locate a question; it does not answer whether the programme created additional profit.
A worked readout that does not confuse attribution with lift
Suppose a hypothetical matched reporting period has $500,000 in eligible store revenue and $140,000 in deduplicated attributed owned-channel revenue. The attributed share is 28%. If flows account for $90,000 across 100,000 delivered messages, flow revenue per delivery is $0.90.
Neither number means the programme created $140,000 that would otherwise disappear. To estimate a specific intervention's effect, compare a suitable treatment and control using retained order contribution, with the same observation window and surrounding treatment. Keep the attribution report and the experiment readout as separate views.
If next month's flow revenue rises because the attribution window becomes longer, annotate the break. Recalculate comparable history where possible, or stop drawing an unqualified trend line across the methodology change.
Build the report after the definitions are stable
The monthly report should show the approved view, comparison period, customer outcomes, campaign and flow context, list movement, operational problems and the next decisions. Attach a settings note. Use fewer charts if that makes the evidence easier to inspect.
Hiro's report generator supports reusable reporting layouts. Review exported content for cut-off tables and missing explanations. Keep internal diagnostic views separate from the client report where their definitions differ.
If you use Hiro through AI, give the request the exact brand, view, date range, comparison and metric. Ask it to show denominators and missing data. Treat suggested causes as hypotheses until the source evidence supports them. Never let a polished summary invent the reason a campaign rose or fell.
The ongoing operating checklist
At each monthly close, confirm data freshness and account identity; review connection or settings changes; reconcile important differences; inspect mature customer cohorts; and carry unresolved questions into a named action list. After changing an integration, order filter or attribution setting, repeat the relevant acceptance checks.
Use our complete monthly email account guide to turn the reporting into work. Thrivelia can help define the measurement view and connect it to lifecycle priorities. Apply to work with us with the specific report or decision you need to trust.
Setup questions
Should Hiro always match Klaviyo exactly?
Not necessarily. Match comparable settings first, then account for documented differences such as historical deleted messages and cross-platform deduplication. Investigate and quantify unexplained gaps rather than forcing a match.
Can I use the same reporting template for every platform?
Use the same business questions, but check each platform's available data and revenue definitions. Hide or explain unsupported measures instead of implying every integration supports identical analysis.
Does Hiro show incremental revenue?
Attribution reporting allocates credit under its configured rules. It does not by itself establish incrementality. A suitable controlled comparison is needed to estimate the additional effect of a particular intervention.

.png)
Comments