QuestionQ30

VerifiedSection 2B: Marketo Campaign Architecture Design

A company's Contact Us form includes a text field labeled "Comments," where prospects describe their needs so that Sales has context for follow-up. Submitting this form generates a Marketing Qualified Lead (MQL) that is sent to Sales.

Key details:

  • The "Comments" field is a custom text field.
  • Leads frequently write lengthy descriptions that exceed 140 characters.
  • The "Comments" field is not synced to CRM.
  • A separate field called "Notes" is synced to CRM and is also a text field.
  • The "Notes" field is commonly used—and frequently overwritten—by Sales.
  • Both Sales and Marketing agree that the "Comments" field is valuable and want to preserve space for prospects to describe their needs in detail.

An Adobe Marketo Engage Architect must configure an Interesting Moment that is triggered by the Contact Us form fill and that includes the value entered in the "Comments" field, so Sales gets immediate context about the inquiry.

Which two actions must the Architect take to achieve this?

Choose two
Explanation

Interesting Moments support tokens, including person-field tokens, so a token can insert the submitted Comments value when the moment is created. A dedicated Comments field must also exist in CRM and be synchronized/remapped to Marketo so the inquiry text is retained in its own CRM field rather than overwriting the Sales-maintained Notes field. Adobe documents that CRM custom fields synchronize to Marketo and that Support can remap existing synchronized fields.

Learn more

Community Discussion

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