Last verified: October 6, 2026
What You Can Now Do
Context Memo now has an offers coverage view, where you can see a sortable and filterable table of memos per offer, view traffic broken down by city, and exclude specific locations from your offers coverage analysis. Before this deploy, offer performance read as one blended number, so a memo set that was working in two metro markets and dead everywhere else looked identical to one performing evenly. Now each memo is attributed to the offer it supports, and the traffic sits next to the city it came from. That changes one concrete decision: which offer gets your next memo, and which market you write it for.
Where It Is in Context Memo
Open the Offers area and select the coverage view. The screen has two parts. The first is a table of memos organized by offer, with columns you can sort and filter. The second is a geographic traffic panel that breaks performance out by city, with a control for excluding locations from the coverage calculation.
How to Use It
- Open the coverage view in Offers. The table loads with every memo mapped to the offer it supports, so you can see coverage per offer rather than one total.
- Sort the table by the column that matters for the question you are asking, whether that is offer, memo, or traffic. Sorting reorders the full set, not just the visible page.
- Filter down to a single offer. Everything on the screen, including the city panel, narrows to that offer's memos and traffic.
- Read the city breakdown. You get traffic per city for the filtered selection, which tells you where the AI-referred visits for that offer are actually landing.
- Exclude locations that are not part of your addressable market. Coverage figures recalculate without them, so a spike in a city you do not sell into stops distorting the view.
- Act on the gap. Where an offer shows traffic in a target city but thin memo coverage, publish a memo against that offer and track it back in the same table.
Why We Built It
The request came in plainly: "I need to see which offers are performing in which cities and control which locations matter to my analysis, rather than viewing offers data in aggregate." Aggregate offer data hid two things that cost money. It hid which offers were already earning AI-referred traffic in priority markets, and it let irrelevant geography inflate numbers used to justify the next round of content. Teams were making memo decisions on an average that described no real market.
What It Does Not Do Yet
City is the finest geographic level available in this view. There are no custom region or territory rollups, so if you manage markets by territory, build the grouping on your side for now and use city exclusions to approximate it.
Exclusions are a manual selection you maintain. They apply to the coverage analysis only. They do not change scanning, data collection, or what appears elsewhere in the product, so a location you exclude here is still being tracked and can be brought back into the view at any time.
The coverage view reports on memos already mapped to an offer. If a memo is not associated with an offer, it will not appear in the per-offer table, and you will need to map it before it shows up in the breakdown.