Memory
The site remembers before anyone signs in.
Memory distils a visitor's behaviour into typed, readable facts — what they compare on, what they keep coming back to, what they have already ruled out. Memories strengthen when they get used and fade when they do not, so what survives is what keeps mattering. Recall them to personalise a page, or ask your visitor data a question in plain English.
Add-on to Analytics
- per month, any Analytics tier€120
How it works.
The mechanism, not the marketing. If any of this turns out not to match what the product does, the page is wrong and we want to know.
Behaviour becomes typed memories
Raw events are rolled into typed entries — a preference, a decision, an insight — rather than left as an undifferentiated event log.
Each memory carries an activation
Recalling a memory strengthens it. Time weakens it. Memories that stop earning attention expire on their own instead of accumulating forever.
Strong memories get promoted
A memory used often enough graduates to a longer-lived stage, and eventually becomes permanent. Anything flagged as personal never reaches that stage.
Recall is scored, not just matched
A recall combines semantic similarity with how active, how recent and how mature each memory is, so you get what is relevant and still alive.
Consent gates the whole thing
Recall runs only for visitors who granted full consent. Withdraw it and the memories are purged, not flagged.
What you get.
Recall API
Ask for what matters about this visitor and get back short, typed hints you can use to change what a page shows.
Ask in plain English
Query your visitor data conversationally — what people who booked had in common, what the ones who bounced were reading — without writing SQL.
Typed, not a blob
Preferences, decisions and insights are stored separately so you can act on one without wading through the others.
Automatic forgetting
No manual cleanup. Decay and expiry are how the store stays small and useful.
Personal data never crystallises
Anything detected as personal is marked and blocked from becoming permanent, no matter how often it is touched.
Portable to the visitor
A visitor can see what is remembered about them and redact any of it.
<script async src="https://antiqore.com/embed/memory.js"
data-embed-key="mk_live_…"></script>What Memory does not do.
Every product page on this site carries this section. It is the fastest way to be believed about the rest.
- It works standalone
- Memory needs the visitor record that Analytics creates. It is an add-on to Analytics, and priced as one.
- It remembers everything
- Deliberately not. Memories that stop being used expire. A store that never forgets becomes noise and gets slower every month.
- It works for every visitor
- Only for visitors who granted full consent. Everyone else is invisible to it.
Questions.
Is this profiling?
It is behavioural personalisation on your own site, under consent, using your own first-party data. It does not build a cross-site profile and nothing leaves your workspace.
What happens on withdrawal?
The visitor's memories and events are deleted. The consent record itself is kept, because we have to be able to show what was permitted and when.
Memory writes to the same record as the other five.
That is the only reason buying more than one is worth anything.