v.1.1.40
14.11.2024
Features
Added an option to set the rejected leads capacity as a percentage of pushed leads capacity
This change eliminates the need for manual rejection capacity management, making the process more efficient.
To enable this functionality, set “Yes“ for the “As % of pushed lead cap“ field in the capacity management window. Then, set the percentage of rejected leads limit for “Rejected Lead Capacity“.
The example above says that the rejected lead capacity is defined as a percentage value of pushed lead capacity (i.e., 20% out of 1000 equals 200). Thus, for the current settings, rejected lead capacity equals 200.
Common
Added an option to copy the affiliates’ API token along with its extra data
Now, you can copy all needed data quickly with a single click.
You can find it via Settings Navigation → API Tokens → Affiliates.
In the “Extra Info“ column you can either copy or preview the following data to copy:
CRM domain
API token
UUIDs of all goal types available
If the column is not displayed, make sure to enable it here:
Note: This functionality is only available if the Unsecured mode is switched on.
Enabled the “Fill First” field for the Comparing folder
The Comparing folder has become more flexible, as you can now prioritize traffic distribution for its subelement.
Note: Only one subelement within a Comparing folder can be prioritized for first-filling.
Added an option to include/exclude specific filters when customizing tables
This makes it easier to precisely configure the data shown in traffic and conversion tables.
Implemented an option to manage pulling for advertisers’ API Overwriting settings
Now, you can easily disable pulling for specific API Settings Overwriting items of an advertiser that don’t need individual updates.
You can manage the pulling activity via a certain advertiser’s page → Integration Settings → API Settings Overwriting section.
Here, when creating or editing an overwriting item, you can define whether it needs to be pulled individually or not via the “Pulling Enabled“ field.
Improved postback error messages
The error messages are now more comprehensive and easier to understand.
Note: The clarity and length of the error message depend on what is provided by the affiliate's tracking system (i.e., the message will appear as received from the tracking system).
Bugs
Fixed an issue when injector tasks could stop after deployment of the Injector service
Now, tasks continue to run smoothly after the deployment process.