— Curated insights from the Marketo field —
Before committing to Marketo's native interactive webinar capability, understanding the licensing structure is essential for procurement conversations. Three tiers exist — the entry level caps at 12 non-overlapping events per year with 500 attendees per room, the mid tier offers unlimited non-overla
A practitioner walked through a foundational but frequently neglected program architecture pattern: separating smart campaigns (all automation and logic) from assets (emails, landing pages, lists, reports) into two distinct folders within every program. The rationale is operational clarity — when tr
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, whi
While AI features dominated Summit headlines, a recurring pattern among experienced practitioners was equal or greater enthusiasm for foundational infrastructure improvements — particularly a ground-up rebuild of the Salesforce CRM sync with improved error visibility and more granular sync reporting
A practitioner demonstrated a repeatable workflow for building Marketo velocity scripts using an AI assistant: pull the field's API name directly from Marketo's Field Management admin panel, paste it into a structured prompt, and the generated script is ready to drop into an email script token. The
A practitioner who migrated early to Adobe Identity Management shared a candid post-mortem covering a range of issues that emerged immediately after cutover. The most disruptive was a severe performance regression — load times of 30 to 33 seconds per page navigation that persisted for roughly three
A presenter introduced a decision framework for selecting the right AI tool tier based on task complexity and frequency: conversational AI for one-off questions, custom GPTs or Projects for repeatable single-step tasks, and agent pipelines for complex multi-step workflows that chain outputs across s
A practitioner walked through a no-code path for sending WhatsApp messages from Marketo using a middleware integration, requiring only standard API credential setup through LaunchPoint. The integration itself is straightforward to configure, but a significant operational gap surfaces immediately: ou
A recurring gap in ABM implementations is the inability to incorporate post-sale behavioral signals — product usage, feature adoption, login frequency — into account scoring. A session discussion surfaced a practical pattern: where product telemetry lives outside the CRM or MAP (in an ERP, data ware
A presenter outlined a layered approach to engagement program architecture that goes well beyond basic stream-and-email setups. Two patterns stood out as particularly non-obvious: using nested default programs within streams to enable fine-grained send exclusions, content swaps, and deduplication ba
A recurring pattern in consent management failures is jumping into Marketo configuration before the legal and operational groundwork is complete. One approach presented structures the preliminary work into four discrete steps: mapping every marketing channel against every operating country, engaging
A recurring and poorly documented behavior in the Salesforce-Marketo native sync causes the Marketo sync user to appear responsible for field updates that were actually triggered by Salesforce Flows or Apex triggers. Because backend automation in Salesforce has no user context to stamp on field hist