1. You are here:
2. Handbook
3. Marketing
4. Global Channel and Alliances Marketing
5. Channel and Alliance Marketing

On this page

• Channel Marketing Campaigns
  • Email Management
  • Scoring
  • Passing to Vartopia and Partner Visibility
  • Types of Partner Campaigns
    • Partner Only Campaigns - MDF funded
    • Joint GitLab and Partner Events
    • Trials from Partners
      • Self-Managed Free Trial
      • SaaS Free Trial
  • Setup in Marketo
    • Trial Campaign Set Up
      • Self-Managed Free Trial
      • SaaS Free Trial
    • Joint Marketing Campaign Set Up
    • MDF funded Campaigns
      • Step 1: Clone Marketo program (TBC)
      • Step 2: Sync Program to SFDC
      • Step 3: Update Tokens in Marketo
      • Step 4: Update SFDC Campaign
      • Step 4b: Update without Allocadia
      • Step 5: Update List Upload Request Issue
    • Step 6: Load List and Activate Smart Campaign
• Alliance Marketing Campaigns
  • Webcast Setup
    • On24 Webcast Hosted by GitLab (Lead capture via forms)
      • Step 1: Setup in Marketo
      • Step 2: Update SFDC Campaign
    • Webcast Hosted by Alliance Partner (Lead capture via list uploads)
      • Step 1: Update Tokens in Marketo
      • Step 2: Update SFDC Campaign
      • Step 3: Update CRM Partner ID Column in Google Sheet
      • Step 4: Update List Upload Request Issue
• Field Glossary
  • Alliance Record
  • Channel Record
  • CRM Partner ID
  • CRM Partner ID (Look up)
  • Lead Acquisition Source
  • Partner Consent
  • Partner Type
  • Partner Managed
  • Partner Manager
  • Subscribe - Partner

Channel Marketing Campaigns

This section is to walkthrough the technical setup of different partner campaign types from Marketo>SFDC>Vartopia, including Marketo and SFDC campaign set up for Joint Gitlab and Partner Events, Partner Trials and MDF funded campaigns. The sections below describe them in detail.

Email Management

When a lead is passed to a partner, they will be suspended from GitLab marketing unless they opt-in specifically to GitLab marketing after being passed, or the partner returns the lead to GitLab. Read more on the email management page.

Keep in mind, they will still be eligible for operational email sends - which includes most follow up emails. If you want to exclude them, you will need to add a parameter to the smart list of that send campaign to say Prospect Share Status not equal to Pending, Sending to Partner, Accepted.

Scoring

Leads that are actively being worked by the partner will be excluded from scoring. Once they are no longer being worked by the partner, they will be scored again. More details on the scoring page.

Passing to Vartopia and Partner Visibility

In order for the Partner to be able to see and action the lead in Vartopia, the SFDC fields must be populated: Vartopia Partner Account, Prospect Share Status and Partner Prospect Status.

To see more about Vartopia, visit the handbook page.

Types of Partner Campaigns

Each campaign has it's own ROE for lead routing and email practices. Follow the Mural to find the type of event and the follow up that results from it.

Partner Only Campaigns - MDF funded

These campaigns are GitLab funded via MDF, but all leads are passed to the partner. We upload these lists into our systems to be able to track pipeline from resulting Deal Registrations in Vartopia. You can find Marketo and SFDC Campaign set up here.

When a lead/contact is associated to a campaign the following steps occur:

1. Marketo processes the lead, marks as Marketing Suspended and syncs to SFDC.
2. LeanData updates the Partner Prospect Status to Qualifying, Prospect Share Status = Sending to Partner.

DRI for the operalization of this process: Channel Marketing

Joint GitLab and Partner Events

When GitLab and Partners participate in events together, they will share leads. The mural above has a visual workflow of these steps. Go here for Marketo/SFDC campaign set up.

NOTE: Phone numbers are required in order for the lead to be passed to Vartopia. If a phone number has not been supplied via the list, Marketo will appended a phone number automatically of 555-555-5555.

When a lead/contact is associated to a campaign the following occurs:

