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.
The FMM (or requester) is responsible for following the steps below to create the epic and related issues in GitLab.
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.
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](https://docs.google.com/document/d/1j43mf7Lsq2AXoNwiygGAr_laiFzmokNCfMHi7KNLjuA/edit) ## :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](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-01-facilitate-tracking) - FMM creates, assign to MPM * [ ] [List clean and upload issue created](https://gitlab.com/gitlab-com/marketing/marketing-operations/issues/new?issuable_template=event-clean-upload-list) - FMM creates, assign to FMM and MOps * [ ] [Follow up email issue created](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-04-follow-up-email) (*optional*) - FMM creates, assign to FMM, MPM and FMC * [ ] [Add to nurture issue created](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-05-add-to-nurture) - FMM creates, assign to FMM and MPM /label ~"Marketing Programs" ~"Field Marketing" ~mktg-status:wip ~"Content Syndication"
=====NEED TO MOVE THIS TO MPM HANDBOOK=====
Salesforce Syncwith "not set", click on "not set"
Enable Bizible Touchpointsto
Include only "Responded" Campaign Members
Start Dateto the date of launch
End Dateto 90 days from date of launch (if this is an ongoing campaign, update appropriately)
Budgeted Costif you have the data available
Campaign Ownerto your name
Content Titleto be the title as it appears in the Content Syndication program
Content Typeto be the type of content
01 Downloadedsmart campaign, the "Smart List" should be listening for
Added to List > Vendor List. This list is under the Asset folder in the program. It will contain all of the members that were uploaded who downloaded the content.
01 Downloadedsmart campaign, the "Flow" will trigger a program status change
Content Syndication > Downloaded, that will trigger a scoring update. An interesting moment to be applied, the
Person Source(note: this maps to
Initial Sourcein Salesforce) will update IF a
Person Sourcedoes not already exist (i.e. it is blank), the
Acquisition Programwill set if blank, the Marketo
Initial Sourcewill populate if blank, and the
Person Statuswill update to
Activate. It should be set that a person can only run through the flow once.