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

Content Syndication


This page focuses on content syndicatio through external vendors as a tactic used within marketing campaigns, including account centric campaigns. When employing this tactic, we have promoted our content through a third-party vendor, but do not direct the end users back to our website. In these cases, we often have given them the resource to make available for download to their audience, and recieve the leads to be uploaded.

If you are interested in running a content syndication campaign, then please reach out to the Demand Generation team. If you are in Field Marketing, please see this page for Field Marketing epic details.

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 creates the main tactic issue
  2. Project owner creates the epic to house all related issues (code below)
  3. Project owner creates the relevant issues required (shortcut links in epic code below)
  4. Project owner associates all the relevant issues to the newly created epic, as well as the original issue
  5. Project owner sets due dates for each issue, based on agreed upon SLAs between teams for each task, and confirms accurate ownership for each issue
  6. Step by step instructions for setup can be found here

Note: if the date of the tactic 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: Content Syndication - [Vendor] - [3-letter Month] [Date], [Year] --->

## [Main Issue >>]()

## [Copy document >>]() - [template](

## :notepad_spiral: Key Details 
* **Project Owner:** 
* **Coordinator:** 
* **Type:** Content Syndication
* **Campaign Tag:**  
* **Persona (choose one):** `Practitioner, Manager, or Executive`
* **Use Case (choose primary):** `CI, VC&C, DevSecOps, Other` (FY21-22 focus on CI and VC&C)
* **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.`
* **Content Type:** [eBook, Report, Whitepaper]
* **Content Title:** [As appears on [this list](]
* **Budget:** 
* **Launch Date:**  [MM-DD-YYYY] (this is the date the content syndication begins through the vendor)
* [ ] [main salesforce program]()
* [ ] [main marketo campaign]()
* [ ] Campaign UTM - Project owner (FM) to fill in (Format: campaign tag - change to all lowercase, no spaces, hyphens, underscores, or special characters)

## User Experience
[Project owner (FMM) to provide a description of the user journey - from communication plan, to what the user experiences upon reciept, plus triggers on our end like confirmation email and how GitLab fulfils with the vendor, up until receipt by the user and answering whether or not we get confirmation that they received it... what is the anticipated journey after that?]

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

## Issue creation
* [ ] [Program Tracking]( - _all content syndications for DG should have the parent campaign set as `Demand Gen Publishers/Sponsorships`
* [ ] [List clean and upload issue]( 
* [ ] [Follow up email issue]( 
* [ ] [Add to nurture issue]( 

/label ~mktg-status:wip ~"Content Syndication"
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license