Schedules and Alerts
Configure recurring tracker and AI Visibility runs without creating noisy campaigns.
Schedules decide when campaigns run. Alerts decide which changes should be brought to your attention.
Schedules and alerts are available in tracking tools and AI Visibility workflows.
Schedule frequency
Section titled “Schedule frequency”Campaigns can run on a recurring schedule. Common options include:
- daily
- weekly
- monthly
Use the lowest frequency that still supports the decision you need to make.
| Workflow | Recommended starting frequency |
|---|---|
| New SEO campaign validation | Weekly |
| High-priority rank monitoring | Daily or weekly |
| PPC brand protection | Daily |
| Competitor ad monitoring | Weekly |
| AI Visibility market monitoring | Weekly |
| Monthly client reporting | Monthly or weekly |
Time and timezone
Section titled “Time and timezone”Schedules include a time and timezone. Choose the timezone used by the team or market reviewing the data.
If a organization serves multiple regions, create separate campaigns by region instead of relying on one ambiguous schedule.
Active and paused campaigns
Section titled “Active and paused campaigns”Only active campaigns run on schedule. Paused campaigns keep their setup and past results but skip scheduled runs.
Pause a campaign when:
- the client engagement ended
- the market is no longer being tracked
- the campaign is being revised
- token usage should stop temporarily
Manual runs
Section titled “Manual runs”A manual run executes the campaign immediately. Use manual runs to:
- test a new campaign
- refresh data before a meeting
- validate changed settings
- investigate an unexpected movement
Manual runs can spend tokens. Review estimated usage before running large campaigns.
How alerts are evaluated
Section titled “How alerts are evaluated”Every alert compares two windows of runs: the three most recent runs against the three before them. A campaign therefore needs at least four completed runs before it can raise anything, and one bad run never fires an alert on its own.
The evaluation is built to stay quiet when the data is not a reading:
- A window where most checks failed is skipped entirely. A bad afternoon on our network is not a keyword that stopped ranking or an ad that stopped showing.
- Position alerts score a keyword the domain does not rank for at all as position 101, one past the top-100 depth. Losing a ranking is a fall, not a keyword that quietly stops counting. Only keywords checked in both windows are compared, so a keyword you just added cannot trigger a drop.
- “Entered the top 10” and “left the top 10” are about whether the domain is on page one for any tracked keyword, not about the average.
- AI Visibility swings must be both material and larger than sampling noise at the campaign’s size. A small campaign alerts only on dramatic moves; a large one on modest ones.
- Competitor ad alerts fire when a competitor starts advertising, not for every run in which an existing advertiser is still there.
Once an alert has been raised, the same event is not raised again as the windows slide past it. The same kind of alert fires again only for a later pair of windows that shows the change on its own, for example a ranking that keeps falling week after week, or when its severity escalates.
Where alerts go
Section titled “Where alerts go”- In the app: every alert appears in the campaign’s alert feed and, for organization owners, in notifications, the moment it is raised.
- Webhook: if the campaign has a webhook URL, every alert is posted to it immediately.
- Email: alerts are batched per organization. Owners receive at most one alert email per hour, carrying every alert raised across all campaigns since the last one, grouped by campaign. A lone alert can therefore take up to an hour to reach the inbox. Each owner can turn alert emails off in their notification preferences, and each campaign can be kept out of the email with its “Email alerts” setting without affecting the in-app feed or the webhook.
Alert types
Section titled “Alert types”SERP Position Tracker
Section titled “SERP Position Tracker”Position alerts can detect:
- entered top 10
- left top 10
- position changes
Ads Position Tracker
Section titled “Ads Position Tracker”Ad alerts can detect:
- ad started
- ad stopped
Maps Visibility
Section titled “Maps Visibility”Maps alerts can detect:
- reached the top 3 somewhere on the grid
- dropped out of the top 3 across the whole grid
- Local Presence Score moved by 10 points or more
AI Visibility
Section titled “AI Visibility”AI Visibility alerts can detect:
- visibility appeared
- visibility lost
- visibility rose
- visibility fell
- new sponsored placement
- sponsored placement stopped
- competitor sponsored activity
Avoid noisy alerts
Section titled “Avoid noisy alerts”Good alerts are tied to action. Before enabling an alert, ask:
- Who receives it?
- What decision will it trigger?
- Is this change meaningful enough to interrupt someone?
- Would a weekly review be better than immediate notification?
Webhook alerts
Section titled “Webhook alerts”Some workflows can send alert payloads to a webhook URL. Use webhooks for automation, dashboards, Slack-style workflows, or internal incident/reporting systems.
Webhook URLs must be public HTTP endpoints that can accept POST requests.
Open in iSearchFrom
Section titled “Open in iSearchFrom”Open SERP Position Tracker in the app. Open the tracker or AI Visibility campaign, then edit its schedule and alert settings.