ABM and Buying Group Orchestration with Adobe Journey Optimizer at AWS — Key Takeaways

Adobe Marketo Engage User Groups | 20250612 | 54:59

This session from Adobe Marketo Engage User Groups covered a lot of ground. 3 segments stood out as worth your time. Everything below links directly to the timestamp in the original video.

How to Divide Responsibilities Between Marketo and AJO B2B Without Duplicating Effort

Topic: integrations  |  Speakers: Erine de Leeuw, Britney Young

A recurring challenge when adopting AJO B2B alongside an established Marketo instance is knowing which tool should own which motion. One enterprise team described a clear division: Marketo remains the system of record for lead management, scoring, CRM integration, and evergreen nurture programs, while AJO B2B handles real-time, behavioral, and omni-channel orchestration — including anonymous journey support and point-in-time trigger events like form abandonment. The bidirectional sync between the two platforms means lead scores and statuses built in Marketo can directly personalize AJO B2B journeys, and real-time signals from AJO B2B can trigger Marketo nurture campaigns in return.

A shared asset library and unified analytics layer further reduce duplication, but the integration only delivers value if the operating model is defined before scale. One team noted that their pilot phase included use cases that were actually a poor fit for AJO B2B — time-based batch campaigns better suited to Marketo — and that sorting this out required deliberate trial and error. The lesson was that building governance documentation and an internal decision framework for 'which tool, when' needs to happen in parallel with technical implementation, not after.

The broader framing offered was that Marketo is fundamentally lead-centric, while AJO B2B is account- and buying-group-centric. Teams with active account-based marketing motions targeting enterprise or named accounts are the natural fit for AJO B2B expansion, whereas standard lead-based nurturing and sales alignment via CRM should remain anchored in Marketo. Journey governance — preventing conflicting or overlapping messages to the same contacts across both systems — was called out as a standing operational risk that needs explicit ownership.

"What quickly became clear is we definitely chose some use cases that aren't necessarily the best fit for AJO B2B. There was definitely some trial and error involved with more traditional time-based campaigns. Whereas ideally you want more the evergreen nurtures, those repeatable campaigns, or multi-channel experiences — those are better marketing use cases for AJO B2B compared to Marketo."

Key takeaways:

• Reserve AJO B2B for real-time behavioral triggers, omni-channel orchestration, and account-based journeys; keep evergreen nurtures, lead scoring, and CRM sync in Marketo.
• The bidirectional sync between the two platforms enables lead scores from Marketo to personalize AJO B2B journeys and behavioral signals from AJO B2B to trigger Marketo programs — design for both directions from the start.
• Build an internal operating model and decision framework for which tool handles which use case before rolling out to broader marketing teams, not after confusion surfaces.
• Journey governance across both systems — preventing duplicate or conflicting outreach to the same contacts — requires explicit ownership and should be treated as an ongoing operational discipline.
• Pilot use cases should be validated against whether AJO B2B's strengths (real-time, multi-channel, buying-group-centric) actually apply; batch time-based campaigns are a common misfit that wastes implementation effort.

Why this matters: If your team is evaluating AJO B2B, the hardest question isn't technical — it's knowing which campaigns should stay in Marketo and which ones actually belong in the new tool. This session maps out that boundary with real implementation experience behind it.

🎬 Watch this segment: 40:09

AJO B2B + Marketo Integration: Undocumented Gotchas, Implementation Timelines, and a Phased Buying Group Model

Topic: integrations  |  Speaker: Britney Young

Several underdocumented technical issues emerged from one enterprise team's AJO B2B rollout that are worth flagging before any practitioner begins a similar implementation. First, AJO B2B can only sync with the default Marketo partition — a significant constraint for any instance using workspaces and partitions. Teams discovered this mid-rollout when leads failed to sync without any clear error, causing considerable troubleshooting time. Second, on initial connection, if engagement scoring has not been in use, AJO B2B triggers a backfill that converts all null engagement score values to zero across the entire database. For large instances, this mass update can create a substantial backlog in any downstream data warehouse receiving daily extracts — a consequence that was not anticipated and caused operational disruption. Third, the sync cadence between AJO B2B and the underlying CDP is slow enough (overnight or multi-hour windows) that testing journeys in a reasonable timeframe requires working directly with Adobe to force-trigger audience syncs — otherwise a single test cycle can take a full day.

On implementation timelines, the data foundation layer — standing up the real-time CDP with correct schemas, tested in dev and then production — took approximately seven to eight months for an enterprise-scale team. AJO B2B itself, once that foundation was in place, took one to two months to stand up, though that estimate was caveated by the need to accommodate an existing email prioritization and frequency-capping system. The total team involved spanned roughly five or six marketing stakeholders across channels plus a technical team of ten to twenty, reflecting the complexity of a large-scale deployment with custom integrations.