1. LeanData reviews the campaign field for Is a Channel Partner Involved? = Yes.
2. LeanData verifies the campaign member is not actively worked by GitLab, thus Person Status is not Accepted, Qualifying nor Qualified, or Actively Being Sequenced = False.
3. If all the above is true, LeanData updates the Partner Prospect Status to Qualifying, Prospect Share Status = Sending to Partner, then LeanData assigns to Partner Queue.

Trials from Partners

Self-Managed Free Trial

Partners can host our self-managed trial form. They will have a specific UTM parameter that is captured upon form submit that allows us to pass that lead directly to the partner. Below explains the backend for the activity. Each page must have the UTM utm_partnerid in the URL populated, otherwise we cannot pass to the partner.

You can find the UTM builder here. For a list of the partner IDs to add, go here.

1. Form is hosted on a GitLab or Partner landing page. Partners should always use the FORM 2983: Partner Self-Hosted Enterprise Trial Form.
   • This form has a hidden field that captured utm_partnerid
2. Once submitted, Marketo then appends that value Vartopia Partner Account fields.
3. Marketo processes the lead and sends the trial activation key via email to the prospect.
4. Marketo suspends emails being sent from GitLab to prospect
5. Marketo sends email alert to partner team and syncs lead to SFDC.
6. LeanData updates the Partner Prospect Status to Qualifying, Prospect Share Status = Sending to Partner if Partner Account is not NULL.
7. Lead/Contact owner is updated to the assigned Partner Queue.
8. Salesforce.com sends alert email to Partner Prospect Admin.
9. Vartopia picks up lead and assigns to partner in Vartopia based on ID.
10. Lead/Contact fields for Partner information are automatically populated.

Returning Trial Requesters

GitLab allows only one self-managed trial license key per user. In the case, when a lead returns and attempts to fill out the self-managed trial form from Partners, they will be prompt with a rejection email.

As partner leads are suspended from receiving marketing communciations, the Marketing Suspended status is temporarily switch to False to send the email to the recipient.

SaaS Free Trial

Partners can use the SaaS free trial submission via GitLab.com. They will have a specific UTM parameter that is captured upon form submit that allows us to pass that lead directly to the partner. Below explains the backend for the activity. Each page must have the UTM glm_source and glm_content in the URL populated, otherwise we cannot pass to the partner.

NOTE: glm source should always be equal to partner and glm_content will be equal to the CRM Partner ID associated with the partner account.

1. Form is hosted on GitLab.com.
2. Once submitted, Marketo then appends that value Vartopia Partner Account fields.
3. The lead will receive a confirmation instruction email and log into the GitLab environment with login and password they created upon sign up.
4. Marketo suspends emails being sent from GitLab to prospect
5. Marketo sends email alert to partner team and syncs lead to SFDC.
6. LeanData updates the Partner Prospect Status to Qualifying, Prospect Share Status = Sending to Partner if Partner Account is not NULL.
7. Lead/Contact owner is updated to the assigned Partner Queue.
8. Salesforce.com sends alert email to Partner Prospect Admin.
9. Vartopia picks up lead and assigns to partner in Vartopia based on ID.
10. Lead/Contact fields for Partner information are automatically populated.

Setup in Marketo

Trial Campaign Set Up

Self-Managed Free Trial

There is no marketo program or SFDC campaign setup necessary to track self-managed trials. Every partner trial campaign can utilize setup from Partner - Trial - Self-managed campaign, without creating a new Marketo or SFDC campaign. Follow directions above to understand what form to use and what processes to follow.

SaaS Free Trial

There is no marketo program or SFDC campaign setup necessary to track SaaS trials. Every partner trial campaign can utilize setup from Partner - Trial - SaaS campaign, without creating a new Marketo or SFDC campaign. Follow directions above to understand what form to use and what processes to follow.

Joint Marketing Campaign Set Up

NOTE: For Vartopia sync, the campaign field, Is Channel Partner Involved? = Yes.

First, use the general set up, found in campaigns and programs page. The partner steps are nested in the typical Marketo program templates to clone. Once the campaign is cloned, follow the steps below in addition to the other setup steps found on the campaigns and programs page.

