Reports and Notifications
Adsafee lets you automate report delivery, share reports with colleagues, and receive operational alerts about suspicious traffic spikes.
Scheduled Reports
You can set up automatic report delivery on a schedule. Open the desired report in Statistics and click Schedule.
| Setting | Description |
|---|---|
| Frequency | From every 30 minutes to monthly |
| Data period | The time range the report covers (last hour, day, week, etc.) |
| Delivery channel | Where to send it (Email, Slack, Telegram) |
| Expiration | When to stop sending (optional) |
Scheduled reports can be paused and resumed in the Reports section -> Scheduled Reports tab.
Delivery Channels
Before creating a scheduled report or alert, set up at least one channel:
| Channel | Description |
|---|---|
| Reports and alerts are sent to the specified email address | |
| Slack | Delivery via Incoming Webhook. Step-by-step setup instructions are available in the interface |
| Telegram | Delivery via bot. Both private messages and group chats are supported |
| Webhook | POST request to your HTTPS endpoint. Requests are signed with the channel secret |
Testing
Any channel can be tested before use — the Test button sends a test message.
Note
Scheduled reports support Email, Slack, and Telegram. Fraud alerts can be delivered to Email, Slack, Telegram, or Webhook channels.
Fraud Alerts
Alerts automatically detect traffic metric spikes. Open Alerts and click New alert.
An alert rule consists of scope, conditions, schedule, and delivery channel:
| Setting | Description |
|---|---|
| Integration | Required integration whose traffic will be evaluated by the rule |
| Group by subs | Which sub1-sub6 fields to group traffic by. The default is sub2:sub3 |
| Conditions | Condition groups over quantitative and percentage metrics. Supported operators: greater than, at least, less than, at most, equals, not equals |
| Period | The recent traffic window to aggregate: 5, 10, 15, 30 minutes, 1 hour, 3 hours, 6 hours, or 12 hours |
| Frequency | How often to evaluate the rule: 5, 10, 15, 30 minutes, or 1 hour |
| Cooldown | How soon the same zone can trigger another alert. Options: off, 30 minutes, 1 hour, 2 hours, 4 hours, or 1 day |
| First check | Schedule the first run in the future or leave empty to start immediately |
| Channel | Email, Slack, Telegram, or Webhook delivery channel |
On each check, Adsafee aggregates events for the selected period, groups them by the selected sub fields, and creates an alert event for every zone where the conditions match. To avoid repeated notifications for the same issue, the rule applies its cooldown to the same combination of rule, integrations, and zone.
Previewing a rule
Before saving, click Preview. Adsafee shows how many events would trigger in the current window, the matched zones, and a sample delivery payload.
Event History
The Events tab in Alerts shows all triggered alert events. You can filter by status and search by rule name, zone, grouping, or channel.
| Status | Meaning |
|---|---|
| Pending | The event was created and delivery is not finished yet or is waiting for retry |
| Delivered | The notification was successfully sent to the channel |
| Failed | Delivery failed |
Event details include the evaluation window, zone, metrics, attempt count, delivery error, and technical payload context.
Alert Webhooks
A webhook alert is sent as a POST request with a JSON payload:
{
"schema_version": "fraud_alert.v1",
"event_id": "string",
"rule": { "id": 123, "name": "High fraud by zone" },
"workspace_id": 1,
"integration_id": 10,
"zone": { "grouping": "sub2:sub3", "key": "source:campaign" },
"window": { "minutes": 10, "start": "2026-06-11T10:00:00+00:00", "end": "2026-06-11T10:10:00+00:00" },
"conditions": {},
"metrics": { "hits": 120, "givt_total_rate": 35 },
"context": { "top_countries": ["US"], "top_asns": ["Example ASN"] }
}The request includes these headers:
| Header | Description |
|---|---|
X-Adsafee-Event-Id | Unique event ID |
X-Adsafee-Timestamp | Unix timestamp of the request |
X-Adsafee-Signature | HMAC-SHA256 signature in the sha256=<hex> format |
The signature is calculated over <timestamp>.<raw_body> using the webhook channel secret. The endpoint must be an HTTPS URL without username or password; private, loopback, and reserved IP addresses are blocked.
Limits
Each workspace can have up to 20 alert rules. A single rule creates at most 50 events per evaluation cycle, and a workspace creates at most 200 events per cycle.
Sharing via Link
In Statistics, click Share to create a public link to the current report.
INFO
The link works without authentication — you can send it to a client or colleague who does not have an account. When creating the link, you can set an expiration date or make it permanent.
All shared links are visible on the Shared Links tab in the Reports section, where they can be copied or deleted.
Export
Data from Statistics can be exported to CSV or Excel via the Export button in the toolbar.
What's next
- Set Up Scheduled Reports — step-by-step instructions
- Track Quality by Campaign — what to analyze in reports
- Metrics Reference — which metrics can be used in alert conditions