CMS-driven analytics: stop paying developers for every tracking change
Structure your CMS so marketers can add tracking events without developer intervention. Save six figures DKK over the lifetime of the site.
The 5.600 DKK button click
The traditional model
Most analytics is hard-coded into components. Adding new tracking means a developer ticket, a PR, code review, QA, and a deploy. For organizations running dozens of campaigns a year, this becomes one of the biggest line items in maintenance.
The pain is invisible until you add it up. Every event change is a sprint commitment. Every campaign timing is dictated by the engineering backlog. Marketing learns to ask for less, not because it doesn't need data, but because the cost of asking is too high.
The CMS-driven alternative
Move tracking definitions into your CMS as first-class content types. A marketer composes the event in the CMS (name, properties, trigger conditions) and the front end picks it up automatically. Engineering builds the engine once. Marketing operates it forever.
- Event content type: name, category, properties, trigger element selector or content reference.
- Tracking link content type: outbound URLs with attached event payloads.
- Form content type: per-field event definitions for analytics-driven funnels.
- Consent gate: which region, which consent category, evaluated at the edge.
What ships out of the box in the Enterprise Starter
- Event-definition content type with schema validation.
- Edge-evaluated tracking dispatcher, cached per page.
- CMS-managed consent gating per region.
- Type-safe event payloads (codegen).
- A small admin UI to test events without leaving the CMS.
The economics
At 24 events/year and 4h per event of senior time at 1.400 DKK/hour, you save ~134.000 DKK/year. The savings repeat every year, with no per-event handoff cost. The break-even on building the CMS-driven model is usually inside the first eight events.
The bigger gain is hidden in cycle time. Marketing ships a campaign on the day they need it, not three sprints from now. That alone has changed how teams approach experimentation.
Want this kind of judgment on your project?
I read every email within one working day. Bring a project, a quote, or a system you're stuck on.
15 things every Contentful enterprise project gets wrong in the first 6 weeks
The 15 production gaps every enterprise Contentful + Next.js build hits in the first six weeks — and how to close each one without burning a sprint. A pre-kickoff checklist for technical leads on a Contentful enterprise starter.
REST + GraphQL hybrids for multi-locale CMS-driven sites
Why neither REST-only nor GraphQL-only is the right call for an enterprise multi-locale CMS site, and how to split by concern instead. Includes the circular-reference problem on full REST payloads, the bundle cost of GraphQL on the client, the decision matrix per call site, the unified fetcher, granular cache tags, the block-as-fragment pattern, locale fallback in one round trip, Live Preview survival, Server Actions for CMA writes, the Algolia Sync API exception, and the migration sequence.
Dynamic CMS linking: why your 'Link' field is a time bomb
Most CMS implementations let authors paste raw URLs. The day someone renames a slug, half your navigation silently 404s. The model that makes that impossible — with a Contentful walkthrough.