Emails & Nurture Programs

An overview of emails and nurture programs at GitLab.

Overview

This page focuses on emails and nurture programs, owned and managed by Lifecycle Marketing, Marketing Campaigns, and Marketing Operations. We are focused on progressing leads throughout their funnel and have programs encompassing prospects (aimed at progressing Unknown > Inquiry > MQL > SAO) and product user journeys (free > trial >paid campaigns). We leverage “always on”, logic-based, trigger-based, and persona-driven nurture engines.

Please visit our other pages for more information on email best practices, email processes and requests, and general team information.

The Persona Nurture (formerly the Intelligent Nurture after relaunch on 2023-11-06) aims at progressing leads from RAW > INQ > MQL > SAO, and leverages segment/region data to provide the right offer to the right person at the right time - based on their region and persona.

Related Handbook: Email Management

Key foundational elements to achieve this:

Email Nurture Programs

Persona Email Nurture

Labels for Persona Nurture Progress

We created several GitLab labels for a better organization of each asset that we are adding to the intelligent nurture.

Below we explain the labels created and what each one is for:

  • intel-nurture: This label is global and will help us identify that the issue we are working on is directly for the intelligent nurture. All “add to intelligent nurture” issues must have this label, and it is included in the issue template.
  • intel-nurture::write-copy: This label helps us know that the issue is in the process of email copy development. We cannot move on to the next step (email-build) until the copy is final.
  • intel-nurture::email-build: This label helps us to know that the email is in production. Verticurl is responsible for building the emails.
  • intel-nurture::email-test: This label tells us that the email has already been built and that the Verticurl team has sent tests to both the requesters AND the lifecycle marketing team for review. In this step we check that the links work correctly, that the content of the email is correct and that the correct utm values are used for appropriate tracking of the links. Once the email is approved, we proceed to the last step.
  • intel-nurture::add-to-streams: This label helps us to identify that the issue is in its final stage where we proceed to add the email to the relevant nurture streams.
    • PLEASE NOTE: the requester indicates the desired streams in the description of the issue, but the Lifecycle Marketing team makes the final decision on which streams are relevant. Please reference the stream alignment rules for what content type is relevant for each stream.

Persona Email Nurture Stream Schedule

The following shows the day of the week and cadence of the different streams in the Intelligent Nurture:

  • AMER: Thursday, 8:30 AM PT
  • EMEA: Thursday, 1:00 AM PT
  • APAC: Wednesday (Thursday APAC time), 6:30 PM PT
  • LATAM: Thursday, 8:30 AM PT.
  • Localized
    • Spanish: Inactive - leads rerouted to English nurtures
    • French: Thursday, 1:00AM PT
    • German: Inactive - relaunching end of Jan 2024
    • Japanese: Wednesday (Thursday JP time), 5:00PM PT
    • Korean: Wednesday (Thursday JP time), 5:00PM PT
    • Portuguese: Inactive - leads rerouted to English nurtures
  • PubSec
    • PubSec Default: Thursday, 7:00AM PT
    • Civilian (CIV): Thursday, 7:00AM PT
    • Department of Defense (DoD): Thursday, 7:00 AM PT
    • Federal Systems Integrators (FSI): Thursday, 7:00AM PT
    • National Security Group (NSG): Thursday, 7:00AM PT
    • SLED: Thursday, 7:00AM PT
  • Non-Demand Generation Nurture
    • All Remote: Thursday, 6:00AM PDT (not actively being maintained)

Persona Nurture Processes

Our Nurture processes have moved to our email processes handbook page.

Persona Nurture Reporting Process

All Nurtures within persona nurture have their link directly to their specific report.

Which are formed as follows:

REGIONAL NURTURES

AMER APAC EMEA LATAM

PUBSEC NURTURE:

PubSec general nurture Civilian (CIV) Department of Defense (DoD) Federal Systems Integrators (FSI) National Security Group (NSG) State, local, and education (SLED)

LOCALIZED NURTURE:

LOC-FRENCH

LOC-GERMAN

LOC-JAPAN

LOC-KOREA

LOC-PORTUGUESE

LOC-SPANISH

To be able to extract a complete report of email metrics, you just must click on the link corresponding to the Nurture where your email is.

Also, in case of not having access to Marketo to download the report you can go to the following folder where the reports of each nurture are uploaded on a monthly basis. Intelligent Nurture KPI

User nurtures (GitLab product users)

Trial nurture

Setup for Trial Nurture

Self Managed owners go through the Marketo Program

UTMs: ?utm_medium=email&utm_source=marketo&utm_campaign=trial-nurture&utm_content=(custom per email)

SaaS owners are now going through the program in Iterable.

UTMs: ?utm_source=Iterable&utm_medium=email&utm_campaign=trial-nurture

Free User Onboarding Email Campaigns

Sent through Iterable We recently moved what was formerly known as “In-product emails” from Mailgun to our newer Iterable system. This will allow greater flexibility and iteration.

These are also known as:

  • User onboarding emails
  • Free user nurture
  • User nurture
  • User emails
  • Any sort of combination of the above

We launched these for:

  • Free SaaS users - Beginning of Feb, 2021, moved to Iterable in August 2023
  • Free Self-managed users - Launched mid-late May, 2021, moved to Iterable in August 2023

Iterations: We relaunched these emails in Iterable and turned off Mailgun. Send time is now based on when the user joins GitLab and implemented skipping weekend send dates. In August 2023, we launched a welcome email and simplified some of the content. We will be iterating more on this program going forward.

Who’s part of this project?

  • Allie Klatzkin - email marketing DRI, Iterable analytics, & assist technical setup
  • Paige Cordero (Growth)
  • Gayle Doud (Growth)

So what’s the deal? Basically, we have a series of emails that deploy to net new namespaces. The goal is to get free users to use features of the product. There are 4 tracks - adopt Create, adopt Verify, invite Team, try a Trial. Each track has emails that try to nudge users to take action. If a user takes the action referenced in the email, they will not get the next email in the series and will move to the next series.

From email and reply-to email info@mg.gitlab.com - which is a group inbox. Amy is also a member of this group inbox. HTML files All of the HTML email files are in Iterable.

For a more in-depth look at how these emails work, please review the Figma journey.

Duo Pro Campaigns

Goal: Emails to share features and guide users on using GitLab Duo Pro. Delivery System: Iterable (SaaS) & Marketo (SM)

Please note that customer onboarding (non-trial) emails are sent through Gainsight.

Programs:

Invited users

Please note we are limited in what we can send to this audience.

  • Goal:* Enable users who are invited to get started using GitLab
  • Delivery System: Iterable (SaaS) & Marketo (SM)

Programs:

Last modified July 12, 2024: Update lifecycle email handbook (8aff81b0)
View page source - Edit this page - please contribute. Creative Commons License