Marketo provides a specific embed code type called "Lightbox" to display a form within a pop-up modal window on an external website. When a marketer approves a form, they can access the "Embed Code" action. Within the embed code options, selecting "Lightbox" generates the necessary JavaScript to render the form in an overlay on the host page. This is the standard and most direct method to achieve the desired outcome without requiring additional modules or complex workarounds.

B. Design a landing page that gives the visual effect of a pop up window

This is an inefficient workaround, not a direct feature. It involves creating a separate page rather than integrating a pop-up directly onto the existing company website.

C. Change the form type to Lightbox under form settings

This option does not exist within the form editor's "Form Settings." The display behavior (e.g., lightbox, embedded) is determined by the embed code generated, not a setting on the form asset itself.

D. Create a New RTP Dialog Web Campaign

While a Real-Time Personalization (RTP) Dialog campaign can display a form in a pop-up, this is a feature of a separate, more advanced Web Personalization module. The most fundamental method uses the form's own embed code functionality.

---

1. Adobe Experience League - Marketo Engage Documentation: Embed a Form on Your Website.

Section: "Embed Code"

Content: This document explicitly details the steps to get a form's embed code. It lists the "Code Type" options, which include "Lightbox." The description for Lightbox confirms it makes the form "appear in a lightbox when a user clicks a link on your page." This directly supports option A as the correct method.

2. Adobe Experience League - Marketo Engage Documentation: Form Settings.

Section: "Settings" under "Form Editor"

Content: This documentation outlines all available settings within the form editor, such as Font Family, Font Size, and Label Position. It confirms there is no setting to change a "form type" to Lightbox, which invalidates option C.

3. Adobe Experience League - Marketo Engage Documentation: Create a Dialog Web Campaign.

Section: "Web Campaigns"

Content: This document describes the process of creating a Dialog (pop-up) campaign using the Web Personalization feature (formerly RTP). It shows that this is a distinct process from embedding a standard form, involving campaign creation, segment definition, and content selection, thus making option D a different, more complex solution than what is required by the question.

In Marketo forms, when configuring a picklist (Select) field, you have two value options: "Display Value" and "Stored Value." The "Display Value" is the text the user sees and selects from the dropdown list on the live form. The "Stored Value" is the actual data that is written to the Marketo database field upon form submission and subsequently synced to the CRM. To meet the requirement, the user-friendly full state name (e.g., "California") should be the "Display Value," while the CRM-required 2-digit abbreviation (e.g., "CA") must be the "Stored Value."

A. This is the opposite of the required outcome; it would store the full state name, which violates the CRM's data requirement.

B. This configuration is reversed. It would display the abbreviation to the user and store the full state name, failing the CRM's data format rule.

D. "Mark Input" is not the correct terminology for this specific Marketo form functionality, making the option technically inaccurate.

1. Adobe Experience League - Marketo Engage Documentation: In the article "Edit Form Field Settings," under the "Values" section for the "Select" field type, the documentation states: "For Select and Radio Buttons field types, you can enter a Display Value that is different from the Stored Value. The Display Value will appear in the picklist, but the Stored Value is what will be pushed to the field in the person's record." This directly supports the use of "Display Value" for the full name and "Stored Value" for the abbreviation. (Source: Adobe Experience League, Edit Form Field Settings, "Values" section).

Adobe Marketo Engage’s Engagement-Program “Dashboard” tab presents three built-in visual components only:

1. Engagement Score – bar chart showing the average score for each stream.

2. Engagement Over Time – line graph that trends engagement score across casts for the chosen date range.

3. Email Performance – a KPI strip that contains cumulative email statistics, namely Sends, Opens, Clicks and Unsubscribes.

Because “Clicks” is one of the individual KPIs in the Email Performance strip, options A, B and D are the three elements that actually appear on the dashboard.

C. Pending sends – Displayed on the Streams tab, not the Dashboard.

E. Highest Engagement – No such widget; highest score can be inferred but isn’t surfaced as a component.

F. Membership ROI – ROI metrics are available via Program Performance reports, not on the Engagement dashboard.

1. Adobe Marketo Engage Product Docs, “Engagement Program Dashboard,” Sections “Engagement Score,” “Engagement Over Time,” and “Email Performance (Sends, Opens, Clicks, Unsubscribes).” experienceleague.adobe.com (Accessed 27-Nov-2025).

2. Adobe Digital Learning Services, “Marketo Core Concepts: Engagement Programs,” Module 3, slides 14-16 (Dashboard overview).

