Piggyback URL configuration

Conversions PiggyBack allows sending a "ping" to an external service every time a conversion event is registered in our systems.
This is useful to signal an affiliate or a partner about the event so that they can take any appropriate action.
To execute this "ping" the system requires an HTTP(S) URL to be used: the system will perform an HTTP GET (a standard action to reach an external URL).

Piggyback conversion parameters:

Along with this URL, you can pass any parameters you want (through a standard query) and you can even use some special keywords that will be replaced with some actual value when the "ping" will be executed.

Keywords for URL:

  • {value} will be replaced with the value of the conversion event
  • {param} will be replaced with the param passed to the conversion event
  • {cost} will be replaced with the cost passed to the conversion event
  • {commission} will be replaced with the commission passed to the conversion event

You can also use custom parameters for datapoints and conversions

Multiple piggyback

For the same conversions, it is possible to create multiple Piggyback URLs (up to 10) in case you need to communicate the conversions to more than one partner. 

How to setup:

Configuring the system is easy,  either in case you've to do it on an existing conversion or in a new conversion.

In case of a new conversion you have a new box in which you can type the URL (for example if the external service is on http://convtracking.mypartner.com/track and we want to track the value for each conversion event) we can type in that box the following:

 

 You can also edit from the "List of Conversions" the piggyback url for the conversion through the fast menu



 This will show a box where you can edit the URL:

 

Conditional piggyback

IMPORTANT: Please note that conditional piggyback is only available for Large and XLarge subscriptions plans.

Each URL specified in Piggyback will be notified when a conversion event is registered, but in some cases, we don't want to send such notification in case some parameter contains a special value or such: in these cases, the conditional piggyback helps.

To define such rules you must click the "Edit rules" button under the notification URL

A popup will show up such as this one:

From this popup you can set some rules: in case those rules are correct, i.e., they're true for the current conversion event then the piggyback URL will be called.

 

How to setup:

Let's suppose we want the Piggyback system to call the URL only if the conversion value is between 5 and 25 then we can put as rule:

 

This will effectively make the system notify only the conversion event with the value contained between 5 and 25. But let's say (for the sake of this example) that we want to restrict the notification to the conversion event that has a value between 5 and 25 and also those in which the conversion parameter 1 is "purchase" and the conversion parameter 2 is " discount".

In order to do so you need to click the button "+ New AND Branch" (2 times) and configure the parameter and operator dropdowns to obtain this:

 

We can also, however, make it work in a case in which the conversion event that has a value between 5 and 25 and also those in which the conversion parameter 1 is "purchase" or the conversion parameter 2 is " discount"

In order to achieve this you need to click the button "+ New OR Branch" (2 times) and configure the parameter and operator dropdowns to obtain this:

You can see in the "Human readable rule" that between the parameters the condition changed to OR so only one of those is the needed to make the notification happens.

Another thing worthy in the "Branch default condition" is by default "All of" that means that all the branches on the same level are evaluated in a way that all of them must be true, but if you select "One of" you just need one of the branches to be true. You can see the difference in the following screenshot:

Have more questions? Submit a request

0 Comments

Article is closed for comments.