Skip to content

MktgOps 20230501 - 20230514

Amy Waller requested to merge mktgops20230501-20230514 into master

Why is this change being made?

Updates for Milestone %"MktgOps: 20230501 - 20230514

  1. Added promotions for @gillmurphy and @stran5
  2. Added new labels and processes for Sales Systems compliance @amy.waller
  3. Marketing Ops campaign support issues @jennyt https://gitlab.com/gitlab-com/marketing/marketing-operations/-/merge_requests/132/diffs
  4. Add MKtg Ops Support details on main MOps page and Campaign and Programs page - @jennyt
  5. Adds resources (requirements template and weekly update template) to new tool section - @nikkiroth
  6. Emergency response hb updates !124110 (merged) @amy.waller
  7. Added LI Lead Gen form instructions for digital marketing - @zbadgley @jennyt
  8. Added wording about do not call / do not email automation to sales dev page, linked section to cognism and zoominfo pages @jburton
  9. Replace pii with personal data https://gitlab.com/gitlab-com/marketing/marketing-operations/-/merge_requests/131
  10. Add GitOps Hands On Workshop Marketo template to campaigns HB page. @bweatherford
  11. Add snippet information and instructions for updating trust snippet to Marketo page. @jennyt
  12. Added info associated with email send marketo program revamp to program and campaign page @jburton
  13. Add detailed QA process for emails to this MR @jennyt
  14. Remove separate processing campaign for in-person workshops @jennyt
  15. Changes to Corporate Events epic to align with new MOps support processes @jennyt
  16. Added / details for landing page types on landing page Hb page @jennyt
  17. Add email and landing page set-up tips and must knows to campaign ops page @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.

Edited by Jenny Tiemann

Merge request reports

Loading