QuestionQ11

Section 2B: Marketo Campaign Architecture Design

Unicorn Fintech and their Adobe Marketo Engage Architect want to update their existing scoring approach for web-based behaviors. One of the areas identified for change is the forms. Instead of using a single score value for all forms, they want to apply three different score values depending on whether a form is:

  • Low value (+3)
  • Medium value (+7)
  • High value (+15)

What is the most scalable way to implement this change?

  • A Update the hidden Behavioral Score fields in each form to have the appropriate “My Token” score for the value of the form.Make sure this triggers a Score field update as well.
  • B Build Smart Campaigns that trigger based on the appropriate form into the Scoring Program.Add the appropriate score values into the ‘Change Data Value’ flow step, then switch on.
  • C Build Smart Campaigns that trigger based on the appropriate form into the Scoring Program.Add the appropriate score value ‘My Tokens’ into the ‘Change Score’ flow step, then switch on.
  • D Update the hidden Behavioral Score fields in each form to have the appropriate score values for the value of the form.Make sure this triggers a Score field update as well.
Explanation

Marketo's recommended scoring architecture centralizes all scoring logic in a dedicated Scoring Program. Smart Campaigns are built to trigger off the relevant behavior (in this case, submission of each specific form) and route into that Scoring Program, where a 'Change Score' flow step applies the point value. Rather than hardcoding the score numbers directly in each flow step, best practice is to reference 'My Tokens' set up in the program (e.g., a token for +3, +7, and +15) so that all score values can be managed and updated from one central location without editing individual forms or campaigns. This token-driven, Change Score flow step approach is scalable because future score adjustments require only a token change in the Scoring Program, not modifications across every form or hidden field.

Learn more

Community Discussion

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