How to connect Elo to Zapier for automated ad revenue alerts

Manually checking the Elo dashboard for revenue swings means you find out about a fill-rate crash or a spend spike a day late. Instead of refreshing a dashboard every few hours, wire Elo's revenue events into Zapier so a Slack message, email, or spreadsheet row fires the second something worth knowing happens.

Why this matters

Ad revenue from a conversational ad SDK moves in bursts tied to advertiser spend, not steady traffic curves. A publisher running Elo across an AI chat app can see RPM double on a Tuesday because one advertiser ramped budget, then flatline the next week when that campaign pauses. Checking a dashboard on a schedule misses both events until it's too late to react.

Zapier removes the polling problem. Once Elo fires a webhook on a revenue event, Zapier catches it and routes it wherever your team actually looks — Slack, email, a spreadsheet, or a CRM. You get a push notification instead of a dashboard habit, and 2026 advertiser spend on AI chat inventory moves fast enough that a same-day alert beats a weekly review every time.

Before you start

• An active Elo integration sending revenue or impression events — you need webhook access or an API key from your Elo account, not just the SDK installed in your app.
• A Zapier account on a plan that supports the Webhooks by Zapier app (basic Catch Hook triggers are available on Zapier's free tier).
• The gotcha: Zapier can't map fields from a payload it hasn't seen yet. If you build the Zap and hit Test trigger before a real ad event has fired through the webhook, Zapier returns nothing to map and the whole setup stalls at step 4. Fire one test event from your Elo integration first, then test the trigger.

Set up your Elo revenue webhook

1. In your Elo account, open the webhook or event-forwarding settings tied to your ad SDK integration and create an endpoint slot (you'll paste Zapier's URL into this in the next section).
2. Confirm which events your integration can forward — revenue events, impression events, and fill-rate events are the three most useful for alerting.
3. If your setup requires an API key for authenticated webhook delivery, generate one now and store it where your team can find it — you'll need it if the webhook call requires an auth header.

Expected result: you have an endpoint slot ready to receive a URL, and you know which event type you're alerting on.

Configure the Zapier trigger

1. In Zapier, click Create Zap.
2. Search for and select Webhooks by Zapier as the trigger app.
3. Choose Catch Hook as the trigger event and click Continue.
4. Zapier generates a unique webhook URL — copy it.
5. Paste that URL into the endpoint slot in your Elo integration settings from the previous section, then save.
6. Trigger one real event from your app (a single test ad impression or a small revenue event works) so a payload actually reaches Zapier.
7. Back in Zapier, click Test trigger. You should see the payload fields — revenue amount, timestamp, campaign or advertiser identifier if your integration forwards it — pulled in and ready to map.

Expected result: Zapier shows a sample payload with real field values, not an empty test.

Configure the alert action

1. Click + to add an action step.
2. Search for the app you want alerts delivered to — Slack, Email by Zapier, or Google Sheets cover most teams.
3. For Slack: choose Send Channel Message, pick the channel, and insert the payload fields (revenue amount, event type, timestamp) into the message text using Zapier's field picker.
4. For Google Sheets: choose Create Spreadsheet Row and map each payload field to a column — this doubles as a running log you can chart later.
5. Click Test action to confirm the message or row lands correctly.
6. Turn the Zap on by toggling it to Published.

Expected result: the test message or row shows real numbers from your Elo ad SDK activity, formatted the way your team wants to read it.

Variant: alert on payout events instead of every revenue event

Alerting on every single ad revenue event gets noisy fast once traffic scales past a handful of events per hour. A second, calmer workflow: trigger the Zap only on payout or settlement events rather than every impression-level revenue tick.

• Repeat the Catch Hook trigger setup above, but point your Elo integration's payout webhook (if it's separate from the revenue event stream) at a second Zapier webhook URL.
• Route this Zap to email instead of Slack — payout notifications matter to finance, not to the engineering channel getting pinged on every ad event.
• If your payout flow already runs through Stripe, connecting Stripe to automate ad revenue payouts gives you a second trigger point on the Stripe side instead of the Elo side, which helps if your Elo webhook only fires on revenue events and not on the payout itself.

Running both Zaps side by side — one revenue-event Zap to Slack for the team, one quiet payout Zap to email for finance — keeps each audience getting only what they need.

Troubleshooting

• Zap won't test successfully / no fields to map: you tested the trigger before a real event reached the webhook. Fire one manual test event through your integration, then retest.
• Slack message shows blank fields: the payload field names changed on the Elo side, which happens after an integration update. Catch a fresh hook and remap the fields in the action step.
• Alerts arrive but numbers look wrong: check whether your integration forwards gross or net revenue per event. A mismatch between what's logged in Elo and what's shown in Slack is usually a mapping error, not a data error.
• Too many alerts, channel gets noisy: add a Zapier Filter step between trigger and action so the Zap only fires above a threshold you set, instead of on every event.
• Zap runs but nothing shows up in the target app: check Zapier's task history for that run. Most silent failures are an expired auth token on the Slack or Sheets side, not the Elo webhook.

Customize your workflow

Once the base alert Zap is running, expand it rather than leaving it as a single Slack ping:

• Add a Filter step so only revenue events above a threshold trigger the alert — useful once daily event volume climbs.
• Fork the same webhook into a second Zap that logs every event to Google Sheets for a running 2026 revenue history, separate from the real-time alert.
• If your reporting needs go past Slack messages, building an ad revenue reporting dashboard covers turning the same event stream into charts instead of one-off alerts.

FAQ

One last thing

The biggest reason these Zaps break in production isn't the trigger — it's action-side auth tokens expiring quietly on Slack or Sheets while the webhook keeps firing fine. Check Zapier's task history monthly in 2026, not just when someone notices the alerts stopped.

Related guides

• Sync ad revenue to Google Analytics automatically
• Measure ad revenue per user in a chatbot
• Track ad impressions inside an AI chat app