Data Architecture
A curated anthology of the best moments on this topic — drawn from across the full video library, ranked by editorial relevance, with direct links to the exact timestamp in every source session.
If your team is piping AI outputs back into Marketo, the storage decision matters as much as the integration itself. Getting the data model wrong means captured data that is effectively unreachable.
Watch full session ↗A Decision Framework for Storing AI-Returned Data in Marketo: Person Fields, Custom Objects, or Custom ActivitiesA recurring architectural challenge when integrating AI into Marketo is deciding where to persist the data that comes back from an LLM or external service. A decision framework discussed in the session treats person and company fields, custom objects, and custom activities as dis
Why Webhook Timeouts Make Self-Service Flow Steps the Better Choice for LLM-Driven Marketo FlowsA non-obvious failure mode surfaces when practitioners use Marketo webhooks to trigger long-running AI processes: webhooks have a hard 30-second timeout, and LLM calls — particularly those generating richer outputs like lead summaries for sales handoff — routinely exceed it. When
If you're building or inheriting a Marketo-to-warehouse pipeline, the four-step async export pattern and its concurrency constraints are the most likely source of silent failures. Understanding the queue model before you scale is cheaper than debugging it after.
Watch full session ↗Marketo Bulk Export Is a Four-Step Async Process — Know the Queue Before You Build a PipelineA common architectural misconception addressed in this session is that Bulk APIs operate on a fundamentally different infrastructure from standard REST endpoints — they do not. Both use HTTPS and OAuth 2.0 authentication. The distinction is architectural intent: standard REST end
If your team is still choosing a deduplication approach by gut feel, this maturity ladder gives you a structured framework to match method to scale — and flags the activity-history gotcha that catches bulk-merge users off guard.
Watch full session ↗A 'Data in Transit' Pattern Using Key-Value Pairs and Velocity Scripting to Avoid Bloating the Data ModelA pattern discussed in this session addresses a common tension in Marketo architecture: how to send rich, complex data through a campaign send without persisting that data permanently in the data model. The approach uses text area fields as temporary containers for structured key
Design Deletion Logic Before Creation Logic: The Orphaned Custom Object ProblemA key operational hazard surfaced in this session is one most practitioners encounter only after it becomes expensive: deleting a person record in Marketo does not delete linked custom object records. Those orphaned records remain in the system, continue to count against custom o
A Decision Matrix for When to Extend Marketo's Data Model — and When to Leave It AloneA clean mental model presented in this session reframes the custom object versus custom activity decision as nouns versus actions: custom objects represent things that exist (enrollments, purchases, assets), while custom activities represent time-series events that happened (vide
A Four-Tier Deduplication Maturity Ladder for Choosing the Right Merge ApproachA recurring challenge in Marketo operations is matching deduplication method to database scale — and a framework shared in this session structures that decision as a four-tier maturity ladder: manual merging in Marketo UI for small, sensitive duplicate sets; bulk Excel-based merg