Ten kinds of visitor, one content library

Your venue, in action.

One WordPress page, with its sections filled differently for every visitor. Here is exactly what Spectare reads, how it classifies intent, and what each visitor sees.

A monthly planner open on a white desk with a cup of coffee, a campaign taking shape

One page, a different experience for every visitor

Spectare assembles each visit from content you write once, with no engineering tickets.

See it live

From: Every visitor gets a different experience

Write copy in your own voice not ours

Spectare writes and assembles content on your behalf, but your brand has a voice that is entirely its own.

Read more →

Automatic

5 scenarios

Spectare reads the signals already in the request, the search or campaign a visitor arrived from and the page they are on, and classifies intent with no setup beyond the WordPress plugin.

Family planning a half-term day out

Search: things to do with kids

Intent classified as

Family/Planning

Atoms assembled

Family shows and ages, times and running lengths, the cafe and parking

How it works

A parent searches for something to do over half-term and lands on your homepage. The Spectare plugin reads the search context on your server and classifies a family at the planning stage, so the zones assemble content about family shows, show times and running lengths, and the practical bits: the cafe, parking, and under-fives.

Someone checking step-free access

Search: wheelchair access

Intent classified as

Visitor/Planning

Atoms assembled

Step-free routes, wheelchair spaces, blue-badge parking, tell us what you need

How it works

A visitor searches for whether your venue is accessible before they commit to booking. Spectare reads the signal and assembles the accessibility content first: step-free routes into every level, wheelchair spaces and companion seats, blue-badge bays nearby, and a clear "tell us what you need when you book". They get the one answer they came for, at the top.

Day-tripper from a tourism site

utm_source=visit-town

Intent classified as

Visitor/Planning

Atoms assembled

What is on today, how to get here, what else is nearby

How it works

Someone clicks through from a "what is on in town" listing. The campaign tag tells Spectare they are a visitor planning a trip, so the page leads with what is on today and this week, how to find you, and what else is nearby to make a day of it.

Clicked a specific show in an ad

utm_campaign=hamlet-autumn

Intent classified as

Visitor/Choosing

Atoms assembled

That production, its dates, nearest performances, related shows

How it works

An ad for a particular production brings them in. The campaign tag names the show, so Spectare assembles that production front and centre: dates, the nearest performances, and a couple of related shows in the same season, rather than a generic what-is-on page.

Cold visit, no signals

No signals

Intent classified as

Any/Planning

Atoms assembled

Your default content: the best general what-is-on page

How it works

Someone types your address straight in, with no search, no campaign and no history. Spectare sets confidence to zero and serves the default content you have chosen: the strongest general page for a first-time visitor. Everyone sees something relevant, never an empty slot.

Behavioural

2 scenarios

A short visit history, kept in the visitor's own browser, builds a picture of their trip over time. Stage moves from planning to booking on its own as they look at more of your site.

A member coming back for the new season

Visit history in their browser

Intent classified as

Member/Choosing

Atoms assembled

What is new since they last came, member priority booking, their perks

How it works

A regular who browsed a couple of shows last month comes back when the new season is announced. Spectare reads the visit history kept in their own browser and reads them as someone choosing, not just looking. They see what is new since they were last here, their member priority-booking window, and the perks they already have, instead of a welcome page written for a stranger.

The visit history decides whether personalisation happens at all

With no history and no search or campaign, this visitor reads at confidence 0 and gets your default page. With a show or two in their history they read as a returning member and get a real assembly. The history is not only shifting which content appears, it is the difference between a personalised page and a default one.

What counts as a visit

The last five pages they looked at, most recent first, kept for 30 days in their own browser. Nothing is stored on your side, and it never follows them to another device or browser.

How returning visits reach a WordPress page

The history lives in the browser, so the WordPress plugin, which renders zones on your server, cannot see it by default, and a zones-only page treats every visit as new. Turn on "Returning visitors in zones" in the plugin settings and it mirrors the last few pages into a first-party cookie on your own domain, so your server can pass them to Spectare and zones recognise return visits too. It is off by default and never leaves your domain.

Looked at a show, then access, then times

Page context in this visit

Intent classified as

Visitor/Booking

Atoms assembled

Book now, the next performances, the access details they just checked

How it works

A visitor reads about a show, checks the access page, then looks at performance times, all in one visit. Spectare reads the path building up and treats them as ready to book. The page shifts to put booking and the next performances first, and keeps the access details they just checked in view, rather than starting the pitch over.

Programmatic

3 scenarios

Your box office, or an AI assistant that found your llms.txt, calls the qualify API directly to set intent with explicit context, then shares the returned link. Used for school and group bookings, enquiry follow-ups, and assistant referrals.

A teacher organising a school trip

qualify API + ?ctx= link

Intent classified as

Teacher/Booking

Atoms assembled

Group rates, the education pack, risk assessments, coach drop-off

How it works

Your box office replies to a schools enquiry with a link made for them. One call to the qualify API with the teacher context returns a personalised URL to drop into the email. When the teacher clicks it, the page is filled for a school group: group rates, the education pack, risk assessments, and where the coach drops off. No new landing page to build.

POST /api/qualify/your-venue
{
  "summary": "Primary school teacher organising a Year 5 trip for 60 pupils, needs group rates, an education pack and coach drop-off details",
  "audience": "teacher",
  "stage": "booking"
}

→ returns { url: "https://yourvenue.co.uk/visit?ctx=<token>" }

A group-booking enquiry follow-up

qualify API per enquiry

Intent classified as

Visitor/Booking

Atoms assembled

Content chosen for their group: size, date, what they asked about

How it works

For a larger enquiry, the box office generates a unique link per enquiry before replying. The qualify API takes a plain-English note of who they are and what they asked, and returns a signed URL. Every enquiry gets a different link, and the page answers the specific group that clicks it, one page filled many ways.

// One link per enquiry, before you reply
const res = await fetch('/api/qualify/your-venue', {
  method: 'POST',
  body: JSON.stringify({
    summary: "Birthday group of 15 adults for a Saturday evening show, asked about pre-show dinner and nearby parking"
  })
});
const { url } = await res.json();
// Drop url into your reply

Sent by someone’s AI assistant

llms.txt + qualify API

Intent classified as

Visitor/Any

Atoms assembled

Content chosen for whatever the assistant asked on their behalf

How it works

A visitor asks their assistant something like "is this venue wheelchair accessible, and what is on this weekend?". The assistant reads your llms.txt, which points at the public qualify endpoint with no API key needed, calls it with a plain-language summary, gets a ready-to-use URL, and shares it. The visitor clicks and the page is already assembled around access and this weekend, without anyone writing a rule or building a variant.

// An assistant reads yourvenue.co.uk/llms.txt (no API key), then calls:
POST /api/qualify/your-venue
{
  "summary": "Visitor asking whether the venue is step-free and what family shows are on this weekend"
}

→ returns { url: "https://yourvenue.co.uk/visit?ctx=<token>" }
// The assistant shares that URL; the visitor lands on a page built for them.

And every one of these is measured

Each scenario on this page feeds the same learning loop: what was shown, whether the visitor continued, and whether they booked, all counted against a live holdout that sees the default page. Winners are called only when the statistics clear a real bar, and every rule Spectare proposes shows you the evidence first. Curious what it read about you just now? See how it works, or turn on the x-ray from there and watch this page explain itself.

See it on your venue’s site

Start a free trial. Spectare drafts your first atoms from your existing pages and goes live on your WordPress site the same afternoon.