All Marketo templates will have 2 tokens added to them that the campaign owner should update, {{My.Partner Name}} and {{My.CRM Partner ID}}

• Partner Name: Does not need to be official, it will be used on the form consent language and interesting moments, so needs to be customer facing. Example: By registering for this GitLab and {{My.Partner Name}} event....
• Partner ID: All partner IDs can be found here.

Online Events: (Lead capture via forms) BEFORE Launch

1. Update token on Marketo program {{My.Partner Name}}
2. Update token on Marketo program {{My.CRM Partner ID}}
3. Update registration landing page to have FORM 3146: Partners w/ consent+token
   • To update the page:
     • Edit the landing page draft
     • Double click on the form
     • Update form FORM 3146: Partners w/ consent+token and click swap
     • Approve and close landing page
   • Forms has a hidden field that captures utm_partnerid to associate to the partner and captures contact consent for the partner.
   • The partner MUST HAVE this utm on their link to the landing page otherwise they will not be routed leads
4. Processing Campaign for partner campaings is separate from the typical one. Do not activate both.
   1. Processing smart campaign's smart list must reference FORM 3146: Partners w/ consent+token or another partner form (translations)
5. Set up asset expiration as described here, if needed.
6. (no setup needed) Marketo will process. 1. If there is a CRM Partner ID
   1. Set Vartopia Partner Account
   2. Set Partner Consent = True
7. (no setup needed) Interesting moments will dynamically change if there is a partner involved to reflect that.
8. (no setup needed) LeanData picks up from there, and the lead is routed accordingly to either GitLab or the Partner in Vartopia.

The process above will work for an event with multiple partners driving to it. Make sure they have their utms correct when sending traffic to the registration page. You still need to fill out the token, but only one value will be accepted. Please decide ahead of time who the default partner is that will receive the leads they did not source.

Offline Events: (Lead capture via list uploads, not)

NOTE: Phone numbers are required in order for the lead to be passed to Vartopia. Please make sure that field is populated.

If a form isn't available to capture registration, follow these steps:

1. In list upload issue, add a column for CRM Partner ID and add the value. - All partner IDs can be found here. If the partner did not source the lead (AKA GitLab did), then leave that column blank.
2. Mark in the list upload issue that this is a joint event and the partner will be following up with leads
3. (no setup needed) Turned on by person who loads the list into Marketo.
   1. If there is a CRM Partner ID
      1. Set Vartopia Partner Account
      2. Set Partner Consent = True
4. (no setup needed) Interesting moments will dynamically change if there is a partner involved to reflect that.

The process above will work for an event with multiple partners driving to it. Make sure they have the partner ID properly appended to each person on the list. You still need to fill out the token, but only one value will be accepted. Please decide ahead of time who the default partner is that will receive the leads they did not source.

MDF funded Campaigns

These campaigns follow their own processes not found on the campaigns-and-programs page.

Step 1: Clone Marketo program (TBC)

• Clone Marketo Template
• Update the name to match the naming convention YYYYMMMDD__MDF Partner Name_Event Name

Step 2: Sync Program to SFDC

• At the program main screen in Marketo, where it says Salesforce Sync with "not set", click on "not set"
• Click "Create New." The program will automatically populate the campaign tag, so you do not need to edit anything.
• Update description with the link to the SFDC MDF request and Coupa ID and Allocadia ID (if you have it)
• Click "Save"

Step 3: Update Tokens in Marketo

• Update {{my.CRM Partner ID}} with the 15-digit CRM ID of the partner that will be following up with these leads.
• Update {{my.Partner Name}} with the name of the partner who will be following up.

Step 4: Update SFDC Campaign

If you included the Allocadia ID, follow these steps. Otherwise, you'll need to update additional fields below.

• Budgeted Cost in SFDC pulls from your plan number, not your forecast number from Allocadia. If you do not have a plan cost in Allocadia then Budgeted Cost in SFDC will remain blank. If this is the case, you will want to add in your Budgeted Cost manually into your SFDC campaign.
• Once Allocadia has updated the SFDC campaign, you will need to double check Campaign Type and make sure it still says Partner - MDF. If it does not, please update the field.

Step 4b: Update without Allocadia

