Update marketing metrics page MQL fields

Why is this change being made?

Changes the Marketing Metrics Page to reflect our current MQL date

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 Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • 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
  • The when to get approval handbook section explains the workflow in more detail
• 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
  • 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

---

sites/handbook/source/handbook/marketing/strategy-performance/marketing-metrics/index.html.md

@@ -62,21 +62,22 @@ There is a set of fields that show information regarding the First Order (FO) st
 1. `FO MQL` - this shows whether or not, at the time of the `MQL DateTime` (the most recent time the record MQL'd), the record was a FO record
 ##### Date of MQL
-Finding when a lead/contact became an MQL requires accounting for leads/contacts who skipped the MQL stage. 
-To do this we take the lesser of `mql_date`(`Marketo MQL DateTime` in SFDC) and `mql_inferred_date` (`SFDC MQL DateTime` in SFDC). Note: Both of these fields are hidden from views and only the SoT fields below are visible, for simplicity and consistency. 
-There are two new fields in SFDC, `MQL DateTime` that is the lesser of the above two fields and `Initial MQL DateTime` which is the SoT for the first time a record MQL'd - these are the only two fields that should be used in reporting on when a record MQLs. 
-The logic for finding when a person became an MQL is captured in the `mql_reporting_date` field. The `mql_reporting_date` field should always be used to report inquiries unless you are looking for something specific.
-| Field Label (SFDC)           | Field API Name           | Definition                                                                                                                            | Purpose and When to Use                                         |
+To find the date of when someone became an MQL, we use the date field from Marketo (`Marketo MQL DateTime` in SFDC). While this field is not stampted and can change if someone re-MQLs, it makes our reporting easier to understand, matches what Sales Development uses, and matches the data in Marketo.
+While we use `Marketo MQL DateTime` for all our standard reporting, we are aware of some of the issues with using this field: 
+- MQL Dates can change if a person re-MQLs
+- The MQL field will be blank for someone who skips the MQL stage
+For circumstances where the cavacts above impact reports, we have created the MQL fields below:
+| Field Label (SFDC)           | Field API Name           | Definition                                                                                                                              | Purpose and When to Use                                         |
 |------------------------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|
+| Marketo MQL DateTime         | MQL_Date__c              | Set by Marketo when a record reaches the MQL Threshold.  Updates each time this happens.                                                 | Default when reporting on MQLs              |
 | [Beta] MQL DateTime          | True_MQL_Date__c         | The true/reportable MQL Date for the most recent MQL of a record. Lesser of Marketo MQL DateTime and SFDC MQL DateTime                   | Current MQL Count/ When a record most recently MQL'd |
 | Initial MQL DateTime         | True_Initial_MQL_Date__c | The true/reportable MQL Date for the first/initial MQL of a record. Lesser of Initial Marketo MQL DateTime and Initial SFDC MQL DateTime | When a record First MQL'd                            |
 | Initial Marketo MQL DateTime | Initial_MQL_Date__c      | Set by Marketo when a record reaches the MQL Threshold. Stamped the first time this happens                                              | input metric - not needed for reporting              |
 | Initial SFDC MQL DateTime    | Initial_MQL_DateTime__c  | Set by SFDC when a record skips the MQL Stage, Inquiry > Accepted for example. Stamped the first time this happens.                      | input metric - not needed for reporting              |
-| Marketo MQL DateTime         | MQL_Date__c              | Set by Marketo when a record reaches the MQL Threshold.  Updates each time this happens.                                                 | input metric - not needed for reporting              |
 | SFDC MQL DateTime            | MQL_DateTime_Inferred__c | Set by SFDC when a record skips the MQL Stage, Inquiry > Accepted for example. Updates each time this happens.                           | input metric - not needed for reporting              |
 ##### Technical Definition