Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Drawio
zoom1
simple0
inComment0
pageId2747072699
custContentId2748973179
lbox1
diagramDisplayNameUntitled Diagram.drawio
contentVer8
revision8
baseUrlhttps://ingenioustechnologies.atlassian.net/wiki
diagramNameUntitled Diagram.drawio
pCenter0
width851
links
tbstyle
height431

Scenario & Goals

  • You own an Ingenious Platform (B) and want to use the advertiser-pool of another Ingenious Platform (A) to provide them to your partners.

  • Your goal is that Conversions, that are tracked within the other Ingenious platform (Platform A) should be automatically be transferred to /tracked in an advertiser in your own Ingenious platform (Platform B).

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.

...

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:

...

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:

  • The creatives should contain the Ingenious tracking link as target URL, that you can get from your (publisher) Ingenious account. We recommend to create at least one text link.

  • Other option: You may export the creatives via your publisher account on platform A (export creatives) and import them again in you advertiser on Platform B.

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.

...

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:

...

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:

  • Validation/Changes to conversions in Platform A are not automatically reflected/synchronized back to Platform B. This is a task that you have to do manually.

  • If you have additional Creatives (i.e. Banners) for campaigns, you have to create them in both platforms A and B.

  • Basket tracking is possible, however it may be difficult using a global webhook. We recommend to use individual webhooks for all cases, where basket-tracking is involved.

  • Tracking of vouchers is also possible, it may also be difficult using a global webhook. We recommend individual webhooks for cases where voucher tracking is needed.

  • The integration via webhooks is just like a normal integration of a conversion tracking tag with all known advantages and limitations of such an approach.
    There can be reasons, why a webhook is not executed (e.g. deactivated relation, recommendation: check the logs regularly) and reasons why conversions are not properly tracked (e.g. unknown conversion target transmitted). So we recommend to have an eye on the integration, just like you would with any advertiser conversion tracking integration.