Marketo Interesting Moments
Commonly used Interesting Moments and what they mean
Overview
Interesting moments are used by Marketo to show relevant information to the sales team and others in Salesforce.com
Interesting Moments show in two places on records, in the Marketo Sales Insight window or in the Last Intersting Moment Description field. This field updates dynamically every time an Interesting Moment is updated and date stamped.
Common Interesting Moments
Use this table as a quick reference when a LIM appears in Marketo Sales Insight.
| SFDC Campaign | Interesting Moment | Description | Action Required |
|---|---|---|---|
| Request - Hand Raise PQL | HandRaise PQL - Contact Us on {{system.date}} |
Product qualified lead who explicitly requested to speak with Sales from within the product. This is a high-intent hand raise, not a passive engagement signal. | Immediate follow-up required. Treat this as an active request for Sales contact, review recent product context before outreach, and prioritize a fast, direct response. |
| Request - DAP Hand Raise PQL | DAP Hand Raise PQL - contacted us to purchase DAP credits on {{system.date}} |
Product qualified lead who explicitly requested to speak with Sales about DAP credits from within the product. This is a DAP-specific hand raise and should be treated differently from a generic Contact Us request. | Immediate follow-up required. Treat this as an active DAP purchase conversation, review the account’s DAP context before outreach, and tailor the response to credit purchase intent rather than general interest. |
| Purchase - DAP Monthly Commit - SM | User purchased DAP monthly commit creates for Self Managed. | A free self-managed EE user completed a DAP monthly commit purchase. Marketo can distinguish first purchase, increase credits, and default purchase variants. | Review the purchase context and tailor outreach based on whether this was a first purchase or an increase-credits event. |
| DAP Monthly Commit Cart Abandonment - First Purchase | User started checkout to first DAP credits purchase but abandoned the cart before completing purchase. |
The person abandoned a DAP monthly commit flow on a first-purchase path. | Follow up based on purchase intent. |
| DAP Monthly Commit Cart Abandonment - Increase Credits | User started checkout to increase DAP credits but abandoned the cart before completing purchase. |
The person abandoned a DAP monthly commit flow on an increase-credits path. | Follow up based on add-on credits intent. |
| Request - Direct Purchase Account Creation Premium Dotcom | User created a GitLab account via the direct purchase GitLab.com signup path. |
The person created a GitLab account through the direct purchase signup path for Premium Dotcom. This is a purchase-intent signal tied to account creation, not a generic signup. | Use this as purchase-path context. Check whether the person completed the purchase or took a later conversion step before outreach, and tailor messaging to Dotcom Premium purchase intent. |
| Request - Direct Purchase Account Creation Premium SM | User created a GitLab account via the direct purchase SM signup path. |
The person created a GitLab account through the direct purchase signup path for Premium Self-Managed. This is a purchase-intent signal tied to account creation, not a generic signup. | Use this as purchase-path context. Check whether the person completed the purchase or took a later conversion step before outreach, and tailor messaging to Self-Managed Premium purchase intent. |
| Request - SM Welcome Flow No Trial Contact | User set up their profile, however doesn't sign up for the SM Trial. |
The person went through the self-managed welcome flow, requested contact, and did not start a trial. This is a self-managed interest signal without a trial event. | Review as a self-managed contact signal. Confirm routing and recent product/account context, then tailor outreach to self-managed interest rather than trial follow-up. |
| Enrichment - SM Free Hostname Match | Self-Managed Free User identified via hostname match (ZoomInfo enriched). Account has active GitLab CE/EE usage. |
A self-managed free user was matched to an account by hostname and enriched with ZoomInfo. The account has active GitLab CE/EE usage. | Keep in nurture until MQL, then route to Sales Dev. |
| FY20_Startup Application | Filled out startup application form |
A person submitted the startup application form. | Pass to User: Community Advocate. |
| TBD | Startups Application Rejected - Sales Dev required to immediately follow up |
A rejected startup applicant re-engaged, and the LIM gives Sales Dev more context. | Review the startup context before outreach. |
| Request - GitLab Dedicated | Filled out Contact Us Form - GitLab Dedicated |
The person submitted interest in GitLab Dedicated. | No action necessary. |
| PF - Fast Moving Buyer Alert | Engaged with Content Track: {{lead.PathFactory Experience Name}}, Session Engagement Time (seconds): {{lead.PathFactory Engagement Time}} |
Fast Moving Buyer alert from PathFactory. | No action necessary. |
| N/A | Lead has reached 6QA status, and this SMB lead has been autosequenced in Outreach |
A new SMB 6QA lead was created and automatically placed into Outreach. | Monitor the sequence for replies and engagement. |
| N/A | Lead has reached 6QA status and this MM/ENTG lead has been added to the SFDC dashboard. Proceed with outreach. |
A new MM/ENTG 6QA lead was created and added to the dashboard for rep action. | Review the lead in the SFDC dashboard and proceed with outreach. |
| N/A | Logged in through the GitLab Subscription Portal |
The person logged in via the subscription portal. | Check for duplicates with Web Direct; no follow-up needed. |
| Various | Downloaded XX from 3rd Party site: Integrate |
The person downloaded a GitLab-owned asset through a content syndication platform. | Review campaign history or campaign details to identify the asset before acting. |
| N/A | This lead is part of a namespace that has checked to setup GitLab for Company/Team use |
The signup owner said the namespace is for company or team use, and this person is a member of that namespace. | No action; FYI only. |
| Note: FY27 UserGems contact-tracking LIM logic is still in progress and is not listed here yet. |
Last modified July 10, 2026: User Signal > Signal Detected updates (
3f84d133)
