Marketing Operations (MktgOPS) supports the entire Marketing team as well as other teams within GitLab. MktgOPS works closely with Sales Operations (SalesOPS) 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 Tech Stack Applications page of the Business Operations handbook where we maintain a comprehensive table of the tools used across the company.
Tools directly used by Marketing and maintained by Marketing Operations:
The MktgOPS team works from issues and issue boards. If you are needing our assistance with any project, please open an issue and use the ~MktgOPS label anywhere within the GitLab repo.
MktgOPS uses a global issue board and will capture any issue in any group/sub-group in the repo. There is also a Marketing Operations project within the Marketing project.
Labels to use:
MktgOPS: Issue initially created, used in templates, the starting point for any label that involved Mktg OPSMktgOPS - FYI: Issue is not directly related to operations, no action items for Mktg OPS but need to be aware of the campaign/email/eventMktgOps-Priority::1 - Top Priority: Issue that is related to a breaking change, OKR focus, any other prioritized project by Mktg OPS leadership. This category will be limited because not everything can be a priority.MktgOps-Priority::2 - Action Needed: Issue has a specific action item for Mktg OPS to be completed with delivery date 90 days or less from issue creation date. This tag is to be used on projects/issues not owned by Mktg OPS (example: list upload).MktgOPS-Priority::3 - Future Action Needed: Issue has a specific action item for Mktg OPS, the project/issue is not owned by Mktg OPS and delivery or event date is 90 days or more from issue creation.MktgOPS::1 - Planning: Issues that are currently being scoped/considered but are not being actively worked on.MktgOps::2 - On Deck: Issues that have been scoped/considered and will be added to the In Process queue next.MktgOPS::3 - In Process: Issues that are actively being worked on in the current week/sprint (week? Month? Two-week period?)MktgOps::4 - UAT: Issues that MktgOps has completed its required tasks for and is ready for review and approval by the Requester/Approver.MktgOPS::5 - On Hold: Issue that is not within existing scope of Mktg OPS current targets, blocked by MktgOps-related task/issue, or external (non-GitLab) blocker.MktgOps::6 - Blocked: Issue that is currently being worked on by Mktg Ops and at least one other team wherein Mktg Ops is waiting for someone else/another team to complete an action item before being able to proceed.MktgOps::7 - Completed: MktgOps has completed their task on this issue although the issue may not be closed.The MktgOPS team is responsible for importing records into Salesforce (SFDC) for both field events and prospecting. The process to follow can be found in the Business OPS section of the handbook.
There is also a request template in the Marketing Operations project within GitLab.
general-list-import-request.md - there is up to a five (5) business day SLA on these requestsevent-clean-upload-list.md - there is a 24 business hour SLA on these requestsWhen creating a live or ondemand webcast it is important to integrate the event program across the platforms/programs used - GitLab Marketing site (about.gitlab.com), Marketo (Marketing Automation), Zoom (Webcast video software) and Salesforce (CRM). This provides transparency about the webcast to anyone with access to Salesforce, namely the Sales and Marketing teams.
For a comprehensive overview on how to set up a webcast, please visit the Business Operations section of the handbook.
| 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 |
| 6120 | Advertising | All media buying costs as well as agency fees and software subscriptions related to media buying |
| 6130 | Events | All event sponsorships, booth shipping, event travel, booth design, event production as well as agency fees and software costs related to events |
| 6140 | All 3rd party email sponsorships as well as agency fees and software costs related to mass email communications and marketing automation | |
| 6150 | Brand | All PR, AR, content, swag and branding costs |
| 6160 | Prospecting | All costs related to prospecting efforts |
Marketing Operations approves invoices in weekly batches by close of business Tuesday all invoices received will be properly coded and approved.
Marketing Program Managers track costs associated with campaigns - such as events, content, webcasts, etc. - by working with the Finance team to create custom tags. These tags can be applied to Expensify reports, corporate credit card charges, and vendor bills processed by Accounts Payable. Campaign expenses that are incurred by independent contractors should be clearly noted and included in their invoices to the company.
The Marketing Programs Team follows the steps below to create and use campaign tags:
Things to Note:
The long term target (Opex/Rev) for Marketing expenses as a percentage of revenue is 13%. This target includes the operating expense related to free usage of gitlab.com.
The ratio of pipeline created that is attributed to demand generation program spend. The target ratio is 5:1 for pipeline to spend.
Email database management is a core responsibility for Mktg OPS. Ensuring GitLab is following email best practices, in compliance with Global spam laws and overall health of active database are all priorities.
Email creation, campaigns, follow up reporting and sending is the responsibility of the Marketing Program Managers. To request an email of any kind, please see the instructions in the Business OPS section of the handbook.
At GitLab, we strive to communicate with people in a way that is beneficial to them, most of our email marketing communications follow an explicit opt-in policy, although at times, we will communicate via email to people who have not explicitly opted-in. We do this to offer something of value (ex. an invite to a workshop, dinner, the opportunity to meet an industry leader, etc. Not an email inviting you to read a blog post) to the person. We always include the unsubscribe link in our communications and we respect the unsubscribe list. In addition to the unsubscribe button at the bottom of all of our emails, we have available our Email Subscription Center, where people can control their email communication preferences. There are currently four 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.
Newsletter
Sent bi-monthly (every 2 weeks). Content Team is responsible for creating the content for each Newsletter.
Security Alerts
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.
Webcasts
Invitation and/or notification emails sent about future webcasts.
Live Events
Invitation emails to attend a live event (VIP or Executive Lunch), meet-up, or in-person training. These emails are sent to a geo-locational 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.
The forms on about.gitlab are embedded Marketo forms. Any changes to the fields, layout, labels and CSS occur within Marketo and can be pushed live without having to make any changes to the source file on GitLab. When needing to change or embed a whole new form, ping Marketing OPS on the related issue so appropriate form and subsequent workflows can be created.
Each Marketo form should push an event after successful submission to trigger events in Google Analytics. We use the following event labels to specify which events to fire.
demo for static demos on /demo/ and /demo-leader/webcasts for forms on any page in /webcast/trial for the form on /free-trial/resources for forms on any page in /resources/events for forms on any page in /events/mktoLead legacy custom event label used on /public-sector/ and Newsletter subscription form submission events.mtkoformSubmit legacy custom event label used on /services/ and /sales/ contact forms.We add the following line above return false in the form embed code. Please update the event label from demo to reflect the appropriate form completion.
dataLayer.push({event: 'demo', mktoFormId: form.getId()});
In the event Marketo has an outage and/or the forms go offline the forms with highest usage/visibility (Free Trial and Contact Us) have been recreated as Google forms that can be embedded on the related pages as a temporary measure to minimize any effect till the outage is past.
