▪️FAQ: Affiliation
Last updated
Last updated
Your registration page is usually located on a site like https://aff.mysite.com.
This site can change UI and the process of registration using the following parameters in the URL
https://aff.theaffiliateplatform.com/?lang=uk - will open the registration page in the specified language
https://aff.theaffiliateplatform.com/?tc=true - will open the T&C page
https://aff.theaffiliateplatform.com/?paff=123 - newly registered affiliate will be assigned as a child to affiliate with ID 123
https://aff.theaffiliateplatform.com/?mgr=123 - newly registered affiliate will be assigned to the manager with ID 123. Note that such affiliates will be automatically approved and assigned to the manager
You can find your manager ID in the user area on the left side of the screen
Every affiliate can use a referral link to bring "friends" to the affiliate network.
Affiliates registered by such link will be set as sub-affiliates to the main one.
Based on the deal setup for sub-affiliates, the main affiliate can earn extra commission based on the traffic brought by sub-affiliates.
The referral link is available in the "Account details" of the affiliate account.
Affiliates registered by this link will be also assigned to the same manager as the main affiliate.
You can provide custom CSS, colors, and background of the page in the Settings \ Custom CSS & JS sections. Please check the example below
You can change a set of required fields in the Settings \ Custom CSS & JS section. Please check the example below
You can also make some fields optional or even hide them
Yes, it is possible to assign a Parent Affiliate to an already approved affiliate, regardless of whether they have generated commission yet. The sub-affiliate commission for the parent affiliate will start to be generated from that point onward, considering new financial activities of both old and new players of the sub-affiliate.
There could be various reasons for this issue:
Mismatch between Player and Deal Configuration:
Example: The player registered via a link for campaign X, but the affiliate's deal(s) do not include campaign X in the additional deal criteria (e.g., only players from campaigns Y and Z can enter the affiliate's deal(s)).
Example: The player registered for brand A, but the affiliate's deal(s) have brand B in the additional deal criteria (e.g., only players from brand B can enter the affiliate's deal(s)).
Player’s Registration Date Predates Deal Creation Date:
The player's registration date might be before the deal creation date, causing the player not to be assigned to the deal.
Yes, TAP can receive a clickid variable in the AFP parameter.
Clickid Value: The clickid is a value sent by the affiliate and can be included in any parameter, including {{afp}}.
Data Storage: Clickid values are not stored in BI (Business Intelligence). However, AFPs are stored in BI and can be used to segment meaningful data.
In this case, the player is not assigned to the correct affiliate because afp values are not registration facts but visit facts.
Afp Values: Afp values are associated with visits, not registrations. Therefore, the presence of an afp parameter in the registration link does not ensure the player will be correctly assigned to the affiliate based on that parameter.
An affiliate will only see their invitation link if they have a sub-affiliate deal configured by the operator.
Sub-Affiliate Deal Configuration: The invitation link is exposed to an affiliate only if there is a sub-affiliate deal configured by the operator.
Location of Invitation Link: Affiliates can find their invitation links for expanding their sub-affiliate network in their profile under "Affiliate Network".
Grouping by the 'Child Affiliate' dimension in the Media Report will show only the sub-affiliates who have generated commission for the parent affiliate.
Commission-Based Visibility: Sub-affiliates who have not yet contributed to the parent affiliate’s commission will not be shown when the report is built this way.
All clicks are shown under “Empty” when grouping by player (registration ID, external ID, username) because, at the time of recording the visit, there is no registration/player ID yet.
Timing of Data Recording: The visit is recorded before a registration/player ID is assigned, so these visits are initially grouped under "Empty."
Visit Information: The visit information is exposed in the player’s profile, including the visit date.
When testing the pixels firing, a 400 error response can occur due to the following reasons:
Dynamic Parameters: Pixel configuration usually includes dynamic parameters, such as {{afp}}. When testing with the Test Pixel button, the server expects these parameters to be populated.
Missing Values: If no values are populated for these dynamic parameters during testing, it is possible to receive the error response 400.
Solution: You can test pixel firing more effectively by reporting test registrations, FTDs, etc., to us so a real pixel will be fired.
