Content Performance Agent
Reports engagement and conversion by piece.
- Industry
- IT Company
- Department
- Content
- Team
- Content Planning
- Kind
- Investigator
- Approver
- Content Lead
- Code
- CON-12
It reports engagement and pipeline influence by piece (demo requests, contact-sales forms, SaaS trial sign-ups and opportunities touched) and explains why pieces over- or under-perform, separating search ranking, persona fit, timing, channel and tracking causes. It ranks the likely causes for each piece off target and recommends the fix. **The problem it solves:** Why each piece is above or below its benchmark: the traffic, conversions and pipeline it drove, what changed in the period, and which cause the evidence supports.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: the conversion events and opportunities touched by each piece in the period, with opportunity amounts..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Content Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it updates the content performance report and opens a task for each recommended fix. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The content measurement plan: conversion events (demo request, trial sign-up, contact sales), pipeline attribution rules, benchmarks by content type and persona, and known tracking changes.
Reads from
the CRM: the conversion events and opportunities touched by each piece in the period, with opportunity amounts.
Acts in
the project management tool: it updates the content performance report and opens a task for each recommended fix.
Hands back
A list with one entry per piece, each with ref, verdict (under, on_target, over or too_early), metrics (an object of metric to value), pipeline_influenced_usd (or null), causes (a ranked list with cause, evidence and confidence) and fix.
Asks a person when
The report attributes pipeline in USD to content for a leadership review, or the diagnosis blames a tracking failure on the website.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Under-performs below (% of benchmark) | 70 | A piece below this share of its type's benchmark is diagnosed. |
| Out-performs above (% of benchmark) | 130 | A piece above this is diagnosed too, to learn from it. |
| Least sessions for a verdict | 300 | Pieces with fewer sessions are reported as too early to judge. |
| Pipeline attribution | multi-touch | How opportunities in the CRM are credited to content; B2B deals touch many pieces. |
| Site-wide drop that means tracking (%) | 30 | A drop across all pieces larger than this is treated first as a tracking or site cause. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Judge a piece only with at least 300 sessions; below that report it as too early.
- Diagnose pieces below 70 or above 130 percent of their type's benchmark.
- When all pieces fall by more than 30 percent together, check tracking and site releases before any content cause.
- Credit pipeline with the multi-touch model and report pipeline influenced in USD from the CRM, never estimated.
- Rank causes by evidence and say what would confirm each.
See the Content Performance Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.