The mechanism of the caps allows you to count the number of traffic on offers, geo, companies and users. On its basis, you can manage the distribution of traffic to company. Working with caps is carried out in the "Caps" subsection "Management" section and is available to administrators.
Examples of possible cap applications in operation:
- The company "Rog and hooves" gives good commissions, but is able to send only a hundred dick creams per day. If the cap is filled, send orders of dick creams to another company with smaller commissions, but with a large warehouse.
- Affiliate John Doe only began to work with a new offer, you need to check his traffic. We make a small cap on a hundred leads personally under Johny and watch it. As soon as the cap is filled, we say "game over" and check the traffic.
- The "Noble Don" arbitration team should give at least a thousand approves a week to get bonus. We make the cap on this team on all offers and on Sunday simply check, is it filled or not. On this we decide to give the bonus or not.
Adding and configuring caps
To add a new cab, specify its name and click the Add button. You will go to the settings page.
General settings
Influence only on display and search for caps in the list.
- Name is used only for convenience, it can be any.
- Tags allow you to group caps and show statistics by groups. The tag should consist of letters and numbers, can not contain spaces. Indicated without hashtag symbol.
- Show capaticy in the list allows you to observe the number of leads in the specified cap in real time. It is recommended to include only if cap is required by the "live" monitoring by the employee.
Basic settings
The basic cap setup consists of specifying its size and the conditions for counting leads.
- Amount determines the volume of the cap, to which it can be filled. After this quantity the cap will be considered unavailable.
- Status determines the kind of leads taken into account when counting cap quantity. We use the affiliate-visible lead status, which uses offer model.
- Any leads. All leads are counted regardless of their statuses and phases.
- Valid leads only. Leads in the phases "Wait", "Hold", "Approve" and "Cancel" are counted.
- Awaiting leads. Leads in the "Wait" phase are counted.
- Approved leads. Leads in the "Hold" and "Approve" phases are counted.
- Any except cancelled. Leads in the "Cancel" and "Trash" phases are not counted.
- Any except new and deleted. Leads with the statuses New and Deleted are not counted.
- Period determines the time for which leads are counted. Option "Starting from midnight" takes into account the leads for the current calendar day, other options - 24 hours/week/month/year/any time - from the current moment.
Important! The 24 hours/week/month/year periods are not fixed ranges. They use each specific "now" (which changes over time) and look backwards over the specified number of weekday.
The classic approach is to count the number of valid leads since the start of the day. The exact configuration always depends on the specifics of the task.
If necessary, you can set more flexible time settings.
- Time shift allows you to manually shift the time window for which leads are counted. It is measured in hours and can be positive or negative.
- Working hours let you set a schedule for receiving leads. It is specified in the format
from-to@day, where time is hh:mm and day is the ordinal number from 1 (Monday) to 7 (Sunday). For example:10:00-18:00@1-5. Outside working hours, the cap becomes unavailable. - Timezone allows assigning a specific time zone to the schedule, instead of adjusting it manually when the advertiser's time does not match the system time.
- Лиды с и Лиды по позволяют установить фиксированный временной диапазон подсчёта лидов. Рекомендуется использовать в сочетании с периодом «За любое время».
- Time of which action will be used for the range. By default this is the system setting from the "Leads and orders" block in "Control - Settings - Advanced". It can be either "Time lead was received by system" or "Time lead was sent to CRM or taken into processing". You can override this setting at the cap level by choosing the desired counting time different from the system. There are also two additional options:
- Time lead was approved or cancelled. Considers the moment the lead transitions to one of the following statuses: Cancel, Packing, Sending, Delivery, Delivered.
- Time lead was paid or returned. Considers the moment the lead transitions to the status Complete or Return.
Filter settings
You can also set additional lead selection criteria. All selected conditions are taken into account simultaneously. For example, when you specify two users and five offers, the number of leads of each of the users for each of the offers is summed.
- Companies, offers and countries are simply selected from the list. You can specify several pieces at once. The button on the right allows you to enter identifiers and codes separated by commas.
- Users are set by the list of identifiers through the comma. If you need to add a whole arbitration team, its ID is indicated with a minus sign. If you need to calculate leads for specific affiliate on the agency side, put the identifier in the format Agency-Affiliate via a hyphen, for example
12-A3B4C. Important: Use the agency identifier, and not it's system user ID.
Tracking the number of leads
On the caps management page you can see the number of leads, available amount and size of the cap. In order to improve performance, the total number is shown only by those caps that are available on the opened page.
Counting the number of leads in cap is heavy task. Therefore, the number of leads on the cap isn't displayed in real time. It is cached for one minute.
You can count the cap amounts by tags. To do this, click on the tag in the list or specify it in the search field with the lattice sign.
Traffic distribution
You can use cap when distributing traffic in offers. To check the cap, add the cap(123) code to the distribution script, where instead 123 specify the cap ID. The script line will be active only with the available cap.
You can check several caps at the same time. In this case, the script line will be active if all the caps are available.
Distribution script example with caps used:
geo:ru 80% cap(1) cap(4) #3 geo:ru cap(2) cap(4) #4
Important! When removing the cap, all script lines with its participation will be inactive, since the cap is considered unavailable.
Even more important! Unavailable cap does not block traffic! You can not use cap to block traffic, since the loss of traffic is contrary to the fundamental principles of AlterCPA. Just distribute traffic to a separate company in order to catch all the leads.