Notifications
Where sourcesignal tells you that something needs you: the notification chip, the notice when tracking stops, reply reminders and the emails it sends. None of them acts for you.
Updated October 22, 2026Markdown
sourcesignal tells you when something needs you in a few set places: one notification chip in the bottom-right corner of every page of the app, counts and reminders inside the app, and a short list of emails. None of them sends anything for you: you decide what to do with each one.
Where notices appear
- The notification chip, bottom right: a tracking feed that stopped, news about your plan, and messages from the sourcesignal team.
- The rail: a count on Autopilot for the decisions waiting in today's deck, and a dot on Outreach while replies wait on you.
- Reply reminders: "Nudge?" on a conversation in the Inbox, and a follow-up card in the deck.
- Your account circle: a dot, and "N new" beside "Support", when the support team has answered you.
- Email: a project's first answers, a won page that no longer mentions you, trial and billing events, your own agent's requests, and support answers. During a trial also your first pitch, a Monday digest, a decision that has waited for you, and replies that went to a mailbox other than your own.
The notification chip
The chip is one line, tinted for info, warning or critical: an icon, a title and a short sentence. When a notice has a page, its title links there. Several notices share the one chip, and the arrows cycle through them ("1 / 3"). Pinned messages come first, then the most urgent, then the newest.
- Press the X ("Close notification") to close the one on screen. It closes for you, not for your teammates, and for that occurrence only: if tracking fails again tomorrow, a new notice appears.
- A message with a pin mark has no X and cannot be closed.
- On a phone the chip spans the screen and hides the "Retry", "Contact support", "Open settings" and "Open project" buttons. The arrows and the X stay. Tap the title to open the page it names.
| Notice | When it shows |
|---|---|
| "Tracking is down for", "Tracking is paused for" or "Tracking isn't connected for", and the project's name | The project's latest data update failed. See below. |
| "Your 14-day trial has started." | For three days after a trial starts, while the trial runs. |
| "You are on Growth now." (your new plan's name) | For a week after a plan change. |
| "Your yearly plan renews on" and the date | From 30 days before a yearly renewal until the day itself. |
| A message from the sourcesignal team | Until it ends, or until you close it. A pinned one stays. |
The plan notices link to Billing.
When tracking stops
A project's AI answers arrive every morning from its Ahrefs Brand Radar report (see The answer feed and data updates). When the latest data update fails, the chip names the project and says what to do. The notice clears on its own once a data update reaches the feed again.
| The chip says | What happened | What to press |
|---|---|---|
| "Tracking is down." "Retry reconnects it, or contact support." | The report sourcesignal created for the project is gone. | "Retry" reconnects it and re-sends your prompts. |
| "Tracking is down." "Choose a report in settings, or contact support." | The report you connected yourself is gone. | "Open settings" and choose another. |
| "Tracking is paused." "Retry turns it back on, or contact support." | Every engine is off in the report sourcesignal manages. | "Retry". |
| "Tracking is paused." "Turn an engine on in Ahrefs, then retry." | Every engine is off in your own report. | Turn one on in Ahrefs, then "Retry". |
| "Tracking is down." "Reconnect the Ahrefs key in the account settings, then retry." | Your organization's Ahrefs API token needs attention. | An owner or admin replaces it in Account settings (your account circle, then "Account settings"), on the Organization tab. Then "Retry". See Organization settings. |
| "Tracking isn't connected." "Connect a report in settings." | No report is connected. | "Open settings". |
| "Tracking is down." "Retry, or contact support if it keeps failing." | Anything else. | "Retry" runs the import again. |
Fix a failing feed
- Go to the project the chip names: press the title, or "Open project". On that project's pages the chip shows its buttons.
- Press "Retry" or "Open settings", as the table says.
- Read the result. "Reconnected. The import landed." means tracking is back. "Report recreated and your prompts re-sent." means a new report is in place, and the first answers usually land within a day.
- If it keeps failing, press "Contact support". The support drawer opens with the request filled in: "We'll attach the failing import, the report it came from and how long it has been failing."
Reply reminders
A reply reminder tells you when a publisher who replied has gone quiet. Once your latest message has waited the working days you set:
- In the Inbox, the conversation reads "Nudge?" with the days waited ("Nudge? · 6d"). That chip opens the thread with a short follow-up drafted in the reply box. "Needs a nudge", under "More", lists every one.
- In the deck, Autopilot deals a follow-up card ("no reply for 4 working days"). "Nudge" opens the thread with the reply box ready, "Snooze" (with the days, such as "Snooze 4d") sets it aside for as many days as your setting, and "Close" stops the reminder for that conversation ("Nothing is sent, and it stays in the Inbox.").
Nothing is sent for you: you edit the nudge and press "Send reply" (see The inbox). Once it has gone the reminder is done; if they go quiet again, a new one comes after the same wait.
Reminders only count conversations where the publisher had replied. A pitch nobody answered is followed up by its sequence instead.
Set reply reminders
- Open Settings in the rail, then Project, and go to Send schedule.
- In "Reply reminders", type a number in "Remind me when a reply is … working days old".
- Press "Save". The toast reads "Reminders after 4 working days", or "Reply reminders turned off" for 0.
| Setting | Value |
|---|---|
| Default | 4 working days |
| Range | 0 to 30; 0 turns reminders off |
| Counted | Monday to Friday, from your latest message |
| Scope | Each project keeps its own |
| Who can change it | Owners and admins |
| Cards in the deck | Up to 10 at a time; "Needs a nudge" in the Inbox holds them all |
Emails
The weekly briefing is written every Monday morning and kept with your reports (see Sharing, printing and briefings). During a trial, a short digest of your week arrives by email on Mondays too (see below). Publisher replies land in the connected mailbox the pitch went from as well as in the Inbox. When that mailbox is not your own address, owners and admins get an email about the reply during a trial.
| Sent when | Sent to | |
|---|---|---|
| "A placement dropped your mention" | The weekly placement check no longer finds your brand on a page you won. | Owners and admins |
| Your first AI answers are in | A project's first AI answers have landed. Once per project, within two hours of them. | Owners and admins |
| Your first pitch is ready | During a trial, Autopilot has drafted a pitch and none has been approved yet. It shows the pitch. Once per trial. | Owners and admins |
| Your week | During a trial, on Mondays: how often AI named you beside the two rivals named most, the emails you sent and the replies you got, and the decision worth making next. | Owners and admins |
| A decision is waiting | During a trial, nobody has opened the console for two days and the deck holds a decision. Once each time you are away. | Owners and admins |
| Your pitch got a reply | During a trial, a publisher replied to a pitch and the reply went to a mailbox that is not your own address. Once per reply. | Owners and admins whose own inbox did not get it |
| Trial and billing emails | A trial, payment or plan event (below). | Owners and admins |
| Your agent asks for a mandate | Your own agent asks for one while you are away from Spot and the deck. | You |
| Support answers | The support team replies to your request, or marks it answered. | You |
| An invitation | Someone invites you to their account. The link expires in 7 days. | The person invited |
| Your scorecard is ready | A free AI visibility report you asked for has finished. | The person who asked |
The placement email links to the wins record. If the check got it wrong, restore the win from its row menu (see Wins and verification). The agent email links to Settings, then Agents: decide within 24 hours, or the request expires and your agent can ask again.
There is no setting to turn emails off: who gets each one follows the person's role (see Members and roles). Sign-in emails are in Profile and sign-in.
Trial and billing emails
Owners and admins get one email for each event:
- A trial starts, has three days left, and ends.
- A payment does not go through. The email links the open invoice.
- A plan ends, or is set to cancel at the end of its period.
- Full access has two days left after a lapse.
- Data is hidden, and later the account pauses. Nothing is deleted.
- A yearly plan renews in 30 days.
- A paid plan starts, a plan changes, or the account is back after an open invoice is paid.
Trial and billing explains each stage.
During a trial
Between the first answers and the end of the trial, sourcesignal writes only when there is something for you, and at most once a day:
- Your first pitch, once Autopilot has drafted it and before you approve one, with who it goes to, its subject and its first lines.
- Your week, on Mondays from the trial's fifth day.
- A decision that has waited two days while nobody opened the console.
None of them arrives on a day you used the console, or within 18 hours of another email about your account. They go out early in the morning, UTC. The email three days before the trial ends also says what is waiting on your deck and what choosing a plan keeps. A reply email is news, so it comes at once and does not count toward the day.
Good to know
- Billing lines at the top of a page, such as a trial's countdown, are not part of the chip and cannot be closed.
- A mailbox that needs reconnecting says so on Settings, then Mailboxes, above the Inbox reply box and on Sequences in Outreach, each with a way to reconnect (see Mailboxes).
- Every project's Data page lists its own failed imports, so check there if an account has many projects.