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.

Process in GitLab to organize epic & issues

The FMM (or requester) is responsible for following the steps below to create the epic and related issues in GitLab.

  1. FMM creates the main tactic issue
  2. FMM creates the epic to house all related issues (code below)
  3. FMM creates the relevant issues required (shortcut links in epic code below)
  4. FMM associates all the relevant issues to the newly created epic, as well as the original issue
  5. FMM 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 the tactic changes, the FMM/requester 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: Content Syndication - [Vendor] - [3-letter Month] [Date], [Year]

<--- 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 
* **FMM/Requester:** 
* **MPM:**  
* **FMC:** 
* **Type:** Content Syndication
* **Account Centric?** Yes/No
* **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 `` - FMM to fill in based on budget doc

## User Experience
[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
[FMM add whatever additional notes are relevant here]

## Issue creation

* [ ] [Facilitate tracking issue created]( - FMM creates, assign to MPM
* [ ] [List clean and upload issue created]( - FMM creates, assign to FMM and MOps
* [ ] [Follow up email issue created]( (*optional*) - FMM creates, assign to FMM, MPM and FMC
* [ ] [Add to nurture issue created]( - FMM creates, assign to FMM and MPM

/label ~"Marketing Programs" ~"Field Marketing" ~mktg-status:wip ~"Content Syndication"


Steps to Setup Content Syndication in Marketo/SFDC

Step 1: Clone this program

Step 2: Sync to Salesforce

Step 3: Update Marketo tokens

Step 4: Activate Marketo smart campaign