> 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/referral-program/branding/popup.md). # Widget & Popup Brand the launcher, panel and referee popup, the surfaces most customers meet. The widget is the part of your programme most customers actually meet: a launcher button that sits on your storefront, a panel that opens when they click it, and a popup that greets a friend arriving on a referral link. All three belong to a [branding theme](/referral-program/branding/themes.md) — open **Branding**, pick the theme you're working on, choose **Customize**, and they're the first three cards under **Widgets & Popup**. Open **Referral → Campaigns**, open the campaign, then **Branding**. The surfaces on this page are under the **Widgets & Popup** section of the theme editor. > **Best practice:** Treat the launcher as advertising and the panel as the product. Keep the launcher quietly visible on high-intent pages (cart, product), and make the panel polished enough that sharing feels worthwhile. ### What tends to win | Element | What tends to win | | ------------------ | ------------------------------------------------------------------------- | | Panel background | A clean, **light background** | | Imagery | **Product-focused** creative over lifestyle photos | | Reward framing | Lead with the **referee's reward** first — reads as a favour, not a pitch | | Launcher copy | A **specific, value-led label** ("Give $10, get $10") over a generic one | | Launcher placement | A **quiet presence on cart and product pages**, not sitewide | These are broad testing patterns, not measured Bloop numbers — confirm them on your own traffic with an [A/B test](/referral-program/ab-testing.md). The underlying rule: simpler and product-led wins. ### Style the widget panel **Widget panel** opens the theme editor, with a live preview you can flip between **Desktop** and **Mobile**, and three tabs. **Appearance** sets the look: | Setting | Options | | ------------------------------- | ----------------------------------------------------------------- | | Background | A solid **colour**, an uploaded **image**, or **no image** at all | | Header text | Colour of the headline | | Body text | Colour of the running copy | | Button background / Button text | The call to action | | Corner style | Square or rounded | Background images accept `.jpeg` and `.png` up to 20 MB. **No Image** is worth trying deliberately: a flat, single-colour panel loads instantly and keeps attention on the reward. **Content** holds every string a customer reads, grouped by the step they're at: | Step | What you write | | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | Referral signup | Title, subtitle, the "They get" / "You get" labels and reward values, email placeholder, button text, invalid-email and no-spam messages | | Referral share | Title, subtitle, the "Or share" label, copy-button text, referral code label, track-referrals link, link-sent confirmation | | Share by email | Title, the "To" label and hint, message label and hint, referral code label, send-invite button | | Claim reward | Title, subtitle, email placeholder, button text | | Reward ready | Title, subtitle, reward value label, copy-button text, button text | Content saves per language. Use the language selector to write each translation, or leave automatic translation on and write only your default language — see [campaign language settings](/referral-program/campaign.md#name-language-and-translation). **Custom code** takes CSS and JavaScript that run on your live storefront, within a size budget the editor shows as you type. **Preview** runs your snippet in the editor preview only; you still have to save to put it on the storefront. Bloop support can't debug or fix custom code, and a broken snippet can change how the panel looks or stop it working — reach for this only when the fields above genuinely can't express what you need. ### Configure the widget launcher **Widget launcher** opens its own settings page — the badge next to the title tells you whether it's currently **Active** on your storefront. | Section | What you set | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Show the widget on storefront | The master switch. Off hides the launcher from every visitor | | Generals | Button title, colour, and icon — Bloop's default or your own upload (`.jpeg`, `.png`, `.ico`, under 20 MB) | | Display | Per device: **Icon and text**, **Only icon**, **Only text**, or **Hide widget** — set separately for desktop and mobile | | Placement | **Bottom right**, **Bottom left**, or **Custom** (drag the button on the preview, separately for desktop and mobile). **Button rotation** turns it into a side tab — none, tab left, or tab right | | Border | The launcher's corner style | | Duration | **None** to leave it on screen, or a **display duration** in seconds after which it disappears | | Visibility | Which pages it appears on | Two of these carry real weight. A value-led title ("Give 10% — get 10%") earns more clicks than "Rewards". And a side tab with a display duration is the polite version of an always-on button: present when someone's looking, gone when they're not. #### Choose which pages show the launcher Visibility has four modes: | Mode | Use it when | | ------------------------------- | ------------------------------------------------------------------------------- | | Show widget on all pages | You want maximum reach and your storefront isn't crowded | | Show widget on selected pages | You want the launcher only where intent is high — cart and product | | Hide widget on selected pages | You're happy sitewide except for a few pages (checkout-adjacent, landing pages) | | Action widget on selected pages | You want the panel to open by itself on specific pages | Pick from Home, Cart, Product, Collection and Search pages, or add a **specific URL** for anything else. ### Customize the referee popup **Referee popup** is what a friend sees when they land on a referral link — your first impression with someone who has never bought from you. It opens the same editor as the widget panel, with the same Appearance, Content and Custom code tabs. Lead with the reward they've just unlocked, name who sent it, and keep it to one button. This is the highest-leverage copy in the whole programme: every referred visitor reads it, and nothing else you write reaches a colder audience. ### Common mistakes to avoid * **Editing the applied theme to try something out.** Duplicate it, change the duplicate, apply it when you're happy — see [branding themes](/referral-program/branding/themes.md). * **Over-branding the panel.** A crowded, heavily styled popup converts worse than a clean one. * **Burying the reward.** Lead with the value in both the launcher title and the panel headline. * **Leaving the launcher sitewide on a busy storefront.** Use Visibility to put it where intent already is. * **Solving layout problems with custom CSS.** A snippet that fixes your theme today breaks on the next release. ### Next steps * Manage and apply themes in [Branding themes](/referral-program/branding/themes.md). * Give customers a permanent destination with the [referral page](/referral-program/branding/page.md). * Prompt buyers right after checkout with the [post-purchase widget](/referral-program/branding/post-purchase.md). * Confirm a design or copy change with [A/B testing](/referral-program/ab-testing.md). --- # 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/referral-program/branding/popup.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.