All three are plain links — no callouts from your storefront. Authentication and routing run on menta's side after the click.
Any placement works with any of the three options — pick the URL strategy once; where the links live is your design team's call.
A Buy resale tickets button next to each performance — mocked on the sold-out ones as one possibility; when and where it shows is a placement decision.
View in context →A generic banner at the top of the event view — the same component applies to events with and without a seat map alike.
View in context →For reference: this is how the same components work on platforms whose storefront can call menta's Smart Access Layer. We understand this wouldn't be possible in AudienceView's storefront today — kept here so you have the full picture of where these access points can evolve.
Placement 1 · resale CTA on the event page — one GET per page load resolves every performance CTA on the screen; you render it with your own component, no iframe, no injected script.
Placement 2 · resale banner in the event view — banner copy comes pre-resolved in the response (title, description, CTA text), editable per event or show via wordings, no code changes.
visible: false ⇒ render nothing — in the dynamic version menta decides contextually with live data.
Availability changes in real time — don’t cache the response.
