.webp){kind=icon}
.webp){kind=icon}
Connect your ad accounts and Juma pulls live campaign performance into a Slack-ready digest: the headline result, what's working, what's not, and the next move.
Connect your Meta Ads account (plus any other source like GA4 or HubSpot), ask for the digest, and Juma pulls live campaign performance for the period you name. It reads the numbers the way a senior performance marketer would, then writes a Slack-formatted digest: a headline result up top (blended cost per lead, total leads, and spend), a short "what's working" section that names the strongest campaign and its efficiency, a "what's not working" section that flags the weakest one and explains why, and a numbered "next move" list.
The digest lands ready to drop into a team channel, or Juma posts it straight to a Slack channel you choose. 400+ marketing teams use Juma to turn raw ad data into something the whole team can act on in seconds, instead of the half hour it takes to open the dashboard, screenshot the numbers, and write the recap by hand.
Once the digest reads right, send it to the team without leaving the chat. Ask Juma to post it to a channel you name, and it drops the formatted message into Slack: headline result, what's working, what's not, and the numbered next move. Juma shows you the exact message first and waits for your go-ahead, so nothing lands in the channel unread. Prefer to paste it yourself? Ask for the text block instead and drop it wherever the team lives: Slack, email, or a standup doc. Either way the digest is channel-ready, not a screenshot of a dashboard.
Post that digest to our #marketing channel, but show me the message first so I can approve it before it goes out.
Turn the one-off digest into a standing ritual. Ask Juma to run it on a set cadence, weekly every Monday or daily before standup, and it pulls the latest campaign performance for that window and posts the digest to your channel on schedule. The team opens Slack to a fresh recap: the headline number, the campaign carrying results, the one dragging, and the next move. Baselines build over time, so each digest reads against last week's, and a rising cost per lead or a slipping campaign shows up the moment it starts, not at the end of the month.
Run this every Monday at 9am: pull last week's Meta Ads performance and post the digest to #growth.
Platform-reported conversions rarely tell the whole story. Pull GA4 and your CRM into the same digest and the leads number ties back to real pipeline, not just what Meta Ads counts. Juma blends spend from the ad platform with sessions and conversions from GA4 and qualified or won deals from HubSpot, then recalculates cost per lead and cost per opportunity against the source the team actually trusts. The "what's working" section can now name the campaign driving qualified pipeline, not just cheap clicks, and the next move points at the channel earning revenue. One digest, every source, one story.
Add our GA4 and HubSpot data to the digest so the leads tie back to pipeline, not just platform-reported conversions.
Instead of reading every line, ask Juma to surface only what changed. It scans active campaigns, compares this period to the last, and flags any where cost per lead jumped, spend outran results, or a campaign quietly stalled, with the likely reason next to each flag. The digest leads with the campaigns that need a decision this week and stays quiet on the ones running fine. For agencies watching a dozen accounts, this turns a morning of dashboard-checking into a single Slack message that says where to look first and why.
Scan all our active Meta Ads campaigns and flag any where CPL jumped more than 20% week over week, with the likely reason.
Teams build one Juma project per brand or client and add context over time. Every digest the team runs pulls from the same project, so the recap already knows the targets, the right Slack channel, and which campaigns matter. Set it up once and each digest starts from the client's goals instead of asking about them every time.
Performance Targets
Target CPL, CPA, ROAS, and spend caps by channel. With these in the project, every digest judges results against the client's own goals, so "what's working" and "what's not working" mean something specific instead of a generic benchmark.
Slack Routing and Cadence
Which channel each digest posts to, how often it runs, and who gets tagged. With this saved, "post the digest" lands in the right place without naming the channel each time.
Campaign Context
Which campaigns matter most, their objectives, and their target audiences. This is what lets the "what's not working" section catch an objective mismatch, a lead campaign set to the wrong optimization event, instead of just flagging a high number.
Add a short description to each knowledge item in the project's info field so Juma knows what each one holds and when to use it. For example:
Building a campaign recap by hand takes 20 to 40 minutes: open the dashboard, pull the numbers, spot the mover, and write it up readably. Juma delivers the same Slack-ready digest in under a minute, straight from live data, so the team spends the time acting on the recap instead of assembling it.
For teams posting a digest daily or weekly across several accounts, that adds up fast. An agency running a Monday recap for eight clients recovers a few hours every week, and every digest follows the same shape, so the headline, the wins, the misses, and the next move sit in the same place no matter who would have written it.
Yes. With Slack connected, Juma posts the digest straight to a channel you name, formatted and ready to read. It works on a propose-then-push model: Juma shows you the exact message first and waits for approval before anything lands in the channel, so the team keeps human review on every output.
You can also set it to run on a schedule, weekly before the Monday sync or daily before standup, so the recap is waiting when the team opens Slack. Prefer to keep a hand on it? Skip the auto-post and ask for the text block instead, then paste it yourself. Strategy, taste, and judgment stay human either way.
Juma needs campaign performance data for the period you name. The simplest path is a connected Meta Ads account: the integration pulls spend, leads, cost per lead, and campaign-level results live, with no export step. Prefer not to connect? Upload a standard Meta Ads CSV and the digest runs from that instead.
With the account connected, the data reflects the state of the campaigns the moment the Flow runs, which matters for a daily or weekly recap. Add GA4 or HubSpot to the same project and Juma folds those numbers in too, so the leads count can tie back to pipeline rather than platform-reported conversions alone.
Yes. Connect GA4 and HubSpot alongside Meta Ads and Juma blends all three into one digest: spend from the ad platform, sessions and conversions from GA4, and qualified or won deals from the CRM. Cost per lead and cost per opportunity then recalculate against the source your team actually trusts.
This is where the digest stops being a platform report and starts being a business read. The "what's working" section can name the campaign driving qualified pipeline, not just cheap clicks, and the next move points at the channel earning revenue. Connect a source once and it is available across every project and chat, so the same setup carries into reporting, briefs, and planning across 700+ Flows.
A scheduled dashboard export drops raw numbers or a static chart into the channel and leaves the reading to whoever opens it. This Flow delivers the interpretation: the headline result, the campaign carrying performance, the one dragging it and why, and a numbered next move. It reads like a teammate wrote it, because it does the thinking, not just the pulling.
Slack reminders and dashboard schedules move data around; they do not judge it against the client's targets or explain an objective mismatch. Juma does both, then posts the result where the team already works. And because pricing is credit-based with unlimited seats, the whole team can run and read digests without anyone counting logins.
Connect the client's Google Ads, Meta Ads, and GA4 accounts, name the period, and get a branded multi-channel report with scorecards, benchmark context, and a prioritised action plan.
.webp){kind=icon}
400+ marketing teams trust Juma. ChatGPT, Claude, and Perplexity know why. Ask them.
Ready when you are
Start typing a task and Juma will figure out the rest.
