What is a marketing center of excellence?

A central team that owns the marketing platform and the standards every campaign follows and lets other teams build campaigns within them. It differs from a help desk in that most of its work goes into making campaigns buildable by others: templates, audiences, rules and approvals set up in advance rather than applied by hand each time.

Is a center of excellence the same as marketing operations?

Usually the same people. The difference is the charter. Marketing operations builds and runs campaigns. A center of excellence also owns the standards, decides what other teams may do for themselves and is measured on how much marketing the company gets out and how little comes back rather than on tickets closed.

Should the center of excellence build every campaign?

No. A center that builds everything is capped by its headcount and becomes the reason every send is slow. It should build the campaigns nobody has run before and turn the routine ones into paths other teams can run inside guardrails it sets.

Which Eloqua permissions should stay with the center?

Set Security on assets, Manage Templates and Manage Blocks, Create an Email Group, the contact upload permissions, Send Email to Globally Unsubscribed Contacts and to Master Exclude members, Delete a Contact Record, Manage Run as User, the Activate permission on campaigns and everything under Settings. Sending teams get asset creation for campaigns and emails and View on the shared templates and segments.

Do we need a separate Eloqua instance for each brand or region?

Usually not. Business units separate assets by brand or division and contact security separates which contacts a team can reach, inside one instance with one database and one unsubscribe list. Separate instances make sense when legal entities have separate data obligations. Then the center needs a way to administer and report across them.

How do we measure a center of excellence?

Turnaround from request to send by campaign type, the share of campaigns other teams complete without the center’s help, how often a campaign is redone, how long approvals take, how many emails one contact receives across every team and results by team and campaign type. Report them monthly to the leaders of the sending teams.

How does Campaign Launchpad fit into a center of excellence?

It gives the center a second path beside Eloqua. The center builds a Launchplan for each campaign type with its templates, audiences, rules and approvers and other teams run them without an Eloqua login. Launchpad builds the campaign in the instance and reports every team’s work in one place.

How to set up a marketing center of excellence in Oracle Eloqua

Every large Eloqua instance ends up with one team that knows how it works and a lot of teams that need email sent. A center of excellence is that arrangement run on purpose. This guide covers what the center should own, how to set Eloqua up around it, how to run the intake and what to measure.

What a center of excellence is

A marketing center of excellence is the team that owns the marketing platform and the standards every campaign follows. Call it marketing operations or campaign operations or shared services. The name matters less than the arrangement: one team decides how campaigns get built in Eloqua and every other team builds within that.

It is worth separating this from a help desk. A help desk builds whatever lands in the queue and its output is capped by its headcount. A center of excellence spends some of its time building campaigns and most of its time making campaigns buildable by other people: templates that can’t go wrong, audiences that are already defined, rules that apply themselves. The measure of a help desk is tickets closed. The measure of a center of excellence is how much marketing the company gets out and how little of it comes back.

Most companies have the first thing and call it the second. The rest of this guide is about making the name true.

Decide what the center owns

Start with a list rather than an org chart. Two columns. On one side everything that affects every team or can’t be undone once it is wrong. On the other everything that belongs to a single campaign.

The center’s column usually ends up like this:

The instance itself. Integrations, the CRM sync, field definitions, data retention and whatever Oracle changes each release.
The contact data model and consent. What each field means, which fields the CRM owns, how opt-in is recorded and which email groups exist.
Templates and brand. Every email and landing page template plus the header, footer and legal blocks they share.
Audiences. The shared segments and filters, the suppressions, the master exclude list and the rules about what a team may upload.
Frequency. How often one contact may hear from the company across every team that considers them theirs.
Approvals. Who signs off on what and when a send may skip review.
Naming and campaign fields. The convention that makes reporting possible a year later.
Reporting. What gets measured, where it lives and who sees it.
Intake and training. How a request arrives and what a requester needs to know.

The teams’ column is shorter: the message, the copy and images inside the template, the audience chosen from what the center allows, the send date inside the windows the center sets and the results of their own campaigns.

Write both columns down and get the people who run the sending teams to agree to them. The arguments you have at this stage are cheaper than the ones you would have after a bad send.

Set up Eloqua around the center

Eloqua has the controls for this arrangement. They sit in six or seven places and the center has to hold the keys to all of them.

Security groups per team

Everything starts with security groups. The center is one group with every license it needs including Analyzer, every interface area, every action permission and Set Security on every asset. Each sending team gets a group of its own with less: asset creation for campaigns and emails only, View on the shared templates and segments, no Activate permission on campaigns and none of the upload, unsubscribe-override or delete permissions.

Permissions in Eloqua are cumulative across groups. A marketer who sits in the careful new group and an older generous one gets the generous one. Audit membership when you set the center up and again every quarter. Oracle’s own advice for checking a group is to log in as a user who only has that group and try to do the things you meant to prevent.

Business units and contact security

A company with several brands or divisions in one instance uses business units to separate what each one can open. A company with regions uses contact security labels so each team only sees and sends to its own contacts. The center owns the label categories, the program on the canvas that assigns them and the administrator group that carries every label so somebody can still process the whole database. The regional teams guide covers how the two fit together.

Email groups

Email groups are where subscriptions and the standard header and footer live. The center creates them, one per region or language or line of business as the subscription page needs, and keeps the Create an Email Group permission to itself. A sending team picks an email group. It doesn’t make one.

Templates the center owns

Brand holds in a shared instance to the extent the templates hold. The center builds protected templates in the Design Editor with the style and design switches off and only the content a team may change left open. It locks the shared content blocks and keeps Manage Templates and Manage Blocks in its own group. Set Security on each template leaves every other group with View so nobody saves over it.

