Dynamite

Personalize the next read for every reader

Dynamite personalizes your read-next module within 300 ms, so every reader sees the story most likely to keep them reading.

Illustrative Meridian website for First article of a visit. More on housing. The three newest housing stories from the feed, not counting the one on screen
  • Message for this visit
  • A matching example
  • Relevant stories to read next
First article of a visit
  • Reading a housing story, arrived from search, no history
Illustrative example: Meridian. Generated design previews.

One read-next module on an article page

Meridian’s articles end with a three-card “Read next” module. Editors approved two headings for it and the topics it may draw from.

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 article of a visit

From every visit

  • Where they came from
  • Campaign and ad
  • Pages they viewedReading a housing story, arrived from search, no history
  • Past visits
  • 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 Meridian website for First article of a visit. More on housing. The three newest housing stories from the feed, not counting the one on screen
  • Message for this visit
  • A matching example
  • Relevant stories to read next

Illustrative example: Meridian. Generated design preview.

One site. Different starting points.

A message that fits

Start with the need that brought this visitor here.

First article of a visit
More on housing

More on housing

Loyal reader
You may have missed

You may have missed

Show the right example

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

First article of a visit
The three newest housing stories from the feed, not counting the one on screen

The three newest housing stories from the feed, not counting the one on screen

Loyal reader
Three unread stories from those topics, skipping the four from this week already opened

Three unread stories from those topics, skipping the four from this week already opened

A relevant next step

Choose the action that fits this visit. Measure second article reads against the original.

First article of a visit
Each card keeps its own headline and link

Each card keeps its own headline and link

Loyal reader
Each card keeps its own headline and link

Each card keeps its own headline and link

The useful things first

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

First article of a visit
The three newest housing stories from the feed, not counting the one on screen

The three newest housing stories from the feed, not counting the one on screen

Loyal reader
Three unread stories from those topics, skipping the four from this week already opened

Three unread stories from those topics, skipping the four from this week already opened

  • Reading a housing story, arrived from search, no history
  • Forty articles read in this browser, mostly housing and transport

Questions

What can editors control?

Which modules may change, each one’s heading, layout and card count, its topics and its freshness limits.

How does content stay fresh?

Dynamite re-reads the public feeds on a set interval and stops using a result past its maximum age. Anything already read in this browser is skipped.

Can the module fall back?

Yes, by default. A stale or empty feed, too few unread stories, a missing image or a late decision each leave the module as editors placed it.

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.

Or email samraaj@ion.design