How should the Marketo Engage Architect approach the platform integration?

An Adobe Marketo Engage Architect is integrating a Marketo Engage instance for a nonprofit client with two different third-party platforms.

The requirements are outlined below:

Scenario 1: Automatically clone existing default programs on Marketo, build the email using the RSS feed of blog section, and schedule the email on every Thursday.

Scenario 2: Before deleting any record on Marketo, push the data to "Donor System".

How should the Marketo Engage Architect approach the platform integration?
A . Scenario 1 – Use Webhook and Scenario 2 – Use REST API
B. Scenario 1 – Use Email Scripting and Scenario 2 – Use REST API
C. Scenario 1 – Use JavaScript API and Scenario 2 – Use REST API
D. Scenario 1 – Use REST API and Scenario 2 – Use Webhook

View Answer

Answer: B

Explanation:

The way that the Marketo Engage Architect should approach the platform integration is to use Email Scripting for scenario 1 and REST API for scenario 2. These methods will help the Architect to automate and optimize the processes of cloning existing default programs, building emails using RSS feed, scheduling emails, deleting records on Marketo, and pushing data to Donor System. Using Email Scripting for scenario 1 will allow the Architect to dynamically generate email content based on the RSS feed of blog section, instead of manually creating email assets. Using REST API for scenario 2 will allow the Architect to programmatically delete records on Marketo and push data to Donor System, instead of relying on manual or offline methods.

References:

https://docs.marketo.com/display/public/DOCS/Email+Scripting

https://developers.marketo.com/rest-api/