What each page, section and content type is producing: traffic, engagement and outcomes, attached to the content itself rather than buried in a separate analytics property.
The problem
Decisions made blind.
Most content estates publish without knowing what any of it produces. The analytics exist, but they live in a separate tool the authors never open, read by a different team, on a reporting cycle that arrives after the decision has already been made. So pages get written because someone asked, kept because nobody checked, and the estate grows without anyone being able to say what is earning its keep. The fix is not another dashboard somewhere else. It is insight inside the environment where publishing decisions actually happen.
What it shows
The estate, visible.
Three kinds of signal, all inside Magnolia, all live. No exports, no waiting for the monthly deck.
Where visitors arrive, where they move, where they stall. The estate seen as journeys rather than pages, so the gaps and dead ends show themselves.
An author opening a page sees how it is performing at the moment they edit it. Publishing decisions get made with evidence in view, not from memory or instinct.
Signature move
The same signals feed the DXP Value Survey evidence base and Grove enhancement work, so what the accelerator shows becomes the ground truth the wider programme stands on.
The signal flow Performance and journey signals come off the live estate and surface in the authoring view, not a separate tool. The decision point carries the one lime mark
Fig 1 · The signal flow Performance and journey signals come off the live estate and surface in the authoring view, not a separate tool. The decision point carries the one lime mark: publish, keep or retire, with the evidence in view.
How it lands
Live in days. An accelerator, not a programme.
There is no discovery phase, no integration roadmap, no steering committee. The accelerator installs, maps and goes live inside the same week on a typical estate.
01
Install
The accelerator installs into your Magnolia instance. Packaged software, not a build project, deployed by people who know the platform from the inside.
Time: a day on a typical instance
02
Map
The signals are mapped to your content model and your journeys, so what authors see reflects your estate, not a generic demo dataset.
Time: days, sized to the content model
03
Go live
The author view switches on. From that point, every publishing decision in the estate can be made with the evidence in view.
Result: insight where the decisions are made
Platform and route to market
Built on Magnolia
Validated Magnolia partner
Available via AWS Marketplace · listing in progress
AWS Advanced Consulting Partner
Where it connects
Part of one estate.
The accelerator stands on its own, and it also feeds the work around it. Here is where it most often joins the rest.
The evidence base
DXP Value Survey
Acting on what it shows
Long-term Partnership Grove
The platform underneath
CMS
The four-week diagnostic. The accelerator's signals feed the evidence the Survey reads.
Enhancement work guided by live estate evidence rather than guesswork.
Magnolia and Contentful implementation, migration and repair of the content platform.
Questions
Frequently asked questions.
Is this a product or a consulting engagement?
An accelerator: packaged software that installs into your Magnolia instance in days, not a programme of work. It was built inside client engagements and hardened on live estates. Practice support is available around it, but the accelerator stands on its own.
Does it work outside Magnolia?
It is built on Magnolia, by a validated Magnolia partner, and it lives inside the Magnolia authoring environment by design. If your estate runs on another platform, the DXP Value Survey covers the same analytics ground as a diagnostic, and we can talk about what insight tooling fits your stack.
How quickly is it live?
Days. The accelerator installs into your Magnolia instance, is mapped to your content model and journeys, and the author view goes live. There is no discovery phase, no integration programme, and no quarter-long rollout.
What do authors and estate owners actually see?
Content performance, journey signals and authoring-time insight, inside the authoring environment. An author sees how a page is performing at the moment they edit it. An estate owner sees what the estate as a whole is producing, without exporting anything to a separate tool.
How is it priced, and is it on AWS Marketplace?
Licensing is shaped to the estate, with pricing on request. The accelerator carries the Available via AWS Marketplace tag, with the listing in progress, so procurement will run through your existing AWS relationship once it is live. Until then, talk to us.
Start here
See what the estate is producing.
If your Magnolia estate is publishing blind, the fix lands in days, not quarters. Tell us about the instance and the content model, and we will show you what the author view looks like on your estate.