Skip to content

MktgOps: 20231127-20231210

Nikki Roth Silverberg requested to merge nikkiroth-main-patch-8849 into main

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.

CHANGEME - add the details saying why, not just what.

  1. Adds guidance about publishing segments to 6sense - @nikkiroth
  2. Add link to gated content set-up instructions on the campaigns and programs page - @jennyt
  3. added info about MQL score stamps to marketo page - @jburton
  4. Creates Nikki's README - @nikkiroth
  5. Created my README - @stran5
  6. Adds stakeholder mapping documentation to main mops hb - @nikkiroth
  7. Removed Self-service from Campaigns page https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/8642 @jennyt @amy.waller
  8. Add Vartopia DR campaign change request - @stran5
  9. Add all of the steps to properly configure a 6sense user in the platform and in SFDC - @nikkiroth
  10. Clarify new tool evaluation process based on tier - @nikkiroth
  11. Marketo template updates @jennyt https://gitlab.com/gitlab-com/marketing/marketing-operations/-/merge_requests/150
  12. Added instructions for what to do if a list is imported to the wrong program (and other issues) @jennyt

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 Jenny Tiemann

Merge request reports