MktgOps2020230612-20230625

Why is this change being made?

Updates for MktgOps2020230612-20230625

1. Updates for non-DG emails and process for Security Releases (WIP) @amy.waller
2. Security release MR updates https://gitlab.com/gitlab-com/gl-security/security-communications/communications/-/merge_requests/29#9f787a6a16a6b8f3fda2896393dacf9291c351d0
3. Iterable + Hightouch Pages @MihaiConteanu !125918 (merged)
4. Internal HB updates @nikkiroth
5. add qualified hb page headers @emathis
6. Added 6sense account buying stage definitions to 6sense hb page - @nikkiroth
7. Issue template updates https://gitlab.com/gitlab-com/marketing/marketing-operations/-/merge_requests/135#note_1432980259 @jennyt
8. PF Page updates !124184 (comment 1433100788)
9. 6sense user roles and role definitions -@nikkiroth
10. Removed conversica as a page @amy.waller
11. Add person region segmentation and definition of person region / region https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/7964 @jennyt
12. Add On-Demand processing for On24 programs that are using On24 for viewing instead of Pathfactory https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/8371 @jennyt

Author Checklist

• 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
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---