Setup Steps
Step 1: Go to the Client Settings page in Hiro.
Step 2: Navigate to Connect Alia in the top menu:
Step 3: In Alia, navigate to Settings.
Create an API key
Select all three options (read:merchant, read:events, read:segments)
Step 4: Copy the created API Key in Alia and paste into the Alia integration page in Hiro
Make sure the Alia Reporting Timezone in Hiro matches the Dashboard Timezone in Alia
Where to view performance
Form Performance
Alia pop-up performance appears under the Form Performance tab once your integration is connected. Each form variation is listed as a line item under the main form — click the expand arrow on the right to show them.
Reporting
Alia pop-up performance is also available in the Report Generator. Under the Forms Table block, Klaviyo and Alia pop-ups are listed together. Each Alia form variation appears as a line item nested under the main form.
Update - Alia Backfill Timeframe
May 12, 2026
Due to increased demand, we will only backfill historical Alia form data from January 1, 2026 onwards to reduce the token usage on Alia's API.
Comparing Alia numbers: Alia platform vs. Hiro
Why numbers may not match for partial date ranges
Hiro stores Alia performance as daily rows, but requests those rows one full calendar month at a time. Alia's dashboard numbers are based on unique users within your selected date range — not raw daily counts.
This means the same shopper can appear on different days depending on which date range you select in Alia.
Example: A shopper views an Alia form 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 in range).
In an April 10–15 view, April 3 is outside the range — so Alia now counts that same shopper on April 10.
Because Hiro always requests data in full calendar-month chunks, the closest apples-to-apples comparison is a full calendar month in Alia at daily granularity, compared to the same full month in Hiro.
How Hiro calculates total submit rate for Alia forms
Why Alia and Klaviyo report submits differently
Alia reports email submits and SMS submits as separate metrics. Klaviyo reports form submits differently: if a visitor submits any step of a form, Klaviyo counts that visitor as a form submit.
This matters most for multi-step forms. For example, if someone submits only the email step of a Klaviyo form and does not complete the SMS step, Klaviyo still counts that as a submit. In Alia, email submits and SMS submits are reported separately, so that same behavior would appear only in the email submit count.
For Hiro’s total submit rate on Alia forms, we use whichever Alia submit channel is higher:
max(email submits, SMS submits) / total form views
We do not add email submits and SMS submits together because that could overstate the submit rate by counting the same visitor twice if they completed both steps.
This is the most practical way to compare Klaviyo and Alia form submit rates in the same table. It gives us the closest apples-to-apples view of “how many visitors submitted the form at least once,” even though the two platforms expose the underlying metrics differently.