WIP MktgOps: 20240527 - 20240609
Why is this change being made?
- Added instructions on Non-MDF campaign - @stran5
- Fix the Marketing Ops and Analytics link in the intro on the Marketing page - @jennyt
- Remove hopin references from the virtual events page - @jennyt
- Various updates to the lead scoring page @jburton
- Added a blurb to push 6senses segments to Marketo in public and internal https://gitlab.com/gitlab-com/content-sites/internal-handbook/-/merge_requests/4883 -
@stran5
- Issue template for adding an audience (6sense) to Marketo https://gitlab.com/gitlab-com/marketing/marketing-operations/-/merge_requests/164 - @stran5
- Added when partner leads shouldn't be worked on by Sales Dev - @stran5
- Added FAQ on Partner Leads for Sales Dev -
@stran5
CHANGEME
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
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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 -
Division: If the update affects your division, share the MR in your division 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 - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- Update file vartopia.md
Edited by Salina Tran