Then retire what people clone from. An old email saved before the protections went on is an unprotected template with a different name. Move those to a folder the teams can’t see.

Audiences

The segments and shared filters teams may use live in a folder the center owns with View for everyone else. The master exclude list and the global unsubscribe are handled centrally and the permissions to send past them stay in the center’s group. Decide now whether teams may upload lists at all. If they may, the Contact Upload Wizard takes whatever mapping they confirm, so the center needs a written rule for what a file has to look like and a plan for checking it.

Approvals

Withhold the Activate permission from the teams’ groups and set up the campaign approval workflow so a campaign waits for a named reviewer before it runs. Know its two limits before you rely on it. Reviewers are named individuals in one global workflow rather than a path per team. And it doesn’t apply to simple email campaigns, which are the campaigns teams send most.

Naming and campaign fields

Agree on a naming convention and put the parts reporting needs into campaign fields rather than the name alone. Eloqua’s standard fields for Product, Region and Campaign Type plus any custom campaign fields your team adds are what let Insight break results out by team and campaign type a year later. Folders per team and per year keep the asset tree readable. A convention only works if the center enforces it, so build it into whatever template or request form a campaign starts from.

Reporting

The center holds the Analyzer licenses and builds the dashboards. Insight folder security lets each team see its own folder under Company Shared and contact security already filters the rows. Decide what a sending team gets to see on its own and what it has to ask for. The teams that ask for the least are the ones who were given a report that answers the questions they actually have.

Write the standard down

The permissions above decide what a team may open. The standard decides what they should do once they have. Keep it short. One page per campaign type is enough: who may run it, which template, which audiences, who approves, which hours it may send and how it is named.

Eloqua doesn’t give you much room to put this where a marketer will see it. Asset descriptions and folder names carry a little. Most centers keep the standard in Confluence or SharePoint and most marketers never open it again after the first week. That is why the next two sections exist.

Run the intake

Even a center that lets teams send for themselves runs a queue for everything else. Give it a form that asks for what the campaign needs and nothing more: the audience and how it was defined, the content, the sender, the date and time zone, the approver and any list to import. Publish a turnaround time you can actually hit. Show the queue to the people in it. The campaign request guide goes into what a good intake looks like and why the queue grows faster than the team however good the form is.

Count a quarter of requests by type while you are at it. The newsletter, the webinar invitation, the product update and the list upload are usually most of the volume and the least varied. Those are the campaign types to turn into paths teams can run themselves. Keep the ticket for everything nobody has done before.

Measure the center

A center of excellence that reports opens and clicks looks like a mailroom. Report on the operation too:

Turnaround from request to send, by campaign type.
The share of campaigns that went out without anyone in the center touching them.
How often a campaign had to be redone and why.
How long approvals take and who they wait on.
How many emails one contact received across every team. Eloqua won’t tell you that without work. The Email Governor will.
Results by team, template and campaign type from the campaign fields you insisted on.

Put the numbers in front of the sending teams’ leaders every month. The first few months make the case for the center. After that they make the case for the next campaign type to hand over.

Where Eloqua stops

Set all of this up and you have an instance where a team can only open what it should. A few things remain and they are worth knowing before you promise anything.

The controls govern access and nothing after it. Contact security stops a region emailing another region. It doesn’t stop them emailing the whole region with something meant for forty accounts. Edit on an email means edit all of it unless the template was protected first, and protections are per template and per editor.

Every marketer who sends for themselves is an Eloqua user with a license, a group to maintain and training that is never finished. Approvals skip the simple sends. Reporting across teams takes an Analyzer license and someone to build it. A second instance for a brand or a region splits the picture again.

None of this argues against the setup. It argues for the center running two paths: Eloqua for its own work and something narrower for everyone else.

Running the center on Campaign Launchpad

Campaign Launchpad is that narrower path. The center builds a Launchplan for each campaign type in the standard: the steps it runs in Eloqua, such as cloning a campaign or creating an email or importing a list, the fields a requester fills in and the pages they fill them in on. The security groups a Launchplan is shared with mirror the sending teams. A requester never opens Eloqua.

Everything on the center’s list from earlier has a place in it:

Templates are the center’s own HTML with the editable regions marked and a rule on each: a character limit on the headline, a minimum width on the hero image, a button that can be removed and nothing else that can.
Audiences come from the segments the center allows for that Launchplan. An uploaded file is checked row by row against the center’s rules before anything reaches Eloqua.
Approval goes to a group or to the requester’s manager or to each email separately, set per Launchplan, with the decision kept on the workflow.
The standard travels with the campaign. Brand rules and legal notes written once in the documentation library show on the wizard pages that need them, including the pages of workflows already started.
The AI Assistant drafts copy under a policy the center sets: tone, length and blocked words.
Steps nobody can automate, a print ad or an email built from an uploaded brief, go to enablement so the center does them by hand and the record stays with the campaign.
Reporting covers every team in one place: a status board of what is in flight and who it is waiting on, how long approvals and enablement take, a calendar of what goes live and each campaign’s results back to the person who sent it.

Launchplans have versions, so the center can change a path without breaking the workflows already started from it. One Launchpad account covers every Eloqua instance you run and any Marketo instances beside them.

The companies that run a center this way describe the same result. 3M has 250 people sending through one small team and a campaign that took eight hours now takes about 45 minutes. Omron lets country organizations send on the central database and subscriptions. The center stays the size it was. What changes is how much goes through it. The same setup for a Marketo instance is covered in its own guide.

Building a marketing center of excellence in Oracle Eloqua

In short