Stop measuring traffic.
Start measuring decisions.
Build an analytics system that tells digital teams what changed, why it changed, and what to do next from event architecture and content performance to experimentation and conversion.
What should the team change next?
Optimization is the output.Dashboards don't create insight. Decisions do.
Enterprise teams rarely suffer from a shortage of analytics. They suffer from disconnected analytics: one system for traffic, another for campaigns, another for content, another for product behavior and no shared model of what matters.
Drupal's 2026 product strategy explicitly includes content analytics alongside personalization, SEO/AEO, lead generation and privacy compliance. The opportunity is to make measurement part of the digital platform rather than a reporting layer bolted onto it.
Instrument the journey.
Not just the page.
Business events
Define the actions that actually matter: lead intent, application progress, product engagement, content consumption or conversion.
Data layer
Create a consistent vocabulary for events, properties, content entities, campaigns and audiences.
Identity & context
Connect sessions, journeys and permitted customer context without creating unnecessary privacy exposure.
Analysis
Turn raw events into funnels, cohorts, content performance, segment behavior and meaningful operational signals.
Action
Feed findings back into content, UX, personalization, campaigns and product decisions.
Four signals worth putting in front of the team.
Good measurement reduces the distance between evidence and action. It makes the important signals obvious enough that a team can respond.
Make improvement a system, not a quarterly project.
Optimization works when measurement closes the loop: observe the behavior, form a hypothesis, change the experience, test the result, learn and repeat.
That approach is already visible in current enterprise digital-experience practice: Acquia describes experimentation as valuable even when a test does not produce a lift, because it prevents teams from scaling ineffective approaches.
See it.
Find the friction.
Explain it.
Define what might improve it.
Change it.
Run a controlled test.
Measure it.
Keep evidence, not opinions.
Apply it.
Turn learning into the new baseline.
Give AI better questions and better evidence.
AI can help summarize patterns, identify anomalies, classify feedback and surface optimization opportunities. But the quality of the answer depends on the quality and governance of the underlying data.
Drupal's current AI direction includes data and insights agents and optimization agents, alongside governance and enterprise integration. That makes a clean measurement foundation increasingly valuable.