3. Adobe Marketo Engage Product Docs, “Streams Tab,” para. 2 – description of Pending Sends displayed per stream (not on dashboard).

4. Adobe Marketo Engage Product Docs, “Program Performance Report,” Section “ROI Analysis,” confirming ROI shown outside the dashboard.

To meet the legal requirements of countries with double opt-in laws (such as Germany), a specific, multi-step process must be implemented. This involves a person first submitting their information via a form and then confirming their subscription by clicking a unique link in a follow-up email. In Marketo Engage, this is accomplished by creating a set of processes, typically involving two smart campaigns: one to send the confirmation email upon form submission, and a second to listen for the confirmation link click, which then officially opts the person into marketing communications. This entire workflow constitutes the "processes" required for compliance.

A. Include an Unsubscribe link in all marketing emails

This is a requirement for opting out under laws like CAN-SPAM and GDPR, but it does not address the initial, two-step confirmation process required for double opt-in.

B. Add a checkbox with verbiage stating that by filling out the form, the lead consents to receive email

This action establishes single opt-in (explicit consent), but it lacks the second verification step (clicking a confirmation link) that defines and is required by double opt-in laws.

C. Suppress all non-US respondents

This is a business strategy to avoid the compliance challenge altogether, not a solution to meet the legal requirements for the leads you wish to engage.

1. Adobe Experience League, Marketo Engage Documentation, "Set up a Double Opt-in Process." This official guide details the necessary steps, which involve creating two distinct smart campaigns. It states, "Double opt-in is when a user subscribes to a mailing list and then receives a confirmation email with a link they must click to confirm their subscription." The entire procedure described is a "process," confirming that option D is the correct high-level action required.

2. Adobe Experience League, Marketo Engage Documentation, "GDPR and Marketo Engage." In the section on "Consent," the documentation emphasizes the need for systems to manage and record consent. It notes that for jurisdictions requiring it, "Marketo Engage can be configured to support a double opt-in process." This configuration is precisely the creation of processes mentioned in option D.

The Recipient Time Zone feature in Marketo Engage is designed for batch-based communications, allowing emails to be delivered at a specified time relative to the recipient's inferred time zone. This functionality is available when scheduling an Email Program (like a newsletter) or a Batch Smart Campaign (like an event invitation). These initiatives have a defined, one-time or recurring schedule where this option can be selected. Triggered campaigns execute in real-time and do not have a schedule, while the core stream cadence of an engagement program is a single, fixed schedule for all members, not individualized by time zone.

A. The stream cadence for an engagement program is set to a single, specific time and time zone for all recipients in the stream, not on a per-recipient basis.

D. Similar to option A, the content of the stream (email assets only) does not change the fundamental way the stream cadence is scheduled as a single, fixed time.

E. Trigger smart campaigns execute immediately in response to a specific event. They are not scheduled in advance, so time zone-based delivery is not applicable.

1. Adobe Experience League, Marketo Engage Documentation, "Schedule an Email Program." This document explicitly shows the "Recipient Time Zone" checkbox in the scheduling step for an Email Program. It states, "Check the Recipient Time Zone box to have the email delivered at the specified time in the recipient's time zone. If unchecked, it will be delivered in the subscription's time zone." This directly supports option B.

2. Adobe Experience League, Marketo Engage Documentation, "Schedule a Batch Campaign." This guide details the scheduling options for a batch smart campaign, which is the mechanism used in option C. The documentation includes a section on the scheduler with the "Recipient Time Zone" checkbox, explaining its function to run the campaign at the specified time in the lead's time zone. This supports option C.

3. Adobe Experience League, Marketo Engage Documentation, "Edit an Engagement Program Stream Cadence." This source clarifies how stream cadence is configured. It shows a single time and time zone selection for the entire stream cast, stating, "Set the day(s), time, and time zone you want the cast to go out." This confirms that the cadence itself is not individualized by recipient time zone, making options A and D incorrect.

4. Adobe Experience League, Marketo Engage Documentation, "Using Triggers in Smart Campaigns." This document explains that triggers "listen for specific events to happen" and "run in near real-time." This confirms that triggered campaigns are not scheduled and therefore cannot use the Recipient Time Zone feature, invalidating option E.

To link the two smart campaigns across different programs, the initiating campaign ("03 Success") must actively call the target campaign ("01 Send Invite"). This is accomplished by adding a "Request Campaign" flow step to the "03 Success" campaign. In turn, the "01 Send Invite" campaign must be configured to listen for this specific call. This requires adding the "Campaign is Requested" trigger to its smart list. This trigger/flow step combination is the standard, most efficient method in Marketo for one smart campaign to execute another, ensuring the demo invite is sent immediately after a person achieves success in the ebook program.

