Integrate offline and online transactions with RTB House

Published August 20, 2021
Modules
Difficulty
Selected Clients
ccc logo

The RTB House engine, one of its kind powered by deep learning algorithms, identifies potential buyers and boosts performance via 1:1 ultra-personalized retargeting up to 50 percent more efficient than standard machine learning AI-based approaches.

Thanks to the RTB House integration with Synerise, you can enhance your advertising performance by creating segments of people based on behavioral and contextual activities in your integrated online and offline ecosystem. You can choose among various segments in Synerise, for example - customers who are ready to buy or those with the highest propensity to purchase.

The following example shows how to create a simple integration - sending all online and offline transactions to RTB House so that this data can be used in, for example, retargeting activities.

Prerequisites


Obtain the following data from RTB House (you need to contact their support):

  • pkey, which is a static key unique to your RTB house account,
  • hash of the source, needed to put into the tag parameter.

Building the workflow


  1. Go to Automation > Workflows > New workflow.
  2. Add a Profile Event trigger node, where the condition is only that the event is transaction.charge
  3. Add an outgoing integration node:
    1. As the integration type, choose Custom webhook.
    2. As the method, select POST.
    3. As the URL, paste the following string:
      https://omni.creativecdn.com/partner/omni/postbacks?pkey=<PKEY>&uid={{customer['uuid']}}&time={{event.params.time}}&tag=pr_<SOURCE-HASH>_orderstatus2_{{event.params.$totalAmount}}_{{event.params.$orderId}}_{% set tab = [] %}{% for p in event.params.products %}{% do tab.append(p.sku) %}{% endfor %}{{tab|join(',')}}
      Click to see the explanation of the parameters

      • pkey: the unique static key of your RTB House account
      • uid={{customer['uuid']}}:the customer’s identifier; UUID from Synerise database; inserted dynamically by Jinjava
      • time={{event.params.time}}: the timestamp of the event; Synerise uses Unix time; inserted dynamically by Jinjava
      • tag: contains the source hash and variables inserted dynamically by Jinjava: the cost of the transaction, the ID of the transaction in Synerise database, and all items in the transaction

    4. In the URL, replace :
      1. <PKEY> with the pkey you received from RTB House.
      2. <SOURCE-HASH> with the source hash you received from RTB House.
    5. Leave the other integration parameters (headers, body, authorization) at default.

Result:

Outgoing Integration definition
Outgoing Integration definition

  1. Add an end node.

  2. Click Save and Run.

    Overview of the workflow
    The structure of a complete workflow

What’s next


To test the automation: 1. Send a transaction.charge event from a test customer profile. 2. Verify that an automation event is visible in the test profile’s customer card. 3. Verify that the data from the test event was uploaded to RTB House.

Read more


😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker