Marvin Live Intercept helps you collect in-the-moment feedback. You can set a trigger on any webpage or within your product, and Marvin launches an AI interviewer to capture user feedback while they are still moving through a workflow.
Visitors to your website or app will see the widget when the trigger condition you set up is met. If they agree to give feedback, the AI Interviewer will begin the session and follow your discussion guide for the entire interview.
What are Live Intercept triggers?
Visitors to your website or product will receive a nudge to give feedback or start an interview only if certain rules are met.
From the Triggers tab, you can control when visitors are intercepted.
Based on the rules you set, Marvin will trigger the widget to pop-up and nudge visitors to give feedback.
Automatic triggers vs button-linked triggers
You can choose to launch an intercept automatically when the conditions you set are fulfilled.
Select Automatically at the top of the page to set the conditional triggers. Automatic launches can even be linked to a custom event on your webpage or domain, such as a successful checkout. To do that, add this snippet in your website/product's code at the exact point where the action happens. Use the same event as your trigger.
window.MarvinIntercept.trackEvent("{{custom event name}}");If you can't make changes to the code, please share this snippet with the team concerned
Or you can show the Intercept to visitors when they click a specific button or link, and all the conditions are met. Linking the Intercept trigger to a button or link can help you gauge intention and target users who show are more likely to complete the interview.
Select Click of link/button to set the conditional triggers. To link the widget to a button, you must locate the button ID. You can do this using your browser’s developer tools.
1. Open the webpage where the button is located.
2. Right-click the button and select Inspect (or press Ctrl + Shift + C [Win/Linux] or Command + Option + C [Mac]).
3. In the Elements tab, locate the highlighted button element and look for the id attribute in the HTML.
Note: If the button does not have an id attribute, contact your web developer or tech team to identify the correct element or assign a unique ID.
4. Copy the ID and paste it in Marvin, under Clicked ID is.
Trigger rules
Whichever option you choose, you can add rules to decide when the Intercept is triggered.
For example, you can limit the Intercept to visitors on a specific page, or those who spend at least 3 minutes on your product.
Use this quick reference guide to identify how each trigger works and which one is the best way to find the right people to interview.
Trigger type | Trigger | Target visitors who |
Page | Current page URL | Visited a specific page of your product or app, such as pricing, or the checkout page.
Example: Learn why users didn't complete their checkout. |
Page | Has visited URL | Visited a combination of pages, such as product features and then pricing.
Example: Ask users if the pricing, checkout issues, or something else prevented them from completing a purchase. |
Events | Clicked | Clicked a specific button, heading, or list on a page.
Example: Gather feedback from visitors who tried a new feature or clicked Learn More. |
Events | Custom event | Did a specific action, such as completed checkout, filled a form, or downloaded a report (you must track these events in your website/product to use them as a trigger).
Example: Engage users who downloaded your latest how-to ebook or guide. |
Session | Duration | Spent at least a certain amount of time on your website or product.
Example: Intercept users who spend more than 10 minutes on the checkout page. |
Session | Active duration | Similar to Duration, but excludes the time the visitor spent on another application or tab. |
Session | First time visit | Are new users
Example: Help onboard users or collect first-impression feedback |
Session | Pages viewed this session | Viewed at least or not more than a certain number of pages on your website product
Example: Speak to visitors who have visited at least 4 pages, indicating they want more information on a topic. |
Location | Country | With an IP address from a specific country.
Example: Gather feedback on localized messaging, region-specific features, or compliance-driven surveys. |
Technology | Browser | Using a specific browser
Example: Debug or collect feedback only from Google Chrome users. |
Technology | OS | Using a specific OS
Example: Get feedback from iOS users. |
Technology | Device | Are on a specific device
Example: Compare feedback from for mobile vs desktop visitors to improve the experience. |
Source | UTM source | Were redirected from a specific campaign, channel, or referral source
Example: Speak to users who saw an ad on Linkedin to understand user personas better. |
Audience
Use the Audience tab to control who sees the Intercept widget. It can be everyone who meets the criteria you set up in Triggers, or you can add more filters.
Select Everyone if you don’t need to set up audience filters.
Select Custom to add criteria for user details, custom properties, and participation is other Intercepts.
To filter by user properties, you must have modified the code in your website/product to collect user properties. You can find and share this snippet under Installation in the Live Intercept tab.
window.MarvinIntercept.identify({
user_id: "{{user_id}}",
name: "{{name}}",
email: "{{email}}",
});
To filter by custom properties, you must add this snippet to your website/product's code.
window.MarvinIntercept.setCustomParams({ {{param1}}: "{{value1}}", {{param2}}: "{{value2}}", {{param3}}: "{{value3}}", });Custom properties could be role, company, cohort, etc.
The filters for Previous Intercepts let you control how often visitors are being
prompted to give feedback. For example, you may not want to show the same user to separate Intercepts currently live in your product. Or you may want to follow up with users who gave feedback on a feature after you release an update.
Use this quick reference guide to identify how to apply audience filters.
Filter type | Filter | How to use this filter |
User | User ID | Show or hide the widget from specific users, based on the user ID in your database.
Example: Intercept users who signed-up for an early access waitlist. |
User | Show or hide the widget from a specific email domain.
Example: Speak to users from specific companies. | |
User | Name | Show or hide the widget from specific users, based on the name in your database. Similar to User ID. |
Custom properties | Custom | Filter by custom attributes you track on your website/product, such as created_first_document or visited_aboutus. You must make changes to the code to see the custom properties in the Audience tab. |
Previous Intercepts | Custom | Include or exclude visitors who may have seen, completed, or skipped another Marvin Live Intercept
Example: Control how often visitors are being asked for feedback |
Choose what happens if a user dismisses/completes the interview
In the Settings tab, you can limit visitors from seeing the widget if they've already dismissed it or completed an interview.
Customize these settings to refine the user experience and improve your chances of getting feedback with an Intercept.
Still have questions? Write to us at [email protected]. We'll be happy to speak to you.