Where performance data would eventually come from.
Content performance requires exposure and engagement events mapped to stable content asset identifiers. Analytics is where those events live — which is why the asset IDs are designed the way they are, long before anything reads them.
In short: Part of Performance & Activation: page and event data maps onto Narraxio content IDs, and nothing is read until you connect a property explicitly.
What it is
The analytics platform most sites already run, and the most likely first source of exposure and engagement data.
What Narraxio reads
- page and event data mapped to Narraxio content IDs
- engagement metrics per asset and variant
- conversion events, where configured
- nothing until the customer connects it explicitly
How it is connected
- OAuth to the properties you authorize
- read-only
- a mapping step between your events and Narraxio asset IDs
- configurable retention for imported metrics
How you verify it
- imported metrics reconcilable against the source property
- the attribution model in use shown alongside every number
Limits worth knowing
- Attribution produces model output, not demonstrated causation, and is labelled accordingly
- Analytics data is subject to your own consent configuration, which is your responsibility rather than ours
Other integrations
Connect the rest of the stack
Give your content a memory. Give your AI the full picture.
Connect a repository read-only and see what has been sitting inside it — every headline, claim and near-duplicate paragraph, with the file and field each one came from.
Keep Git and your existing stack Read-only to start Narraxio runs on Narraxio