If you did not include the Allocadia ID in the description, you'll need to update the steps below:

• Update Campaign Type Details to reflect the type of MDF campaign it is.
• Change the Campaign Owner to your name
• Update Large Bucket based on criteria
• Update Start Date to the date of launch
• Update End Date to when the campaign concludes
• Update Budgeted Cost - If cost is $0 list 1 in the Budgeted Cost field. - NOTE there needs to be at least a 1 value here for ROI calculations, otherwise, when you divide the pipeline by 0 you will always get 0 as the pipe2spend calculation.
• Update Region and Sub-region if you have the data available
• Update Budget Holder
• Update Is this an in person event?
• Update Will there be MDF Funding?
• Update Is a Channel Partner Involved?
• Update Channel Partner Name
• Click Save
• Add the Marketo program link and SFDC campaign link to the epic.

Step 5: Update List Upload Request Issue

• Update the List upload request issue to have these leads imported in. This should already have been created and linked to the epic.
  • Create issue (if not already done))
  • Please follow the list import criteria and guidelines
• NOTE: Leads should NOT be marked as opt-in unless they specifically opted in to GitLab emails.
• NOTE: Phone numbers are required in order for the lead to be passed to Vartopia. Please make sure that field is populated.

Step 6: Load List and Activate Smart Campaign

• Once list is loaded, loader should go to the 01 - Processing campaign and Run Once
  • Campaign will assign leads to the partner you specified in step 3 in Vartopia

Alliance Marketing Campaigns

This section is to walk through the technical setup of webcasts hosted by GitLab and/or Alliance Partner. Unlike Channel leads, Alliance leads follow the regular lead and contact statuses and scoring model.

Webcast Setup

All Marketo templates will have 2 tokens added to them that the campaign owner should update,{{My.Partner Name}} and {{My.CRM Partner ID}}.

The CRM Partner ID can be retrieved by identifying the Account ID (18) of the Alliance Partner - refer to this list.

First, use the general set up found in campaigns and programs page. The partner steps are nested in the typical Marketo program templates to clone. Once the campaign is cloned, follow the steps below in addition to the other setup steps found on the campaigns and programs page.

On24 Webcast Hosted by GitLab (Lead capture via forms)

GitLab can drive webcasts with Alliance Partners using On24. To incorporate the steps required for partners, follow these additional steps.

Step 1: Setup in Marketo

1. Update {{my.CRM Partner ID}} with the Account (18) of the partner.
2. Update {{my.Partner Name}} with the name of the partner.
3. The registration landing page must have the following:
   • FORM 3299: Alliances with a hidden field that captures utm_partnerid.
   • The URL must include the utm parameter with the CRM Partner ID to the landing page to lead to be associated with the Alliance partner.
4. Activate 01a Registration Flow (single timeslot)
5. Activate 00 Interesting Moments and interesting moments will dynamically change if there is a partner involved to reflect that.
6. (no setup needed) Marketo will process.
   1. If there is a CRM Partner ID
      1. Set CRM Partner ID (Look up)
      2. Set Partner Type = Alliance Partner (by Salesforce)

Step 2: Update SFDC Campaign

• Update Campaign Type Details
• Change the Campaign Owner to your name
• Update Large Bucket based on criteria
• Update Start Date to the date of launch
• Update End Date to when the campaign concludes
• Update Budgeted Cost - If cost is $0 list 1 in the Budgeted Cost field. - NOTE there needs to be at least a 1 value here for ROI calculations, otherwise, when you divide the pipeline by 0 you will always get 0 as the pipe2spend calculation.
• Update Region and Sub-region if you have the data available
• Update Budget Holder
• Update Is an Alliance Partner Involved?
• Update Alliance Partner Name
• Click Save

Webcast Hosted by Alliance Partner (Lead capture via list uploads)

NOTE: Upon list import, ensure the Google sheet column for CRM Partner ID is populated, this will help associate the partner lead with the Alliance partner.

If a form isn't available to capture registration, follow these additional steps:

Step 1: Update Tokens in Marketo

• Update {{my.CRM Partner ID}} with the Account (18) of the partner.
• Update {{my.Partner Name}} with the name of the partner.
• (No setup required) Interesting moments will dynamically change if there is a partner involved to reflect that.

