Integrating Hiro Analytics with Alia
Step 1: In Hiro, navigate to the Client Settings page.
Step 2: Navigate to Connect Alia in the top menu.
Step 3: In Alia, navigate to Settings.
Under API Keys:
Create a new API key
Select all three permissions:
read:merchantread:eventsread:segments
Step 4: Copy the API key from Alia and paste it into the Alia integration page in Hiro.
Make sure the Alia Reporting Timezone in Hiro matches the Dashboard Timezone configured in Alia.
Where to View Performance
Form Performance
Once connected, Alia popup performance will appear under the Form Performance tab inside Hiro.
Each popup variation will appear as a line item nested under the main form. You can click the expand arrow on the right side to view individual variations.
Reporting
Alia popup performance is also available inside Hiro’s Report Generator.
Under the Forms Table block:
Klaviyo forms and Alia popups are displayed together
Each Alia popup variation appears as a nested line item under the main popup
Comparing Alia Numbers Between Alia and Hiro
Why numbers may not match for partial date ranges
Hiro stores Alia performance data as daily rows, but requests those rows in full calendar-month increments. Alia’s dashboard metrics are based on unique users within the selected date range rather than raw daily totals.
Because of this, the same shopper may appear on different days depending on the date range selected in Alia.
Example:
A shopper views an Alia popup on April 3 and again on April 10.
In a full April 1–30 view, Alia counts that shopper on April 3 (their first activity within the selected range)
In an April 10–15 view, April 3 falls outside the range, so Alia instead counts that shopper on April 10
Since Hiro always requests data in full calendar-month chunks, the closest apples-to-apples comparison is:
A full calendar month in Alia using daily granularity
Compared against the same full month inside Hiro
How Hiro Calculates Total Submit Rate for Alia Popups
Why Alia and Klaviyo report submits differently
Alia reports Email Submits and SMS Submits as separate metrics.
Klaviyo handles form submits differently. If a shopper submits any step of a Klaviyo form, Klaviyo counts that shopper as a form submit.
This difference matters most for multi-step forms.
Example
If a shopper submits only the email step of a Klaviyo form but never completes the SMS step:
Klaviyo still counts that visitor as a submit
Alia reports the email submit and SMS submit separately
Hiro’s Total Submit Rate Formula for Alia
For Alia popups, Hiro calculates total submit rate using:
max(email submits, SMS submits) / total form views
Hiro does not add Email Submits and SMS Submits together because that could overstate total submit rate by counting the same shopper twice if they completed both steps.
Using the higher of the two submit counts creates the closest apples-to-apples comparison between Klaviyo forms and Alia popups within the same reporting tables.