One digest of the people you follow and your clan, weekly or daily. Besides it, only mail with something for you to do or read: clan actions waiting, cheers on your play, your collector's week, and answers to your feedback.
Elixir sends one digest: the people you follow and your clan's week, in one email, weekly by default. It is the only scheduled email most people get. Besides it, Elixir mails you only when there is something for you: a clan action that is yours to do, cheers and new followers you have not seen yet, your collector's week if you run one, and an answer to feedback you filed.
Your digest counts how many players posted and how many played. A question or a post about a battle counts as a post. A friend who did both counts once in each group. Their words come first, with a battle record when they played. A gold check beside a linked player name marks a player verified in Elixir, even if they have not chosen an image.
Mail apps that support custom fonts show the same game titles as Elixir. The text and links still work with custom fonts or images blocked.
| Kind | When | What it is |
|---|---|---|
| Your digest | Mondays at 11:00 UTC, right after the weekly reset, or daily, or off: your choice | The people you follow and your clan's week in one story, each player once: below. Skipped when nothing happened. |
| Clan actions waiting | When an action becomes yours | From Clan, when something new in your clan is yours to do (promote, welcome, answer a departure, say whether you are away), with everything waiting for you and a link to act. Clan checks each morning, after its daily read, and mails only when something new is yours since your last one: nothing waiting, nothing sent, and at most one a day per clan. Only if you can act on it, only to the account that verified the player. Clan writes the words and Elixir sends them, so the app needs no address to mail you. |
| Collector activity | Sundays at 14:00 UTC | Only if you run an Elixir Collector: each collector by its card, its full reported version and the collector page's security status (signed, dev build, unverified or mismatch), whether it is checking in, silent or stopped, its fetches this week and how many of them added new facts to the record; how much was blocked as already recorded, and your limits: an active collector raises them to Family. One mail per account, every collector you run pooled. Covers Saturday 00:00 UTC to the next Saturday 00:00 UTC, the week that closed the night before. |
| Cheers on your play | At most once a day, around 6 pm in your account's time zone | When people cheered your players' battles and posts, or started following your players, and you have not seen it in Elixir yet: how many cheers on each item and how many new followers, never who. Each line opens the session, the battle or the player. Nothing new, nothing sent. What you already saw in the bell, or in your last one of these, is not told again. Only about the players you verified. |
| Answers to your feedback | When answered | When Elixir's maintainer answers feedback you filed and you have not read the answer yet: what you wrote, the answer, its status and the version it shipped in, with a link to the item. One mail per answer, sent after ten quiet minutes, so a correction made straight away is one mail. Getting the email does not count as reading the answer: opening the item does. An agent's feedback is answered to the agent, never mailed. |
All of them start on for an active person account, and each is a switch (Settings › Emails), with a turn off link in every issue and one-click unsubscribe in mail clients that support it. Sign-in codes and account notices are service mail and arrive whatever you choose here.
Every email is built from your record by the same readers the tools answer with, with no language model anywhere in it. Every number is the number a tool would give you, with the coverage note the tools carry, because a report that hides a gap in the record is a report that lies. Clan actions waiting carries Clan's own words, the lines its Feed shows, and an answer to your feedback is the maintainer's answer as it was written.
Your digest
Your digest is your timeline for your inbox: the people you follow and the clans you follow, told as one story. The email chooses what to say, and the timeline keeps everything.
- When: weekly, on Mondays at 11:00 UTC, by default: an hour after the game's weekly reset, so the week and its River Race are done. In Settings › Emails it is three choices, Weekly, Daily (every day at 11:00 UTC) or Off: tap one.
- What it covers: the week (or the day) before it comes, starting no earlier than your last digest, so nothing is told twice. It tells what the record learned in that time, so a battle recorded late still arrives, once.
- From people you follow: each friend who played or posted, up to twelve with the rest counted. Each has their sessions, then their battles and record, their trophies, and up to three things: their posts and questions, including posts about battles, first, with their own words and attached deck or cards. Read and reply opens a question in Elixir after sign-in. Following an account includes its new posts even when you do not follow its player separately. Then the big firsts (a new arena, league, best band, form, legendary badge or career step), a move between clans or a return, each with a link to the battle that did it when the record knows it. Cards unlocked and badge levels are a count. A clanmate you follow says which of your clans they are in. Each post and game update shows its original day and time in your time zone. Open item and comments opens that exact update and its thread, keeping the destination through sign-in. Elixir checks its current audience when you open it.
- Their sessions: up to three of each friend's biggest sessions, told the way your feed's session card tells them, the rest counted with a link to their page. A session of three or more battles shows its result ("Won 8 of 12 on Trophy Road, 5 in a row"), its record and trophies, three-crown wins, the widest win, a Ranked climb, a challenge's furthest run, who you follow it was played with, and the deck played most, with the deck's eight cards on one session a friend. A session of one or two battles is one line. Each session's result opens its own page. In a busy digest, later friends' sessions get shorter, then become a link to their page, and in a very busy one the last friends' posts and firsts are counted with a link to your timeline, so your email is never cut off. Your own sessions stay on your feed; under You, the digest keeps your week's count and your firsts.
- Your clan: each clan you follow with news of its own: a river race that finished (its place and fame), who joined and departed, and role changes, as a headline and at most three facts with the rest counted. It's yours to turn off: Clan news under the digest on Emails. Off, the digest has no clan part, and a clanmate you follow who joined, left or changed role is told under them instead.
- You: your own week, posts, firsts, your cards and badges counted, and each alt that played, with its firsts.
- Never an empty week: when no one you follow played or posted, neither did you, and no clan you follow has news, no digest comes.
Each player once. Following everyone in your clan is common, so the digest never tells a player's week twice: their battles, firsts and posts are told under them, and the clan's part keeps to the clan's own news. A clanmate you follow who left the clan is told in the clan's part, not again under them. A clan's battle count and who went quiet are on Clan, not in the mail.
What is attested (Clan's departures, roles, awards and messages, Drop's personal records) stays out of the digest; the timeline still carries them to their readers. Anything a person typed, a name, a nickname or a post's words, is shown as text.
A post appears once, in the digest covering when it was created. Editing it does not send it again. Deleted or hidden posts, posts you reported, and posts from someone blocked in either direction are left out when the digest is built. A copy already prepared or delivered by email cannot be taken back; its link checks who can see the post now.
Collector upgrade notices
The collector email switch also controls upgrade notices: one email for each collector whose installed version Elixir sees change to a higher released version. Five upgraded collectors produce five separate emails, normally within a few minutes of their check-ins. Naming an available release sends nothing. Each notice names the old and new versions, the reading time and security status. First check-ins, unknown/dev versions, downgrades and same-version restarts produce no upgrade notice. A later upgrade following a rollback is a new recorded transition.
When available, the notice includes the target release’s published notes and a maintainer-supplied reason for naming it. These explain the release’s purpose; they do not prove whether a particular machine updated automatically or was changed by its operator. Missing reasons and notes are stated explicitly. Security status uses the same self-reported version/hash comparison as the dashboard, and is not remote attestation. A signed collector can still be behind the current release.
What every email looks like
Every email Elixir sends wears the same frame, so a sign-in code and a digest are plainly from the same sender: Elixir's logo and name at the top with a plain label naming the part of Elixir it comes from, the mail itself, and a footer that says why you got it and when the next scheduled one comes, in your own timezone. Each mail uses readable headings and rows, and its coverage note stays visible below the main link. A scheduled email's footer then has one line, Turn off this mail · Manage emails · Send feedback · Mail and the first six characters of its id, then the disclaimer; a sign-in code or a welcome has no such line, because you asked for it. The logo and card art are PNGs served from elixir.poapkings.com, never Supercell's servers, and each card says its name to a mail client that does not show images. The one other image is the open pixel (below). A deck is drawn the way the game draws it, eight cards in a row, with the tower troop named under it. A digest stays small enough that Gmail never cuts it short: it counts what it leaves out and links the rest.
Turning one off
Each kind has its own switch on Emails (Settings › Emails). The digest shows its local day and time and its cadence beside its switch, and its Clan news switch under it. The other kinds follow below, then the latest sent records. Every email turns them all off, or all back on. Every issue's footer has a turn off link for that kind, which opens a page with one button to confirm; mail clients that support one-click unsubscribe show their own button, which needs no confirming. Turning a kind off is immediate and yours to reverse.
Notifications
Elixir can also tell your phone or computer, with a notification, when something about you happens:
- Cheers on your play. "3 cheers on your play". How many, never who. A burst of cheers waits a couple of minutes and comes as one.
- New followers of your players. Counted, never who.
- Clan Actions waiting for you, if you can act on them.
- Answers to your feedback.
- Close friends' play, if you starred a close friend: one when they finish a session of 3 battles or more, or a shorter one with a climb in Ranked or a run of 5 wins or more in a challenge. It shows their name and the session's result, like "Pip Ember" and "Won 3 of 4 on Trophy Road". A new best, a new league in Ranked or a new Arena is told in the Timeline's own words. It comes once the session is over (no battle for 30 minutes), never while they're still playing, and once per session, even if they play on. Friends who finish around the same time come as one, like "Pip Ember and 2 other close friends played", which opens your Timeline on Close friends. At most three a day, and only about play from the last two hours. Only you see who you starred: your friend is never told, and it never comes if either of you blocked the other.
Turn them on in Notifications (Settings › Notifications) on each device you use: tap Turn on notifications, then allow them when your browser asks. Elixir never asks on its own. On iPhone and iPad, notifications come only to Elixir added to your Home Screen (iOS 16.4 or later): tap Share in Safari, then Add to Home Screen, and turn them on from there.
Each kind has its own switch, and every device you turned on is listed there with a Remove. At most one notification every ten minutes and eight a day. Tap one to open what it's about. A notification you tapped is left out of the next Cheers on your play email. Close friends' play is a notification only: it is never in an email or the digest.
Every email, on the record
Every email Elixir sends you has its own id, shortened in its footer ("Mail a1b2c3") with the whole id in the link; the link opens that email's record in your account, and Send feedback in the same footer opens the feedback form with that email attached, one click from your inbox. Back leaves that automatically opened form; Forward returns with the email attached. Closing the form sends nothing. All sent on Emails (/settings/emails/sent) lists every product email sent to your account, newest first; open one to see the mail as it went out. A report about an email carries the mail itself, so nobody has to describe it, and the maintainer reads the same body you were sent. Quote the id and we can find the one send you mean in our logs. Reading your own record is never counted as an open (the open pixel is stripped before it is shown). Sign-in codes are not listed.
Every product email is kept as it was sent for a year, so what we send can be audited without waiting for anyone to report it.
What the mail counts
Mail is counted by issue, never by reader, through
Tinylytics, the same cookie-free analytics the
site uses. A 1×1 GIF from Tinylytics in each mail counts an open at a
path that names the mail, not the reader (/mail/tracking_report/2026-W37); it is an
estimate, and a low one, since image blocking and caching both cut
against it. The other images, the logo and card art, are plain files
and count nothing. Links into the site carry a campaign tag (the mail's
kind and issue), so the site's own counts can say which mail brought
people to which page. There is no redirector: a link goes where it
says, and the turn off link carries no tag. The footer's links to the
email's own record and to feedback about it carry the email's id,
because they open one of your own records; the website counts those
pages as "an email record", never which one. Privacy
covers the rest.
A player's name opens their player page, for every
reader. A clan you are in opens at Clan, War, and its roster link at
Members; another clan opens its record. A battle opens its own page, and
an action opens in Clan. Signed out, a page says why it needs you to sign in,
and signing in brings you back to it. Tags appear only where a name alone could
be ambiguous. A link to a season or a race names it:
Stats links carry the season the mail describes (/home/you/stats?season=136),
and a finished race's link its Season and Week, so a mail opened
after the next roll still opens what it described. Nothing in a report is
advice.
This material is unofficial and is not endorsed by Supercell. For more information see Supercell's Fan Content Policy: www.supercell.com/fan-content-policy.