Some MQL clarification
Why is this change being made?
As we move into new territory with online events, we are seeing an increase in actions that have not been done before with requests for points related to Lead Scoring. Until we can completely revamp the scoring later this month, this clarifies what it means to MQL and that my approval is required for scoring any new types of events.
@amy.waller @cbeer not sure if you also just want to update more info in the scoring model as I know we've made some additional tweaks since March?
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency] -
Assign this change to the correct DRI - If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack].
- If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping
@gl-static-site-editor
in a comment for a review and merge. For example changes to.gitlab-ci.yml
, JavaScript/CSS/Ruby code or the layout files.
Merge request reports
Activity
This is great. One suggestion to add under the description is that they have to provide scoring examples on how they got to the suggested new score. Reason being, the recent adjustments that I have seen were high and the explanation is then tied to a score that is high and not necessarily within the tactic.