No variants serving
Why you may not see Luria changing your pages yet, from the normal baseline period to paused sites, pending approvals, and sticky versions.
First, the reassuring part: in most cases "no variants yet" is expected. Check the reasons in order.
1. You are in the baseline period (expected)
baselineDay 0 to 3Luria spends roughly the first 3 days learning your site as it is before changing anything. The first tests usually appear between a few hours and 3 days after install on sites with around 3,000 or more sessions a month. With less traffic, stretch those windows proportionally; a site with 500 sessions a month can take a couple of weeks to reach its first test. See Timeline.
What to do: nothing. Check the dashboard's training stage; if it says Baseline, you are on track.
2. Your traffic is low
Luria only starts a test when it expects to learn something from it in a reasonable time. Very low traffic pages may not get a test for a while, or ever. Luria prioritises your highest-traffic pages first.
What to do: make sure your main landing pages and product pages are where your traffic lands. See What to expect.
3. The site is paused
A paused site serves nothing. You or a teammate may have paused it (for example during a sale or a theme change).
What to do: open the dashboard and check the site status at the top. Resume if it says Paused.
4. Free allowance reached
Luria's free allowance covers your first 5 attributed conversions. After that, serving waits until billing is set up.
What to do: add a card in Billing. Serving resumes within a few minutes.
5. A change is waiting for approval
If you turned on approvals, nothing ships until you approve it. Proposed changes sit in the queue meanwhile.
What to do: open Approvals and approve or reject what is waiting.
6. You are seeing your own sticky version
Luria keeps each visitor on the same version of a page so their experience is consistent. If your browser was assigned the original (the control), you will never see a variant in that browser, even while half your visitors do.
What to do: open a fresh private window (extensions off) and load the page a few times across new private windows. Or use the dashboard's preview for the test. Better still, judge by the dashboard numbers, not your screen: see Variants.
7. The page is not in a test yet
Luria tests one page at a time per site at first and picks the page with the most to gain. Your favourite page may simply not be up yet.
What to do: look at the Tests list in the dashboard to see which pages are active. If a specific page matters, tell Luria in How to train.
8. The snippet is not firing on that page
No snippet, no variants. This also happens when a page template lacks the tag (for example a landing page built in a different tool).
What to do: run Snippet not firing on the specific page.
9. Your do-not-say rules blocked the generated copy
Very strict Brand Brain rules can mean every proposed variant for a page fails the check and nothing ships.
What to do: review your rules in Brand Brain. Keep the must-not list to genuine no-gos.
10. Consent is holding it back
In consent-required regions, Luria shows a consistent page but waits for consent before full testing. If most of your traffic is in the EU or UK and declines, tests take longer. See Consent.
Allow about 60 seconds after resuming, approving, or adding a card before you check your site again.