QuestionQ14

Section 2A: Marketo Data Architecture Design

An Adobe Marketo Engage Architect works for a car manufacturing company in Japan and wants to resolve two issues:

  1. The team is receiving errors when trying to integrate Marketo Engage with a Salesforce Custom Object. This Salesforce custom object stores the offers and gifts given to each car owner.

  2. The company needs to store periodic car service details for owners inside Marketo Engage. This would let the team edit the records directly in Marketo Engage, and also use Filters and Triggers to send service reminders through Marketo Engage. Currently, this data is maintained offline in Excel.

Which two approaches can the Architect use to address these challenges?

Choose two
  • A Problem 2: The Admin can use Marketo Engage custom activities
  • B Problem 1: Set the user profile of the Marketo Engage sync user to Admin in Salesforce
  • C Problem 2: The Admin can use Marketo Engage Custom object
  • D Problem 2: The Admin can create a segmentation in Marketo Engage
  • E Problem 1: Set the language of Marketo Engage sync user to English in Salesforce
Explanation

For the Salesforce Custom Object sync errors, the Marketo-Salesforce sync user's language must be set to English in Salesforce, since Marketo's custom object integration requires this setting to correctly map and sync custom object fields and records; leaving it in another language causes sync failures. For storing and managing the periodic car service data with editable records plus the ability to use Filters and Triggers, Marketo Engage's native Custom Objects feature is the correct tool, as it lets admins define, import, and update custom object records tied to leads and use them directly in smart list filters and smart campaign triggers, unlike Custom Activities (built for one-off event logging) or Segmentation (used for content personalization, not data storage).

Community Discussion

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