Skip to content
Browse documentation

Automation overview

The Automation hub — alerts, scheduled reports and changes, offer link checks, optimisation rules, partner messages, webhooks and your notifications — and the background jobs behind them.

Last updated 4 min read

On this page

Reporting → Automation (/app/automation) collects everything the worker does for your workspace on a schedule. Analysts can view most tabs (the Webhooks tab needs a manager); creating and changing automation needs a manager role or higher, and managing webhooks an admin.

The tabs#

TabWhat it doesArticle
OverviewKPI cards, automation settings and recent cap alerts.This page
KPI alertsNotify when a metric crosses a threshold over a rolling window.KPI alerts
Scheduled reportsE-mail a saved report view as CSV daily, weekly or monthly.Scheduled reports
Scheduled changesChange offer status, payout or caps at a set time.Scheduled changes
Offer link checksFollow every active offer's destination daily and flag broken links.Below
OptimisationRules that notify, block sources or pause offers by CR, conversions or EPC.Optimisation rules
Partner messagesE-mail announcements to partners.Below
WebhooksSigned JSON events to your systems.Webhooks
My notificationsWhich events reach you in the bell and by e-mail.Below

Overview tab#

KPI cards: Active KPI alerts (with triggers in the last 7 days), Scheduled reports, Pending scheduled changes, Broken offer links, Active webhooks (with failed deliveries in 7 days) and Cap alerts (recent).

Automation settings#

"Background jobs run by the worker for this workspace."

SettingEffect
Cap alertsNotify staff once per period when a cap reaches 90 % and 100 % (checked every minute). See Cap alerts and pacing.
Tell partners about their capsAffiliate-level caps also notify that partner in the partner portal.
Daily offer link checkFollow every active offer's destination once a day (up to 10 redirects) and flag broken links.
Pause offers with broken linksPause an offer after 3 failed checks in a row (audited, staff notified).

The worker wakes hourly and checks each active offer at most once a day. It requests the offer's destination URL (macros replaced by neutral sample values) with a Chrome user agent and follows up to 10 redirects, recording every hop. Only public addresses are fetched.

ResultMeaning
OKFinal status below 400 within 10 hops.
Broken / Broken · pausedNetwork error, final status ≥ 400 or more than 10 hops; "paused" when auto-pause applied.
Host differs from previewThe final host is not the host of the offer's preview URL.
Not checked yetNewly active offer.

Columns: Offer, Result, Status, Hops, Final URL, Checked and hidden Failures in a row. Use Check again on a row to re-check now. Staff are notified once when an offer turns broken. Results are kept 90 days.

Partner messages#

Send e-mail announcements — new offers, payout changes, holiday schedules — to all partners or a segment.

  1. Click New partner message (optionally Start from a template).
  2. Enter Subject and Message.
  3. Choose the Audience: a saved audience or Custom rules… — Partner status, Tags, Account manager, Approved on offers, Only these partners. Every set condition must hold.
  4. Under Send, send now or at a date and time.

Each partner address gets its own e-mail with a one-click unsubscribe link (/unsubscribe/<token>). Unsubscribed partners and partners without an address are logged as skipped. Open a message for the Per-recipient delivery log. Templates and Audiences can be saved for reuse. Sending requires outgoing e-mail (SMTP).

My notifications#

Each user chooses which events reach them in-app (the bell) and by e-mail:

EventDefault
Offer status changesIn-app
Partner sign-upsIn-app
Offer access requestsIn-app
Caps reachedIn-app
Invoices createdIn-app
New-device sign-insIn-app and e-mail

Teammates set their own preferences.

Jobs behind the scenes#

JobRuns every
KPI alerts, scheduled reports, partner messages1 minute (panel cron)
Cap alerts, scheduled changes1 minute
Offer link checks, optimisation rules1 hour
Webhook delivery2 seconds
Notification dispatch30 seconds
Something unclear or missing in this article?Tell us