What was the main challenge Aberdeen Standard Investments needed to solve in Eloqua?

They needed a fund subscription framework that could accurately reflect investment permissions and product entitlements for every contact, synchronising Salesforce investor records with Eloqua while enforcing strict controls around jurisdiction, investor category, geo IP and fund subscription status.

How was the fund subscription architecture implemented in Eloqua?

The solution used a one-CDO-per-fund model with thousands of CDOs storing subscription records, combined with Visualforce pages making real-time web data lookups into Eloqua. This allowed the system to determine whether a contact was subscribed, unsubscribed or restricted for each fund and to power highly personalised, compliant communications.

What would you do differently if you rebuilt this architecture today?

Today the same underlying model would be modernised using a unified data warehouse for fund metadata, Salesforce Experience Cloud for subscription management, real-time or OCI Functions for CDO updates, fully API-driven subscription management, event-based messaging and AI-powered personalisation for fund recommendations.

What impact did this Eloqua and Salesforce architecture have for Aberdeen Standard Investments?

The architecture delivered accurate real-time fund subscription information in Salesforce, zero compliance breaches in content distribution, fully personalised fund updates powered by CDO-driven dynamic content, improved investor engagement and unified regulatory rules across regions, categories and investor types.

Aberdeen Standard Investments Eloqua and Salesforce fund subscription architecture.

Case Study · Aberdeen Standard Investments

Enterprise scale fund subscription architecture using Eloqua, CDOs and Salesforce

Q: How did you ensure regulatory compliance across jurisdictions and investor types?

All data was cross-checked against investor category, domicile and geo IP, and content was restricted accordingly. Contacts only saw funds suitable for their regulatory classification, and if they were out of region or not entitled, the associated content and documentation were automatically hidden.

Aberdeen Standard Investments manage hundreds of billions in assets across thousands of funds. Their subscription model needed a deeply accurate, compliant and personalised communication flow driven by Salesforce, Visualforce and high volume Eloqua CDO relationships.

Aberdeen Standard Investments Eloqua architecture.

Client background

Aberdeen Standard Investments are one of the largest and most regulated investment houses in the world. Their portfolio includes thousands of funds, each with its own regulatory classification, documentation and distribution rules.

Investor communications are highly controlled. What a contact can see is determined by:

their investor category
their jurisdiction
their verified identity
their subscribed funds

They required a powerful technical framework that could synchronise Salesforce investor entitlements with Eloqua to deliver highly regulated, personalised, fund specific content at global scale.

At a glance

Industry: Asset Management
Funds: 3,000+ fund products
Global users: 80 countries
Architecture: Salesforce + Eloqua + Visualforce
Key feature: 1 CDO per fund

The challenge

Aberdeen Standard needed a fund subscription framework that could accurately reflect investment permissions and product entitlements for every contact. The system had to:

sync with Salesforce investor records and their subscription profiles
store subscription status against thousands of funds
support Visualforce pages that dynamically displayed what each user could see
restrict content based on jurisdiction, investor type and geo IP
drive fully personalised emails powered by fund specific dynamic content
ensure that no unauthorised contact could see materials they were not permitted to access

This was a highly technical, highly regulated and zero error tolerance environment.

My approach

The solution required a meticulous data architecture between Salesforce, Eloqua and Visualforce. I architected and built a multi layer system that allowed contacts to manage fund subscriptions and only receive information they were entitled to.

Layer 1

1 CDO per fund

Every fund had its own CDO storing a subscription record for the contact. With thousands of funds, this created a massive but highly flexible relational model that Eloqua could query in real time.

Layer 2

Visualforce + Eloqua web data lookups

When a subscriber logged in, Salesforce rendered Visualforce pages that called Eloqua in real time via web data lookups to determine if the user was subscribed, unsubscribed or restricted from each fund.

Layer 3

Jurisdictional compliance

All data was cross checked against investor category, domicile and geo IP. Contacts only saw funds suitable for their regulatory classification. If they were out of region, content was automatically hidden.

Behind the build

This was one of the most technically challenging Eloqua CDO architectures I have ever built. The system had to scale, respond instantly and adhere to investment regulations with absolute precision.

Thousands of CDOs connected to millions of subscription records
Visualforce pages making live GET requests into Eloqua
Conditional rendering based on regulatory flags
Geo IP restrictions baked into subscription handling
CDO driven dynamic content blocks inside all investment emails
Salesforce reported subscription accuracy based on Eloqua’s real time values

Building this required very careful structuring of CDO naming, keys, index fields, and performance tuning to keep lookup times low even under heavy load.

What I would build today

Today I would take the same underlying model but modernise it:

Store fund metadata in a unified data warehouse feeding both SFDC and Eloqua
Use Salesforce Experience Cloud for subscription management
Use real time functions or OCI Functions to streamline CDO updates
Make subscription management fully API driven
Introduce event based messaging rather than cycle based sends
Use AI powered personalisation for fund recommendation content

But the core principle would remain. Regulatory email communication must be powered by clean, structured data and clear entitlements.

Impact

Accurate real time fund subscription information rendered in Salesforce
Zero compliance breaches in content distribution
Fully personalised fund update emails powered by CDO driven dynamic content
Improved investor engagement through relevant and timely updates
Unified regulatory rules across regions, categories and investor types

In my words

Aberdeen was one of the most technical and highly regulated implementations I have ever worked on. The combination of CDO heavy architecture, real time Visualforce lookups and geo IP regulation made it a standout project. Getting it right mattered and I am proud of what we delivered.

- Greg Staunton

Need a senior Eloqua architect for complex CDO and Salesforce integrations

If you are handling regulated data, complex subscription entitlements or multi layer Salesforce + Eloqua architectures, I can help you design, stabilise or modernise your platform.