RTB House

Datafly Signal delivers conversion events to RTB House server-to-server for deep learning-powered retargeting, campaign attribution, and personalised ad delivery optimisation.

Why route RTB House through Datafly Signal

Events survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server to the RTB House Conversions API, so the events RTB House optimises against are not filtered by the browser.
A stable first-party visitor ID. Every postback carries the Signal anonymous ID as RTB House’s aid, the same identifier across page views, product views and orders.
One consent decision governs every destination. RTB House is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Set Up an RTB House Account

Contact RTB House to set up an advertiser account, or reach out to your existing RTB House account manager.
Ask your account manager to enable server-to-server postbacks (the Conversions API) for the account. Postbacks are rejected until they do.

Get Your Credentials

Ask your RTB House account manager for:

The Partner Key (pkey), the advertiser public key that authenticates postbacks.
The Tagging Hash, the static client identifier every event tag is built from (pr_<tagging hash>_<event>).
The Region your account is served from: ams (Europe), us or asia.

Configure in Signal

Configuration Fields

Field	Required	Description
`partner_key`	Yes	The advertiser public key (`pkey`) for server-to-server postbacks.
`tagging_hash`	Yes	The static client identifier used in every event tag.
`region`	Yes	`ams`, `us` or `asia`. Selects `https://{region}.creativecdn.com`.

Management UI Setup

Go to Integrations > Add Integration > RTB House.
Choose the Default or Ecommerce preset.
Enter the Partner Key, Tagging Hash and Region.
Select consent categories (typically advertising) and click Save.

Request format

Each event is one postback with every value in the query string and no body:

POST https://ams.creativecdn.com/partner/omni/postbacks
  ?pkey=<partner key>&aid=<Signal anonymous ID>&time=<epoch milliseconds>
  &su=<page URL>&sr=<referrer>
  &tag=pr_<tagging hash>_conversion_order_439.99_T-1001_SKU_1,SKU_2

pkey, a user identifier (aid) and time are required on every postback.

Event Mapping

Signal event	RTB House tag	Preset
`page`	`pr_<hash>` (generic page view)	Default, Ecommerce
`view_item`	`pr_<hash>_offer_<product ID>`	Default, Ecommerce
`add_to_cart`	`pr_<hash>_basketadd_<product ID>`	Default, Ecommerce
`purchase`	`pr_<hash>_conversion_order_<value>_<order ID>_<product IDs>`	Default, Ecommerce
`view_item_list`, `view_search_results`	`pr_<hash>_listing_<product IDs>`	Ecommerce
`view_cart`	`pr_<hash>_basketstatus_<product IDs>`	Ecommerce
`begin_checkout`	`pr_<hash>_startorder`	Ecommerce

Product IDs come from items[].item_id and must match the IDs in your RTB House product feed. Underscores in an order ID are sent as hyphens, because _ separates the parts of a tag.

Signal forwards properties the preset does not map unless the integration’s strict output contract is on. For RTB House those would become extra query parameters, so turn on strict_output_contract for this integration.

Testing Your Integration

Step 1: Send a Test Event

Trigger a product view or purchase event on your website.
Check the Signal event debugger in the Management UI to confirm the event was captured and delivered.

Step 2: Verify with Your Account Manager

Contact your RTB House account manager to confirm events are being received.
RTB House does not provide a self-service event viewer; your account manager can verify delivery on their side.

Step 3: Validate Retargeting

After events are flowing, your RTB House account manager will confirm that retargeting campaigns can use the event data.
Review campaign performance reports provided by your account manager.

Troubleshooting

Problem	Solution
Events not being received by RTB House	Confirm server-to-server postbacks are enabled for the account, and that the Partner Key, Tagging Hash and Region are correct.
Connection errors	The region must be exactly `ams`, `us` or `asia`.
Product events not mapping correctly	Ensure product identifiers in your Datafly events match those in your RTB House product feed.
Events delayed or missing	Check Signal’s delivery status. If delivery is confirmed, contact your RTB House account manager, as the issue may be on their side.

Visit RTB House for more information. For API documentation and integration support, contact your RTB House account manager directly.

Ringier Axel Springer Polska (Onet Ads)Snapchat Ads (deprecated)