Key Takeaways

• Your MAP already supports ABM marketing automation.
• Segment contacts by account attributes, not individuals.
• Roll up engagement signals across all stakeholders.
• ABM nurture runs on account stage, not persona.
• Clean CRM sync is the non-negotiable ABM foundation.
• ABM is a config change, not a new platform.

B2B marketing ops teams have built sophisticated demand gen engines. Lead scoring is tuned. Nurture programs are running. Segmentation is tight. Eloqua or Marketo is humming along, doing exactly what it was configured to do.

But when leadership asks about ABM, the conversation almost always turns to new tools. A separate ABM platform. Additional budget. A new team learning curve. ABM starts to feel like a separate project bolted onto the side of the existing stack.

It does not have to work that way. If your organization already runs on Oracle Eloqua or Adobe Marketo, you have the infrastructure for account-based marketing. The gap is not tooling — it is configuration. This post walks through four setup changes that move your MAP from lead-first to account-first.

Why Your MAP Is Already Your ABM Platform

Account-based marketing does not require a purpose-built ABM tool to get started. What it requires is a platform capable of segmenting and scoring at the account level, running personalized campaign tracks, and syncing cleanly with your CRM. Eloqua and Marketo both do this — and with 70% of B2B marketers now running active ABM programs, the infrastructure question is largely settled. For broader ABM strategy context, see the Complete Guide to ABM Metrics and Framework.

The difference between lead-first and account-first is architectural, not technological. Getting your ABM marketing automation setup right starts with understanding this distinction. Lead-first configuration surfaces individual contacts who are engaging. Account-first configuration surfaces companies where multiple stakeholders are engaging — which is the signal ABM decisions are actually made on.

Step 1: Shift Your Segmentation from Lead-Level to Account-Level

Standard segmentation filters contacts based on their own attributes: job title, industry, behavioral score, form submissions. Account-level segmentation filters contacts based on the company they belong to — including firmographic data, CRM account stage, account tier, and account-level intent signals.

In Eloqua

Store account attributes in a Custom Object (CO) synced from your CRM, then build segments that filter contacts by their linked CO values rather than individual contact fields. This CO-based approach is the foundation of Eloqua ABM segmentation. For a deeper look at how Eloqua handles this at enterprise scale, see Rethinking ABM Tech for Complex B2B Marketing with Eloqua.

In Marketo

Marketo syncs Salesforce Account fields directly to the lead record. Filter Smart Lists using those account-level fields. If your org uses the Marketo ABM module, Named Account lists handle account-level targeting natively.

Step 2: Build an Account Scoring Model Alongside Your Lead Score

Lead scoring measures individual contact engagement. Account scoring rolls up signals across every contact at a target company to produce a single score representing the account’s buying readiness. Both scores are needed in a functioning ABM program.

A contact scoring 45 looks moderate on its own. If three other contacts at the same company are also active, the account-level picture signals a buying motion that lead scoring alone would miss.

In Eloqua

Build a second scoring program in Program Builder that aggregates contact scores by company identifier and writes the rollup value back to the account CO. Alternatively, create the rollup in Salesforce and sync it back into Eloqua as an account CO field.

In Marketo

Marketo ABM module includes a native Account Engagement Score that aggregates activity across all contacts on a named account. Without the module, approximate this using a Salesforce rollup field synced back as a Marketo custom field. For context on how scoring fits your broader stack, see the B2B Marketing Automation Strategy Playbook.

Step 3: Create ABM-Specific Nurture Tracks for Target Accounts

Standard nurture is contact-centric — a contact enters a track based on persona or lifecycle stage. ABM nurture is account-centric — track entry is determined by account tier and pipeline stage, and content is personalized to the account’s industry, not just the contact’s job title.

This is not a relabeling exercise. The content assets, send cadence, and escalation logic inside an ABM nurture track should differ meaningfully from a demand gen sequence. This structural difference is what makes ABM marketing automation feel distinct from conventional lead nurturing.

In Eloqua

Use Program Canvas with dynamic content blocks driven by account CO fields. Configure separate entry criteria per account tier so Tier 1 accounts enter a high-touch sequence while Tier 2 and 3 receive lighter, automated tracks.

In Marketo

Build Engagement Programs filtered by Named Account segment membership. Use dynamic content tokens tied to account-level field values (industry, tier) to personalize without building separate programs per segment. Add escalation rules to alert sales when account engagement crosses a threshold. These triggers are where ABM creates real sales and marketing alignment at the account level.

Step 4: Sync Your CRM as the Account Data Foundation

Every configuration above depends on accurate, current account data flowing from your CRM into your MAP. Without a clean bidirectional sync, account segmentation is unreliable, account scores drift, and nurture tracks fire on stale data. A reliable CRM sync is what makes your ABM marketing automation program trustworthy and actionable.

For ABM, the fields that matter go beyond standard lead-sync: account tier, sales stage, account owner, and any intent signals your sales team captures. These drive segmentation entry, scoring updates, and track routing.

In Eloqua

Your Eloqua ABM sync starts by mapping Salesforce Account fields to a Custom Object — not just Lead-to-Contact. The Account CO must update in near real time when a rep changes account stage or tier in Salesforce. For platform architecture guidance, see the Eloqua vs Marketo comparison guide.

In Marketo

Confirm Salesforce Account fields are included in the connector sync settings and add ABM-specific fields (account tier, named account flag, account owner) if not already syncing. For orgs using the Marketo ABM module, the Named Account sync handles this automatically when Salesforce accounts are designated as named accounts.

Eloqua vs Marketo: Quick Platform Reference

The table below summarizes the key configuration approach for each step across both platforms.

Step	In Eloqua	In Marketo
Step 1: Segmentation	Custom Object (CO) linked to contacts; segment by CO field values synced from CRM.	Account fields synced from Salesforce to lead record; filter Smart Lists by account fields or Named Accounts.
Step 2: Scoring Model	Second scoring program in Program Builder aggregates contact scores into account CO; or Salesforce rollup synced back to CO.	Native Account Engagement Score in ABM module; or Salesforce rollup field synced as custom Marketo field.
Step 3: Nurture Tracks	Program Canvas with dynamic content driven by account CO fields; separate entry criteria per account tier.	Engagement Programs filtered by Named Account segments; dynamic tokens for industry/tier personalization; sales escalation rules.
Step 4: CRM Sync	Map Salesforce Account object to Eloqua CO; verify sync is Account-to-CO, not only Lead-to-Contact; near real-time updates.	Confirm Account fields are in connector sync settings; add tier/owner fields; ABM module auto-handles Named Account sync.

Conclusion

ABM marketing automation does not require a separate platform or a new budget line. If your team already runs Eloqua or Marketo, the four configurations above are your starting point: account-level segmentation, a parallel account scoring model, ABM-specific nurture tracks, and a CRM sync built for account data. Each change builds on your existing setup rather than replacing it. Contact 4Thought Marketing to discuss how to configure ABM inside your Eloqua or Marketo instance.

Frequently Asked Questions