Step 2: Update SFDC Campaign

• Update Campaign Type Details
• Change the Campaign Owner to your name
• Update Large Bucket based on criteria
• Update Start Date to the date of launch
• Update End Date to when the campaign concludes
• Update Budgeted Cost - If cost is $0 list 1 in the Budgeted Cost field. - NOTE there needs to be at least a 1 value here for ROI calculations, otherwise, when you divide the pipeline by 0 you will always get 0 as the pipe2spend calculation.
• Update Region and Sub-region if you have the data available
• Update Budget Holder
• Update Is an Alliance Partner Involved?
• Update Alliance Partner Name
• Click Save

Step 3: Update CRM Partner ID Column in Google Sheet

• In the list upload, include the CRM Partner ID value in the spreadsheet column. If the lead is not associated with an Alliance partner, leave the column blank.

Step 4: Update List Upload Request Issue

• Please follow the list import criteria and guidelines

Field Glossary

Below are the glossary of fields used for Channel and Alliance partner campaigns and workflows.

	Channel Partner	Channel Partner	Distributor	Distributor	Alliance Partner	Alliance Partner
	Leads	Records	Leads	Records	Leads	Records
Alliance Record						X
Channel Record		X		X
CRM Partner ID	X		X		X
CRM Partner ID (Look Up)	X		X		X
Lead Acquisition Source	X				X
Partner Consent	X		X
Partner Managed	X
Partner Manager	X
Partner Type	X		X		X
Subscribe - Partner	X		X		X
Vartopia Partner Account	X

Go to the Vartopia page to review fields that are relevant to Vartopia.

Alliance Record

This field shows when a record belongs to an Alliance Partner meaning they are an employee of said Alliance Partner. When this field is checked = true, the record will be suppressed from general marketing communications.

Channel Record

This field shows when a record belongs to a Channel Partner meaning they are an employee of said Channel Partner. When this field is checked = true, the record will be suppressed from general marketing communications.

CRM Partner ID

This field is the Salesforce Account ID (18) associated with the partner account.

For a running list of Channel Partners and their CRM IDs, which is critical to the channel partner lead flow, click here, while the CRM Partner ID for Alliance Partners can be found here.

If you are working with an Open or Select partner who is not listed in the linked SFDC report, their partner ID which can be found in their Partner Account record within SFDC, in the 9th section called Vartopia Deal Registration Access. If you can't find the field, do a quick commandF for the word Account ID (18) and that will take you to the ID or you can retrieve the 18 character ID from the Salesforce URL. If for some reason the ID is missing, reach out in the #channel-programs-ops slack room.

CRM Partner ID (Look up)

The lookup field retrieves the name of the partner account associated with the Account ID (18).

Lead Acquisition Source

This field records the source type of the partner lead. The biggest driver for this field is to isolate the source type that applies to the recall process including Owned Event and Trial - Enterprise.

The reason why Initial Source isn’t used for this use case is because the field value must equal to Channel Qualified Lead to be attributed to and sourced by Channel Partner.

Partner Consent

This field indicates when a lead has granted consent to allow their information to be shared with a Partner. This only applies to Channel Partners because Alliance Partners are not enrolled in the lead-sharing module.

Partner Type

This field specifies when a partner lead is associated with a Channel or Alliance Partner account.

Partner Managed

This field marks when a lead is managed by a Channel Partner via Vartopia. Vartopia Partner Account must be populated and their Prospect Share Status and Partner Prospect Status must have a status that suggests they are being worked on by a Channel Partner.

• Partner Prospect Status = Qualifying, Qualified or Converted to DR, or
• Prospect Share Status = Sending to Partner, Pending or Accepted.

Partner Manager

This field reflects the Account Owner, Channel Account Manager or Partner Account Manager associated to the partner account.

Subscribe - Partner

This field records when a lead has opted-in to GitLab marketing communications. Subscribe - Partner resides only in Marketo and mainly to Alliance Partner leads.

Channel Partner leads are immediately marked as marketing suspended and this field does not apply to them until they come back (recalled) to GitLab.