Native rendering is the practice of presenting a commercial offer inside an AI product using the product's existing interaction and visual language.
In AON, the AI product receives structured offer data and chooses whether to render it as inline text, a card, a banner, a comparison module, or another appropriate surface. Native rendering does not remove disclosure, attribution, merchant responsibility, or the user's control over the next action.
Native rendering with AON
AON gives AI products structured Offers that can fit naturally into their own interface. This is the product-side expression of AON's offer-discovery layer: the AI product retains the user experience while AON preserves the supported handoff and attribution context.
Review AON presentation surfacesHow native rendering works
Receive structured data
The AI product receives an Offer with the fields needed to understand the option, merchant, action, Goal, and available presentation context.
Decide whether it helps
The product evaluates relevance and user value rather than showing every returned offer or treating payment as proof of quality.
Choose the surface
The product selects an inline recommendation, merchant card, banner, comparison module, or another native component that fits the task.
Preserve trust and attribution
The product labels the commercial relationship appropriately and preserves the returned action or tracked destination for the user handoff.
Implement Native rendering safely
Keep
- The Offer's title, merchant meaning, supported action, required disclosure, and tracked destination.
- AI-product control over the surface and the decision to show an offer only when it helps the current task.
- A clear distinction between a native presentation and merchant-controlled checkout.
Do not
- Rewriting the action, merchant meaning, or commercial disclosure to fit a component.
- Using a native surface to imply that a paid offer is universally best or guaranteed by AON.
- Calling an iframe or generic ad widget native rendering without preserving the required offer semantics.
Native rendering surfaces
A native surface should match the user's task while keeping the offer understandable, clearly disclosed, and actionable.
| Concept | Meaning |
|---|---|
| Inline text | A lightweight recommendation can appear inside an answer when the offer adds useful context without interrupting the conversation. |
| Merchant card | A card can group the offer title, merchant, price or terms, and the next action for comparison or decision support. |
| Actionable banner | A banner can provide one clear next step at a high-intent moment, such as continuing to a booking or product page. |
| Custom surface | A product can use its own comparison, carousel, or workflow UI as long as it preserves the payload meaning and handoff requirements. |
- Native rendering is not disguised advertising; commercial relationships and material disclosures still need to be clear for the product and market.
- A native component must not rewrite the action URL, invent missing terms, or imply that AON or the AI product guarantees merchant fulfillment.
- The product may change the UI, but it must preserve the Offer's title, merchant meaning, action, and required disclosure.
- Presentation control belongs to the AI product, but relevance, disclosure, and attribution remain part of a trustworthy implementation.
Example in practice
A finance assistant answers a question about business cards and renders one eligible merchant offer as a clearly labeled card using the assistant's own design system. The card explains why it is relevant and uses the returned tracked action; it does not imply that AON approved the user's application or that the assistant controls the issuer's terms.
Common questions about native rendering
Does native rendering mean the offer is not an advertisement?
No. Native rendering describes how an offer is presented, not whether a commercial relationship exists. An AI product should make material commercial relationships clear and follow the disclosure requirements that apply to its surface and market.
Who controls the design of a native offer?
The AI product controls the presentation surface. It must still preserve the meaning of the returned payload, the supported action, and required disclosure information.
What must an AI product preserve when rendering an AON Offer natively?
An AI product must preserve the Offer's merchant meaning, supported action, attribution context, and required disclosure when it renders an AON Offer natively. The product can adapt the layout to its own interface, but it must not rewrite merchant terms or imply that AON guarantees the Offer.
Does native rendering replace merchant checkout?
No. Native rendering happens in the AI product. The merchant or downstream provider remains responsible for current terms, checkout, payment, order acceptance, and fulfillment.
Sources
- AON Best PracticesAON documentation
- AON Offer Query APIAON documentation
- AON Core ConceptsAON documentation
- FTC Native Advertising GuideIndustry source