Case Study · Vodafone B2B
Eloqua integration in one of the most political environments of my career
Vodafone connect people, governments and businesses at global scale. Their B2B vision was clear: one Salesforce instance called 1SF, and one streamlined Eloqua instance to match. I was brought in to help make the Eloqua side of that happen.
This case study is not just about architecture and integration. It is about what happens when technical projects run straight into politics, territory and competing consultancies.
Client background
Vodafone's purpose is to connect for a better future. Their networks keep families, businesses and governments online, and they play a critical role in keeping economies and essential services running.
Internally, Vodafone were aligning their B2B landscape. They had recently brought their different B2B business units onto a single Salesforce instance known as 1SF. The CIO wanted Eloqua to be rationalised in the same way so that the entire B2B ecosystem could operate on a unified sales and marketing platform.
On paper, it was a strong vision. In practice, the environment around the programme was one of the most political and contested I have worked in.
At a glance
- Industry: Telecommunications (B2B)
- Platforms: Eloqua, Salesforce 1SF
- Role: Eloqua architect and integration lead
- Markets: GB, ES, IE plus further rollout
The challenge
The CIO wanted one B2B Salesforce instance and one B2B Eloqua instance. The theory was simple. The reality was a battlefield of competing agencies, territorial teams and different ideas of what “one source of truth” actually meant.
A crowded field of consultancies
Vodafone Global Enterprise (VGE) already used Eloqua and did not want anyone else on their platform. Accenture had implemented 1SF and were deeply invested in protecting the Salesforce design. Sojourn Solutions were heavily embedded with VGE on Eloqua.
On top of this, there were eight different sandboxes and a strict change board that scrutinised every technical decision, often without deep understanding of Eloqua or marketing automation.
A CRM that was not truly one source of truth
There are two ways to build a global CRM. The hard way is to agree on global lead layouts, picklists and status models so that one record really does reflect one truth. The easy way is to have one Salesforce instance with many record types, many picklists and many localised behaviours.
Accenture had understandably taken the easy way. It made delivery faster and more politically acceptable. But it also meant that creating a genuine 360 degree view and clean Eloqua integration was far more complex than the original vision suggested.
My approach
In that environment, the only viable approach was to anchor the work in a single market, prove the pattern and then generalise it. We chose the UK as the vehicle and built an Eloqua implementation package that could be rolled out to other countries.
Step 1
Use the UK as the blueprint
We designed a complete Eloqua implementation package around the UK market, including data model design, consent logic, segmentation, campaigns and integration patterns.
Step 2
Solve contact level security
VGE had their own program to identify enterprise contacts. Everyone else had to be separated by country and business group. Contact level security was the key to onboarding other business units without exposing data between areas that should not see each other.
Step 3
Push through the integration
The crucial part was the integration between Eloqua and 1SF. VGE did not want their existing integration opened up to include country codes for leads and contacts. It took time and political effort to understand why and to make progress.
As the work progressed, I discovered the deeper issue. The CRM had been built in a way that made everybody happy locally but made it extremely difficult to achieve the CIO's original goal of a true single source of truth. From an Eloqua point of view, that meant constant compromise and inventive integration design just to maintain basic consistency.
Despite the politics and a very strict change board, we got the integration working for Great Britain, Spain and Ireland and built an implementation package that could be used as the foundation for other markets.
Impact
- A reusable Eloqua implementation package was designed and proven using the UK as a model.
- Eloqua to Salesforce integration was delivered and tested for GB, ES and IE.
- The foundation was laid for other B2B units to be onboarded to the same Eloqua instance.
- Technical success was achieved in an environment that was more political than technical.
In my words
This was the most hostile and political Eloqua engagement I have ever been on. I met some very good people and I also met some of the most aggressive internal politics I have seen in the civilian world. Eventually I was removed from the project after making a mistake during the Salesforce integration. I wrote about that mistake publicly because it taught me a lot and I believe in owning what happened.
Vodafone's super power is politics and autocracy. In many ways this project was my Afghanistan in the civilian world. I learned from it, I delivered what I could and I will not trade with Vodafone again.
- Greg Staunton
Need Eloqua delivered in a difficult environment
If your organisation is complex, political or burdened with legacy decisions, I can help you design and deliver Eloqua implementations and integrations that still work in the real world, not just in the slide deck.