QuestionQ29

VerifiedSection 2B: Marketo Campaign Architecture Design

A Marketo Engage Architect is integrating a Marketo Engage instance for a nonprofit client with two different third-party platforms. The requirements are as follows:

  • Scenario 1: Automatically clone existing default programs in Marketo, build the email using the RSS feed from the blog section, and schedule the email to send every Thursday.
  • Scenario 2: Before any record is deleted in Marketo, push that record's data to the "Donor System."

How should the Architect approach this platform integration?

Explanation

Cloning default programs, assembling an RSS-driven email, and scheduling recurring sends are administrative and automation tasks that are best handled programmatically by calling Marketo's REST API, which provides endpoints for program cloning, asset creation/configuration, and scheduling. In contrast, pushing data to an external Donor System immediately before a record deletion is an event-driven action that must occur as part of a smart campaign's flow (triggered by the Delete Lead trigger), and the mechanism Marketo uses to call out to an external system in real time within a flow step is a Webhook. This division of responsibilities corresponds to using the REST API for Scenario 1 and a Webhook for Scenario 2.

Community Discussion

No comments yet. Be the first to start the discussion!