How to configure affiliate email notifications
Affiliate emails keep partners moving — they confirm approval, announce tracked sales, and signal that a commission is on its way. Bloop sends these automatically across the affiliate lifecycle, from application through coupon assignment and payout. Every message is a template you can enable, rewrite, and personalise with variables.
Manage them on the Affiliate → Email tab. Each email stores its own subject and body per store (Reset password also has a button), plus a recipient list for owner-facing notifications.
Which emails to enable, and why defaults matter
Section titled “Which emails to enable, and why defaults matter”Several templates ship disabled. A couple being off is a sensible default — but the two owner-facing notifications being off can quietly leave you in the dark. Walk the list deliberately before launch rather than trusting defaults.
| Trigger | Default | Enable it when… | |
|---|---|---|---|
| Registration pending | An affiliate signs up, awaiting review | On | Keep on — it confirms the application landed |
| Registration approved | You approve an affiliate (carries activation link) | On | Keep on — it’s the partner’s first impression and their way in |
| Registration denied | You decline an application | Off | Only if you want to email rejections; many programs leave it off |
| New coupon | You assign a coupon code | On | Keep on — the affiliate needs the code to promote |
| New sales | A referral order is tracked | On | Keep on — confirms tracking works, which builds trust |
| Sales approved | You approve a tracked sale | On | Keep on — tells the partner the commission is confirmed |
| Sales declined | You decline a tracked sale | Off | Only if you want to explain declines proactively |
| New commission payout | You pay out a commission | On | Keep on — this is what keeps affiliates promoting |
| Reset password | An affiliate requests a portal password reset | On | Keep on — partners can’t get back in without it |
| Manually added | You add an affiliate manually (invite + activation link) | On | Keep on — it’s the invite |
| New affiliate registration (to you) | A new affiliate signs up | Off | Enable + set a recipient if you want to know about new applicants |
| New affiliate sales (to you) | An affiliate generates a sale | Off | Enable + set a recipient if you want sales alerts |
The owner-facing notifications require a recipient address. If you assume Bloop is alerting you to new registrations or sales but never enabled them, applications can sit unreviewed for days. Turn them on if you rely on alerts; leave them off if you check the dashboard yourself — but decide deliberately.
The “declined” and “denied” templates being off is the opposite case: a reasonable default, since not every store wants to email a rejection. Enable them only if a graceful “thanks, not this time” message fits your program.
Affiliate emails sent to your affiliates
Section titled “Affiliate emails sent to your affiliates”
| When it sends | Default state | |
|---|---|---|
| Registration pending | An affiliate signs up and is awaiting your review | On |
| Registration approved | You approve an affiliate — includes their portal activation link | On |
| Registration denied | You decline an application | Off |
| New coupon | You assign a coupon code to an affiliate | On |
| New sales | A referral order is tracked to the affiliate | On |
| Sales approved | You approve a tracked sale | On |
| Sales declined | You decline a tracked sale | Off |
| New commission payout | You pay out an affiliate’s commission | On |
| Reset password | An affiliate requests a password reset for the portal | On |
| Manually added | You add an affiliate manually — invites them with an activation link | On |
The registration-approved and manually-added emails both carry the affiliate’s activation link, which works once and lasts 3 days. The Reset password link lasts 1 hour. An affiliate who opens an expired link can request a new one from that page, so keep these emails turned on. The new-sales, sales-approved, and sales-declined emails reference the specific order so the affiliate can track its status.
Sales approved and Sales declined send only when you change a sale’s status yourself in the Sales tab. A sale that arrives approved because order approval is set to Immediately, or that Bloop rejects automatically after a cancellation or refund, sends neither email.
With Affiliate approval automation set to Immediately in settings, a new applicant skips Registration pending and receives Registration approved straight away. If your store gets an unusual burst of sign-ups, Bloop holds the extra applications as pending and sends no email at all, to the applicant or to you, so check the Affiliates tab for them.
The Manually added email is an invitation the person didn’t ask for, so it carries a one-line unsubscribe footer and a one-click unsubscribe header, as mailbox providers expect from bulk senders. Someone who unsubscribes stops receiving your store’s marketing emails from Bloop, including these invitations. Every other affiliate email is a direct response to something the partner or you did, and has no unsubscribe link.
Emails sent to you (the store owner)
Section titled “Emails sent to you (the store owner)”Both owner notifications ship disabled — turn them on and set a recipient address if you want them.
| When it sends | |
|---|---|
| New affiliate registration | A new affiliate signs up — includes their name, email, and any note |
| New affiliate sales | An affiliate generates a new sale |
Both emails share one Send to list. Type an address and press Enter to add it. The list holds up to 3 addresses, and the same addresses receive both emails. Some older plans lock the field.
What good partner-facing emails say
Section titled “What good partner-facing emails say”- Open by name. Lead with
{{FirstName}}. A partner who sees their own name reads on; a generic “Hello affiliate” signals they’re just a row in a database. - Lead with what they care about. The approval email should say “you’re in, here’s your dashboard” before anything procedural. The payout email should confirm the amount and thank them first.
- Make the next step obvious. Every email that gives access (approval, manual-add, password reset) should point clearly at where to go. Only Reset password has a button, so in the other emails make the
{{AffiliateActivationLink}}or{{AffiliatePortalLink}}link its own short line in the body, not buried in a paragraph. - Use the right variable for the moment. Approval and manual-add emails carry
{{AffiliateActivationLink}}; once active, point partners to{{AffiliatePortalLink}}; use{{SalesOrderId}}on sales emails. - Sound like your store. Edit the default templates so the voice matches your brand, reinforcing the legitimacy your portal and registration form already established.
Editing an affiliate email
Section titled “Editing an affiliate email”Open any email on the Affiliate → Email tab to edit:
- Subject line — supports variables.
- Body — the message, with formatting and variables.
- Button: text, colour, and font. Only the Reset password email has a button; the others carry their link in the body.
- Send to: for owner-facing notifications, the addresses the alert is sent to (up to 3, shared by both owner emails).
- Image — an optional header image.
Changes save per store and apply to every future send of that email type.
Template variables
Section titled “Template variables”Variables are placeholders in double braces, like {{FirstName}}. Bloop swaps them for real values at send time; if a value isn’t available, the placeholder is left in place.
| Variable | Fills in |
|---|---|
{{FirstName}} |
The affiliate’s first name |
{{LastName}} |
The affiliate’s last name |
{{Email}} |
The affiliate’s email |
{{CouponCode}} |
The coupon code assigned to the affiliate |
{{SalesOrderId}} |
The tracked order (rendered as a link to the order in the portal) |
{{AffiliateActivationLink}} |
The link an affiliate uses to activate their account |
{{AffiliatePortalLink}} |
The affiliate’s portal dashboard link |
{{store_name}} |
Your store name |
{{note}} |
The note submitted with a registration (owner notification) |
The new-coupon email uses {{FirstName}} and {{CouponCode}}; sales emails use {{SalesOrderId}} and {{AffiliatePortalLink}}; approval and manual-add emails use {{AffiliateActivationLink}}. An unavailable value leaves the placeholder visible. A test send does not fill the affiliate’s values, so confirm them with a real affiliate address, as described in the test section below.
A worked example: the lifecycle a new partner sees
Section titled “A worked example: the lifecycle a new partner sees”An affiliate applies (Registration pending fires automatically, and if you enabled it, New affiliate registration alerts you with their {{note}}). You approve them (Registration approved carries {{AffiliateActivationLink}} as a warm welcome) and assign a coupon (New coupon delivers {{CouponCode}}). A sale tracks and gets approved (New sales → Sales approved, reassuring the partner tracking works), then you pay them (New commission payout — make this the warmest email of the lot, since it’s what keeps them promoting).
Send yourself a test of every email in this chain before launch to check layout and wording. A test leaves placeholders such as {{FirstName}} and {{CouponCode}} unfilled, so to see them resolve, add yourself as an affiliate with an address you control and follow the real steps.
Test before you go live
Section titled “Test before you go live”Send yourself a test from the email editor to preview the final layout and wording. A few limits apply:
- Test sends are rate limited to 10 per minute from the same connection.
- A single test can go to at most 20 recipients at once.
If you hit the limit, wait a moment and try again. Test emails don’t affect any real affiliate record.
A test fills in your store’s details, such as {{store_name}}, but not the affiliate’s. Placeholders like {{FirstName}}, {{CouponCode}}, {{SalesOrderId}} and the portal and activation links stay as they are in the template, so a test checks layout and wording only. To see real values, trigger the email for an affiliate address you control, for example by adding yourself as an affiliate.
Common mistakes to avoid
Section titled “Common mistakes to avoid”- Assuming everything emails someone. The owner notifications are off by default. If you rely on alerts you never enabled, applications and sales go unnoticed.
- Shipping the default copy. Generic templates read as automated. Edit at least the approval and payout emails to sound like your brand and open with
{{FirstName}}. - Skipping test sends. They catch layout and wording problems before a real partner sees them. Variables stay as placeholders in a test, so check those with a real affiliate address.
When and why to revisit your emails
Section titled “When and why to revisit your emails”- Applications sit unreviewed → enable the owner registration notification and set your address so you’re alerted in real time.
- You change your brand voice or program name → re-edit the templates, especially approval and payout.
- You start handling declines proactively → enable the “denied” and “sales declined” templates and write them to be gracious.
- A partner reports a confusing email → check that template’s wording and variables; a misplaced variable or a misordered message is usually the cause.
Related
Section titled “Related”- Affiliate settings — payment methods and broader email configuration.
- Affiliate sales — approving and declining the sales these emails announce.
- Affiliate payouts — paying commissions, which triggers the payout email.
- Email sender domain — send these emails from your own branded domain.
- Affiliate program setup — approving registrations and assigning coupons.
- Recruiting affiliates — a professional email lifecycle is part of attracting and keeping good partners.