Advertising.chat documentation¶
Advertising.chat grows and monetizes the conversations brands run with their customers, on RCS first, with SMS and webchat as the fallback channels. Conversation Ads brings more customers into a brand's messaging agent, and Offer Manager makes each of those conversations more valuable with offers that fit the moment. Both products share one decision engine and one measurement layer.
-
Offer Manager
Decide when an offer belongs in a conversation, pick the offer for each customer, and render it natively for RCS, SMS, or webchat.
-
Conversation Ads
Run ads whose click opens a conversation with your agent, measured through the conversations they start and what those produce.
-
Network
Host clearly labeled ads in a chatbot, AI assistant, or web page with AdKit, the web embed, or the Fetch API.
-
Reference
The Fetch API, the Events API, the Offer Manager API, and the glossary.
How the products fit together¶
Conversation Ads works before the conversation. It buys click-to-conversation ads on Google Search and on Advertising.chat placements, and it reports cost per conversation and cost per outcome. Offer Manager works inside the conversation. The brand's agent asks it for an offer at the moments that matter, and it reports how each offer performs.
A brand that runs both reports one number: revenue from its conversations, minus the cost of starting them.
The network is the set of placements in chatbots, AI assistants, and web pages that host ads, and it is one of the sources of traffic for Conversation Ads.
Channels¶
| Channel | How offers and ads appear |
|---|---|
| RCS for Business | Rich cards with an image, a title, and suggested actions, from a verified sender. |
| SMS | Text followed by a tracked link, for devices and carriers without RCS. |
| Webchat | Cards drawn by the webchat from structured data. |
The same offer renders for each channel. See Render formats.
Get access¶
Request access to get an account and sign in to the console.