What this is
RTB House Conversions API (CAPI) is a real-time destination: it sends on-site and conversion events out of Zeotap CDP to RTB House, one event per customer as they pass a Send to Destinations node in a journey. RTB House is a DSP platform that specialises in personalised retargeting, so the events you stream describe what a customer did on your site — viewed a category, viewed a product, changed their cart, completed an order — and RTB House targets against that behaviour. Every event is keyed on the customer’s RTB House Cookie, so cookie syncing between Zeotap CDP and RTB House has to be in place before anything will match. This page covers the real-time, journey-driven integration. To send a whole audience to RTB House instead, see RTB House, the batch destination that attaches to an audience rather than a journey and delivers RTB House Cookies to the S3 bucket RTB House provides.Supported identifiers and actions
Select Stream events to RTB house under Choose your Action when you create the destination.Prerequisites
Address all of the following before you start the integration.- PKey. An advertiser’s public key is a unique string RTB House uses for authentication and authorisation. Obtain it from your RTB House representative.
- API Tagging Hash. This is the static client tagging hash identifier associated with your RTB House account. Obtain it from your RTB House representative.
- Cookie syncing is enabled between Zeotap CDP and RTB House. The integration keys every event on the RTB House Cookie, so without the sync there is no identifier to send. See Cookie Syncing.
- RTB House has enabled server-to-server (S2S) requests on your account. Notify RTB House of your intent to send S2S requests so they can enable the configuration on their end.
- Custom event names are shared with RTB House in advance. If you plan to send custom events, give RTB House the event name (key) first so they can configure it.
RTB House event names and parameters
RTB House identifies each piece of on-site behaviour by an event name of its own. The Event Type list on the destination uses the same vocabulary.Event names
Sending events directly to RTB House
RTB House also accepts server-to-server postbacks sent straight to its own endpoint. This is RTB House’s API, not Zeotap’s: the request goes from your server to RTB House and does not pass through Zeotap CDP. Send it as an HTTPS POST, for example with curl:Create the RTB House CAPI destination
The destination is created under Integrate > Destinations, or inline from a journey’s Send to Destinations panel. Either route opens the same two-step form. For the general model behind destinations, actions and mappings, see Configure a destination.
The Send to Destinations panel, with the + Add New Destination link above the search box and a grid of existing destination cards
- Destination Name — a name that makes the destination easy to identify later.
- PKey — the PKey obtained from your RTB House representative.
- API Tagging Hash — the tagging hash associated with your RTB House account.

The Enter Destination Details step of the RTB House CAPI destination, with the Destination Name, PKey and API Tagging Hash fields

The Mapping step, with Stream events to RTB house chosen as the action and the Map the Fields table grouped by event
Add the destination to a journey
A real-time destination does not attach to an audience. Once it exists, you link it in a Send to Destinations node inside the journey workflow.
The Choose an action menu on the journey canvas with Send to Destinations selected

The destination picker with the search box highlighted above the grid of available destinations

The Destination Details tab of the RTB House CAPI node, with the Event Type list open

The attached RTB House CAPI destination card showing its Stream events to RTB house mapping, above the destination picker
Verify the delivery
Once the journey is live, confirm the events are leaving Zeotap and landing at RTB House:- On the journey canvas — open the execution details for the Send to Destinations node. A node that has run reports the total events entered, the successful events and the failed events. See Identify Journey Errors.
- For one customer — use Journey Traces to follow a single record through the node and inspect the input and output event data.
- With RTB House — confirm with your RTB House representative that events are arriving against your PKey. Zeotap reports what it sent; only RTB House can confirm what it accepted.
Troubleshoot delivery failures
When a journey execution fails at this node, a failure status code is recorded against the node. Journey Error Codes is the full reference; these are the ones most likely to appear on a conversions-API destination.- No RTB House Cookie on the profile. Every event is keyed on this identifier, so a customer without a synced cookie has nothing to send. Confirm cookie syncing is in place — see Cookie Syncing.
- A custom event RTB House has not configured. RTB House has to set up the event name (key) before you send it. If a custom event was never shared with them, confirm with your RTB House representative that it has been configured.
- S2S not enabled on the account. RTB House has to enable server-to-server requests for your account before it accepts them.
FAQ
What is the difference between the RTB House and RTB House CAPI destinations?
What is the difference between the RTB House and RTB House CAPI destinations?
Which destination fields do I have to map?
Which destination fields do I have to map?