Email governance5 min read
When your emails start arguing with each other
Too much email is annoying. Email that contradicts itself is worse because now you look like you have no idea who you’re talking to.
Read the article
Resources
Guides and articles for Eloqua and Marketo teams
Things we’ve learned working inside large Eloqua and Marketo instances, mostly about how the platforms behave at scale and what to do when they stop doing what you need.
More guides and articles
Email governance5 min read
AI can write 50 emails before lunch. Please don’t send all of them.
For years the slowest part of email marketing was writing the email. Annoying, but it also kept send volume in check. AI got rid of the wait and now somebody has to decide how much email your contacts get.
Guide6 min read
Fatigue Analysis in Oracle Eloqua
Fatigue Analysis tells you which contacts are getting more email than they want but it doesn’t send them any less. That is left to your campaigns and it takes more than one decision step to get right.
Guide4 min read
Letting contacts choose how often they hear from you in Eloqua
Eloqua lets contacts choose which kinds of email they get or none at all, but not how many. A contact who just wants less email can only get it by unsubscribing.
Guide5 min read
Marketo communication limits, rebuilt in Eloqua
Teams moving from Adobe Marketo Engage to Oracle Eloqua tend to notice the missing setting after their first heavy week. Marketo caps email per person on one admin screen. Eloqua has no such screen so each thing those limits did for you has to be rebuilt.
Guide5 min read
Send Time Optimization in Oracle Eloqua
Send Time Optimization holds each email until the hour its contact usually opens. While the email waits no other campaign knows it is coming, which is how an optimized email can slip past a frequency cap.
Email governance6 min read
Email fatigue: the conversation killer
Nobody unsubscribes over one email. It’s the tenth one that week that does it. A few ways to tell whether your contacts are getting sick of hearing from you and what to do before they tune out for good.
Guide7 min read
Knak, Stensul, Jeto and Campaign Launchpad compared
All four promise the same thing: marketers get campaigns out without waiting on Marketing Ops. They keep that promise at different points. Two of them build the email and two build the whole campaign, and the difference decides who still has to open Eloqua or Marketo.
Email governance3 min read
Who owns the inbox when every team can send?
Self-service email means every team can reach your contacts whenever it needs to. Nobody is deciding how much all of that adds up to and your contacts will notice before you do.
Guide4 min read
Email frequency limits in Oracle Eloqua
Eloqua can tell you how much email each contact receives, but it has no setting that stops them receiving more. Many teams build their own cap, and it holds until campaigns start sending at the same time.
Case studies and white papers
Longer reads you can download as a PDF and pass around your team.
Case study
How Broadcom got dozens of divisions onto one set of email rules
How Broadcom got send volume under control across dozens of divisions and brands with one shared set of frequency rules built with DemandByte.
Get the PDF
Case study
How 3M enabled 250 senders and got 5,000 hours back
How 3M moved 250+ users onto Campaign Launchpad and cut campaign build time from hours to minutes while keeping every region on brand without adding headcount.
Get the PDF
White paper
Why waiting for sales to qualify is killing conversion rates
A DemandByte white paper on reaching prospects while they’re still interested and what that does for lead quality and sales engagement.
Get the PDF