In Marketo, Program Success is calculated from program statuses that are flagged “Success” within the channel definition. When you create a custom channel you must therefore include (and mark as “Success”) at least one status—most commonly named “Responded.” Without a success-flagged status, the Program Success and related ROI metrics cannot be tracked for any program that uses that channel.

A. Local forms are irrelevant to the Program Success calculation; success is derived solely from program statuses.

B. Merely uploading members doesn’t mark them with a success status, so success metrics still would not populate.

C. Updating statuses is operationally important but impossible until a success-flagged status exists; the prerequisite is to create that status.

1. Adobe Marketo Engage Product Documentation – Admin > Tags > Channels, Section “Create/Edit Channel,” para. 4: “You must select at least one Program Status as Success (typically ‘Responded’) for program success reporting.”

https://experienceleague.adobe.com/docs/marketo/using/product-docs/admin/tags/channels

2. Adobe Marketo Engage Product Docs – Measure Program Success, “How Program Status Drives Success Metrics,” para. 2.

3. Marketo University (Adobe Digital Learning Services) Course “Core Concepts II,” Module 3 slide 17: “A channel must contain at least one status marked ‘Is Success’ (e.g., Responded) to enable program success reporting.”

The primary purpose of a default value in a token is to serve as a fallback. When a token is used to pull data from a field (e.g., a lead's first name), the default value will be displayed if that specific field is empty for a given record. This ensures that communications do not have awkward blank spaces and maintain a level of personalization, for instance, by substituting "Valued Customer" when a first name is unavailable. This mechanism is crucial for maintaining the quality and professionalism of automated communications.

A. This describes the function of System Tokens (e.g., {{system.dateTime}}), which dynamically insert system-level information, not the purpose of a default value.

C. This describes the function of Program Tokens (e.g., {{program.name}}), which reference attributes of the program they are used in, not a default value.

D. This describes the general purpose of My Tokens, which are custom variables, but it does not explain the specific function of the default value setting within a token.

1. Adobe Experience League, Marketo Engage Documentation. "Add a Default Value to a Token." This document states, "You can add a default value to your token in case the field it’s referencing is blank." This directly supports the correct answer. (Accessed under the "Tokens" section of the Marketo Engage product documentation).

2. Adobe Experience League, Marketo Engage Documentation. "Tokens for a Field in an Email." In the section describing how to insert a token, the documentation instructs: "If you want to add a default value (in case the field is empty), enter it in the Default Value box and click Insert." This confirms the function of the default value as a substitute for empty fields. (Accessed under the "Email" section of the Marketo Engage product documentation).

Marketo's Munchkin code is a JavaScript snippet placed on a website to track user interactions. Its fundamental, out-of-the-box behavior is to log a "Visit Web Page" activity every time a page containing the code is loaded by a user. Additionally, the Munchkin JavaScript API provides developers with the ability to explicitly track link clicks. By invoking the clickLink function, a "Clicked Link on Web Page" activity is recorded in the lead's activity log. These two behaviors—page visits and link clicks—are the core web activities that Munchkin is designed to track.

C. Social media activity: Munchkin tracks activity on your web properties. It cannot track actions a user takes directly on third-party social media sites.

D. Web page bookmarks: Bookmarking is a browser-level function. Client-side JavaScript like Munchkin does not have access to this browser action and cannot track it.

E. Average time spent on site: This is a calculated metric derived from the timestamps of multiple page visits. Munchkin tracks the discrete visit events, not the duration between them.

1. Adobe Experience League, Marketo Engage Documentation, "Understanding Munchkin." This document explicitly states, "Munchkin is Marketo’s custom JavaScript for tracking person activity on your website. It is required to track 'Visits Web Page' and 'Clicks Link on Web Page' activities..." This directly confirms that web page visits and clicks are the primary trackable behaviors.

2. Adobe Experience League, Marketo Engage Documentation, "Munchkin Javascript API." Under the "Supported Methods" section, the clickLink method is detailed. The documentation states, "Use this method to track a link click for a known or anonymous person." This confirms the capability to track web page clicks.

3. Adobe Experience League, Marketo Engage Documentation, "Web Page Activity Tracking." This article describes the types of web activities logged by Marketo. It lists "Visit Web Page" as the activity logged when a person visits a page with the tracking code and "Clicked Link" as the activity for when a person clicks a tracked link, reinforcing that these are the specific behaviors captured.

The most direct and appropriate method for a marketer to identify duplicate leads based on a field other than the default email address is by creating a Smart List. Within the Smart List, the marketer can use a filter for the "Full Name" field and apply a "has duplicate" constraint. This instructs Marketo to query the database and populate the list with all individuals who share the same value in the "Full Name" field, effectively identifying potential duplicates without altering any system-wide settings.

A. Adjust the duplicate System Smart List filter value to Full Name: The "Possible Duplicates" System Smart List is automatically generated based on the system-wide deduplication key (email address by default) and its filters cannot be modified.

C. Edit duplicate identification settings in the Admin panel: This action changes the fundamental, system-wide unique identifier for the entire Marketo instance. It is a significant architectural change, not a simple identification task, and is generally not recommended for a non-unique field like "Full Name".

D. Create a segment using Full Name: Segmentation is used to group people into distinct audiences for targeted marketing campaigns (e.g., by industry or region), not for identifying records with duplicate field values.

1. Adobe Experience League, Marketo Engage Documentation, "Find Duplicate Leads": This document outlines the process for finding duplicates. It states, "You can find duplicate people based on any field you choose... Create a smart list of people who have duplicates." It then provides a step-by-step guide using a filter (e.g., Email Address) with a "is not empty" operator and a "has duplicate" constraint, confirming this is the correct procedure which can be applied to the "Full Name" field. (See section: "Find Duplicates Based on a Field").

2. Adobe Experience League, Marketo Engage Documentation, "Deduplicate Leads": This document clarifies the system-level functionality. It states, "By default, Marketo Engage uses the Email Address field to identify duplicate people." This confirms that changing the deduplication logic requires an administrative change (Option C), which is distinct from simply identifying duplicates via a Smart List (Option B). (See section: "How Deduplication Works").

3. Adobe Experience League, Marketo Engage Documentation, "Understanding Segmentation": This resource defines the purpose of segmentation. It explains, "A segmentation is a sub-division of your database... Use segmentations to run more targeted and relevant marketing campaigns." This confirms that segmentation (Option D) is a tool for audience grouping, not for data quality tasks like deduplication. (See section: "What is a Segmentation?").