Your campaigns load from a server close to each visitor, wherever they shop from.
What it is
When a visitor opens your store, their browser needs two things from OptiMonk: a small loader script, and your campaigns — the settings, the texts and the images. If all of that came from a single data center, a shopper in Sydney would wait longer than one in Frankfurt.
So OptiMonk doesn't serve it from one place. Your campaign files sit on a content delivery network (CDN): a network of servers spread around the world. Each visitor gets them from the edge server nearest to them.
The loader itself is tiny — under 5 KB — and it loads asynchronously, so your page never waits for it. It's always fetched fresh, so fixes and improvements reach your store without you doing anything.
For you, it comes down to one thing: adding OptiMonk doesn't make your store slower for shoppers in other countries. You don't pick regions, you don't upload files anywhere, and you don't pay extra for it.
Compare that with hosting popup images on your own server, or a tool that serves everything from one region. There's nothing here to manage and nothing to keep in sync.
When to use it
CDN delivery is always on. These are the situations where you feel it most.
A store in Hungary with shoppers in Germany and Austria: each of them gets the campaign from a nearby server, so the welcome popup shows up just as fast for all of them.
On a slow mobile connection, every round trip counts. A nearby server keeps the wait short. That matters most for campaigns that should appear early, like a first-visit discount.
On Black Friday, traffic jumps. Your campaign files are cached at the edge, so the extra traffic is spread across the CDN instead of hitting one server.
When you activate or pause a campaign, OptiMonk refreshes the cached copy on the CDN. Shoppers see the change shortly after, not hours later.
Key benefits
A shopper's browser gets your campaign from a server nearby, not from another continent. Popups show up on time, even when your traffic comes from many countries.
CDN delivery is part of how OptiMonk runs on every site. There's no region to choose and no setting to switch on. Install OptiMonk once, and it's working.
When you activate, pause or edit a campaign, the copy on the CDN is refreshed automatically. Your shoppers don't keep seeing an old version.
How it works
Their browser loads the OptiMonk loader from your install snippet, or from the OptiMonk app embed on Shopify. It loads asynchronously, so your page doesn't wait.
The loader asks the CDN for your active campaigns and their images. The edge server closest to the visitor sends them back.
OptiMonk checks your targeting and shows the campaign that fits this visitor — or none, if nothing fits.
Settings & limits
CDN delivery works on every site where OptiMonk is installed.
That's fine. Clear its cache after you add the OptiMonk snippet, so the snippet shows up on your pages.
OptiMonk doesn't run on Shopify preview links. Check your campaigns on your live store.
The CDN speeds up OptiMonk's own files. It doesn't change how fast the rest of your store loads.
Step-by-step setup lives in the Help Center guide.
No. The loader is under 5 KB and loads asynchronously, and your campaigns come from a nearby edge server. Your page renders without waiting for OptiMonk.
No. CDN delivery is on for every OptiMonk account, with no setup.
No. Clear its cache once after you add the OptiMonk snippet, so the snippet appears on your pages.
Shortly after you save. When you activate, pause or edit a campaign, OptiMonk refreshes the copy on the CDN automatically.
OptiMonk doesn't run on Shopify preview links. Open your live store to check your campaigns.