Thrad gives Gomry another distribution route through sponsored placements in AI products. Publishers can present a relevant event offer while a user is planning a trip or deciding what to do, then direct them to Gomry to explore ticket options.
For an AI publisher, this connects conversational advertising with real-world events. For businesses whose events are included in the available inventory, it offers a way to reach people during that planning process. The placement opens a route to purchase; it does not itself reserve or buy a ticket.
An event offer in the right conversation
Consider a user planning a weekend in Miami with two friends. They want live music, preferably outdoors, and have a budget of $120 each. That context can make an event placement more relevant than an advertisement unrelated to the trip.
Thrad evaluates eligible advertising against the conversational context and the publisher's configuration. The publisher presents the selected creative and identifies it as sponsored. The user can follow the placement to Gomry and explore the event's current ticket options.
Whether a placement appears depends on the advertising available, relevance and the publisher's implementation. Including an event in the catalog does not mean it will appear in every conversation.
The publisher's role
Publishers integrate Thrad's advertising API or SDK into their product and choose where placements belong in the experience. Thrad returns advertising creative for the publisher to render, rather than taking over the conversation's interface.
The publisher is responsible for displaying the placement and sponsorship disclosure and reporting the relevant impressions. A click follows the supplied destination into the advertiser's experience. This gives the product team a clear boundary: Thrad handles advertising selection, while the publisher controls how the user encounters it.
From a placement to Gomry ticket options
Gomry supplies the event catalog and ticket information on the purchase side. When a customer explores a listing, the application or Gomry page retrieves current ticket choices and prices. The checkout result, not the advertisement, determines the order's status.
An application that also wants to search events or handle ticket purchases can integrate Gomry's catalog and checkout interfaces separately. Depending on the supported purchase route, the customer completes checkout through the application or follows a Gomry checkout link. Thrad's placement API is not that checkout integration.
| Part of the journey | Who handles it |
|---|---|
| Selecting eligible sponsored creative | Thrad, using the request context and publisher configuration |
| Presenting the placement and disclosure | The AI publisher |
| Providing event details and ticket options | Gomry |
| Continuing to purchase | The supported application integration or Gomry checkout |
Publishers can start with Thrad's integration documentation. For a product that also offers event search and ticket purchases, Gomry's developer documentation covers those separate capabilities.