CDN with Preloading
With a CDN (Content Delivery Network) and preloading, your messages appear instantly and reliably across the globe.
CDN with Preloading is the delivery infrastructure behind OptiMonk's campaign assets — ensuring that your popup images, fonts, scripts, and templates load instantly for visitors anywhere in the world, rather than being fetched from a single central server on demand. OptiMonk uses Amazon CloudFront, one of the world's largest and most widely distributed content delivery networks, to serve campaign assets from edge locations geographically close to each visitor. This means a visitor in Tokyo, São Paulo, or Berlin receives OptiMonk's campaign assets from a nearby server rather than routing a request halfway around the globe, dramatically reducing the time between a page load and a campaign appearing. On top of CDN delivery, OptiMonk preloads campaign assets in the background before the campaign trigger fires — so when the moment comes to display a popup or sticky bar, the required resources are already in the visitor's browser cache and the campaign appears without any perceptible delay. Together, CDN delivery and preloading eliminate the two main causes of slow-loading campaigns: network latency and on-demand asset fetching. For further information please visit this site: http://aws.amazon.com/cloudfront/details/
Key benefits
- Campaigns appear instantly, regardless of visitor location. Amazon CloudFront operates edge locations across multiple continents, meaning OptiMonk assets are served from a server physically close to each visitor. A campaign displayed to a visitor in Southeast Asia loads from a nearby edge node — not from a data center on the other side of the world. Combined with preloading, the result is campaigns that appear at their trigger point without a visible loading delay, regardless of where in the world your store's traffic originates.
- Preloading eliminates the fetch delay at the moment of display. Without preloading, a campaign would need to request and download its assets at the exact moment it fires — introducing a window where the visitor might see a blank space or a partially rendered popup before the creative fully loads. OptiMonk's preloading fetches campaign assets before the trigger fires, so the images, fonts, and template elements are already present in the browser when the campaign is ready to display. The transition from page to popup is seamless.
- Reliable delivery under high traffic and globally distributed load. CloudFront is designed to handle massive, concurrent traffic volumes with automatic failover and redundancy built in. During peak traffic events — flash sales, viral traffic spikes, Black Friday — OptiMonk's CDN infrastructure scales to serve campaign assets reliably without degradation. There is no single point of failure that could cause campaigns to load slowly or not at all when your store is busiest.
How it works
When you publish an OptiMonk campaign, its assets — images, template files, scripts, and fonts — are distributed to Amazon CloudFront's global network of edge locations. From this point forward, when any visitor triggers a condition that might cause the campaign to display, the assets are available from a server geographically close to them rather than from a centralized origin server.
Once the OptiMonk script initializes on a page — asynchronously, without blocking page rendering — it identifies which campaigns might be eligible to fire for that visitor and begins fetching their assets into the browser's cache in the background. This preload happens quietly during the visitor's natural browsing activity, well before the campaign trigger condition is met.
When a visitor meets a campaign's trigger condition — reaching a scroll depth, spending a set time on page, or showing exit intent — OptiMonk checks whether the campaign qualifies under the targeting rules and, if so, renders it. Because the assets were already preloaded from the nearest CloudFront edge location, the campaign appears without a loading interval. The visitor experiences an immediate, polished display rather than a delayed or flickering popup.
Frequently asked questions
What is CDN with Preloading in OptiMonk?+
CDN with Preloading refers to the delivery infrastructure OptiMonk uses to ensure campaign assets load quickly and reliably for visitors worldwide. OptiMonk uses Amazon CloudFront to serve assets from edge locations geographically close to each visitor, and preloads campaign assets into the browser before a campaign trigger fires — so that when the campaign is ready to display, the required resources are already in cache and the popup appears without delay.
What is Amazon CloudFront and why does OptiMonk use it?+
Amazon CloudFront is Amazon Web Services' global content delivery network, with edge locations distributed across multiple continents. It is designed to deliver content with low latency by routing each visitor's request to the nearest available edge server rather than a single origin. OptiMonk uses CloudFront to ensure that campaign images, scripts, and template assets load quickly for visitors regardless of their geographic location. More information about CloudFront is available at aws.amazon.com/cloudfront.
What is preloading and how does it differ from standard on-demand loading?+
With standard on-demand loading, campaign assets are fetched from a server at the moment the campaign fires — meaning the visitor waits for the download before seeing the popup. Preloading fetches the same assets in the background during the visitor's normal browsing session, before the trigger is met. By the time the campaign fires, the assets are already in the browser's local cache and display immediately. Preloading trades a small amount of background bandwidth for a dramatically faster perceived display time.
Does CDN delivery affect how the OptiMonk script itself loads?+
Yes. The OptiMonk script is also delivered via CDN, meaning it loads from a server close to the visitor rather than from a single origin. Combined with asynchronous loading (which prevents the script from blocking page rendering), CDN delivery of the script itself contributes to fast initialization — OptiMonk becomes ready to evaluate and display campaigns quickly after the page begins loading, regardless of where the visitor is located.
Does CDN with Preloading require any configuration on my end?+
No. CDN delivery via Amazon CloudFront and campaign asset preloading are built into how OptiMonk operates — they are not optional features or settings you need to enable. Every campaign you publish automatically benefits from CloudFront-based delivery and preloading behavior without any technical setup, hosting configuration, or integration work on your part.
Try OptiMonk for free
Launch your first campaign, learn what works, then scale what converts.