Demand Generation Campaigns Team

Campaigns Team

What our team does

{: #goals .gitlab-purple}

Responsibilities

{: #responsibilities}

Global Campaigns Managers are responsible for building integrated marketing campaigns including the strategy, execution and analytics. They work in a cross-functional manner to gain alignmnent with internal stakeholders and inter-departmental dependencies. Building a Global Campaign may consist of the following: Target Audience segementation, campaign journey, asset and content recommendations, marketing message, email nurture, recommeded marketing channels for promotion (both organic and paid), top funnel events (virtual and in-person), and Alliance partnership (Technology Partners).

Regional campaigns managers are responsible for localizing and activating global campaign bundles, prioritizing program mix and delivery channels to support regional revenue goals. They partner with paid digital, ABM, lifecycle, field marketing, product marketing, customer marketing, SDR/BDR and regional sales teams to create integrated go-to-market plans.

Read the job family here »

Goals

{: #goals}

The goals for new first-order MQLs and SAOs are derived from workbacks of sales pipeline projections. These differ by segment and geo, and can be discussed internally.

Demand Generation Key Metrics

{: #key-metrics}

• North Star Metric: MQLs (New First-Order Logo)
• Efficiency Metric: Cost per MQL (New First-Order Logo)
• Business Impact Metric: CWA/Spend (closed-won attribution)
• Supporting/Activity Metrics: SAOs, Attributed Pipeline

OKRs

{: #okrs}

OKRs = Objective + Key Result

Meet the Team

{: #meet-the-team}

Agnes Oetama Manager, Marketing Campaigns

• Team Prioritization: plan prioritization of campaigns, related content and webcasts, event support, and projects for the team
• Hiring: organize rolling hiring plan to scale with organization growth
• Onboarding: create smooth and effective onboarding experience for new team members to ramp quickly and take on responsibilities on the team
• Transition of Responsibilities: plan for and organize efficient handoff to new team members and between team members when prioritization changes occur
• Campaigns DRI for Sisense attribution reporting (working closely with Marketing Ops)

Shari Rances Sr. Marketing Campaign Manager

• Campaign strategy for Automated Software Delivery (AutoSD) Global Campaign
  • Partner with campaign core team (Product Marketing, Developer Advocacy, Content, Analyst relations, Design) to develop and deploy Automated Software Delivery integrated marketing campaigns bundles
  • Host monthly enablement sessions on Automated Software Delivery global campaign updates and new LIVE assets
  • Produce half-yearly Automated Software Delivery global campaign performance reporting and optimization plan
  • Project manage and run top-funnel global campaign webcasts (e.g: Quarterly release webcasts, Forrester TEI webcast, DORA webcast) Host monthly enablement sessions on global campaign updates and new LIVE assets
  • Campaigns DRI for integrating Alliances motion into global campaigns

Eirini Panagiotopoulou Sr. Marketing Campaign Manager

• Campaign strategy for DevSecOps Platform and Security & Compliance (S&C) Global Campaigns
  • Partner with campaign core team (Product Marketing, Developer Advocacy, Content, Analyst relations, Design) to develop and deploy DevSecOps Platform and Security & Compliance integrated marketing campaigns bundles
  • Host monthly enablement sessions on DevSecOps Platform and Security & Compliance global campaigns updates and new LIVE assets
  • Produce half-yearly DevSecOps Platform and Security & Compliance campaigns performance reporting and optimization plan
  • Project manage and run top-funnel global campaign webcasts (e.g: Quarterly release webcasts, Forrester TEI webcast, DORA webcast) Host monthly enablement sessions on global campaign updates and new LIVE assets

Timothy Tran Marketing Campaign Manager

• Campaign strategy for All Sales Segments, APAC*
  • Plan, organize, implement, and optimize campaign strategy for all segments in APAC
  • Analyze and share results/findings of full-funnel attribution reporting for all segments in APAC
  • Organize execution schedule, timeline, and DRIs for tactics aligned to top-funnel APAC campaign plans, including email nurture, virtual events, digital ads, etc. aimed primarily at driving Inquiries + MQLs (with consideration of SAO attribution)
  • Support email marketing initiatives with Lifecycle Marketing focused on email marketing
  • Campaigns DRI for localization (translation of assets with Smartling)

Indre Kryzeviciene Sr. Marketing Campaign Manager

• Campaign strategy for All Segments, EMEA
  • Plan, organize, implement, and optimize campaign strategy for all segments in EMEA
  • Analyze and share results/findings of full-funnel attribution reporting for all segments in EMEA
  • Organize execution schedule, timeline, and DRIs for tactics aligned to top-funnel EMEA campaign plans, including email nurture, virtual events, digital ads, etc. aimed primarily at driving Inquiries + MQLs (with consideration of SAO attribution)
  • Support email marketing initiatives with Lifecycle Marketing focused on email marketing
  • Campaigns DRI for localization (translation of assets with Smartling)
  • Campaigns DRI for UTM strategy
  • Campaigns DRI for Weekly tech demo series

Meilynda Herbst Sr. Marketing Campaign Manager

• Campaign strategy for All Segments, Americas
  • Plan, organize, implement, and optimize campaign strategy for all segments in AMER
  • Analyze and share results/findings of full-funnel attribution reporting for all segments in AMER
  • Organize execution schedule, timeline, and DRIs for tactics aligned to top-funnel AMER campaign plans, including email nurture, virtual events, digital ads, etc. aimed primarily at driving Inquiries + MQLs (with consideration of SAO attribution)
  • Support email marketing initiatives with Lifecycle Marketing focused on email marketing
  • Campaigns DRI for Content
  • Campaigns DRI for Drift Chat Bot Strategy
  • Campaigns DRI for Tier 2 Referral Sites: Trust Radius, Gartner Digital/Capterra

Each team member contributes to making day-to-day processes more efficient and effective, and will work with marketing operations as well as other relevant teams (including field marketing, content marketing, and product marketing) prior to modification of processes.

Communication

{: #communication .gitlab-purple}

In line with GitLab’s overall communication guidelines, campaign managers work through MRs first and issues second (in order to preserve documentation), and our slack channel #marketing-campaigns is used for team updated and quick questions.

The #marketing_integratedmarketing channel is used for weekly check-ins and interaction with the larger integrated marketing team.

In between bi-weekly Campaigns Team Connect calls:

• Updates should be added to MRs when possible
  • Add to #marketing_programs Slack
  • Begin with UPDATE: <brief description> (i.e. UPDATE: Marketo segmentation live for sales segment)
  • Include link to MR (preferred) or issue
• Topics that need input should be added as an MR when possible, with issues as a secondary option, and pinged in Slack with DISCUSS
  • Add to #marketing_programs Slack
  • Begin with DISCUSS: <brief description> (i.e. DISCUSS: Marketing tool champions)
  • Include link to MR (preferred) or issue

Out of office team coverage

Whenever team members are out of the office for more than 7 business days, they are required to create an ooo coverage issue outlining the coverage needed and assign that to their team counterpart providing coverage. The same process and issue template can optionally be used when team members are out of the office for less than 7 days but requires coverage for time sensitive project(s).

Half-yearly Field Marketing & Campaigns Planning Workshop

Every 6 months, Regional campaigns managers will conduct a joint planning workshop with their Sr Manager/Manager, Field marketing counterparts (below):

Collaboration Timeline/Deliverables:

• X week before planning session: Manager/Sr Manager of field marketing shares next quarter planned field marketing events with regional campaign managers.
• By planning session: Regional campaign manager to pull invite list for each planned event.
• During planning session: Manager/Sr Manager of field marketing & campaign manager reviews invite list. If invite list for a particular planned event is too small, collectively decide if FMM should change the event venue or work with their regional campaign manager on a strategy to grow the invite list via paid or organic channels.

Meeting Cadence

{: #meeting-cadence}

Most of our team meetings are recorded and can be found here.

• Bi-weekly - Campaigns Team Connect Call (every other is AMER/EMEA and EMEA/APAC)
• Monthly - Marketing All-Hands (all marketing)

The Handbook

{: #handbook}

Is our single source of truth (SSoT) for processes and relevant links

• Individual teams should link back to these SSoT sections to avoid confusion
• Collaborative tactics contain their own handbook pages
• The handbook will be iterated on as we establish and optimize processes for optimal efficiency

Project Management

{: #project-management .gitlab-purple}

Prioritization

{: #prioritization-boards}

1. Campaigns Team - Prioritization
   • At start of milestone, ensure that issues are in the proper category of prioritization. Align them to the priority definitions.
   • Consider the time you have available in a 2 week period, recognizing meeting commitments and planned PTO.
   • Only add issues to account for 70% of your available work hours. Don’t max out at 100% since there will likely be things that arise and need immediate attention throughout milestone.
   • Ask yourself: considering realistic time this milestone, am I overcommitting? The first to drop from a milestone should be “Low” priority issues based on definitions.
   • Discuss milestone with Agnes and if need help determining what to drop and how to communicate (potentially) to issue requestors.
2. Campaigns Team - Current Milestone
   • Minimize the “Low” and “Medium” columns. Your focus should first be on the “Top” and “High” priority issues.
   • Prioritize completion of “Top” priority issues, then “High” priority issues.

Labels

{: #labels}

Prioritization labels

{: #prioritization-labels}

• DG-Priority::Top: Immediate action needed, aligned to OKRs, GTM motions/sales plays, or segment/region MQL generation. This category will be limited because not everything can be a priority. Timeframe: Immediate action needed.
• DG-Priority::High: Not requiring immediate action, but aligned to OKRs, GTM motions/sales plays, or segment/region MQL generation. Timeframe: Within weeks.
• DG-Priority::Med: Requests submitted that align to OKRs, GTM motions/sales plays, or segment/region plans. Process improvements to fix broken processes, or improve campaign team efficiency. Timeframe: Within months.
• DG-Priority::Low: Requests submitted that would be helpful, but can be pushed for higher priority issues. Nice-to-have improvements for campaign team processes. Timeframe: No specific timeline.
• DG-Priority::ToBePrioritized: Requests that have not yet been prioritized by Demand Gen.

Team labels

{: #team-labels}

• mktg-demandgen: DRI is in Demand Gen team
• dg-campaigns: DRI is in Campaigns team
• dg-request: Issue requesting Demand Gen support (did not originate from DRI team)

Status labels

{: #intake-labels}

• mktg-status::wip: the issue is assigned and moved into appropriate time-based milestone
• mktg-status::review: the work (or build) has been done, and is ready for Quality Assurance (QA) Review
• mktg-status::scheduled: issues related to Marketo (email, landing page, form, automation) have been scheduled and are ready to deploy
• mktg-status::complete: work (or build) is complete and the issue can be closed
• mktg-status::blocked: there were insufficient details in the issue for work to be completed
• mktg-status::plan: this is used for work that is in an earlier stage of planning and a specific request has not been made (backlog issues)
  • This will likely be used mainly by campaign managers on issues that are not high priority but there is a desire to capture the idea/notes.

Campaign Team Issue Templates

{: #campaign-issues-templates}

The following issue templates are used by the Campaigns Team to organize their work, with appropriate labels applied for project management.

• campaigns-manager-wip
  • to be used by Campaign Managers ONLY for simpler project management for their own initiated issues
  • puts straight in WIP status with pre-set for curent milestone and assignment to the person opening the issue
• campaigns-add-to-email-nurture
• campaigns-landing-page-copy
• campaigns-mural
• campaigns-pathfactory-track
• campaigns-pf-buyer-journey
• campaigns-post-webcast
• campaigns-program-tracking
• campaigns-reporting
• campaigns-remove-from-email-nurture
• campaigns-sdr-enablement
• campaigns-translation-review
• campaigns-webcast-dryrun-host
• campaigns-webcast-dryrun-sched
• campaigns-webcast-live-host
• campaigns-webcast-prep

Request Issue Templates

{: #request-issue-templates}

We ask that teams request work using the following issue templates in the campaigns project. These templates more clearly indicate what information and details are required in order for the request to be triaged.

Note on timelines: The Campaigns Team is focused on campaign strategy, execution, and optimization. Team member milestones focus on work to drive MQLs and SAOs, and requests will be committed to as bandwidth permits at discretion of Campaign Team Manager.

• request-email-followup - these will triage to Verticurl
• request-email-invitation - these will triage to Verticurl
• request-email-newsletter - these will triage to Verticurl
• request-email-reminder - these will triage to Verticurl
• request-email - only for general email requests these will triage to Verticurl. For customer communications, please work with Marketing Ops.
• request-mkto-landing-page - should mainly be used for pre-set processes where epic code includes need for landing page.
• request-pathfactory-track - creation of pathfactory tracks for one-time use is responsibility of owner. If used for demand generation prescriptive buyer journey, it will be triaged.
• request-pathfactory-upload - the content owner is responsible for uploading to Pathfactory.
• request-pathfactory-upload-bulk - issue to discuss more efficient process with MOps
• request-resource-page-addition - issue to discuss leveraging pathfactory for the resources page)
• request-sales-nominated - process should be used sparingly
• request-zoom-license-date - please use this issue template with Field Marketing (owner of Zoom)
• request-webcast-dryrun-sched
• idea-campaign
• idea-webcast

Fundamental principles of issue requests

{: #fundamentals}

The following issue templates are used by the campaigns team to organize their work, with appropriate labels applied for project management.

• /assign @ - issues should have only DRI based on who will complete the work in the issue. If work needs to be completed by multiple people, consider breaking into separate issues with clear deliverables and due dates. (example: /assign @jgragnola)
• /due 2021- - add due date based on workback schedules (example: /due 2020-07-13 or /due tomorrow or /due 07/13/2020)
• /milestone % - add milestone based on the due date of the issue (example: /milestone %"Mktg: )
• /weight - add weight between 1-5, with 1 being easiest (between 1-4 hours of time) and 5 being most complex (a full week of work). The majority of issues should fall into 1-2. If estimation is weight of 3+, break into separate issues for more manageable pieces to fit into milestones. (example: /weight 1)
• /epic - add epic of the overarching campaign or project to keep things organized. In almost all cases, there is a larger initiative that the issue relates to, so it is best practice to associate issues to the most relevant epic for visibility. (example: /epic [https://gitlab.com/groups/gitlab-com/marketing/-/epics/370](https://gitlab.com/groups/gitlab-com/marketing/-/epics/370))

/label ~"mktg-status::wip" 
/assign @
/milestone %Mktg:2021-

Milestones

{: #milestones}

The campaigns team uses the overall 2-week marketing milestones (format of Mktg: YYYY-MM-DD) to organize, prioritize, and balance campaigns, projects, and requests.

• The date in the milestone name is the END date of miltesone (Sunday)
• Note: Use of milestones was introduced to the campaigns team as of 2020-07-21.
• If issues in a milestone are not closed out by end of milestone, they are pulled to the next milestone. We will document total issues and total weight moved, to understand relative commitment levels and avoid overcommitment as we begin using milestones.

FY24 Marketing Milestones

• To be added

Campaigns Team Backlog Milestones:

• DG-OKRs - holds issues that are KRs in OKR initiatives
• DG-Backlog:Requests - holds issue requests to be triaged, typically related to Marketo (landing pages, emails, etc.)
• DG-Backlog:Ideas - holds issue requests related to campaign and webcast ideas submitted to demand generation
• DG-Backlog:Documentation - holds issues related to needed documentation (handbook, issues, etc.)
• DG-Backlog:General - holds general issue backlog that don’t fit into request, ideas, or documentation/process

Boards and Lists

{: #boards-lists}

Boards

{: #boards}

Campaigns Team Current Milestone - this board provides a high-level status view of issues in the current milestone by team member.

All Milestones Board - this board provides high level of all milestones in consecutive order

Board View Priorities Current Milestone

• All Team Members Priorities Current Milestone
• Agnes Oetama Current Milestone
• Eirini Pan Current Milestone
• Indre Kryzeviciene Current Milestone
• Shari Rances Current Milestone
• Meilynda Herbst Current Milestone

Board View by Milestone

• All Team Members Priorities Current Milestone
• Agnes Oetama by Milestone
• Eirini Pan by Milestone
• Indre Kryzeviciene by Milestone
• Shari Rances by Milestone
• Meilynda Herbst by Milestone

Board View Current Mile by Team Members

• Current Milestone by Team Members
• Upcoming MIlestone by Team Members

Lists

{: #lists}

Issue List Current Mile by Team Member

• All Team Members Current Milestone
• Agnes Oetama Current Milestone
• Eirini Pan Current Milestone
• Indre Kryzeviciene Current Milestone
• Shari Rances Current Milestone
• Meilynda Herbst Current Milestone

Issues by Status

• Issues in triage status (campaigns)
• Issues in blocked status (campaigns)
• Issues in ready-to-build status (campaigns)
• Issues in plan status (campaigns)

Tips & Tricks

{: #tips-tricks}

Creating a MacBook shortcut for repetitive statements

{: #macbook-shortcuts}

Example: in an issue to update all of MPM, instead of typing out every name, I have added a shortcut in my computer to populate all of the MPMs GitLab handles when I type asdf + Enter.

How to:

• On your Mac, choose Apple menu (ever-present top left logo)
• Go to System Preferences
• Click the Keyboard section
• Click Text on the top nav options
• Cick the + at the bottom of the option list
• In Replace column, add the shortcut that you would type in to populate the repetitive text
• In With column, add the repetitive text that you want to populate when you type in the shortcut

Reporting

{: #reporting .gitlab-purple}

Demand Generation Reporting

{: #demand-gen-dash .gitlab-purple}

See reporting on Demand Generation Hanbook Page: https://about.gitlab.com/handbook/marketing/demand-generation/#reporting

Key metrics tracked on the Demand Gen Dashboard

{: #dashboard-key-metrics}

See reporting on Demand Generation Hanbook Page: https://about.gitlab.com/handbook/marketing/demand-generation/#reporting

💡 Questions that the Integrated Campaign dashboards attempt to answer

{: #dashboard-questions-to-answer}

Overall (WIP to deliver all)

{: #questions-overall}

See reporting on Demand Generation Hanbook Page: https://about.gitlab.com/handbook/marketing/demand-generation/#reporting

By Campaign

{: #questions-by-campaign}

See reporting on Demand Generation Hanbook Page: https://about.gitlab.com/handbook/marketing/demand-generation/#reporting

Drilling down into the dashboards

{: #dashboard-drilldowns}

See reporting on Demand Generation Hanbook Page: https://about.gitlab.com/handbook/marketing/demand-generation/#reporting

Offer-Specific Dashboards

{: #dashboard-by-offer}

See reporting on Demand Generation Hanbook Page: https://about.gitlab.com/handbook/marketing/demand-generation/#reporting

Key Metrics tracked on ALL virtual events dashboards

{: #dashboard-virtual-events}

See reporting on Demand Generation Hanbook Page: https://about.gitlab.com/handbook/marketing/demand-generation/#reporting

Virtual Events Reporting

{: #reporting-virtual-events}

See reporting on Demand Generation Hanbook Page: https://about.gitlab.com/handbook/marketing/demand-generation/#reporting

View page source - Edit this page - please contribute.