Case Study · VMware
Global Eloqua operations, multilingual delivery and enterprise nurture programs
VMware operate at a scale most marketing teams never touch. Millions of contacts, dozens of audiences, 28 languages, multiple product pillars and year round outbound marketing. They needed someone who could architect and run an enterprise grade Eloqua operation with no room for error.
Client background
VMware are one of the biggest technology companies on the planet. Their global marketing operation spans every region, every vertical and every digital channel. Their Eloqua instance sat on Eloqua 9 with a database of more than 6 million contacts.
That kind of scale creates serious operational pressure. Slow load times, heavy program processing, multi language branching and constant campaign demand meant VMware needed more than template building. They needed someone who could treat Eloqua like critical infrastructure.
I worked as a senior Eloqua developer and consultant, helping them stabilise day to day work and deliver a flagship annual nurture program that reached almost every product category globally.
At a glance
- Database size: ~6,000,000
- Languages: 28
- Key work: BAU delivery + flagship nurture
- Platform: Eloqua 9
The challenge
VMware’s challenge was not a single campaign. It was the cumulative weight of scale. Multilingual complexity, product sprawl, legacy infrastructure and a constant stream of demand from the business.
28 languages and countless variants
Every major campaign needed localised versions, translated content and logic to route correctly by region, language and product.
Eloqua 9 under heavy load
With 6 million contacts, even small inefficiencies in segmentation or campaigns could slow the platform down and frustrate everyone.
BAU plus a flagship nurture program
Day to day campaigns alone were a demanding workload. On top of that, the annual nurture program required a large, highly structured build that could not fail.
Small core team
At one point I had to bring in a colleague from Singapore just to help carry the load for the flagship program. The demand was that high.
My approach
I treated VMware’s Eloqua instance like a shared global utility. The job was to impose structure, reduce chaos and make sure that even with 6 million records the system behaved consistently and predictably.
Part 1
BAU intake and delivery model
I implemented a campaign request process using Zoho ticketing so marketers submitted structured briefs. This reduced back and forth, created clarity on requirements and made work more predictable.
Part 2
Reusable patterns and templates
Emails, landing pages and nurture paths were built as patterns, not one offs. This made multi language rollouts realistic and kept the build time under control for each new wave.
Part 3
Flagship nurture program build
The flagship annual nurture was architected as a multi step program with clear entry criteria, language splits and product based content tracks, designed to cope with the size and shape of VMware’s database.
Behind the build: the technical reality
From a technical perspective, VMware was all about respect for scale. Eloqua 9 on a 6 million record database punishes sloppy thinking. You have to be deliberate with segments, programs and any heavy lifts on the platform.
Tech Insight 1
Performance aware segmentation
Segments were written to minimise strain. Where possible I used pre filtered shared lists and avoided overly complex nested logic that would slow down recalculation.
Tech Insight 2
Language and region abstraction
I separated language and region logic where I could, so we were not duplicating entire campaigns. This helped keep the canvas count under control even with 28 languages.
Tech Insight 3
Ticketing and work tracking
The Zoho based ticketing layer gave me visibility into workload, but in hindsight it was still a bolt on. The work was flowing, yet the data about that work was split between systems.
Tech Insight 4
Coordinating a small team at scale
Running this level of volume with a small core team meant obsessing over reusability, naming conventions and documentation. It was the only way to avoid drowning in our own work.
Tech Insight 5
Heavy QA under time pressure
Every campaign wave required systematic QA. At this scale a single broken link in a single language version can undo a lot of good work very quickly.
Tech Insight 6
Reality of operations
VMware taught me a lot about how far you can push Eloqua and where operational process is just as important as clever canvas design. It hardened a lot of the ways I now approach enterprise work.
What I would build today
If I were doing this again today, I would lean much harder into Salesforce as the operational backbone and treat Eloqua as the orchestration and experience layer on top of it.
Today 1
Ticketing in Salesforce as Cases
Instead of Zoho ticketing, I would build the intake and workflow directly into Salesforce using Cases. Every campaign brief would become a Case with fields for scope, region, language and status.
Today 2
Billing and effort tracking on the same object
With Cases as the core object, time and effort could be logged against each request. That would allow clean billing, internal showback or agency invoicing, all tied directly to the work actually delivered.
Today 3
Eloqua as an execution engine
Eloqua would read from structured Salesforce data and push activity back. All the operational context, approvals and cost controls would live in Salesforce, where leadership already spend their time.
Today 4
Stronger observability
I would add a simple observability layer for monitoring campaign health, segment sizes and program performance so we could spot issues before they hit a send.
Today 5
Repeatable enterprise patterns
I would formalise the nurture patterns in a way that other business units could adopt with minimal change, turning the VMware build into a blueprint rather than a one off.
Today 6
Closer loop between finance and ops
By tying Cases, time tracking and campaign performance together, finance and operations could see exactly what was being delivered, what it cost and how it performed, all in one place.
Impact
The VMware engagement was demanding, but it gave me a deep appreciation of what it takes to run Eloqua at real enterprise scale. It hardened my approach to process, naming, architecture and respect for platform limits.
It also gave me one of my favourite consulting stories. I flew in a colleague, Chris, from Singapore to help with the flagship nurture build. He met a friend of mine on the team, they fell in love, moved back to Singapore and now live in Dubai. Sometimes the best outcome of a project is not just the campaigns you ship.
In my words
VMware taught me more about scale than almost any other client. It made me sharper, more structured and more opinionated about what good Eloqua operations look like. I look back on it with a lot of respect and a fair bit of fond chaos.
- Greg Staunton
Need help running Eloqua at enterprise scale
If you are dealing with large databases, multi language workloads or complex global nurture programs, I can help you design, stabilise and run Eloqua like a proper enterprise platform.