B. The "03 Success" campaign is the initiator; it requires a flow step to request an action, not a trigger to listen for one.

C. While this could work, using "Request Campaign" is the more direct and standard best practice for inter-campaign communication without the side effect of changing program membership.

D. This is incomplete. Adding the "Campaign is Requested" trigger is necessary, but without the corresponding "Request Campaign" flow step in the other campaign, it will never be activated.

1. Adobe Experience League - Marketo Engage Documentation: The "Request Campaign" flow step is used to trigger a separate smart campaign. The documentation states, "Use the Request Campaign flow step to trigger another smart campaign." This confirms the need for this step in the "03 Success" campaign.

Source: Adobe Experience League, "Request Campaign Flow Step," in Marketo Engage Product Docs.

2. Adobe Experience League - Marketo Engage Documentation: The "Campaign is Requested" trigger is the corresponding listener for the "Request Campaign" flow step. The documentation specifies, "Use the Campaign is Requested trigger in a smart campaign when you want it to be triggered from another smart campaign's Request Campaign flow step." This confirms the need for this trigger in the "01 Send Invite" campaign.

Source: Adobe Experience League, "Campaign is Requested Trigger," in Marketo Engage Product Docs.

Program report subscriptions in Marketo Engage can be managed in two primary locations. First, you can manage the subscription for a specific report directly by navigating to that report within a program in the Marketing Activities area and using its dedicated "Subscriptions" tab. Second, the Analytics area provides a centralized "Subscriptions" tab where a user can view, edit, or delete all of their report subscriptions from across the Marketo instance, including those for program-specific reports. This centralized view is essential for holistic management of all automated report deliveries.

B. In the Subscriptions tab in Marketing Activities: There is no global "Subscriptions" tab at the top level of the Marketing Activities area; subscription management is done within individual reports.

D. In the Subscriptions tab in Database: The Database area is used for managing person records, lists, and data quality. It does not contain functionality for managing report subscriptions.

---

1. Adobe Experience League. (n.d.). Subscribe to a Report. Marketo Engage Documentation.

Section: "Subscribe to a Report" and "Good to Know".

Content: The documentation details the process of opening a report (such as a Program Performance Report in Marketing Activities) and clicking the "Subscription" tab to create a new subscription. It also explicitly states, "To see a list of all your subscriptions, go to the Analytics area and click the Subscriptions tab." This supports both correct answers (A and C).

2. Adobe Experience League. (n.d.). View and Manage Report Subscriptions. Marketo Engage Documentation.

Section: "View and Manage Report Subscriptions".

Content: This document confirms that the central location for managing all subscriptions is within the Analytics section. It states: "You can view and manage all of your report subscriptions in one convenient place... Go to Analytics... Click the Subscriptions tab." This directly supports answer C as a location for managing subscriptions, including those for program reports.

The most effective and intended method to filter the Program Performance Report by a program-level attribute, such as geographic region, is by using Program Tags. Tags are metadata specifically designed to categorize and organize Marketo assets. By creating a "Region" tag type and applying the appropriate tag value (e.g., "EMEA," "NA") to each program, the marketer can then use the "Program Tag" filter on the report's Setup tab. This precisely configures the report to include only the programs that match the specified geographic region, directly fulfilling the requirement.

A. Custom columns are used to add data fields to the report's output for viewing; they do not filter which programs are included in the report's scope.

C. The smart list within the report setup filters the people whose activities are counted in the report's metrics, not the programs themselves.

D. The drill-down feature is used for exploring data within an already generated report; it is not a tool for setting the initial scope or filtering criteria.

---

1. Adobe Marketo Engage Documentation, "Program Performance Report." This document details the report's configuration. Under the "Setup Tab" section, it explicitly lists "Program Tag" as a primary filter to "select the program tag(s) you want to report on." This directly supports using tags as the filtering mechanism.

2. Adobe Marketo Engage Documentation, "Program Tags Overview." This guide states, "Tags are a great way to add metadata to your programs for filtering and reporting purposes." This confirms that using tags for reporting is a best practice and the feature's intended function.

3. Adobe Marketo Engage Documentation, "Create a Program Tag." This article explains the process of creating tag types and values. It notes that once created and applied, these tags become available in report filters, reinforcing that this is the correct procedure for achieving the user's goal.