Automated Eloqua Deliverability Monitoring
Every morning, WebRun opens Oracle Eloqua, reads the hard bounce, soft bounce, unsubscribe and complaint rates for every campaign sent in the last 24 hours, compares each against your acceptable thresholds, posts the results to Microsoft Teams, and WhatsApps the email owner when a send crosses the line.
How do I monitor Eloqua bounce and unsubscribe rates after every send?
WebRun opens Oracle Eloqua every morning and reads hard bounce, soft bounce, unsubscribe, and complaint rates for every send from the last 24 hours. It posts the check to Microsoft Teams against your thresholds and WhatsApps the campaign owner whenever a send breaches, before deliverability suffers.
- A bad list is caught after one send, not after five
- Campaign owners hear about a breach the next morning
- Pausing and suppressing stay in human hands
Built for marketing operations · email marketers · demand generation teams · enterprise marketers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
login.eloqua.comin a real browser with your saved login - no setup, no API keys. -
1
Oracle Eloqua - read bounce and unsubscribe rates
- Sign in to Eloqua and open the campaign analysis views for sends in the last 24 hours
- Capture delivered volume, hard bounces, soft bounces, unsubscribes, and complaints for each send
- Work out each rate as a percentage of delivered and compare it with your acceptable threshold and with the same campaign's previous send
Done when Every send from the last 24 hours has its bounce, unsubscribe, and complaint rates against threshold.
-
2
Microsoft Teams - post the deliverability check
microsoft.com
WebRun opens Microsoft Teams to post the deliverability check. - Post yesterday's sends to the marketing operations channel, worst hard bounce rate first
- Show delivered volume with each rate beside its threshold so the gap is obvious
- Name the segment or list behind any send that breached, since the list is usually the cause
Done when Yesterday's deliverability check is in the marketing operations channel.
-
3
WhatsApp - warn the email owner
whatsapp.com
WebRun opens WhatsApp to warn the email owner. - Message the owner of any campaign that crossed a threshold, with the rate and the list involved
- Recommend pausing the next send on that list until it is cleaned
- Leave pausing campaigns, suppressing contacts, and editing lists to a human inside Eloqua
Done when Every breaching campaign owner has been warned, or the day is confirmed clean.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it pause a campaign or suppress contacts by itself?
No. WebRun reads the numbers and recommends. Pausing a campaign, suppressing a contact, or editing a segment stays with a human inside Eloqua, so no live campaign is stopped without a decision.
What thresholds does it use?
The ones you set. A common starting point is flagging hard bounces above 2 percent, unsubscribes above 0.5 percent, and any complaint rate rise against the same campaign's previous send.
Does it send a message every day?
The Teams post goes up daily so the trend stays visible. The WhatsApp warning only fires when a send actually crosses a threshold, so it stays worth reading.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.