Marketing Operations (Mktg OPS) supports the entire Marketing team as well as other teams within GitLab. Mktg OPS works closely with Sales Operations to ensure information between systems is seamless and we are using consistent terminology in respective systems.
For information regarding the tech stack at GitLab, please visit the Business Operations section of the handbook where we maintain a comprehensive table of the tools used across the Marketing, Sales and Customer Success functional groups.
For Q4 2017, we will be using an Issue Board to track our department OKRs.
To create an OKR issue do the following:
When you start working on an OKR, update the label from ‘Not Started’ -> ‘Progressing’. If creating "sub-Issues" related to your META OKR Issue, associate using the 'Related Issue' section.
Merge Requests related to OKRs should also be associated ‘Q4 2017’ Milestone and contain ‘OKR’ & team label.
When creating an event (live or online), webcast, or gated content its important to integrate the campaign across the three main platforms used - Unbounce (landing page), Marketo (Marketing Automation) and Salesforce (CRM). This provides transparency about the event to anyone with access to Salesforce, namely the Sales and Marketing teams.
Instructions to create an event from scratch or clone an existing event.
|GL Code||Account Name||Purpose|
|6100||Marketing||Reserved for Marketing GL accounts|
|6110||Marketing Site||All software subscriptions, agency fees and contract work intended to improve the marketing site should go here|
|6120||Advertising||All media buying costs as well as agency fees and software subscriptions related to media buying should go here|
|6130||Events||All event sponsorships, booth shipping, event travel, booth design, event production as well as agency fees and software costs related to events should go here|
|6140||All 3rd party email sponsorships as well as agency fees and software costs related to mass email communications and marketing automation should go here|
|6150||Brand||All PR, AR, content, swag and branding costs should go here|
Email database management is a core responsibility for Mktg OPS. Ensuring GitLab is following email best practices, in compliance with International spam laws and overall health of active database are all priorities.
To request an email, create an issue in Marketing and assign it to JJ Cordz (in addition to whomever else needs to be aware of email). Required request information, please be as complete as possible in providing detail related to the email:
As of 22 August 2017, all email marketing communications are explicit opt-in. Using the Email Subscription Center, users can control their email communication preferences. There are currently 4 email segments.
Database segments and how someone subscribes to specific segment:
Breaking Change Emails
These are operation emails that can be sent on a very selective as needed basis. This is an operational-type email that overrides the unsubscribe and does not provide the opportunity for someone to opt-out. Usage example: GitLab Hosted billing change, Release update 9.0.0 changes, GitLab Page change and Old CI Runner clients. It is very important to have Engineering and/or Product team (whoever is requesting this type of email) help us narrow these announcements to the people that actually should be warned so we are communicating to a very specific targeted list.
Sent bi-monthly (every 2 weeks). Content Team is responsible for creating the content for each Newsletter.
Sent on an as needed basis containing important information about any security patches, identified vulnerabilities, etc related to the GitLab platform. These emails are purely text based.
Invitation and/or notification emails sent about future webcasts.
Invitation emails to attend a live event (VIP or Executive Lunch), meetup, or in-person training. These emails are sent to a geolocational subset of the overall segment. This type of email is also used when we are attending a conference and want to make people aware of any booth or event we may be holding and/or sponsoring.