Last verified: September 16, 2026
What You Can Now Do
Context Memo now shows offer impressions on memo pages, with funnel metrics broken down by offer and by stage, in the memo view itself. Before this deploy, a memo told you it was being read and cited. It didn't tell you which offer inside that memo was being seen, or where readers stopped. Now the memo page carries both: impression counts per offer, and stage-level progression underneath each one. The decision this changes is concrete. When a memo draws traffic but produces nothing, you can tell whether the offer was never seen or was seen and skipped, and you fix the right thing instead of rewriting the whole memo.
Where It Is in Context Memo
The data lives on the memo page itself, in the performance area alongside the memo's existing metrics. Each offer attached to the memo appears as a row with its impression count. Stage-level detail renders as styled sub-rows beneath the parent offer, so funnel progression sits under the offer it belongs to rather than in a separate report. No new navigation, no separate analytics tab to learn.
How to Use It
- Open any published memo from your memo list. The performance area now includes an offer section listing every offer that appears on that memo, each with its impression count.
- Read the impression numbers first. An offer with low impressions is a placement problem. An offer with high impressions and thin downstream movement is a copy or fit problem. These are different fixes and they were indistinguishable before.
- Expand an offer row to reveal the stage sub-rows. Each stage shows its own metrics for that specific offer, so you see where progression holds and where it drops.
- Compare offers on the same memo side by side. If two offers sit on one memo and one carries the stage movement, you have evidence to cut or replace the other rather than an assumption.
- Act on the memo, not the dashboard. Move the surviving offer higher in the memo, rewrite the framing around it, or change the persona the memo targets. Republish and check the same rows on your next review cycle.
- Repeat on your highest-traffic memos first. Memos already pulling AI citations and bot crawls give you the largest sample to read, so start where the signal is strongest.
Why We Built It
The question we kept getting was some version of "which offers actually drive conversions, and at which stage?" Customers had the answer in pieces: memo traffic in one view, funnel data somewhere else, offer performance inferred by guesswork. Answering a single question meant leaving the memo, rebuilding context in another tool, and coming back without confidence that the two views described the same thing. That cost real time on every review, and it cost more than time when teams optimized the wrong layer, editing memo copy when the offer was never surfaced, or swapping offers when the memo was pulling the wrong readers. Offer performance belongs where the offer is published. Now it's there.
What It Does Not Do Yet
These metrics are scoped to the memo you're viewing. There is no rolled-up view yet that ranks the same offer across every memo it appears on, so if you run one offer across a set of memos, comparing its performance means opening those memo pages in turn. That comparison is on us to build, and it's a manual step until we do.
The stage breakdown reports what happened. It does not recommend which offer to move, rewrite, or retire. That judgment stays with you, and it should, because the right call usually depends on the persona the memo targets and where that memo sits in your funnel strategy.
One more thing worth being plain about: this reporting reflects activity on memos published through Context Memo. Offers living elsewhere in your stack, in your CMS or your marketing automation platform, still report there. We're not replacing those systems, and the numbers here don't pretend to be your whole funnel. They answer a narrower question with more precision: inside this memo, which offer got seen, and how far did readers get.
