> 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/account-extension.md). # Customer Account Extension Put referral blocks in the logged-in customer account, where repeat buyers already are. Your most likely referrers are repeat customers, and the customer account is where they spend their logged-in time. The post-purchase widget catches a buyer once; the account blocks are there on every return visit, next to the orders and details they came for. That makes this the best surface for steady, long-tail referrals — and the only place a referrer can give you the payment details a [cash reward](/referral-program/rewards.md#cash) needs. Bloop ships three Shopify customer account UI extensions. You add them in Shopify's customer account editor, and edit their wording in Bloop under **Branding → Customer account extension**. > **Best practice:** Add the Referral link block to the **order index** as well as the profile. A customer checking "where's my order?" is already engaged and already logged in — that's a better moment to ask than a profile page they visit twice a year. ### The three blocks | Block | Where it can go | What it does | | --------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Referral link | Order status, order index, profile | Shows the customer's referral link and code, the share buttons you enabled, and a link that emails them their [referral hub](/referral-program/referral-hub.md) login | | Referral rewards | Profile | Lists what they've earned — discount codes, store credit, cash, free products and [custom rewards](/referral-program/rewards.md#custom) | | Reward payment method | Profile | Lets a referrer choose how they want to be paid and fill in their details | ### Add them to your store 1. In Shopify admin, open **Settings → Customer accounts** and edit your customer account pages. From Bloop, **Edit in customer account editor** takes you straight there. 2. Choose the page you want — Profile, Orders, or an order's status page. 3. **Add block**, then pick the Bloop block under **Apps**. 4. Position it and save. The Reward payment method block only belongs on the **Profile** page. If your campaign pays cash, add it before you turn the reward on — otherwise referrers earn money you have no way to send. ### Edit the wording **Branding → Customer account extension** has a tab per block — **Referral link** and **Referral reward** — with a live preview beside the fields. Content saves per language; switch with the language selector, or leave automatic translation on for the campaign and write only your default language. Switching language discards unsaved edits, so save first. ### The hub link The Referral link block ends with a line that emails the customer a link to their [referral hub](/referral-program/referral-hub.md) — their full dashboard of rewards, tier progress and referral history. They click it, Bloop sends the email, and the block confirms which address it went to. This matters because the hub link is a credential, not a URL you can put on a page: emailing it to the address on the account is the safe way to hand it over. Give the link text a reason to click — "See all your rewards" reads better than "Referral hub". ### Collect payment details for cash rewards The Reward payment method block shows the referrer the payout methods you enabled in **Referral → Settings → Payment method**, lets them pick one, and collects the fields that method needs. Bloop stores the details and shows them beside the referrer when you run a payout in [referral orders](/referral-program/management/orders.md#pay-out-cash-rewards). Until a referrer fills this in, their cash rewards sit in the payout queue with a **Referrer hasn't added payment details yet** warning. ### Common mistakes to avoid * **Adding the blocks and never mentioning them.** Nothing announces a new profile block — link to it from your welcome or reward emails. * **Turning on cash rewards before the payment method block is live.** You'll owe money you can't pay. * **Putting the Referral link block only on the profile.** The order pages get far more traffic. * **Leaving the default copy in one language.** These blocks reach your most loyal customers — they deserve their own language. ### Next steps * Catch buyers at checkout with the [post-purchase widget](/referral-program/branding/post-purchase.md). * Give referrers somewhere to track everything in the [referral hub](/referral-program/referral-hub.md). * Set up payout methods in [Referrer and referee rewards](/referral-program/rewards.md#cash). --- # 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/account-extension.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.