Gitlab hero border pattern left svg Gitlab hero border pattern right svg



This page focuses on surveys that we or a 3rd party sends out and is a tactic used within marketing campaigns, including account centric campaigns.

Process in GitLab to organize epic & issues

The project owner is responsible for following the steps below to create the epic and related issues in GitLab.

  1. Project owner (FMM) creates the main tactic issue
  2. Project owner (FMC) creates the epic to house all related issues (code below)
  3. Project owner (FMC) creates the relevant issues required (shortcut links in epic code below)
  4. Project owner (FMC) associates all the relevant issues to the newly created epic, as well as the original issue
  5. Project owner (FMC) sets due dates for each issue, based on agreed upon SLAs between teams for each task, and confirms accurate ownership for each issue

Note: if the date of a survey changes, Project owner (FM) is responsible for changing the due dates of all related issues to match the new date, and alerting the team members involved.

Code for epic

<!-- Name this epic using the following format, then delete this line: Survey - [Vendor] - [3-letter Month] [Date], [Year] --->

## [Main Issue >>]()

## [Copy for landing page and emails >>]() - [template](

## :notepad_spiral: Key Details 
* **Project Owner (FMM):** 
* **FMC/FMS:** 
* **Type:** Survey
* **Sales Segment (choose primary):** `Large, Mid-Market, or SMB`
* **Sales Region (choose one):** `AMER, EMEA, APAC`
* **Sales Territory (optional, if specific):** 
* **Goal:** `Please be specific on the metric this is meant to impact.`
* **Campaign Tag:**  
* **Budget:** 
* **Launch Date:**  [MM-DD-YYYY] (this is the date the survey begins through the vendor)
* [ ] [main salesforce program]()
* [ ] [main marketo campaign]()
* [ ] Campaign UTM - FM to fill in (Format: campaign tag - change to all lowercase, no spaces, hyphens, underscores, or special characters)

## User Experience
[What is the anticipated user experience? FMM to provide a description of the journey as if they were the end user - from communications received (both from GitLab and/or from vendor), to what the user provides in survey, what happens after they submit, what do they receive from us after we upload the leads, and beyond... what is the end-to-end journey for the user?]

## Additional description and notes about the tactic
[FMM add whatever additional notes are relevant here]

## Field Marketing Issue Creation

* [ ] [Program Tracking]( - FMC creates, assigns to FMC
* [ ] [Write copy issue]( - FMC creates, assigns to FMM
* [ ] [Marketo Landing Page & Automation Issue]( - FMC creates, assigns FMM (issue will be triaged)
* [ ] [Sales Nominated Issue]( - FMC creates, assigns to the FMM (issue will be triaged)
* [ ] [Email Invitation Issue]( - FMC creates one for each invitation requested, assigns to FMM (issue will be triaged)
* [ ] [Email Reminder Issue]( - FMC creates, assigns to FMM (issue will be triaged)
* [ ] [Follow Up Email issue]( - FMC creates, assigns to FMM (issue will be triaged)
* [ ] [Add to Nurture]( - FMC creates, assigns to FMM (issue will be triaged)
* [ ] [List Clean and Upload]( - FMC creates, assigns to FMM and MOps 

**If we receive final PDF of Survey Results:**
* [ ] [Field Marketing Pathfactory Asset Upload and Track Creation Issue]( - FMM creates, assigns to FMC

**Optional: create the optional issues only we have rights to survey results and there is a multi-channel plan for how the survey will be promoted*

/label ~"Field Marketing" ~"mktg-status::wip" ~"Survey"

SimplyDirect <> Marketo Integration

SimplyDirect and Marketo are integrated, so that SimplyDirect can send leads to Marketo immediately without a list upload. You must follow these directions exactly, each time you set up a new survey program, or else the integration will not work.

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license