Dynamite
ExamplesTalk to sales

Personalize your website for returning visitors

Dynamite remembers what each visitor looked at, so when they come back the page picks up where they left off.

Talk to sales
Illustrative Switchboard website for First visit. Good work. Less coordination.. All six workflows, from Creative review to Team onboarding
  • Message for this visit
  • A matching example
  • Relevant content first
First visit
  • No earlier visits recorded in this browser
Illustrative example: Switchboard. Generated design previews.

A first visit and the one after it

On a first visit someone reads the Switchboard homepage, then the pages for two operations workflows, Request desk and Team onboarding. The next time that browser opens the homepage, the hero is about operations and points at the handoff playbook.

The data behind every decision

Dynamite decides what each visitor sees from how they arrived, what they do on your site, and the data you connect.

First visit

From every visit

  • Where they came from
  • Campaign and ad
  • Pages they viewed
  • Past visitsNo earlier visits recorded in this browser
  • Device, location, time

Data you connect

  • De-anonymizer
  • Company and contact matches
  • Your CRM and product data
  • Custom connectors

Install on any website with one line of JavaScript

<script defer src="https://www.usedynamite.com/dynamite.js" data-site="your-site"></script>
  • Shopify
  • Webflow
  • Framer
  • WordPress
  • Squarespace
  • Wix
  • Next.js

Built for your agents

Dynamite can be driven entirely over MCP, so your agents create, manage, and optimize personalization themselves.

  • Claude
  • OpenAI
  • Any MCP client

Self-improving

Dynamite reviews performance across all variants and personas, so each iteration gets better.

You keep control

Dynamite doesn't generate new designs on the fly. You configure the possible designs on our dashboard, along with who they are for.

Illustrative Switchboard website for First visit. Good work. Less coordination.. All six workflows, from Creative review to Team onboarding
  • Message for this visit
  • A matching example
  • Relevant content first

Illustrative example: Switchboard. Generated design preview.

One site. Different starting points.

A message that fits

Start with the need that brought this visitor here.

First visit
Good work. Less coordination.

Good work. Less coordination.

Return visit
A calm place for the moving parts.

A calm place for the moving parts.

Show the right example

Put the product, workflow or story they care about in view.

First visit
All six workflows, from Creative review to Team onboarding

All six workflows, from Creative review to Team onboarding

Return visit
The handoff playbook: one intake queue that captures the goal, the owner and the date

The handoff playbook: one intake queue that captures the goal, the owner and the date

A relevant next step

Choose the action that fits this visit. Measure next-step completion against the original.

First visit
Explore workflows

Explore workflows

Return visit
Try Request desk

Try Request desk

The useful things first

Help each visitor find their starting point in the same site.

First visit
All six workflows, from Creative review to Team onboarding

All six workflows, from Creative review to Team onboarding

Return visit
The handoff playbook: one intake queue that captures the goal, the owner and the date

The handoff playbook: one intake queue that captures the goal, the owner and the date

  • No earlier visits recorded in this browser
  • This browser read the Request desk and Team onboarding pages earlier

Questions

What can be remembered?

Visit count, pages read with recency and time spent, goals reached, and the campaign a landing URL named. It lives in the visitor’s browser for your site only and expires.

Does returning mean existing customer?

No, only that this browser has been here before. Customer status has to come from your own system through a data connector you host.

What happens on another device?

The visitor starts fresh, because nothing is shared between devices or browsers.

Who is Dynamite for?

Any website whose visitors arrive wanting different things: online stores, SaaS and B2B sites, and publishers.

Do I need to redesign anything or migrate?

No. It works with any website out of the box.

How long until I see results?

You should be implemented in a day and start seeing results within a week.

Do I get help setting up?

Yes. Every account starts with an onboarding call, and we help you set up your first personalizations.

Are there guides?

We take you through setup on your onboarding call and share what works for sites like yours. Dynamite also bootstraps the first setup itself.

How much management does it take?

Dynamite can bootstrap the implementation and drive itself. The more data you give it, the better it gets. If you want to hold control over exactly what is shown and when, you can. Otherwise, the agents are good at it.

Will it affect my page speed?

No. Dynamite runs at runtime, after your page has painted.

Where does the data live?

In a cookie in the visitor's browser, backed up and enriched on a server.

What can be changed?

Dynamite can be pointed at any component or control to replace sections, add new ones, reorder, filter, and more.

How fast is it?

Dynamite caches variants, so the decision engine can render new content within 300 ms.

Sell to every visitor like they are the only one.

Talk to sales