Oracle Eloqua vs Salesforce Marketing Cloud: Architecture and Security

Due to major differences in core architecture, both platforms have significantly different data and security models. This matters before you make a purchase decision or migrate.

Flat org vs business units

Eloqua represents a single business unit setup, where all records reside within the same data tables of that instance. All records are available to all users in that instance, and the same applies to any asset, campaign or program. For a large enterprise with multi-regional requirements this is a challenge. Eloqua offers two routes around it: contact-level security through label-based access control, or upgrading to Eloqua Enterprise, which gives you twenty separate instances that cannot share anything between them, and sits at the highest end of Oracle’s pricing.

Marketing Cloud provisions accounts with business units. Typically one per country or brand. You can add more (up to around a thousand without materially affecting performance), and unlike Eloqua you can share data, journeys and assets across them. That scalability is one of the key things that makes Marketing Cloud an enterprise-grade solution.

Single app vs studios and builders

Eloqua is simple: all features are built within the same application, same database, same data centre. The learning curve is fast.

Marketing Cloud is a bundle of studios and builders: products acquired at different times and integrated into one GUI. They belong to different technology stacks, which means different unique record keys that have to be mapped in order to relate data. That makes the architecture more complex to configure and maintain, but the plug-and-play flexibility is again what makes it enterprise-grade.

Security

Eloqua controls access through security groups: bundles of permissions assigned to users, with quite granular control. Notably, MFA is not among the settings; you would address that through SSO.

Marketing Cloud uses roles with create, update, view and delete permissions configured at business unit level, and its security settings include multi-factor authentication, login IP allowlisting, domain allowlisting and SSL certificates.

Sandboxes

Eloqua sandboxes mirror production one way only (production to sandbox), so any configuration built in a sandbox must be manually reimplemented in production. In Marketing Cloud a sandbox is an additional business unit, and keeping them in sync is a manual effort or a third-party tool, though Package Manager eases some of it.

Summary

Depending on organisation size and needs, Eloqua may do the job well. If you want true enterprise-grade architecture and scalability, particularly across channels, Marketing Cloud is likely the way to go. On security both are strong, with a slight advantage to Marketing Cloud around MFA.

Archive: this article dates from an earlier phase of our work, when marketing automation was our main focus. We have kept it online because the thinking still holds, but it is not where our practice sits today.