> For the complete documentation index, see [llms.txt](https://help.theaffiliateplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.theaffiliateplatform.com/faqs-and-connected-products/faq-affiliation.md).

# FAQ: Affiliation

### How to control language, assigned manager, and automatic approval of affiliates on the registration page.

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 window
* <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. The affiliate is not approved automatically: it waits in **Affiliates → Pending Approval** until someone approves it

See [Registration page](https://help.theaffiliateplatform.com/apis-and-configurations/registration-page.md) for all parameters of the page.

To get the registration link with the right manager ID, open any affiliate of this manager (**Affiliates → Active Affiliates**, then the affiliate) and click the copy icon next to the **Manager** name. It copies the registration page link with `?mgr=` and the ID of this manager.

![The copy icon next to the Manager name in the affiliate details](https://2789002490-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkbip9hFgRFwIv4mXJPnz%2Fuploads%2FvBax7EtwzoHr82Ix7eSB%2Faffiliate-manager-copy-link-918b41c0-e1f1dc.jpg?alt=media)

### How to change UI of the affiliate registration page

You can provide custom CSS, colors, and background of the page in **Configuration → Settings**, on the **Custom JS & CSS (Reg. Screen)** tab. Please check the example below

![The Custom JS & CSS (Reg. Screen) tab in Settings](https://2789002490-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkbip9hFgRFwIv4mXJPnz%2Fuploads%2F6o49gLYVRZgLS2RyRsFj%2Fsettings-custom-js-css-reg-screen-851f6a02-10a841.jpg?alt=media)

```html
<style>
	body {
		background-image: url('https://static.smr.vc/2576047dbc254e7266bfc9-WheelBg, pumpkins.jpg');
		background-color: transparent !important;
		background-size: cover !important;
		color: #fff !important;
	}

	#reg_form {
		padding: 40px !important;
		background-color: #000;
	}

	form label {
		color: #fcd004 !important;
		font-weight: bold !important;
	}

	form input,
	form select,
	form textarea {
		border-color: #fcd004 !important;
		border-width: 2px !important;
		border-radius: 6px !important;
	}

	form>div>div.input-group>input,
	form>div>div.input-group>select,
	form>div>div.input-group>textarea {
		border-color: #fcd004 !important;
		border-top-right-radius: 6px !important;
		border-top-left-radius: 0px !important;
		border-bottom-right-radius: 6px !important;
		border-bottom-left-radius: 6px !important;
		border-width: 2px 2px 2px 0px !important;
	}

	form .input-group .input-group-prepend span {
		background-color: #fcd004 !important;
		border-color: #fcd004 !important;
		border-width: 2px 0px 0px 0px !important;
		border-top-left-radius: 6px !important;
		border-bottom-left-radius: 6px !important;
	}

	form button.btn-primary[type="submit"] {
		color: #fff;
		background-color: #fcd004;
		border-color: #fcd004;
	}
</style>
```

### How to change the set of required fields on the affiliate registration page

You can change a set of required fields on the same **Custom JS & CSS (Reg. Screen)** tab in **Configuration → Settings**. Please check the example below

```html
<script>
$('#web_site_url').attr('required', 'true');
</script>
```

You can also make some fields optional or even hide them

```html
<script>
	$('#skype').attr('required', false);
	$('#company').attr('required', false);
	$('#web_site_url').attr('required', false);
	$('#comments').attr('required', false);
	$('#country').attr('required', false);


	$('#skype_block').css('display', 'none');
	$('#company_block').css('display', 'none');
	$('#web_site_url_block').css('display', 'none');
	$('#comments_block').css('display', 'none');
	$('#country_block').css('display', 'none');
</script>
```

### Is it possible to assign a Parent Affiliate to an already approved affiliate?

**Yes**, it is possible to assign a Parent Affiliate to an already approved affiliate. Open the affiliate, click **Edit** in the affiliate details and set **Parent affiliate**. If the affiliate has already earned commission, two rules apply:

* You can set a parent only if the affiliate has no parent yet and the setting **Allow setting parent affiliate when there was not previous parent** is on (**Configuration → Settings**, **General** tab).
* You cannot change a parent that is already set.

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.

### Why was a player registered via an affiliate link, mapped correctly to the affiliate but not assigned to a deal?

There could be various reasons for this issue:

1. **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 **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 **Deal criteria** (e.g., only players from brand B can enter the affiliate's deal(s)).
   * The same applies to the other deal criteria: **Countries**, **Product**, **Source ID(s)** and the **Active** dates of the deal.
2. **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.

### Does TAP receive a clickid variable in the AFP parameter?

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.
* **Pixels**: TAP keeps all parameters of the visit link with the registration, also a separate clickid parameter. A pixel can send such a value back with a tag of the same name, for example {{clickid}}.

### Why was a player not assigned to an affiliate even though they registered using a link with an afp parameter?

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.

### Why can't an affiliate see their 'invitation link' to refer sub-affiliates?

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. The operator sets it on the affiliate's page: open the **Sub-Affiliate Network** menu and choose **Sub-Affiliate Deal**.
* **Location of Invitation Link**: Affiliates can find their invitation links for expanding their sub-affiliate network in the affiliate portal menu, under **Analytics → Affiliate Network**. Without a sub-affiliate deal, this menu item is hidden.

![The invitation link on the Affiliate Network page of the affiliate portal](https://2789002490-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkbip9hFgRFwIv4mXJPnz%2Fuploads%2F0ECgW69klKbJeqinOJsW%2Faffiliate-network-invitation-link-8db1e42d-b25487.png?alt=media)

The operator can copy the same link in the back office, on the affiliate's **Sub-Affiliate Network** tab (top right). The link has the ID of the parent affiliate (`paff`) and the ID of its manager (`mgr`).

![The invitation link on the Sub-Affiliate Network tab of the affiliate](https://2789002490-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkbip9hFgRFwIv4mXJPnz%2Fuploads%2FUGteWRHpdNIcHbkEjN1u%2Fsub-affiliate-network-invitation-link-20a474a1-210bb8.jpg?alt=media)

### Why don't I see all sub-affiliates related to a parent in the Media Report?

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.

### Why is grouping by registrations/players in the Media Report showing all visits under 'Empty'?

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. Open the player from **Reports → Registrations**.

### Why am I receiving error response 400 when testing pixel firing?

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 **Send 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 give a test value after a colon inside a tag, for example {{afp:test123}}. The **Send test pixel** button sends test123 in place of the tag. A real pixel ignores the test value and sends the player's real value. You can also test pixel firing more effectively by reporting test registrations, FTDs, etc., to TAP so a real pixel will be fired.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.theaffiliateplatform.com/faqs-and-connected-products/faq-affiliation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
