Marketo

1. You are here:
2. Handbook
3. Marketing
4. Marketing Operations
5. Marketo

Maintained by:

On this page

• About Marketo
• Marketo <> Salesforce.com Connection
• Sandbox
• Forms
  • Website Form Management
  • Campaign Limits
    • Standardization of Country &/or State values
• MQL Definition
  • Re-MQL
  • Scoring Model
    • Behavior Scoring
      • Score Boosters
    • Demographic Scoring
• Lists and Segmentation
  • Segmentations
  • Other Field Documentation and Definitions
  • Account Based Marketing List
  • Geographic DMA List
    • Focused Email Lists
    • SLA for Targeted Lists:
    • List Exports
• Mailchimp sends

About Marketo

Marketo is our marketing automation platform used for email marketing, lead management, and program management.

To see the different systems that are connected to Marketo, please visit the Marketo System Infrastructure Mapping Mural.

Marketo <> Salesforce.com Connection

When any lead/contact is created in SFDC, it will automatically sync and create in Marketo - nothing is held back. Likewise, when a lead/contact is deleted in SFDC, it will delete in Marketo as well. Alternatively, Marketo does not automatically push all records to SFDC and a deleted record in Marketo will not delete in SFDC unless specifically told to.

A lead will sync from Marketo to SFDC in these scenarios:

1. Member of Program that is synced to SFDC
2. When they reach MQL status and reach 100 points
3. Specifically told to sync via a flow step Sync to SFDC

Marketo also can create and edit SFDC campaigns. The Active checkbox must be checked in order for Marketo to be able to map to that campaign. Go here for campaign set up directions.

Sandbox

We do have a sandbox to work in for Marketo. The sandbox is used for training, creation of API links and overall testing before we move to production. There is not a way to promote a program from the sandbox to Prod, so building programs in the sandbox first is not always required. Guidelines for when to build in the sandbox is TBD, but for custom API and webhook integrations, it is highly recommended.

If you'd like access to the sandbox, please fill out an AR.

Forms

Nearly all the forms on our website (about.gitlab.com) are Marketo embedded forms. Marketing Operations is responsible for maintaining existing forms and creating any new forms. If you need a new form created, please open a form creation issue.

Form documentation can be found here. It contains all of our current forms, as well as standardized country and state picklists.

Translated Forms Available: Spanish, French, Italian, German, Portuguese, and Japanese. If you require a new language, please gather the translations and then create an issue. Due to resource constraints, we are only creating new forms for P0 countries.

All forms should follow these guidelines:

• Field labels are always ALL CAPS
• Label width = 150 / Field width = 300
• Fields should be stacked in a vertical line
• State/Province only visible when Country = United States or Canada; the visibility rule dynamically displays Province when Canada is selected or State when United States is selected
• Generally City is only visible when Country = Ukraine
• Forms should all contain a checkbox for opting in to communications via email
• When Country = Ukraine there is an additional checkbox for the submitter to confirm they do not belong to the Crimean region of the Ukraine
• Country should not include embargoed countries
• All forms should have hidden fields for Demandbase, gclid and google analytics tracking
• Do not use lightboxes

If you are collecting home addresses for direct mail campaigns, you must include the following language on the landing page or form. Additionally, you must set up a deletion campaign in Marketo to remove their address information once you have sent the item. Please also ensure the vendor we are using to ship the items also deletes this from their records. By giving us your home address, you are giving us permission to mail items to your home. We will not use this data for any other purposes.

Website Form Management

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, please open an issue using the form_request template.

If you are having trouble seeing a Marketo form, please reference this page.

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.

1. demo for static demos on /demo/ and /demo-leader/
2. webcasts for forms on any page in /webcast/
3. trial for the form on /free-trial/
4. resources for forms on any page in /resources/
5. events for forms on any page in /events/
6. services for form on /services/
7. sales for form on /sales/
8. public-sector for forms on /solutions/public-sector/
9. mktoLead legacy custom event label used on Newsletter subscription form submission events. Currently used for primary, security, and all-remote newsletter form submissions.

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(),
  'eventCallback' : function()
  {}, 'eventTimeout' : 3000
});

Campaign Limits

There is a set limit of 250,000 records that can be processed through a given smart or email campaign. If the smart campaign smart list is set to update or email over 250,000 records, it will not run and will be aborted. This is in place to prevent accidental mass updates and emails. If you need to run a campaign over that limit, reach out to MarOps.

Standardization of Country &/or State values

There are several workflows that clean the Country &/or State fields to ensure the value meets required Salesforce format. States should be spelled out, not using abbreviations (ex. CA should be California). If a Country &/or State/Province standardization does not match SFDC exactly, the lead will not sync. If a new standardization is needed, please open an issue in the Marketing Operations project.

All of the standardization smart campaigns are contained in:

Marketing Activities -> Operational - Do not edit -> Data Management -> 01 Data Management -> 04-Normalize Data

• These countries are the only ones that accept a state value: United States, Canada, Ireland, India, Brazil, Australia, China, Italy, Mexico
• All 50 US states and all Canadian Provinces have standardization campaigns to set them from their two letter abbreviation to their full spelling.
• The following countries have common variations updated to their accepted values: United States, Bolivia, Canada, China, France, Germany, Hong Kong, India, Iran, Ireland, Macao, Myanmar, Netherlands, Russia, South Korea, Sweden, Switzerland, United Kingdom, Venezuela, Vietnam.