For teams earlier in their account-based marketing journey, a phased buying group maturity model was outlined: starting with persona-based content targeting (role types such as technical decision-maker or business decision-maker), progressing to rule-based buying groups tailored to specific solutions and ABM motions, and eventually evaluating whether a machine-learning model for automatic buying group identification is worth the investment. A final practical note: AJO B2B only accelerates execution speed if the marketing strategy side — journey design, content, ABM thinking — is already mature. Technical readiness without marketing strategy readiness will bottleneck the rollout regardless of platform capability.

"If you are using workspaces and partitions, you can only sync to one default partition from AJO B2B. When we initially launched we didn't know that and we were driving ourselves crazy trying to figure out why certain leads weren't syncing. Upon initial connection, if you are not using engagement score, there is an initial backfill where everyone in your instance — the engagement score has to be set to a number, it can't just be null. For us, we had to update several millions of records to just update to zero, and depending on how large your instance is, that could potentially cause a backlog if you're doing any sort of data extraction."

— Britney Young

Key takeaways:

• AJO B2B currently syncs only with the default Marketo partition — if your instance uses workspaces and partitions, leads outside the default partition will silently fail to sync.
• Connecting AJO B2B to a Marketo instance that has not been using engagement scoring will trigger a mass backfill setting all null values to zero; for large databases with daily data warehouse extracts, plan for a significant temporary backlog.
• Testing AJO B2B journeys requires coordinating with Adobe to force-trigger audience syncs — the default overnight sync cadence makes iterative testing impractical without this workaround.
• Budget seven to eight months for the real-time CDP data foundation before AJO B2B work begins; the AJO B2B layer itself can follow in one to two months once the foundation is stable.
• Structure buying group development in phases: persona-based targeting first, then rule-based groups tied to specific solutions, then evaluate ML-driven automatic identification only once the earlier phases are validated.

Why this matters: The AJO B2B documentation won't warn you about partition sync limits or engagement score backfills — but one enterprise team learned about both the hard way. These are the implementation details worth knowing before you go live.

🎬 Watch this segment: 28:57

First-Wave AJO B2B Use Cases: What One Enterprise Team Prioritized for Initial Deployment

Topic: use-case  |  Speaker: Erine de Leeuw

When an enterprise marketing operations team selected their foundational AJO B2B use cases, the choices reflected a deliberate mix of retention, acquisition, and adoption signals rather than simply replicating existing Marketo programs in a new tool. Use cases centered on behavioral triggers — form abandonment retargeting, credit balance threshold alerts — alongside account-level intent signal activation for enterprise segments using AI/ML-derived signals from both first-party and third-party data sources. Adoption-focused flows targeting existing customers and regional nurture programs rounded out the initial scope.

The through-line connecting these use cases was the shift from lead-level to account-level thinking. Intent signals aggregated at the account level were used to route contacts into relevant audience segments without waiting for batch sync cycles, enabling more timely engagement. The buying group construct was applied selectively — beginning with persona-based segmentation (decision-makers, technical buyers) as the most tractable starting point before more sophisticated account-level configurations.

For practitioners evaluating which use cases to prioritize first, this example suggests a useful heuristic: lead with use cases that are either behaviorally triggered or require real-time account-level data that Marketo cannot surface quickly enough on its own. Evergreen or time-based programs are better left in Marketo during initial rollout.

"We want to deliver the right message at the right time through the right channel — that's what marketing really is about if you want to break it down to one sentence."

— Erine de Leeuw

Key takeaways:

• Prioritize behaviorally triggered and account-level intent use cases for initial AJO B2B deployment — these are where the platform's real-time capabilities create the most differentiation from Marketo.
• Intent signals aggregated at the account level can enable audience routing without waiting for overnight sync cycles, making timely engagement on high-interest topics operationally feasible.
• Form abandonment and similar behavioral retargeting flows are natural early candidates for AJO B2B because they require real-time event detection that batch-oriented Marketo programs handle less effectively.
• Persona-based buying groups (by role archetype) offer the lowest-friction starting point before investing in solution-specific or ML-driven buying group configurations.

Why this matters: Knowing which use cases to launch first with AJO B2B matters as much as knowing how to configure it. This breakdown of one enterprise team's initial deployment scope gives you a concrete reference point for scoping your own P0.

🎬 Watch this segment: 26:22

Content summarized from publicly available MUG recordings. Not affiliated with Adobe. Summaries reflect my interpretation — always validate before implementing in your environment.

This is a personal project by JP Garcia. I work at Kapturall but this publication is independent and not affiliated with or endorsed by my employer. All credit belongs to the original speakers and Adobe Marketo Engage User Groups. I curate and link back to source — I never re-upload or reproduce full sessions. Full disclaimer →

🤔 Why have these segments been selected?