> 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/social-sharing.md).

# Social Sharing

A referral spreads through the channel your customers already use to talk to friends — most often a private message, not a public post. The share buttons you offer, and their order, steer which of those moments turns into a referral. Manage this in your campaign's **Share Methods** area: **Sharing Method** and **Social Message** tabs.

> **Best practice:** Lead with the channel your audience uses privately, then trim the rest. On mobile, put WhatsApp and Native Share at the top; on desktop, email and X tend to fit better. Fewer, well-chosen buttons convert more shares than a crowded row.

### Which channel for which customer

| Channel                                 | Best for                                | Notes                                               |
| --------------------------------------- | --------------------------------------- | --------------------------------------------------- |
| WhatsApp                                | One-to-one, mobile-first, international | Lead with it on mobile                              |
| Native Share                            | Whatever app the customer prefers       | Mobile only — hands off to the device's share sheet |
| Email (Gmail / Mail App / Custom Email) | Considered, personal recommendations    | Fits desktop, higher-value products                 |
| X (Twitter)                             | Public, fast, low-commitment            | Tech/media/creator audiences                        |
| Facebook                                | Broad public reach                      | Communities, older demographics                     |

**Private channels out-convert public ones** — a WhatsApp message to one friend carries more weight than a public post to strangers. Lead with private, offer public as a secondary option, and confirm the mix with an [A/B test](/referral-program/ab-testing.md).

### Choose the sharing methods

Drag channels from **Available channels** into your **Desktop** and **Mobile** lists separately — order matters, since the top channel gets the most clicks. Native Share is mobile-only, and each channel can appear once per device list.

### Write a message that gets shared

Each channel (X, Facebook, WhatsApp) has its own editable message, with an optional custom image for X and Facebook (1200×630px recommended). What matters:

* **Write in the customer's voice**, not an ad's — "I love these — here's 15% off" beats "Shop our referral program."
* **Name the reward** in the first few words.
* **Keep WhatsApp short** — one line plus the link.

### A worked example

*Illustrative, not measured Bloop results.* A mobile-first store puts WhatsApp first and drops Facebook/X from mobile entirely, since its audience doesn't share that way; on desktop it leads with email instead. An [A/B test](/referral-program/ab-testing.md) confirms the trimmed mobile list lifts shares per visitor, and [share-channel performance](/referral-program/analytics/analytics.md) shows which buttons customers actually use.

### Common mistakes to avoid

* **Offering every channel.** A crowded row turns an easy share into a decision — pick the few your audience actually uses.
* **The same row on desktop and mobile.** Set them separately; the channels people reach for differ by device.
* **Leading with public channels.** They add reach but convert worse per share than a private message.

### Next steps

* Decide between links and codes in [referral methods](/referral-program/referral-methods.md).
* Confirm your channel order 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/social-sharing.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.