The buyer is not always asking which product is best. Sometimes the question is whether a new component will work with something already owned. That makes compatibility a useful part of a ChatGPT advertising brief, but also an easy place to overstate an offer. A familiar brand name in a hint does not explain the relationship, and “works with existing equipment” can hide a long list of conditions.
The editorial task is to describe a supported combination clearly enough for someone else to verify. The examples below are fictional. They show how to prepare contextual wording, not how to guarantee exposure to a specific customer question. OpenAI’s targeting documentation provides the platform reference for context hints.
Define both sides of the connection
A compatibility statement has at least two sides: the advertised offer and the thing it must work with. “Replacement shelf for storage systems” leaves both too vague. Which shelf dimensions, mounting method and system range are involved? “Exporting data to accounting software” leaves the format and receiving workflow unresolved.
Write the connection in a working sentence before shortening it. For example: “The advertised bracket attaches this monitor to a mount supporting the specified hole pattern, within the documented weight range.” This is not polished hint text. It is a way to expose the facts the final wording depends on.
Do not assume that a shared connector shape establishes full compatibility. Physical fit, power requirements, data exchange and supported functions can be different questions. Choose the relationship relevant to the customer’s task and verify that relationship specifically.
Use a dependency card
For every compatibility-based candidate, prepare a small card:
| Question | Example of the detail to record |
|---|---|
| What is being advertised? | Exact product model or software package |
| What must it work with? | Named system, interface, format or component |
| Which version matters? | Model generation or supported software version |
| What else is required? | Adapter, account permission, setup step or accessory |
| What is outside the claim? | Unsupported functions or combinations |
| Where was it confirmed? | Current manufacturer or product documentation |
The card is internal evidence, not a requirement to put every detail into the hint. Its purpose is to prevent an editor from removing a condition that changes whether the statement is true.
If nobody can fill in the supported relationship, keep the candidate out of the approved list. A recurring customer request tells you that compatibility matters. It does not prove the product supplies it.
A connection needs two clear sides
- The advertised item
Identify the exact model or software package.
- The counterpart
Name the system, format or component and relevant version.
- The dependency
Check whether an adapter, permission or preparation is required.
Three drafts that mean different things
Take a fictional reporting tool with a documented CSV import workflow. Compare these candidates:
- “Reporting for teams using spreadsheets” describes a broad situation but says little about the supported transfer.
- “Importing supported CSV exports into a reporting workspace” names a narrower, inspectable task.
- “Live reporting connected to every spreadsheet” adds real-time behaviour and universal support that a CSV import does not establish.
The middle candidate is useful only if the advertised package actually includes that workflow. It still needs a check on file requirements and any preparation the customer must perform. The point is not that technical phrasing is always preferable. It is that the wording should describe the connection that exists.
If the task depends on a named third-party product, verify the reference carefully and keep its role clear. Mentioning it should not imply a partnership, certification or endorsement that you cannot substantiate. You can describe a supported relationship without inventing a commercial one.
Preserve the direction of the connection
Import, export and ongoing synchronisation describe different workflows. The fictional tool’s ability to read a CSV file does not establish that it can write changes back to the original application. Avoid shortening “importing exported files” to “connecting the systems” if the latter implies a two-way connection. Establish which information moves, and in which direction, before selecting a shorter phrase. When that connection is the reason for choosing the software, use the integration-offer planning guide to decide what the campaign can actually invite the buyer to assess.
Verify each combination separately as well. If an accessory works with model A and model A resembles model B, that does not establish support for both. A compatibility hint should rest on the confirmed combination. The model name describes the use case; it does not establish that delivery is restricted to people who already own that model.
Decide which conditions belong in the phrase
Some conditions define the use case and should remain visible. A replacement part for a particular model generation is different from a universal replacement part. Other conditions may belong in the supporting brief because they explain setup rather than the core relationship.
Ask a reviewer to read the proposed hint without the dependency card. Would they infer a broader combination than the evidence supports? If so, restore the missing boundary or choose a different description. Do not rely on a hidden note to correct the ordinary meaning of the phrase.
Check the ad group as well. A hint based on a premium package’s integration should not casually accompany an ad for a different package. The contextual description, advertised offer and verified combination need to line up.
Plan for the next version
Compatibility facts can change when software or hardware changes. Give the evidence card a review owner and a reason to reopen it, such as a product release or an altered support statement. A checked date tells you when the fact was examined; it does not promise that it stays true indefinitely.
When a supported combination is withdrawn, review the associated wording before reusing the campaign brief. When a new combination is added, confirm that it is available in the advertised offer rather than only announced or planned. Keep the old and new facts distinguishable in the working notes.
The final hint should help explain a real, supported customer task without claiming more than the connection provides. For the underlying fact review, use the hint evidence ledger. For the choice between necessary detail and excessive detail, use hint specificity. Those checks address different risks: an accurate connection can still be described unclearly, and a clear sentence can still be wrong.
Sources and scope
Describing a supported compatibility requirement in an ad group's contextual wording.
Working methods and examples are editorial suggestions. Check current platform requirements and available features before implementation.