Emails we send

Two kinds of email leave this product, and the difference decides whether you can switch one off.

Transactional email is the consequence of something you did, or something you need in order to use what you pay for: receipts, password resets, payout notices, application decisions, security alerts, sign-in codes. It carries no unsubscribe link and it cannot be switched off. That is deliberate. Nobody should be able to unsubscribe themselves out of a password reset, and no partner should be able to miss the email that says their money moved.

Lifecycle email is everything we send because we think it will help: getting-started nudges while you are setting up, the weekly summary, a note when your program does something for the first time. Every one of these carries a one-click unsubscribe and a link to your preferences, and you can turn any of it off without touching the first kind.

What you get while you're setting up

Each of these is one email, sent once, and says what to do next.

Three days before your trial ends you get a reminder, and one more on the day it ends if there's no card on the account. The trial emails stop the moment you pay. Nothing in that group goes to somebody who already subscribed.

The one email we send to somebody else

If the person who deploys your website is not you, the tracking step has a Send this to your developer box. It sends one email, once, to the address you type: the tag, where it goes, what it does, and a note from you if you write one. Replies come back to you, not to us, and we never write to that address again. It is the only email this product sends to anyone who is not you or one of your partners.

What you get about money

Receipts when a payment goes through, and a notice when a plan or interval changes. If a card is declined you hear about it three times over a week rather than once, and the last one says exactly what happens if it stays unpaid. Annual plans get a reminder thirty days before they renew, saying the date and the amount.

Your plan covers a set amount of partner revenue each month. That amount is your band. Test sales from Stripe test mode never count toward it. You hear when your partners have brought in 80% of it, and again if you pass it. Passing a band is the program working. Nothing is charged for it, and nothing switches off during the seven-day grace that follows.

What you get about your program

Then there's the operational set. It's all transactional, because missing one costs you money:

• A payout batch waiting for your approval.
• A payout didn't go through. One email, the moment PayPal or Wise fails it. It quotes their reason and says what to do.
• A payout still stuck at "processing" after eight days. We stop checking on it by then, so nothing else will tell you.
• Fund a payout in Wise. Wise set up the transfer and needs you to pay for it. Once, per payout.
• A payout needs a look. PayPal says it already has a payout but won't say which one, so we stopped it. That way it can't go out twice. The email links to the payout, where you check and press Clear it. Once per hold: pressing Send again on a payout that's still on hold doesn't send you another one.
• A payout is on hold until you check PayPal or Wise. A different email, for a different reason: the payout first went out more than 29 days ago, so the provider can't spot a repeat any more. We won't send it again. Check the provider's own activity, then clear it and mark it paid if the money left, or email support if it didn't. Once per hold, same as above. If you clear it and it goes back on hold, that's a new hold, and you're told again.
• Risk flags. One email per program for every flag the last check raised, each with its evidence in a sentence.
• A payment processor that has disconnected.
• A Stripe program that was making sales and then sent us nothing for a week. Its webhook may need re-adding. We mention it at most three times.
• A domain whose DNS record never appeared.
• We turned off a webhook. An endpoint that failed every event we sent it for five days or more, with no answer in between. It names the endpoint's host, not its full address; find that in Settings. Failed deliveries stay in the log, so you can replay them once it works again.
• Your campaign didn't send. A scheduled campaign that couldn't start, for example an empty audience. It's back to a draft, and the email says why.
• Payouts over PayPal or Wise have stopped. A connected account refused its key, or was turned off with a batch waiting. The email names the provider, what stopped and what's unaffected.
• Money is due and there's nowhere to send it. A payout batch is waiting and no payout account is connected. You hear before it fails, not after.

Neither of the last two carries an unsubscribe, because both mean your partners can't be paid. Each fires once per incident, never daily.

After the first one, partner applications arrive as one digest, and only for applications that have waited a day. Six applications in an afternoon is one email. Each application is in three reminders at most, counting the first-application email. After that, only the weekly summary mentions it.

The weekly summary

Once a week, per program: clicks, new partners, commissions earned, what's due to be paid, applications still waiting, and one thing worth doing. It counts real activity only. Test-mode sales and the demo data your account starts with are left out. A program with nothing to report gets nothing, so a quiet week is a quiet inbox.

What your partners get

Everything in the Messaging guide. Here's when each one goes:

A partner can switch off First referral and New referral in their portal settings, and we honour it. You can switch off any template except invitation, approved, declined and the payout reminder.

Two more are ours. A monthly earnings summary, which they can switch off. And a tax-form email where your program requires forms, which they can't, because a missing form is what stops them being paid. It goes when they join, if there's no form on file, and again in December if their form is about to run out.

Turning things off

Every lifecycle email carries a link to your preference page, and mail clients that support one-click unsubscribe get a button at the top of the message. The page has three choices: tips and product news, the weekly summary, or everything on that list. It also spells out, before you choose, exactly what will keep arriving.

You do not need to sign in to reach it. The link carries a signature of its own, so it works from any device and cannot be guessed by anybody else.

If somebody reports one of our emails as spam, we stop sending them lifecycle email everywhere, immediately, without waiting to be asked twice.

Sending limits

Campaigns and sequences leave through our sending infrastructure, so there are two limits on them, both enforced on the server.

There is a daily ceiling per program, sized to your plan, from 500 messages a day on trial up to 200,000 on Enterprise. It is an abuse ceiling rather than a product limit: a program mailing 400 partners twice a week never comes near one. A program that reaches its ceiling picks up again at midnight UTC with the queue intact.

And a program whose spam-complaint rate goes above 0.30% over a rolling seven days is paused automatically and told why, with the numbers it was measured on. The rate is only computed once at least 500 messages have been delivered in that window, so a single complaint on a handful of emails never pauses anybody.