> 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/affiliate-program/branding/portal-guide.md).

# Portal Guide

The portal guide briefs every affiliate on how to get their link, what they earn, and how to promote — without you being in the room. A partner who has this information starts driving sales sooner and asks fewer support questions. Bloop ships a ready-made guide you can edit freely with a rich-text editor. This page covers what's in the default guide, how to edit it, and the dynamic value it supports.

You'll find this under the affiliate **Branding** tab, in the portal guide area. A "Go to portal" action opens the live guide screen so you can see your changes as affiliates will.

> **Best practice:** Treat the guide as activation, not legal fine print. Open with the fastest path to a first sale, state the commission clearly using `{{commission_value}}` so every affiliate sees their own rate, and give two or three concrete promotion ideas they can act on today. For ready-made angles you can adapt into this section, see [how to promote your program](https://bloop.plus/blog/how-to-promote-referral-programs/). Keep terms to a short, linked reminder at the end.

### What the default guide covers

The default guide is structured into four sections:

* **Getting started** — a numbered checklist: sign up, complete the profile, add payment details, get the affiliate link, and start promoting.
* **Commission structure** — how affiliates earn, including a placeholder for your actual rate.
* **Promotion tips** — practical ways to promote, such as honest reviews, social sharing, and product mentions in content.
* **Terms and conditions** — a reminder to review your full program terms.

You can keep this structure, rewrite it, or replace it entirely.

### Editing the guide

The guide uses a rich-text editor — format headings, lists, and paragraphs, and upload images with no HTML required. Write the way you'd brief a new partner: short sections, clear steps, friendly tone.

Changes are tracked as you edit and surfaced through the save bar at the top of the page. Save to publish, or discard to revert to the last saved version.

### The commission value variable

The guide supports one dynamic value: `{{commission_value}}`. When the guide renders in an affiliate's portal, Bloop replaces this placeholder with that affiliate's actual commission rate, read from their assigned campaign.

* For a **basic** (single-rate) commission, it shows that rate — a percentage like `15%`, or a formatted amount for flat commissions.
* For an **advance** (tiered) commission, it shows the rate from the top tier.

Because the value resolves per affiliate at view time, you can write the rate once and every affiliate sees the figure that applies to them. To learn how rates and tiers are configured, see [Affiliate campaigns and commissions](/affiliate-program/campaigns.md).

### Related

* [Affiliate campaigns and commissions](/affiliate-program/campaigns.md) — set the rates that `{{commission_value}}` resolves to.
* [Style your affiliate portal](/affiliate-program/branding/portal-style.md) — colors, logo, and title for the same portal.
* [Portal translations](/affiliate-program/branding/portal-translations.md) — translate the guide screen and the rest of the portal.
* [Getting started with affiliates](/quick-start/getting-started-1.md) — overview and onboarding.


---

# 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/affiliate-program/branding/portal-guide.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.
