> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/account-and-settings/portal-link.md).

# Portal Link

The affiliate portal link is where partners log in to track sales, grab their links, and request payouts. A branded portal under your own domain signals an established program worth joining; a generic shared URL can read as an afterthought. By default, every store's portal lives on the shared Bloop portal domain with your store's unique subpath: `portal-domain/your-subpath`. You can replace the shared domain with something like `partners.yourstore.com` so the experience feels native to your business.

This page covers the default portal link and how to request a custom portal domain. For everything inside the portal, see [Affiliate portal branding](/affiliate-program/branding/portal-guide.md).

### The default portal link

Open **Settings → General** and find the **Affiliate portal domain** card. The link shown combines the shared portal domain with your store's unique subpath:

```
https://<portal-domain>/<your-subpath>
```

The subpath is fixed per store and always present, so affiliates can reach your portal even before you set up a custom domain. The card is read-only — you cannot type a new domain directly into it.

> The affiliate portal card only appears on plans that include the affiliate program. On the legacy plan tier it is hidden entirely.

### Use your own portal domain

A custom portal domain gives affiliates a branded login and management experience under your own URL. This is a guided request because it requires a DNS change on your side and activation on ours.

1. On the **Affiliate portal domain** card, select **Customize**.
2. Contact support to get the IP address of the Bloop portal service.
3. Point your domain or subdomain to that IP in your DNS provider.
4. Share the portal URL you picked. Bloop verifies the DNS and activates your branded portal domain.

Once active, the domain is saved as your `custom_portal_url` and affiliates reach the portal at your branded address instead of the shared one. Your subpath still applies underneath it.

> A custom affiliate portal domain is available on higher paid plans. If your plan changes to one without it, the custom domain is removed and the portal falls back to the shared domain.

### What stays the same

| Item               | Behavior                                                     |
| ------------------ | ------------------------------------------------------------ |
| Subpath            | Fixed per store, always part of the link                     |
| Default domain     | Shared Bloop portal domain until you set a custom one        |
| Custom domain      | Optional, request-based, premium plans only                  |
| Affiliate accounts | Unaffected by a domain change — the same logins keep working |

### Related

* [Affiliate portal branding](/affiliate-program/branding/portal-guide.md) — customize the look of the portal pages.
* [Getting started with affiliates](/affiliate-program/getting-started.md) — program overview and onboarding.
* [General settings](/account-and-settings/general.md) — overview of every store-level setting.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bloop.plus/account-and-settings/portal-link.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.