Skip to main content

Proxying Plausible through Akamai

Proxying Plausible via your own property on Akamai is easy, fast and privacy friendly.

note

The instructions assume you use the default paths /js/script.js and /api/event. You can change these based on your preferences.

Step 1: Proxy Analytics Script​

This Rule Group serves incoming requests matching /js/script.js directly from the Akamai edge caches. In case of a cache miss the request is forwarded to plausible.io in a privacy friendly way.

Add new Rule Group​

In Akamai Property Manager add a new Rule Group Plausible (Script) with these settings:

In Akamai Property Manager add a new Rule Group

Set Criteria​

  • Path matches one off: /js/script.js

Add Behaviour: Caching​

  • Caching Option: Cache
  • Force revalidation of stale objects: Serve stale if unable to validate
  • Maxage: 6 hours

Add Behaviour: Origin Server​

  • Origin Type: Your origin
  • Origin Server Hostname: plausible.io
  • Forward Host Header: Origin Hostname
  • Cache Key Hostname: Origin Hostname
  • Supports Gzip Compression: Yes
  • Send True Client IP Header: No (Privacy: No need to expose IP)
  • Verification Settings: Choose your own
  • ... (Other settings can be left as is)

Step 2: Proxy Event API​

This Rule Group forwards incoming requests matching /api/event to plausible.io. It adds extra headers (X-Forwarded-Proto, X-Forwarded-Host and X-Forwarded-For) to the outgoing request so your Plausible statistics are complete. For privacy & security reasons incoming cookies are removed before sending to plausible.io.

Add new Rule Group​

In Akamai Property Manager add a new Rule Group Plausible (Event API) with these settings:

Property Manager Rule to proxy the Event API

Set Criteria​

  • Path matches one off: /api/event

Add Behaviour: Origin Server​

  • Origin Type: Your origin
  • Origin Server Hostname: plausible.io
  • Forward Host Header: Origin Hostname
  • Cache Key Hostname: Origin Hostname
  • Supports Gzip Compression: Yes
  • Send True Client IP Header: Yes
  • True Client IP Header Name: X-Forwarded-For
  • Verification Settings: Choose your own
  • ... (Other settings can be left as is)
Property Manager Rules to remove outgoing request headers and cookies

Add Behaviour: Modify Outgoing Request Header​

  • Action: Add
  • Header Name: X-Forwarded-Proto
  • Header Value: {{builtin.AK_SCHEME}}

Add Behaviour: Modify Outgoing Request Header​

  • Action: Add
  • Header Name: X-Forwarded-Host
  • Header Value: {{builtin.AK_HOST}}

Add Behaviour: Modify Outgoing Request Header​

  • Action: Remove
  • Header Name: cookie (Privacy: No need to expose cookies to origin servers)

Optional:​

In case you are using SureRoute, please disable it:

In case you are using SureRoute, please disable it

Thanks to Tim Vereecke, Akamai's web performance architect, for these instructions!