Checking the Elo dashboard every morning to copy revenue numbers into a spreadsheet is a job for a script, not a person. Instead of manually pulling CPM, fill rate, and RPM figures from Elo each day, wire a Make.com scenario that pulls the numbers on a schedule and drops them into Slack, Google Sheets, or email automatically.
- Make.com ad revenue reporting automation pulls Elo's revenue data via API and pushes it to Sheets or Slack on a schedule.
- Elo's adserver exposes revenue and event data per app; Make.com's HTTP and JSON modules do the parsing without code.
- A basic daily-digest scenario takes under 30 minutes to build on Make.com's free tier.
- Real-time revenue-threshold alerts use the same trigger with a filter step instead of a fixed schedule.
- Most setup failures trace back to an unscoped or expired Elo API key, not a broken scenario.
Why this matters
Manual reporting doesn't scale past one app. If you run ads across two or three AI chat products through Elo's SDK, checking each dashboard separately and reconciling revenue by hand eats an hour a week you don't get back. In 2026, a Make.com scenario that fires once a day costs nothing beyond the Make.com plan you're already on, and it never forgets to run.
The other reason this matters: revenue visibility drives decisions. If your ad-supported chatbot's RPM drops 15% week over week, you want a Slack message the next morning, not a discovery three weeks later when you're reconciling a quarterly report. Automated reporting turns Elo's revenue data into a standing signal instead of a manual chore.
Before you start
- An Elo account with an active API key. Generate this from your Elo dashboard settings — treat it like a password, since it reads live revenue data.
- A Make.com account. The free tier supports scheduled scenarios; heavier daily-report volumes may need a paid plan once you exceed the free operation quota.
- A destination connected in Make.com — Google Sheets, Slack, or an email module, depending on where you want the report to land.
- The gotcha: Make.com's free plan runs scenarios on 15-minute minimum intervals and caps monthly operations. If you're also running the Elo-to-Zapier alert workflow described in connect Elo to Zapier for ad revenue alerts on the same account tier, your Make.com scenario and any parallel automation will compete for the same quota — plan your call frequency before you build, not after you hit the cap mid-month.
Set up your Elo data trigger
- In Make.com, create a new scenario and add an HTTP module as the first step.
- Select Make a request, set the method to GET, and enter your Elo revenue endpoint URL.
- Under Headers, add an entry with key Authorization and value Bearer followed by your Elo API key.
- Click Run once to test the connection.
Expected result: the module returns a JSON payload with revenue, impression, and RPM fields for the date range you queried. If you get a 401 response, the API key is wrong or expired — regenerate it from the Elo dashboard before continuing.
Parse and map the revenue data
- Add a JSON > Parse JSON module right after the HTTP step.
- Feed it the Body output from the HTTP module.
- Map the fields you care about — revenue, CPM, fill rate, impressions — as separate variables for the next step.
Expected result: each metric now appears as its own selectable field in the scenario's data mapping panel, ready to drop into a spreadsheet row or a message template.
Send the report to Google Sheets or Slack
- Add a Google Sheets > Add a Row module (or a Slack > Create a Message module) after the JSON parser.
- Map the parsed fields — date, revenue, CPM, RPM — into the corresponding row columns or message text.
- For Slack, format the message with a short summary line, for example: revenue for the last 24 hours, CPM, and fill rate in plain text.
- Run the scenario once manually to confirm the row lands or the message posts correctly.
Expected result: a new row appears in your sheet, or a message posts to the configured Slack channel, with the previous day's Elo revenue numbers.
Schedule the scenario
- Click the scenario's clock icon and set the schedule to Daily at a fixed time — early morning works well since it reflects the full prior day.
- Save and toggle the scenario to ON.
Expected result: the scenario runs unattended every day at the scheduled time and the report updates without anyone opening the Elo dashboard.
Variant: real-time revenue-threshold alerts
Run the same scenario whenever revenue drops below a set number instead of waiting for the daily digest. Add a Filter step between the JSON parser and the Slack module, condition set to revenue < [your threshold]. Only messages meeting the condition fire, so the channel stays quiet on normal days and loud the moment RPM or fill rate falls out of range. This variant pairs well with a shorter polling interval — hourly instead of daily — since the point is catching a dip fast, not archiving history.
Get your Elo API key
Generate credentials and start pulling live ad revenue data into Make.com.
Troubleshooting
- HTTP module returns 401 Unauthorized. The API key is missing, expired, or malformed in the Authorization header — regenerate it in Elo and re-test.
- JSON Parse module errors on the response. The HTTP module likely returned an error page or empty body instead of valid JSON — check the raw response in Make.com's execution log before assuming the parser is broken.
- Rows or messages arrive duplicated. The scenario is probably scheduled to run more often than intended, or a previous run wasn't marked complete — check the scheduling interval first.
- Numbers don't match the Elo dashboard. Confirm the date range and time zone used in the HTTP request match what the dashboard displays; a UTC-vs-local mismatch is the usual culprit.
- Scenario stops running with no error. Free-tier Make.com accounts pause scenarios once the monthly operations cap is hit — check your usage panel before assuming the scenario itself failed.
Customize your workflow
A daily revenue row in a spreadsheet is the starting point, not the ceiling. Once the base scenario runs reliably, extend it:
- Push the same data into a live view instead of a static sheet — see build an ad revenue reporting dashboard for a setup that turns raw numbers into charts.
- Feed revenue events into your existing analytics stack by following sync ad revenue to Google Analytics, so ad performance sits next to your product metrics.
- Project where revenue is headed instead of just reporting where it's been — see forecast ad revenue for an AI chatbot.
- Close the loop from reporting to cash by pairing this scenario with automate ad revenue payouts via Stripe, so the same automation stack that reports revenue also triggers the payout.
Every one of these builds on the same three modules — HTTP request, JSON parse, destination write — you already set up here.
FAQ
How do I automate ad revenue reporting with Make.com in 2026?
Build a Make.com scenario with an HTTP module pulling Elo's revenue API, a JSON Parse module to map the fields, and a Google Sheets or Slack module to deliver the report on a schedule. The whole chain takes three modules and one API key.
Does Elo have a native Make.com integration?
Elo's adserver exposes a revenue API you connect through Make.com's generic HTTP module rather than a dedicated app listing. This works the same way as connecting Elo to Zapier — you're calling the API directly instead of using a pre-built connector.
Is Make.com better than Zapier for ad revenue automation?
Make.com's free tier generally allows more complex, multi-step scenarios than Zapier's free tier, which matters once you add filters or threshold alerts. Both tools work fine for a basic daily digest; the choice usually comes down to which automation tool your team already uses.
How much does Make.com cost for ad revenue reporting automation?
Make.com's free plan covers a basic daily scenario for most single-app setups; higher-frequency or multi-app scenarios may need a paid tier once you exceed the monthly operations quota. Check Make.com's current plan pricing directly since limits change.
Why is my Make.com scenario returning a 401 error from Elo's API?
A 401 error means the API key in your Authorization header is missing, expired, or malformed. Regenerate the key from your Elo dashboard settings and re-enter it in the HTTP module's headers.
Can I get real-time alerts instead of a daily report?
Yes — add a Filter module between the JSON parser and the destination step, set to trigger only when revenue or fill rate crosses a threshold you define. Run the scenario hourly instead of daily so the alert fires close to when the dip happens.
What data does Elo's ad revenue API return?
Elo's revenue API returns per-app metrics including revenue, CPM, RPM, impressions, and fill rate for a given date range. Exact fields available depend on your account's API access — check current API documentation for the full schema.
Do I need to know how to code to set this up?
No. Make.com's HTTP, JSON Parse, and destination modules are configured through dropdown fields and mapped variables, no scripting required. The only technical step is copying your Elo API key into the Authorization header correctly.
One last thing
The scenario described here reports revenue after the fact — yesterday's numbers, delivered this morning. If your goal is catching a monetization problem before it costs you a week of lost RPM, build the threshold-alert variant first and the daily digest second; most teams do it backwards and pay for it in a slow week they didn't notice until the monthly total came in low.
