Features

Personalises from visitor one. Learns from every visit after.

Three capability areas, one unified system. No training data. No segments. No configuration beyond one script tag.

One content library, unlimited visitor experiences

Spectare reads visitor intent and assembles personalised content in real time, without code changes or developer involvement.

The learning loop

Most tools personalise. Spectare improves.

Set an exploration rate and Spectare begins testing different presentations automatically. A developer at decision stage might convert better with a StatGrid first. An executive at consideration stage might respond to a TestimonialCard before technical depth. Once enough visits accumulate, the winning arrangements are fed back into assembly, so the pages a visitor sees are shaped by what actually converted for people like them. The atom content never changes. Only the arrangement is tested.

1.Set an exploration rate in Settings. Spectare runs experiments automatically on a share of visits.
2.Each arrangement is tracked with impression and conversion counts. Signal accumulates quietly in the background.
3.Once your signal threshold is reached, the winning arrangements go back into assembly and Spectare starts preferring what converts.

Content model

Atoms: the content Spectare assembles

Focused, single-purpose content blocks. Feature descriptions, FAQ answers, pricing breakdowns. Write once, assembled differently for every visitor.

Learn about atoms →

How Spectare works

Every visitor gets a personalised experience built from the same source material. When someone arrives, Spectare classifies their intent from referrer URLs, UTM parameters, and session context, then passes a context token describing their audience, buying stage, and confidence level to the assembly step.

Assembly runs on the server. Claude receives the context token alongside three ranked inputs: a vector search over your atom library finding the most semantically relevant candidates, a conversion history showing which atoms and arrangements have converted for this audience and stage before, and an image selection picking the best visual for the moment. From these signals Claude selects which atoms to include and maps them to one of nine component types.

Two of those nine components are written entirely by Claude in your brand voice: HeroStatement and ImageCtaHero. The remaining seven components, including StatGrid, FeatureList, TestimonialCard, ComparisonTable, CodeBlock, AtomCard, and CtaStrip, are drawn directly from your atoms without modification. Your words reach the visitor unchanged; Claude only writes the headline and hero layer.

The assembled page is cached at the edge so subsequent visitors with the same intent pattern are served instantly without another AI call. Every impression is recorded against the variant, audience, and stage that produced it, feeding back into the conversion history that informs the next assembly decision.

Signup

Every conversion event teaches Spectare what works

Spectare brings real conversion history into every page assembly decision. When the AI selects which content atoms to show a visitor, it weighs which atoms have actually converted for visitors with the same audience type and buying stage in past sessions. Content that has a proven track record of driving action is ranked higher for similar future visitors.

Every conversion event you record tells Spectare which atoms and images were shown during that session. This data feeds directly into the assembly algorithm, so the system gets more accurate the more traffic your site receives. Early on, Spectare relies more heavily on semantic similarity to match content. Over time, conversion history becomes the dominant signal for well-trafficked audience and stage combinations.

Tracking a conversion requires either setting a thank-you URL pattern in your dashboard settings, which fires automatically when a visitor reaches that page, or calling the conversion method manually from your own code for more complex flows such as multi-step forms or in-app upgrades. The conversion guide describes both paths.

The result is a personalisation system that continuously improves without any manual tuning. You write the atoms. Spectare learns which ones work for which visitors and adjusts every future assembly accordingly.

90 DaysConversion History Required
Conversion Guide

Ready to see it in action?