Integration
Slack Conversion Drop Alerts
A conversion incident is only useful if the right person sees it in time. Quarkad delivers each one to Slack with the page, the metric that moved, and the likely cause already in the message.
What Quarkad sends
When a monitor raises an incident, Quarkad posts it to your Slack channel through an incoming webhook. The message is built to be triaged in place rather than to send you hunting through a dashboard:
- Severity, so a critical incident reads differently from a minor one at a glance
- The client name, so a shared channel stays readable across accounts
- The incident type — a metric drop, a connection issue, or a CRM handoff failure
- The affected page, and the metric that actually moved
- The ranked likely cause, when Quarkad reached a conclusion rather than guessing
Routing
Your workspace has one default destination — Slack or email — and every monitor inherits it. Any monitor can override that default, which is what makes per-client routing work: the client’s website monitors, ad connection monitors, and CRM handoff monitor can all report into that client’s own channel while the rest of the workspace keeps the default.
Deliveries are logged either way. A monitor that fires with no destination configured is recorded as skipped with that reason, so a missing webhook shows up as a gap you can fix rather than as silence you mistake for calm.
Example alert
Illustrative message.
🚨 CRITICAL [Northside Dental] metric drop Likely cause identified /free-consultation Submit rate 14% → 6% over the last hour Cause: Required field added to the consultation form at 14:12
Setup
- Create a Slack incoming webhook for the channel you want alerts in.
- Paste the webhook URL into Quarkad as your workspace's alert destination.
- Send a test alert to confirm it lands in the right channel.
- Optionally override the destination on individual monitors, so each client or funnel routes to its own channel.
Limitations
- Delivery is one-way. Quarkad posts incidents into Slack; it does not read your channels, and you cannot resolve an incident from Slack.
- Alerts depend on the monitors you enable — a layer with no monitor produces no alert.
- Monitors on paused funnels are skipped by design, and recorded as such.
- Ranked causes are likely explanations, not guarantees — always confirm before acting.
Frequently asked questions
- How do I connect Slack to Quarkad?
- With a Slack incoming webhook. Create the webhook for the channel you want alerts in, paste the URL into Quarkad as your alert destination, and send a test to confirm it lands. There is no Slack app to install and Quarkad never reads your messages.
- What does a Quarkad Slack alert contain?
- The severity, the client name, the incident type, the affected page, the metric that moved, and — when Quarkad reached a conclusion — the ranked likely cause. Enough to triage from the channel without opening the dashboard first.
- Can different clients or funnels alert to different channels?
- Yes. Your workspace has a default destination, and any individual monitor can override it. Agencies typically point each client's monitors at that client's own channel.
- Can I use email instead of Slack?
- Yes. Email and Slack are both supported destinations, and you can pick per monitor. Email is the default if you never set up a webhook.
- What happens if a Slack delivery fails?
- Quarkad retries a failed send with backoff, and records the outcome either way. Every delivery is logged as sent, skipped, or failed — including the reason it was skipped — so an alert never disappears silently.
- Will Slack get noisy?
- Alerts fire on monitors you enable, not on every fluctuation. Incidents are evaluated against the funnel's recent baseline, and monitors on paused funnels are skipped rather than delivered.
Keep going
Get the incident in Slack, not in next month's report.
Point Quarkad at a channel and let every conversion incident arrive with its likely cause attached.