Configuration reference

The API Worker (apps/api) reads all of its settings from apps/api/wrangler.jsonc and from Worker secrets. This page lists every binding, variable, and secret it reads. To change a variable, edit vars in wrangler.jsonc and deploy again. To set a secret, run wrangler secret put <NAME> in apps/api. Locally, put secrets in apps/api/.dev.vars, which git ignores.

#Bindings

The consumer retries a batch 5 times, then moves it to the dead-letter queue misomoon-events-dlq. The cron trigger (*/5 * * * *) checks traffic-spike alerts and moves data off retiring shards every 5 minutes. At minute 15 of every hour, it also sends email reports, checks traffic-drop alerts, applies retention, and deletes old salts and usage rows older than 400 days.

#Variables

Set these in vars in apps/api/wrangler.jsonc.

#Secrets

Without an email provider, the dashboard shows invitation links to copy by hand, and reports, alerts, password resets, and the daily-cap notice are not sent.

The managed proxy is on only when CF_API_TOKEN, CF_ZONE_ID, and PROXY_CNAME_TARGET are all set. Serve the tracker from your own domain explains the proxy and its other options.

#Daily ingest cap

The cap limits how many events one site stores per UTC day, so a bot flood or a broken script can't run up D1 writes. It counts every stored row. A pageview, a custom event, and an engagement ping each count as one. The queue consumer applies the cap before it writes to a shard, and keeps the earliest events of the day. Several consumers can run at once. Each adds the room it takes to the day's count in CONTROL in one statement, so together they never store more than the cap, and it gives back the room it didn't use once its write is done. If a consumer fails before it can give the room back, the day stores a little less than the cap, never more. A queue retry never counts an event twice or drops one that was already stored. Once a day is full, the edge also drops beacons for that site within a minute, before they reach the queue. A ref-only beacon is an engagement ping that carries only payment refs. The edge drops it for a site that takes no payments. For a site that takes payments, it counts as one stored row, not as an event, and a queue retry doesn't count it twice. It takes room under the cap like any other row, but once queued it is never dropped, so the payment keeps its visit. Those beacons are the one way a day can store more than its cap: one row each, for those queued before the edge saw the day full. Payments from webhooks are never capped. The day starts over at 00:00 UTC.

Each site has an ingest_cap column in the sites table of CONTROL:

To give one site its own cap, run:

wrangler d1 execute CONTROL --remote --command "UPDATE sites SET ingest_cap = 500000 WHERE id = 'shop-com'"

Workers pick up the change within a minute. The first time a cap drops an event on a given day, the team's owners and admins get one email. A block sends no email. GET /api/v1/sites/:id/usage returns the cap and the counts for the last 31 days. The dropped count includes only events that the consumer dropped. Beacons that the edge dropped are not counted, because counting them would cost a write each.

#Tracker attributes

The tracker reads these attributes from its own <script> tag. The tracking guide shows them in use.

Which paths count, the search parameters, and what the tracker collects are site settings, not attributes: see Choose what to track. A browser the tracker doesn't count says why in its console.

Attributes on a page's own elements (data-misomoon-content, data-misomoon-media, data-misomoon-id, data-misomoon-mask) are in the tracking guide.