A product release can make an existing context hint more useful, leave it untouched or make it inaccurate. The deciding factor is what a customer can actually do with the advertised offer after the change. A new button, a renamed feature or a redesigned settings page does not automatically require new wording in your ChatGPT advertising.
Treat release notes as a reason to review affected hints. They are not a ready-made hint list. The method here is an editorial recommendation for one bounded decision: update, retain or withdraw each existing description that the release could affect.
Describe the difference before rewriting
Put two short statements in your working document. The first describes what the advertised version supports today. The second describes what that same offer will support once the change is available. Avoid words such as improved and smarter; they often conceal the actual difference in the customer’s task.
Record the version, subscription and availability date. An announcement might describe a future capability while the ad still leads to the current product. If the launch applies only to a paid extension, capture that condition. A capability offered somewhere in the catalogue is not automatically included in the offer being advertised.
Use the guide to checking evidence behind a hint when the capability itself is uncertain. This release review uses that evidence to decide what changed over time.
Follow one release through three existing hints
The following example is fictional. A site-inspection product introduces the ability to record notes without an internet connection and synchronise them later. Assigning inspection owners continues to work as before. At the same time, editing an older form format is discontinued. Those are three product decisions within one release, with different consequences for the advertising brief.
An existing hint about recording inspections on connected tablets may need updating because connectivity is no longer required during note capture. A hint about assigning owners can stay. A hint about customising legacy forms should be withdrawn from the new version’s brief if that task is no longer supported.
These are decisions about descriptions. The example does not represent an actual launch, a campaign result or an observed user conversation.
What did the release change for the existing hint?
- Update
Notes can now be recorded offline. Describe capture now and synchronisation later.
Checkpoint - Retain
Assigning owners remains supported. Keep the hint and record the review.
- Withdraw
Legacy forms can no longer be edited. Remove the hint describing that task.
Update when a previous constraint changes
Read the old hint and mark the part that the release makes outdated. In this example, that is the connection requirement. A possible replacement is: “Record inspection notes at sites without internet access and synchronise afterwards.” The wording describes the changed task while preserving the distinction between recording information and transferring it later.
Do not say the entire product works offline if only note capture does. Scheduling, attachments and approvals may have different conditions. Removing a constraint from one activity does not establish that every neighbouring activity has the same support.
Replace the earlier wording when the revised hint describes the same task more accurately. Keeping both without explanation can leave conflicting accounts of the product’s requirements. If both remain necessary for different offers, make that distinction explicit in the working document.
Retain when the customer’s task remains the same
A redesigned administrator view might make assignment easier without changing who can be assigned or what problem the function solves. The hint about allocating inspection responsibility can therefore remain. The size of the engineering effort is not a reason, by itself, to rewrite the context.
Still record the decision: “Reviewed against this release; the use case remains supported.” This distinguishes intentional retention from a forgotten row. The note belongs in your working document, not inside a context hint.
Avoid inserting version numbers or the word new merely to demonstrate that somebody completed the review. Those additions date quickly and rarely help explain the customer’s need.
Withdraw when support for the task ends
In the fictional inspection product, old forms remain readable but can no longer be edited. A hint about customising those forms is now misleading even if the same terms still appear in help documentation. Reading historical material and performing the described task are different capabilities.
Do not try to rescue the description by adding “not legacy forms”. Treat this as an accuracy decision, and do not treat negative wording as a negative-targeting mechanism. Remove the outdated row from the intended list and keep the reason in the change record.
If an older version is still being sold, review its brief separately. Do not apply the same withdrawal decision to every offer simply because the versions share a product name.
Choose the effective date and affected group
Distinguish the announcement, availability to the relevant customer and retirement of previous support. They need not happen together. Keep an uncertain new capability as a proposal with a clear condition for another review. Retain the old hint in the meantime only if its description remains accurate.
OpenAI’s campaign documentation describes hints as shared across an ad group’s ads. Check the affected offers before applying a version-specific change there. It also documents that updating the hint field replaces the list, so save the complete intended list and confirm the result afterwards.
Finish with a reasoned change record
Keep the previous wording, decision, replacement if needed and product information supporting the change. Record when the decision can take effect. If the release is withdrawn, this lets you review which rows should return without restoring other obsolete uses along with them.
Under OpenAI’s targeting guidance, hints provide context rather than exact keywords or guaranteed impressions. More current wording therefore does not promise greater reach. The aim is a description that fits the product the customer can obtain.
Once the changes are settled, review the needs covered by the hint list. That broader check can follow the release decision, after you have established which existing rows remain usable.
Sources and scope
Decide whether a changed product capability requires updating, retaining or withdrawing existing context hints, based on when the advertised version actually changes.
Working methods and examples are editorial suggestions. Check current platform requirements and available features before implementation.