Priority Levels in Partners Platform

In such parts of the Partners Platform system as Payouts, Revenues, Targeting, Fees we have 4 levels of priority - Custom Level, Offer Level, Affiliate Level and Default (system-wide) Level. In this article we will speak about two most used levels - Offer and Affiliate levels, while briefly touching the other two.

Our PP system operates based on the binary tree structure, and as any tree it has higher-lower priority structure. Every feature listed above is actually a separate tree with possibility to edit certain parts of it from Offer or Affiliate page. In other words, you’re adding rules to the folder in a tree.

Understanding the order may help you to resolve some cases when you thing the wrong value or action has been applied to a lead. For instanse, wrong payout, despite the fact that you have placed the correct one for sure.

The priority structure is (from top to bottom):

1. Custom

2. Affiliate (when you add something inside an affiliate page)

3. Offer (when you add something inside the offer)

4. Default (system-wide)

Affiliate level is acessable through the Affiliate page. When you add payout/revenue or any other rule inside an affiliate page you place it on Affiliate level.

Offer level is acessable through the offer page. When you add payout/revenue or any other rule inside an offer page you place it on Offer level.

When two rules (one placed on the Affiliate level and second placed on the Offer level) could be applied to the same lead, the Affiliate rule will have the priority and will be applied.

When two or more rules are placed on the same priority level (let’s say two payouts inside an Affiliate page) and all of them could affect the same lead - the newest created will be applied.

Let’s say we have a payout of 150$ for Argentina on the Offer level. Then we add a payout of 200$ for Argentina on the specific affiliate. In that case:

• AG traffic from this particular affiliate will recieve a payout of 200$

• AG traffic from all other affiliates will recive a payout of 150$

  • Unless those affiliates has their own payouts for AG setup inside their pages.

We can twist the example a bit, and say: we have a payout of 150$ for Argentina on the Offer level, and a payout of 200$ for AG traffic with Aff_Sub=Best on the specific affiliate. In that case:

• AG traffic from this particular affiliate with Aff_Sub=Best will recieve a payout of 200$

• The rest of the AG traffic from this affiliate will recieve the payout of 150$

• AG traffic from all other affiliates will recive a payout of 150$

  • Unless those affiliates has their own payouts for AG setup inside their pages.

Or enhance it: we have a payout of 150$ for Argentina on the Offer level, a payout of 200$ for AG traffic with Aff_Sub=Best on the specific affiliate, and the payout for general AG traffic of 175$ on that same affiliate. In that case:

• AG traffic from this particular affiliate with Aff_Sub=Best will recieve a payout of 200$

• The rest of the AG traffic from this affiliate will recieve the payout of 175$

• AG traffic from all other affiliates will recive a payout of 150$

  • Unless those affiliates has their own payouts for AG setup inside their pages.

And by the end of the day we accidentely placed a third payout for AG traffic on the same affiliate: we have a payout of 150$ for Argentina on the Offer level, a payout of 200$ for AG traffic with Aff_Sub=Best on the specific affiliate, the payout for general AG traffic of 175$ and new accidently created one for AG of 140$ on that same affiliate. In that case:

• AG traffic from this particular affiliate with Aff_Sub=Best will recieve a payout of 200$

• The rest of the AG traffic from this affiliate will recieve the payout of 140$

• AG traffic from all other affiliates will recive a payout of 150$

  • Unless those affiliates has their own payouts for AG setup inside their pages.

⚠️

Information presented in this section is additional and is not required to make the best use of our system. It is purely for the better understanding of the principals listed above.

A tree structure is an algorithm for placing and locating records, in our case, they’re Settings (Revenues, Payouts, Dashboard, DrillDown, etc.). The algorithm finds data by repeatedly making choices at decision points called nodes. A node can have as few as one branch, or as many as several dozen. The structure is straightforward, but in terms of the number of nodes and branches, a tree can be gigantic.

In a tree, records always exist at endpoints; there is nothing beyond them. The starting point is called the root. The maximum number of branches per node is called the order of the tree. The maximum number of access operations required to reach the desired record is called the depth. In some trees, the order is the same at every node and the depth is the same for every record. This type of structure is said to be balanced. Other trees have varying numbers of children per node, and different records might lie at different depths. In that case, the tree is said to have an unbalanced or asymmetrical structure. Our trees are asymmetrical, although some nodes will have predefined depth.

Both nodes and records can have PQL passing rules, meaning that specific records can be reached only if such rules are passed. For us it allows for placing Payouts on specific Affiliate or Offer, enabling certain metrics for needed roles and so on.

Order in the trees defined by a position - the higher the node/record is, the higher is the priority. Meaning if the algorithm can access two records by passing the rules, it will access the record which is placed higher in the tree, same goes for nodes and branches.

➡️

Key Points:

• Tree consists of Nodes, Branches and Records inside a Root.

• Nodes themselves do not operate anything, actual operators and settings are Records.

• Each Node and Record can have a PQL access rule.

• Order is defined by a position of the Node or Record, higher position = higher priority.

• Folder = Node

• Setting = Record