Scenario & Goals

1. Create a Partner in Platform A

In Platform A, you create a Partner A which represents the Platform B in Platform A. This you only have to do once, as tracking for all shared Advertisers will be passed through this Partner Account via Webhooks.

2. Create an Advertiser in Platform B

For each advertiser of Platform A you want to share with Platform B, you create an advertiser in Platform B.

Considering the diagram above, Advertiser XY of Platform A should be shared with Platform B. In Platform B you create a surrogate of the Advertiser XY. It should basically have the same settings as the original Advertiser.

Here are the recommended settings for the surrogate Advertiser XY in Platform B:

2.a. Additional Parameters for Click Redirect


It should have the following additional parameters configured:

smc1=#{PARTNER_ID}

smc2=#{ICLID}

smc3=#{EXTERNAL_ADVERTISER_ID}

which makes sure, that essential parameters (smc2 and smc3) needed for tracking later on will be added to each creative. With smc1 you optionally may also transmit the partner ID of Platform B, so in the report of platform A there is a bit of transparency which partners bring conversions.

2.b. Creatives

When setting up the creatives:

2.c. Conversion Target

We recommend setting up the same conversion targets for Advertiser XY in Platform A and Platform B.

2.d. Tracking Categories

We recommend setting up the same tracking categories for Advertiser XY in Platform A and Platform B.

3. Fire conversion in Platform A

In Platform A, the Advertiser XY operates normally. When a conversion happens, and the Partner A representing Plaform B) is attributed to be the winner of the conversion, we want the conversion to be forwarded to Platform B.

3.a. Implement the Ingenious Click Tag in Webhooks

In Platform A, you create an Ingenious webhook for Partner A (Read more here: webhooks). The webhook has to be configured to be server-side. The target of the webhook is the conversion tag of Platform B.

This is a template you can use:

https://marketing.ingenious.cloud/ts/#{FREE_PARAM_smc3}/tsa?typ=s&tst=#{TIME_STAMP}&trc=#{TRACKING_CATEGORY}&ctg=#{CONVERSION_TARGET}&sid=Sale-#{ADVERTISER_MID}&cid=#{CONVERSION_ID}&orv=#{BOOKING_AMOUNT}&orc=#{BOOKING_CURRENCY}&cli=#{FREE_PARAM_smc2}&uniqid=#{TRACKING_UUID}

You have to replace the tracking domain marketing.ingenious.cloud by the tracking domain of Advertiser XY of Platform B.

Please note, that the configuration of the webhook target above requires the same conversion targets and tracking categories in both systems.

Log into your publisher account of Platform A and set up the webhook. It may be used for all future surrogate advertisers as a global webhook. It should be used for all conversion targets, all tracking categories and should be executed server side.

3.b. transmitting the commission from Ingenious platform A

You can transmit the calculated commission from Platform A to the Platform B via another parameter in the webhook target:

commissionfix=!!!commission!!!

The webhook target then looks like this:

https://marketing.ingenious.cloud/ts/#{FREE_PARAM_smc3}/tsa?typ=s&tst=#{TIME_STAMP}&trc=#{TRACKING_CATEGORY}&ctg=#{CONVERSION_TARGET}&sid=Sale-#{ADVERTISER_MID}&cid=#{CONVERSION_ID}&orv=#{BOOKING_AMOUNT}&orc=#{BOOKING_CURRENCY}&cli=#{FREE_PARAM_smc2}&uniqid=#{TRACKING_UUID}&commissionfix=!!!commission!!!

Remember that you have to replace the tracking domain marketing.ingenious.cloud by the tracking domain of Advertiser XY of Platform B.

Here are more details on how to create a API key in the Ingenious System.

4. Limitations

In the setup described above there are some limitations you should know: