mktgops-20230403-20230416

Why is this change being made?

HB Updated for Milestone: MktgOps: 20230403 - 20230416

What was done:

  1. Added Iterable page @amy.waller @MihaiConteanu
  2. Added banner to the DB page about the switch to 6sense - @nikkiroth
  3. Created 6sense page - @nikkiroth
  4. Added hyperlink from DB page to 6sense page - @nikkiroth
  5. Moving Remaining Licenses Comms Plan from Mops Page to Zoominfo page - @RobRosu
  6. Zoominfo Licensing Policy and Procedures - @RobRosu
  7. Added Partner Sponsored Event workflow - @stran5
  8. Added documentation on the #mktgops slack emoji responses - @nikkiroth @jburton

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 Nikki Roth Silverberg

Merge request reports

Loading
Loading