SettingsSet the heatmap-capture override

Set the heatmap-capture override

Turn heatmap capture on or off for a location. Requires an agency key (ak_) and ?location_id=; viewer keys get 403 agency_required.

Accepted values for capture_heatmaps:

  • true — capture click positions and scroll depth with SDK defaults. - { "flushIntervalMs": 5000, "maxBufferPoints": 200 } — on, with those overrides. flushIntervalMs must be 1000–60000 and maxBufferPoints 10–1000; values outside the range are rejected rather than clamped, and unknown keys are rejected rather than ignored.
  • false / null — off. Both mean the same thing here.

Capture adds one event per click and one per page-scroll, so this is off until asked for. The override is served to the SDK via remote config and wins over the site's init() configuration — which is the point: an agency can enable heatmaps on a client site whose install snippet it cannot edit. Browsers pick it up on their next remote-config fetch.

Two cases where it does not apply: a site with disable_remote_config: true never fetches remote config, and HIPAA-mode locations never capture heatmaps regardless of what is stored.

Turning capture on is not retroactive — there is no backfill of past traffic. Read the data with the Heatmaps API.

curl -X PUT "https://mythic-analytics.gulp.workers.dev/client/v1/settings/heatmaps" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
  "capture_heatmaps": true
}'
{
  "success": true,
  "data": {
    "capture_heatmaps": true
  }
}
PUT
/heatmaps
PUT
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Builder/client key as a bearer token. Agency key for read-write (Bearer ak_...) or viewer key for read-only (Bearer sk_...). Scoped keys (mcp_) are accepted too and need settings:read or settings:write. See Using an mcp_ key over HTTP.

Builder/client key as a bearer token. Agency key for read-write (Bearer ak_...) or viewer key for read-only (Bearer sk_...). Scoped keys (mcp_) are accepted too and need settings:read or settings:write. See Using an mcp_ key over HTTP.
Content-Typestring
Required

The media type of the request body

Options: application/json
capture_heatmapsstring
Required

true, false, null, or { flushIntervalMs, maxBufferPoints }.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Builder/client key as a bearer token. Agency key for read-write (Bearer ak_...) or viewer key for read-only (Bearer sk_...). Scoped keys (mcp_) are accepted too and need settings:read or settings:write. See Using an mcp_ key over HTTP.

Body

application/json
capture_heatmapsstring
Required

true, false, null, or \\{ flushIntervalMs, maxBufferPoints \\}.

Example:
true

Responses

successboolean
dataobject