Last verified: September 12, 2026
What You Can Now Do
Context Memo now treats an offer as a record with a lifecycle instead of a text field someone pasted into a page. Each offer carries a start date, an end date, a state, and a position in a portfolio tied to a placement. A scheduler reads that portfolio, checks the clock, and cycles the next eligible offer into the placement, so the page stays current without a ticket or a manual edit. What changes for you is the unit of work: you stop tracking expiry dates in a spreadsheet and start deciding which offers belong in a portfolio and in what order. Each offer also accumulates its own performance record, because the system knows exactly which offer was live during which window.
Where It Is in Context Memo
This sits in the memo publishing side of the product, on the offer record itself and on the portfolio that feeds a placement. The offer record screen now shows lifecycle state, start and end dates, and portfolio membership. The portfolio view shows rotation order and which offer is currently live in the placement.
How to Use It
- Create the offer as a record with its copy, destination, start date, and end date. On save it enters a scheduled state rather than going live immediately, so nothing publishes before its window opens.
- Assign the offer to the portfolio attached to the placement where it should render. The portfolio view updates to show it in the rotation queue.
- Set rotation order for the portfolio. The scheduler serves offers in that order, skipping any whose window does not include the current date.
- Publish the placement on your domain. From that point the live offer changes when the clock says it should, not when someone remembers.
- After the first full rotation, open the per-offer performance record. You see clicks from AI-referred traffic scoped to the window each offer was live, instead of one blended number for the placement.
- When an end date passes, confirm the state flipped to expired and the next eligible offer took the slot. If a portfolio runs dry, the placement has no eligible offer, which is your signal to add one.
Why We Built It
The complaint we heard was blunt: "that page is still advertising a webinar from two quarters ago, and nobody caught it." Static offer fields cost teams twice. A dead link to a closed promotion reads as abandonment to a human buyer, and an expired offer sitting on an otherwise accurate page creates a contradiction a model has to resolve, which is the kind of ambiguity that makes it hedge or skip the source. Freshness is a documented ranking input for traditional crawlers; how answer engines weight it is less transparent, but stale content raises interpretive load either way, and that works against an accurate citation.
What It Does Not Do Yet
- Rotation executes on placements Context Memo publishes to your domain. Offers living in your CMS or marketing automation stay manual, and we are not replacing those systems. Keep a single owner for offers that sit outside Context Memo so the two sets do not contradict each other.
- Eligibility is date driven. There is no rule set yet for rotating by traffic source, geography, or persona, so if you need different offers for different audiences, build separate placements.
- Performance attribution is windowed, not causal. The system records which offer was live when, which is enough to compare offers against each other over similar periods. It does not isolate the offer from everything else that changed in that window.
- Rotation depends on the dates you enter. An offer with no end date never expires and will hold the placement until you change it, which is the one failure mode worth auditing after setup.
