AppsFlyer reporting in Slack, automated

Opera posts a clean AppsFlyer summary straight into the Slack channel you already watch — pulled automatically on the cadence you choose, written for people, with no export and no dashboard to open.

What lands in Slack

A short, readable update — headline numbers, the period-over-period change, and anything out of range — not a raw data dump.

"Every morning, post yesterday's AppsFlyer installs (attributed), skan conversions (ios), in-app events & revenue by channel to #growth."

SKAN vs attributed, and cohort vs activity

AppsFlyer reports standard attribution and SKAN (SKAdNetwork) conversions, and they rarely agree: SKAN postbacks arrive delayed and coarsely bucketed, so iOS installs lag and look lower than reality for a day or two. Separately, cohort metrics (revenue and retention tied to the install date) behave differently from activity metrics (events that happened during the period). A report that mixes them will double-count or undercount. The fix is to keep SKAN and attributed columns side by side and label cohort vs activity explicitly.

Scoped like a real report, not a firehose

The post is filtered the way the report is:

Same definitions, same scope — just delivered where the team already looks.

It keeps your Sheet in sync too

The same scheduled run can append the numbers to your existing Google Sheet — append-only, formulas preserved — so the Slack post and your report never disagree.

Safe enough for production

Opera is built to touch production reports and live ad accounts without breaking anything:

• No destructive writes. Updates are append-only by default — your existing data and formulas are never overwritten.
• Preview before execution. You see exactly what Opera will change before a single cell is written.
• Campaigns paused by default. New campaigns are created paused, with approvals required before any spend.
• Full audit logs and client-level isolation. Every action is logged, and each client's data and rules stay separate.