MQL Definition

A Marketing Qualified Lead is a lead that has reached a threshold of 100 points, based on demographic/firmographic and/or behavioral information. The MQL Scoring is detailed below and is comprised of various actions and/or profile data that are weighted with positive or negative point values. When a Person Score changes it will be inserted into the routing flow. Using LeanData every time a Person Score is updated, LeanData will run a check to see if the record needs to be processed through the flow.

Re-MQL

A Lead/Contact will be allowed to re-MQL if they are in a Nurture status and reach the MQL threshold again.

The number of times they MQL will be counted with the MQL Counter field. The Initial MQL DateTime contains the very first time a prospect reached the MQL threshold. MQL Date will be overwritten to be the most recent date that a lead has reached the MQL threshold.

When a lead is set to Nurture, their Behavior Score is reset to 0. Their Person Score is reset to the value of the Demographic Score. Additionally, a person who has reached MQL in the past, is given an additional score of +20 when they are reset to Nurture. If a lead was Accepted before it reached the MQL threshold, and is then set to Nurture within 30 days, the lead's Behavior Score will reset to the value it was while in Inquiry, the Demographic Score will be re-run and their overall Person Score will be the sum of those two values.

When a lead Re-MQLs from Nurture to MQL, their Nurture Reason field is set to Null, but that Nurture Reason value is preserved in the field Previous Nurture Value on the lead or contact. That field is set by Marketo only. The Nurture DateTime only updates the first time. When a lead re-reaches an MQL status, they are not re-routed by LeanData for round-robin, they stay in their original owners name.

Follow the workflow mural to see the lead lifecycle. Notice you cannot go backwards in status to Raw or Inquiry from a later step.

Scoring Model

The lead scoring model is a 100 point system in order to MQL. Positive and negative points are assigned to a record based on their demographic and/or firmographic information, and their behavior and/or engagement with GitLab marketing. Their Person Score is the sum of their Behavior Score and their Demographic Score. The Person Score must reach 100 in order to MQL.

For account scoring, visit the DemandBase page.

There is a flow that runs everynight to reset leads that have gone negative back to 0.

The model below is updated as of 2021-07-08.

Some leads are exluded from scoring if they:

• Have a @gitlab.com email address
• Are a competitor
• Status = Unqualified or Bad Data
• Company name of student, personal, test and similar

Behavior Scoring

Behavior scoring is based on the actions that person has taken. The cadence of how often they can be scored is listed below. For campaign scoring, there must be a success in order to capture the score, those below are marked with a *. Refer to the programs page and progression statuses to see what constitues a success.

Score Boosters

These are boosters to scores that occur when a special action takes place above the traditional action above.

Demographic Scoring

For Job role/function and seniority descriptions can be found here.

Lists and Segmentation

Segmentations

Marketo segmentations are used similar to a smartlist, but they are permanent and can only be changed by marketing ops. They are used to create dynamic content (emails and landing pages) and are used for faster processing of lists. Segmentations are constantly running in the background in Marketo, so they never need to be refreshed for current numbers. We can only have 20 total segmentations in Marketo. Segmentation criteria waterfalls down based on the order of the segment lists that make up the segmentation. You can only be in one segment of a segmentation.

The following segmentations that are approved and live.

Other Field Documentation and Definitions

Account Based Marketing List

ABM lists are built by request for the Field Marketing and Marketing Program team to target & send emails/invitations to accounts deemed to be high priority by Sales. You can find these lists in the DMA folder in the Marketo Database. The MktgOps team is responsible for creating & maintaining these lists.

If a new ABM list is needed, please open an issue using the Target list issue template and tag marketing ops.

Geographic DMA List

The Geographic DMA (direct marketing area) were built for the Field Marketing and Marketing Campaigns team to target & send emails/invitations related to Field &/or Corporate marketing events. The MktgOps team is responsible for creating & maintaining these lists. You can find these lists in the Database of Marketo in the Geographic DMA List Folder.

If a new DMA list is needed, please open an issue in the Marketing Operations project & utilize the DMA_request issue template.

Focused Email Lists

The Field Marketing and Marketing Campaigns teams use targeted email lists as a tool when pursuing specific regions, sectors or companies. Email list requests must be submitted using this template. From there, the campaign managers or marketing ops will build or review the list

SLA for Targeted Lists:

• List request is required 7 days prior to email deployment - FMM / MPM
• Final Smart List is available 2 days prior to email deployment - MOps

List Exports

«««< HEAD If you need a list export, please fill out an export request issue. If sharing externally, please follow guidance to help inform your request. ======= If you need a list export, please fill out an export request issue. If sharing externally, please follow guidance to help inform your request.

42c5e7866afa16dbfc45af80e04ef443261a62ee

Mailchimp sends

Our Mailchimp subscription is currently paused to prevent being billed while we deprecate. We are allowed to unpause 2x a year. We can unpause only in the rare case of needing to send a large security alert email. The External Communications person for security has access to Mailchimp to send these notices out. Prior training is required before a user can be given access. Please reach out to Mops if this access is required.