Draft: mktgops 2025-10-22-2025-10-31

Why is this change being made?

• Update Subscription portal LIM & Scoring @jennyt
• Internal HB updates https://gitlab.com/gitlab-com/content-sites/internal-handbook/-/merge_requests/7623 @amy.waller @jennyt

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct
  • The when to get approval handbook section explains when DRI approval is required
  • The who can approve handbook section explains how to identify the DRI
  • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
  • The approver may merge the MR. If they approve but don't merge, you can merge.
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• update LIM

---

This change updates the description of what happens when someone interacts with GitLab's subscription portal. Previously, it tracked when someone "created" something from the portal (indicating they started a purchase process), but now it tracks when someone simply "logged in" to the portal. The updated description clarifies that this is just a login event and that no follow-up action is needed from the sales team, whereas before they would check for duplicate records with web direct purchases.