What is RTB House?

RTB House is a global advertising technology company that provides AI-driven solutions for personalized retargeting and marketing campaigns. Its platform uses deep learning algorithms to analyze user behavior and deliver customized ads across various devices and channels. RTB House works with e-commerce brands and digital marketers to improve audience targeting, optimize performance, and increase conversions. The company's infrastructure supports data localization with regional data center options to comply with privacy and data protection requirements.

Product Type: Advertising

Integration Type: ID Sync

Capabilities

Sends MetaRouter’s ajsid to RTB House via a POST request for identity synchronization.
Enables personalized retargeting by syncing users to RTB House’s platform.
Supports regional data routing through configurable data center endpoints.
Tracks sync status with a locally stored value used to determine re-sync timing.
When using Fetch Sync, supports optional cookie matching. RTB House may return a list of partner sync URLs (IMG or IFRAME) used to link user identities across advertising vendors. MetaRouter filters these URLs using the customer-defined Allowed Cookie Matching Endpoints array, firing only the partner URLs that the customer has approved and user has consented for.
When using Tag Sync, loads the RTB House tag directly on the page for client-side identity synchronization.

Considerations

Data center selection is required and should align with the user’s geographic region (AMS, US, or Asia).
Re-syncs are triggered when the stored identifier expires or becomes unavailable.
Cookie matching is available only when using Fetch Sync and requires enabling the Allow Cookie Matching setting and defining valid matching endpoints.

Sync Details

IDs:
- ajsid – A unique MetaRouter session identifier used to match users with RTB House’s system.
Description:
- The sync sends the MetaRouter ajsid to RTB House using a POST request to a region-specific endpoint.
- The data center (e.g., us, ams, asia) and client tagging hash are required for routing and identity mapping.
- When cookie matching is enabled, the response includes an array of sync URLs (IMG or IFRAME) that are embedded in the page for user syncing.
- A sync "fired" marker is stored in first-party storage with a defined lifetime (e.g., 30 days).
- Values are refreshed when expired or when no valid ID is present.
- Sync results are appended to the server-side event payload for retargeting and audience matching.
Server-side Event Payload:
Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload.
```
{
  "rtbHouse": {
    "fired": "human-readable date when sync was fired"
  }
}
```
Cookie Name:
- Cookie: _meta_rtbHouse_fired
- IndexedDB: [your storage prefix]_rtbHouse_fired
- For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Gather Credentials

To configure the RTB House sync, you will need the following details from your RTB House account manager or implementation team:

Tagging Hash – A unique identifier assigned to your RTB House account.
Data Center – Region where your data should be routed (us, ams, or asia).

2. Add a RTB House Sync in MetaRouter

To trigger the RTB House identity match using the MetaRouter ajsid, you must add a RTB House sync.

From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
In the Identity Syncs section, select the RTB House sync.
Fill out the following fields:
1. Data Center – Use a string: "us", "ams", or "asia" based on your target region.
2. Tagging Hash – Paste your RTB House tagging hash as a quoted string (e.g., "Xu0m620aed1PAR1VZ7Pf").
3. Lifetime (in days) – Enter a numeric value indicating how long the sync should be retained (e.g., 30).
4. Sync Type:
  1. Tag Sync - Loads the RTB House tag directly on the page.
  2. Fetch Sync - Uses server-side, fetch-based synchronization to send identifiers to RTB House. If Fetch Sync is selected, cookie-matching settings must also be configured:
    1. Allow Cookie Matching – Boolean value (true or false). When enabled, the RTB House fetch response will be inspected for cookie-matching URLs. Only URLs that appear in the Allowed Cookie Matching Endpoints array (and satisfy user consent) will be embedded on the page.
    2. Allowed Cookie Matching Endpoints – (Required if cookie matching is enabled) A JSON array of endpoint objects. Each object must contain an endpoint URL and a consentCategory string. Example:
      1. [ {"endpoint": "https://ams.creativecdn.com/topics-membership", "consentCategory": "C0004"}, {"endpoint": "https://sync-service.net/user-sync", "consentCategory": "C0004"} ]
Scroll down and click the Save and Build File button.
Deploy your AJS file to propagate changes to your web property.