Daily Pulse

The Daily Pulse is a short digest for each brand that goes out after its scheduled tracking run. It shows the headline numbers for the period, then lists what went well (highlights) and what needs attention (warnings). It is delivered two ways:

• Email — cloud only.
• The daily_pulse.created webhook — on cloud and self-hosted alike. See Webhook delivery.

​

Configure it

Open Settings → Notifications. Every active brand in your organization has its own row with a frequency and a recipient list. Admins and managers can change them; other members see the settings read-only. The Manage notification settings link at the bottom of every pulse email opens this tab.

​

Frequency

A brand with no saved setting uses Daily. “Notable” means at least one highlight or one warning survived the rules below — including the 7-day warning cooldown. A day whose only warnings were already reported that week counts as not notable.

​

Recipients

Enter a comma-separated list of email addresses.

• Leave it empty to send to every member of the organization.
• Each address is checked when you save. If any entry is not a valid email address, the save is rejected and the invalid entries are listed under the field — fix or remove them and save again. A mistyped address is never silently dropped, because an empty list would widen the audience to the whole organization.
• Up to 50 addresses are stored.

Recipients only affect email. Webhook delivery does not use them.

​

When it is sent

A pulse is generated after a brand’s scheduled daily tracking run finishes. Manual runs and single-prompt refreshes never trigger one. Before computing anything, the pulse waits (up to 90 minutes) for the AI engines’ late answers from that run to arrive, so its numbers match what the dashboard shows for the same window. No pulse is sent when:

• the frequency is Off, or it is Weekly and today is not Monday (UTC)
• the brand already had a pulse today, or a pulse for the same tracking run was already sent
• there are no tracking results in the window
• the frequency is Only when notable and there is nothing notable
• on the cloud, the organization’s subscription is not active or trialing

If a scheduled run finished but its pulse was lost (for example, the server restarted at the wrong moment), it is sent at the start of the next daily cycle instead.

​

What’s in a pulse

​

KPIs

For Daily and Only when notable, the period is the latest completed tracking run (at most 24 hours), compared with the run before it. For Weekly, it is the last 7 days compared with the 7 days before. The email subject carries the score and the weekly trend, for example: Acme Daily Pulse — visibility 42.5 (+1.2 pts this week).

​

Highlights

Highlights other than first citations and new engines compare the last 7 days with the 7 days before, whatever the frequency.

​

Warnings

Cooldown. The same warning about the same subject — for example, a surge by the same competitor — is not repeated within 7 days. Highlights have no cooldown. Data-collection guard. If an AI platform’s result volume collapses on our side (under a quarter of its usual daily volume across the whole instance), the pulse treats it as a collection problem rather than a real change: Sharp drop, Visibility slipping and Lost citations are held back, and the email notes which platforms were affected. The webhook reports them in degraded_platforms.

​

Webhook delivery

Every generated pulse is also sent as a daily_pulse.created event to the brand’s active webhook, configured under Content → Configure Webhook. This works on self-hosted instances too, where it is the only delivery channel. The webhook payload contains the same KPIs, highlights and warnings as the email, plus the pulse date, the frequency and a link to Insights. The frequency setting applies to the webhook as well: Off sends nothing, Weekly sends on Mondays only. The recipient list does not. See Webhooks for the full payload, field reference and delivery rules.