What does the Slack integration actually do?

It's outbound — Admaxxer posts notifications and digests into a Slack channel of your choice. Low-ROAS alerts, daily MER summaries, trial-end reminders, AI-agent destructive-action confirmations. It's not for ingesting Slack data into Admaxxer.

How do I attribute revenue from Slack-shared links today?

Two paths. (1) Auto: the pixel's smart-referrer classifier (GL#361) already maps slack.com referrers to utm_source=slack — no tagging needed for organic Slack shares. (2) Manual UTM tagging: append ?utm_source=slack&utm_medium=social&utm_campaign= to internal-share links if you want per-thread or per-campaign granularity.

When will the native Slack integration ship?

In active development. Star the integration on /integrations to be notified.

Can I get email digests in the meantime?

Yes. Daily and weekly digests are already supported via /dashboard/notifications — the same digest content will be routable to Slack once native lands.

Coming soon · Slack integration

Slack integration — coming soon

Native API integration for Slack is in active development. Until then, you can attribute every Slack dollar today with a two-step UTM-and-pixel bridge: tag your Slack URLs with the UTM template below, paste the Admaxxer pixel on your storefront, and our 30-platform smart-referrer classifier (per GL#361) auto-attributes revenue with 365-day first-touch persistence.

Star the integration on /integrations FAQ

The bridge — use our pixel + UTM tagging today

Three steps. About five minutes total.

Step 1 — Install the Admaxxer pixel

If you haven't already, drop the Admaxxer pixel into your storefront's <head>. Works on Shopify, WooCommerce, BigCommerce, Squarespace, Wix, Webflow, and any custom storefront. See install instructions for 35+ platforms.

Step 2 — Tag every Slack URL with UTMs

In the Slack UI, append these query parameters to every destination URL:

utm_source=slack — identifies Slack as the source
utm_medium=social — categorizes the channel type
utm_campaign=<your_campaign_name> — for per-campaign breakdown in MER, ROAS, and cohort LTV
utm_content=<creative_or_keyword> — optional, for per-creative reporting

Example tagged URL:

https://yourstore.com/black-friday?utm_source=slack&utm_medium=social&utm_campaign=internal-bf-share-2026&utm_content=hero-creative

Step 3 — Revenue auto-attribution kicks in

The first time a visitor lands on your site from a tagged Slack URL, the Admaxxer pixel writes the UTM tuple into localStorage for 365 days. Slack doesn't expose a per-click ID parameter, so first-touch UTM persistence (365 days) is the canonical attribution path. When the visitor checks out — even months later, even from a different device that we stitch via email_hash — the order is attributed back to the original Slack campaign on the visitor_payments row.

Tag once, our 30-platform classifier (including AI-chat referrers) does the rest.

What's already working today via UTMs

Revenue attribution per campaign — both last-touch and first-touch, on every order row.
Click-ID coverage — first-touch UTM persistence covers attribution; no click-ID needed for this platform.
Cohort LTV by acquisition campaign — 7 / 30 / 90-day windows, partial-refund-aware.
MMM contribution analysis — the channel shows up in the geometric-adstock model with full per-campaign granularity.
Cross-session stitch — first-touch UTMs persist 365 days, so a click in March that converts in August still attributes correctly.
One classifier, every channel — tag once and the 30-platform smart-referrer classifier (including AI-chat traffic) handles the rest with no per-source config.

What native integration will add when shipped

UTM tagging gets you accurate revenue-side attribution today. Native API integration adds spend-side reconciliation and platform-side reporting depth:

Real-time low-ROAS alerts pushed into a Slack channel.
Daily / weekly revenue + MER digests rendered as Slack canvases.
Inline Slack interactivity for AI-agent destructive operations (pause campaign, scale spend) with explicit confirmation.
Trial-end and quota-warning notifications routed to your team's billing channel.

Slack specifics

The Slack integration on /integrations is alert + digest delivery into a Slack channel — sending Admaxxer's outbound notifications (low-ROAS warnings, trial-end reminders, daily revenue digests) into your team's workspace. That's distinct from attribution. For attribution: when teammates share product links in Slack threads, UTM-tag them so internal-share traffic is correctly bucketed as utm_source=slack&utm_medium=social. The 30-platform classifier already covers slack.com referrers (per GL#361), so even un-tagged Slack-shared links resolve to utm_source=slack.

Frequently asked

What does the Slack integration actually do?: It's outbound — Admaxxer posts notifications and digests into a Slack channel of your choice. Low-ROAS alerts, daily MER summaries, trial-end reminders, AI-agent destructive-action confirmations. It's not for ingesting Slack data into Admaxxer.
How do I attribute revenue from Slack-shared links today?: Two paths. (1) Auto: the pixel's smart-referrer classifier (GL#361) already maps slack.com referrers to utm_source=slack — no tagging needed for organic Slack shares. (2) Manual UTM tagging: append ?utm_source=slack&utm_medium=social&utm_campaign=<name> to internal-share links if you want per-thread or per-campaign granularity.
When will the native Slack integration ship?: In active development. Star the integration on /integrations to be notified.
Can I get email digests in the meantime?: Yes. Daily and weekly digests are already supported via /dashboard/notifications — the same digest content will be routable to Slack once native lands.

Next steps

Install the Admaxxer pixel — 35+ platforms supported.
UTM best practices — canonical UTM templates for every channel.
Revenue tracking deep-dive — how the 30-platform classifier and 365-day first-touch model work end-to-end (GL#361).
Star the Slack integration on /integrations — you'll be notified the moment native API support ships.