Before creating In-Browser Message campaigns, confirm the following are in place. These are one-time configuration tasks shared across the Treasure AI platform team.
- RT Personalization 2.0 is enabled for your account. Contact your Customer Success Manager if unsure.
- HTTPS is required — the target website must be served over HTTPS. RT Personalization 2.0 does not operate over HTTP.
- ID stitching is configured so user identities are resolved across events (for example,
td_client_idlinked to your internal user ID).
- A Parent Segment exists with the relevant customer data and RT attributes.
- A Real-Time Personalization and at least one section are created in Audience Studio using the relevant parent segment.
- The TD Web SDK is installed and initialized on the target website. See SDK Integration for the full implementation guide.
- Business events are flowing into Treasure AI (
view_item,add_to_cart, etc.). See Event Tracking for event definitions and naming conventions. - (Recommended) Server-Side Cookie (SSC) infrastructure is deployed on your domain. SSC issues
td_ssc_idfrom your own server, avoiding browser ITP restrictions that cap JavaScript-set cookies to 7 days on Safari/iOS. Requires a small server endpoint on your domain (e.g.,ssc.yourdomain.com). Contact your Customer Success Manager for the SSC setup guide.
When the RT Personalization API returns a campaign payload, the SDK renders the message automatically:
| Message Type | SDK Rendering Behavior |
|---|---|
| Popup | Injects a popup container overlay on top of the page. The popup is positioned according to the placement setting configured in the campaign. Only the popup with the latest created_at timestamp is displayed when multiple popups are returned. |
| Inline | Replaces the innerHTML of the DOM element matched by the campaign's CSS selector (Zone ID). All returned inline messages are rendered. If the selector does not match any element, the message is silently skipped. |