Frequently asked questions
Pageviews alone rarely answer the questions leadership actually cares about: task completion (did the visitor find the form, the fact sheet, the service they needed?), content findability, search success/failure rates, and drop-off points in key journeys. A mature analytics setup on Drupal ties these behavioural metrics back to specific content types and site sections so content owners can see which pages are underperforming and why.
Yes. Privacy-conscious analytics (first-party tracking, consent-aware tag management, avoiding third-party ad-tech trackers) is achievable on Drupal and is the expected default for government sites, which typically can't use the kind of invasive tracking common on commercial marketing sites. This is also the same underlying approach used for privacy-respecting personalisation.
Personalisation and recommendation engines are only as good as the behavioural data feeding them; analytics is the input layer that makes DXP capability (targeted content, recommendations, journey optimisation) possible in the first place, so an analytics strategy shouldn't be scoped separately from a personalisation strategy.
Insights