> 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-style.md). # Portal Style The portal is where affiliates grab their link, watch sales come in, and request payouts. A portal carrying your logo and brand color reads as a real partnership; a generic, unbranded dashboard reads as a third-party tool that partners give less attention. Bloop gives you four settings to make the dashboard feel native — primary color, portal title, logo, and favicon — under the affiliate **Branding** tab. Use "Go to portal" to preview changes in a live tab. > **Best practice:** Match the portal to assets affiliates already see elsewhere — the logo from your storefront, your real brand color, and a portal title that names your program. Consistency between your store, your [registration form](/affiliate-program/branding/registration.md), and the portal signals an established brand. Preview with "Go to portal" before saving to confirm the accent color leaves text readable. ### Why branding the portal builds trust * **Legitimacy.** Your logo and color signal that your program is serious. A bare, default-skinned dashboard suggests it was switched on as an afterthought — and partners ration their effort accordingly. * **Recognition.** Affiliates often work with several programs at once. When your portal looks like your store, partners know instantly which dashboard is yours. * **Continuity.** A prospect moves from your storefront, through your branded [registration form](/affiliate-program/branding/registration.md), into the portal. If all three match, the journey feels seamless. A portal that suddenly looks like a different product introduces doubt at the moment a partner is committing. ### What you can customize | Setting | What it controls | | ------------- | -------------------------------------------------------------------------- | | Primary color | The portal's accent color, applied to buttons, links, and highlights | | Portal title | The name shown for the portal (for example, in the browser tab and header) | | Logo | The brand logo displayed in the portal | | Favicon | The small icon shown in the browser tab | #### What to match to your storefront Pull each setting from assets you already use publicly — the goal is continuity, not a fresh design. | Element | What to set it to | Recommendation | | ------------- | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Primary color | Your store's main brand accent — the same hex you use for buttons and links | Confirm in the preview that text on top of it still reads clearly; a too-light accent on white can make buttons hard to see | | Portal title | Your brand or program name (for example, "Acme Partner Program"), not the app name | Name the *program* so the browser tab says something a partner recognizes — never leave it as a generic default | | Logo | The same logo file from your storefront header | Upload a clean image with a transparent background; avoid a logo with a baked-in white box | | Favicon | The same favicon your store uses | Upload a square image so the portal tab carries your mark even when a partner has many tabs open | #### Primary color Set a **primary color** and the portal applies it throughout — buttons, active states, and links. Use your brand's main color. Because the same color drives buttons and links, check contrast in the preview: an accent that looks great as a large block can leave small link text hard to read. #### Portal title The **portal title** is the label affiliates see for your program. Set it to your brand or program name. If left blank, the portal falls back to its default title — always name it. #### Logo Upload your brand **logo** to replace the default placeholder. It appears in the portal header. Use a transparent-background image. You can remove the logo at any time to revert to the default. #### Favicon The **favicon** is the small icon browsers show in the tab and bookmarks. Upload a square image so the portal tab carries your brand even when affiliates have several tabs open. ### A worked example: matching the portal to your store A storefront using deep teal (`#0F766E`) buttons, a transparent-PNG wordmark, and a leaf favicon needs a five-minute pass: set the primary color to `#0F766E`, the portal title to "Acme Partner Program," upload the same logo and favicon, then click "Go to portal" to confirm white button text reads cleanly on teal before saving. Zero new design work — every asset came from the storefront. ### Saving and previewing Changes are tracked as you edit and surfaced through the save bar at the top of the page. Save to publish, or discard to roll back to the last saved version. Use "Go to portal" to confirm colors, title, logo, and favicon look right before finishing. ### Common mistakes to avoid * **Leaving the title blank.** The portal shows a generic default where a partner most expects to see your name. Always set it to your brand or program name. * **Ignoring contrast.** A pale or very bright accent can make button and link text hard to read. Check the preview before saving. * **Saving without previewing.** "Go to portal" shows the live result; relying on the editor alone is how a low-contrast color or misaligned logo slips through. ### When and why to revisit portal branding * **You rebrand or refresh your store theme** → update the portal's primary color, logo, and favicon to match, or the portal will drift out of sync with your storefront. * **You launch a named program** ("Acme Insiders," "Creator Club") → set the portal title to that program name so the dashboard reinforces the brand affiliates joined. * **Partners aren't engaging with the portal** → a generic, unbranded dashboard is one quiet reason. Branding it is a low-cost first step before assuming the problem is your commission or content. * **You're recruiting higher-profile partners** → a fully branded portal signals the professionalism those partners expect; see [recruiting affiliates](/best-practices/recruiting-affiliates.md) for the wider picture. ### Related * [Build your affiliate registration form](/affiliate-program/branding/registration.md) — brand the signup page that comes before the portal. * [Portal translations](/affiliate-program/branding/portal-translations.md) — translate the portal UI into your affiliates' languages. * [Portal guide](/affiliate-program/branding/portal-guide.md) — write the help content affiliates read inside the portal. * [Getting started with affiliates](/quick-start/getting-started-1.md) — overview and onboarding. * [Recruiting affiliates](/best-practices/recruiting-affiliates.md) — why a professional portal helps you attract better partners. --- # 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-style.md?ask=&goal= ``` `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.