What is Edge Content Protection?

Edge Content Protection (ECP) validates entitlement cookies at the Akamai edge through the Edge Integration Framework (EIF). Unauthorized requests are blocked before premium content is rendered, making paywalls secure and virtually impossible to bypass.

ECP works alongside the client-side paywall in the Subscriptions product, which handles metering, audience targeting, and personalized upgrade experiences.

Server-Side vs. Client-Side Paywalls in Arc XP

Arc XP supports both client-side and server-side paywall enforcement. Each approach determines where access logic is applied — in the browser (client-side) or at the content delivery layer (server-side, where ECP operates). Understanding these models helps you choose the right balance of flexibility, performance, and security for your site.

Client-Side Paywalls

Description	Entitlement logic runs in the browser via JavaScript after the page is delivered. The paywall script decides what to show or hide, and rules can be configured in the Subscriptions Paywall Admin and combined with audience targeting and personalization tools.
Advantages	Flexible, easy to iterate or test Supports personalized targeting and experimentation Requires minimal backend configuration
Considerations	Content is delivered before access validation occurs Users or bots can sometimes bypass protections via cached or intercepted requests Requires strong client-side obfuscation and rate limiting
Use cases	Dynamic experiences Metering A/B testing paywall strategies

Server-Side Paywalls

Description	Entitlements are enforced before content is delivered. Content rendering and caching occur at the edge, only after a user’s entitlement has been validated.
Advantages	Protects premium content before it is rendered to your site Virtually impossible to bypass because logic runs at the CDN layer Uses verified entitlement cookies for consistent authentication
Considerations	Requires Edge Integration Framework (EIF) configuration and entitlement cookie setup
Use cases	Subscription or premium sites with strict entitlement enforcement Environments vulnerable to scraping, bot traffic, or credential sharing

Hybrid Paywalls

Description	A server-side paywall handles entitlement enforcement while a client-side layer adds targeting or metering (for example, a set number of free articles per month), combining strong premium-content protection with personalized reader journeys.
Advantages	Combines server-side enforcement with client-side flexibility Strong premium-content protection alongside personalized reader journeys Supports metering on top of strict entitlement enforcement
Considerations	Requires both EIF configuration and client-side paywall setup More moving parts to maintain across layers
Use cases	Publishers offering free article allowances with strict premium-tier enforcement Sites needing both targeted upgrade experiences and bypass-resistant content protection