Skip to content

MktgOps: 20231016 - 20231029 - Handbook MR

Jenny Tiemann requested to merge mktgops20231016-20231029 into master

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

  1. Update Persona - Level segmentation details (updated to add localized titles and better segment our marketing database) - @jennyt
  2. Update instructions to close a webcast landing page manually (simplified instructions) - @jennyt
  3. Adds a note regarding self-service events and how FM no longer utilizes this campaign type. - @krogel
  4. Update with vartopia sync automation @stran5
  5. Added more context and documentation on the Hightouch page @MihaiConteanu
  6. Updated Search Discovery to Tier 3, un-condensed the list so you can see the tiers more easily. Removed tools that have been canceled. @amy.waller
  7. Added lead scoring slides to the hb page @amy.waller
  8. Update list import template to tag mops in follow up issues https://gitlab.com/gitlab-com/marketing/marketing-operations/-/merge_requests/146#note_1621270329 @jennyt @bweatherford
  9. Create guidelines on Working with Vartopia @stran5
  10. Added info on integrate dap webhook triggers @jburton

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
Edited by Jameson Burton

Merge request reports