Skip to main contentTailor AI LogoTailor AI

    Experiment Health

    Tailor detects when a change to your site affects a live test, and repairs it.

    How It Works

    Each change in a test is attached to a specific element on your page, such as a headline, button, or image. When your site changes, that element can move or disappear. Tailor handles this in four steps.

    1. Step 1

      We watch

      Visits to your tested pages report whether each change applied.

    2. Step 2

      We notice

      When a change stops applying, our team is alerted within 24 hours.

    3. Step 3

      We prepare a fix

      Tailor automatically finds where the element went and stages a fix for review. It never publishes on its own.

    4. Step 4

      Our staff signs off

      The fix is previewed on your live page before it is published. Every version is saved and can be rolled back.

    When Your Site Changes

    Whether a site change needs a fix comes down to one question: can Tailor still recognize the element? Tailor identifies each element by several of its details at once, so no single edit decides it.

    Handled automatically

    The element is still recognizable.

    How: Enough of the element's details still match, so Tailor finds it on every visit and the change applies as usual. No action required.

    Example changes
    Spacing or capitalization changes in text
    The words are the same.
    Tracking parameters added to links
    The link still goes to the same page.
    Restyling, like new colors or fonts
    The content is unchanged.
    Content that loads late
    Tailor keeps checking while the page loads.

    Caught and fixed

    The element is still on the page, but no longer recognizable as it was.

    How: Tailor detects that the change stopped applying, finds the element in its new form, and stages a fix. Our team reviews the fix on your live page before it is published. If Tailor is not confident in a match, we select the element by hand.

    Example changes
    A site rebuild or platform release
    The code changes, even when the page looks the same.
    A redesigned section
    The layout around the content changed.
    An element moved to a new spot
    Same element, different place on the page.
    Translated pages, after the source copy changes
    The translation must be updated to match the new copy.

    Hard to catch

    The element is hidden, removed, or ambiguous.

    How: Tailor does not guess on these. Applying a change to the wrong element is worse than skipping it, so our team handles each one, often with your input.

    Example changes
    Content behind a click, like pop-ups, tabs, or banners
    Many visits never open it.
    Your own A/B test on the same page
    The other version can have different elements.
    Rewritten copy on a tested element
    The words may be all that identify it.
    Removed content
    Nothing is left to attach to.
    Numbers that update often, like review counts
    Each update breaks the match.
    Low-traffic pages
    Too few visits to spot a break.

    How You Can Help

    • Planning a redesign or major release? Notify us beforehand, and we will check your live tests when it ships.
    • Changing a pop-up, tab, or banner on a tested page? Notify us. These are the hardest changes to detect automatically.
    • Something looks wrong? Email support [at] tailorhq [dot] ai with the page URL and test name.

    Related: Watchdog & Alerts for drops in traffic and spend, and Running Alongside Other Platforms if you test on the same pages with another tool.