PathFactory is an intelligent B2B content experience platform used to create personalized content journeys for your audience. The global content team is primarily responsible for all the of the content within the PathFactory. Campaign managers work with other teams in marketing to organize and curate assets into tracks that are then disseminated for use in Marketo, about.gitlab.com, and other campaign-related channels.
PathFactory is used primarily for email nurture streams, landing pages, advertising, and virtual event follow-up.
Assets are bundled together (around 5-7) in a "content track" and shared as one link. Instead of sharing multiple links to individual assets, one link provides a curated content experience.
Sharing individual assets. It's meant to encourage a visitor to "binge" the content and self-nurture towards MQL. For sharing individual assets, please direct to the GitLab website.
Creating web pages. Pathfactory is a content library that curates experiences (think of it like Netflix for B2B content). Pathfactory is not a replacement for Marketo.
☝️ PathFactory ≠ Email Nurture. PathFactory is a tool that - instead of driving to a single asset - drives to a related-content experience.
Nurture is a channel to bring an individual to the content. Just like ads, social, website, etc. drive to CTAs, PathFactory link is the CTA - a powerful CTA because it can lead the individual down a "choose your own adventure" path of consumption which we track.
What are the differing goals of PathFactory and Marketo?
Can records be in Marketo nurture and PathFactory nurture at the same time? If not, is 1 prioritized over the other?
Yes, the PathFactory track acts as a supplement to the existing Marketo nurture instead of a replacement. It allows us to provide related content in a seamless way for the end-user (better than simply providing a PDF link and to improve "binging" of content).
PathFactory is not a single source of truth (SSoT) for all GitLab content, but rather content that has been activated in a marketing campaign.
Content Management System (CMS) - A content management system is a software application that can be used to manage the creation and modification of digital content.
Digital Asset Management (DAM) - Digital asset management (DAM) is a system that stores, shares and organizes digital assets in a central location.
PathFactory - Content experience software used to allow buyers to binge-consume content, remove friction, and create more qualified leads, faster.
PathFactory for Sales allows B2B sales teams to deliver and track personalized content to engage buyers and close deals.
The Marketing Operations team is responsible for managing access requests & provisioning the appropriate level of access for each role/function. PathFactory is not provisioned as a baseline entitlement. If you or your team require access, please open a Single Person Access Request issue and provide business reason why access is needed. For certain permissions or roles, you may be required to go through training before access is provisioned.
There are three levels of access - Admin, Author, Reporter - which are granted based on the persons' role and team function within GitLab. All access levels have the ability to view analtyics within the tool.
Admin access is granted to Marketing Operations and at times, other teams such as sales or business operations to manage integrations between systems.Author access allows user to build, edit and publish content tracks applying existing tags to the assets.Reporter access provides general visibility to content within PathFactory but does not allow end user to create or modify any of the content, tracks or tags. This level of access is granted for the general GitLab team member both within Marketing and elsewhere who have a business need to have access.Sales User is anyone who has a valid email domain associated with our PathFactory instance, but who does not have a login. These users are not able to login to PathFactory, but they will be able to share any content tracks that Admins select on the Sales Configuration page.For more info on the capabilities of each role, see the knowledge base article.
| Team | User Roles | Rules of Engagement |
|---|---|---|
| Marketing Operations | Admin |
Manage, quality assurance, user management, system integrations, training |
| Content Marketing | Author |
Add content, quality assurance, participate in quarterly content audits |
| Campaign Managers | Author |
Add content, create and edit tracks for use in campaigns, define form strategy for conversion on tracks, participate in quarterly content audits |
| Product Marketing | Author (select users), Reporter (select users) |
Upload new content, participate in quarterly content audits, collaborate with Authors of tracks on content selection |
| Field Marketing | Author (select users), Reporter (select users) |
Upload content from virtual workshops, clone existing workshop tracks for use in follow-up emails, view content performance |
| Account-Based Marketing | Author |
Add content, create and edit content tracks for use in campaigns |
| Customer Reference Programs | Author |
Upload new case studies and customer content |
| Developer Evangelism | Author |
Upload new technical content |
| Sales Development Representative (SDR) | Sales user (PathFactory for Sales only) |
PathFactory for Sales (SFDC) |
| All Remote | Author |
Upload new all remote content, create and edit content tracks for use in all-remote campaigns |
| Partner Marketing | Author (select users) |
View content library, create and clone content tracks for partners, reporting |
| Customer Programs | Author (select users) |
View content library, create content tracks for customer onboarding where a TAM is not assigned or requested, reporting |
PathFactory has no built-in audit log or trail for changes that are made within the content library (only that it was updated and by whom) or content tracks. It is critically important that everyone with Author role access to PathFactory follow the instructions and documentation outlined in this handbook. Any changes made to the content library or content tracks can have a negative impact on those content tracks which are tied to campaigns, reporting, and attribution.
For instance, if an asset is deleted from the content library and that asset exists in campaign-related content tracks, the user that visits that asset within that track will be redirected to about.gitlab.com, which has the following impacts:
The same impacts above can happen if an Author role makes changes to an existing content track without collaborating with the Author of that track.
Before making any of these impactful changes, please collaborate with the Author of a content track before making any changes or asking in #mktgops before deleting any assets in the content library.
If these changes are made, it is also critically important to input them to the PathFactory changelog so that we can correct them accordingly.
Periodically, significant changes are made or added to PathFactory and processes that affect overall data and reporting. As such we have a changelog. Everyone with Author access that is making significant changes in PathFactory should add their changes to the changelog with a linked issue and/or relevant PathFactory links.
Scenarios for adding to the changelog:
[LIVE] content track[LIVE] content track[LIVE] content track and whyInstructions
The content library is where all content uploaded to PathFactory is added and tagged for use in content tracks and experiences. An asset must exist in the content library first before it can be utilized in a PathFactory experience.
There are multiple types of PathFactory experiences that you can create under Campaign Tools:
Explore Page you create is built on top of an existing Target or Recommend Content Track.When adding assets to the content library, please ensure both the public and internal titles match the title of the asset. Do not add any extra prefixes to the asset title (ex: [BLOG] - Title of blog). Content types are already indicated by the content type field. Remove any extra SEO meta title information such as |GitLab that is appended to the title once PathFactory pulls in the information about the asset from the URL. Follow the editorial team's guidelines for formatting and case (sentence case).
When adding localized content to Pathfactory, enter the localized title and description in the Public Configuration section. This is what external viewers of the content will see. Under Internal Configuration, enter the language with the English asset name (example: [Japanese] GitLab in Action Overview Demo). Internal Configuration is only viewable internally in Pathfactory.
When creating and editing content tracks, please use the following naming convention to let others know the status of your track. These track names are not shown to the visitor of the track. Name the track so that other Author roles understand the use of your track. Add start and end dates for your campaign if relevant so it can be archived/deleted at a later date. Add persona in the track title if the track is for a specific persona. Add a GTM motion to the title if the track assets are focused toward a specific GTM motion.
[WIP] - [Campaign Name] - work in progress track; not live[LIVE] - [Campaign Name] - live track; traffic is flowing to track[ARCHIVED] - [Campaign Name] - arhived track; not in active use; traffic may or may not be flowing to trackTrack labels are used to document the channels that a content track is distributed on. These track labels are arbitrary and do not tie to any functionality within PathFactory. They are simply used to indicate to other Author roles within PathFactory how you intend to use your content track.
| Label | Use |
|---|---|
| archived | content track no longer in use and marked for archiving, possibly future deletion |
| content track to be sent from a Marketo email or nurture stream | |
| event | content track is shared as part of a corporate event or partner event |
| external | content track is shared externally (ex: third-party website) |
| in-app | content track sent from an in-product message or notification |
| integrated campaign | content track is part of an integrated campaign |
| internal use only | content track is distributed to GitLab team members only |
| landing page | content track is sent to a visitor after filling out a form on a landing page |
| organic social | content track is shared in an organic social media post |
| outreach | content track is sent via Outreach |
| paid search | content track is part of a paid search campaign |
| paid social | content track is part of a paid social campaign |
| SAL inbound | content track is enabled for PathFactory for Sales for SALs to share inbound |
| SAL outbound | content track is enabled for PathFactory for Sales for SALs to share outbound |
| SDR inbound | content track is enabled for PathFactory for Sales for SDRs to share inbound |
| SDR outbound | content track is enabled for PathFactory for Sales for SDRs to share outbound |
| survey/quiz | content track is shared in a survey or quiz |
| web promoter | content track is used in a website promoter within PathFactory |
| website | content track is linked on a web page on about.gitlab.com |
Track folders are set up by team as different teams within marketing use and distribute content tracks for various use cases. This helps to ensure that team members only make change to content tracks within their team folder.
Forms should not be served based on the amount of time spent in a track, but rather after a visitor consumes 2-3 pieces of content. When a visitor progresses to the next piece of content (after the initial 2-3), they'll be asked to complete a form.
When naming forms, please follow the naming convention:
[WIP] Language - Purpose - Marketo Form ID (example: [WIP] Korean - Contact Us - 2963)[LIVE] Language - Purpose - Marketo Form ID (example: [LIVE] Korean - Contact Us - 2963)[TEST] Language - Purpose - Marketo Form ID (example: [TEST] English - PF<>Bizible - 2715)Before creating a new content track, decide what type of content track (target vs. recommend) you want to create. Use the criteria below to decide the best option:
Target track
Recommended track
Campaign Tools in the top navigation bar and select the content track type you want to create (target or recommend).Create track button in the top right.Create Track.ci-awareAdd content button at the top right. A window will pop up with the content library. Use the sorting options at the top to quickly add content by topic, type, funnel stage, etc. PathFactory content tracks are meant to encourage content binging (visitors reading more than 1 asset to accelerate them in the pipeline by helping them self educate faster in one visit). So as best practice, have more than 1 asset in a track.custom URL slug for the content track. Follow the instructions for creating a custom URL slug for an asset.
No Index, No Follow.Links & Sharing set to default.External ID set to default.Cookie Consent before providing the approved content track link for live use.Promoters are the tools that allow visitors to navigate the Content Tracks and encourage them to view additional recommended content. Think of promoters as the guides through a content track; the promoters you use determine how and when content will be presented to visitors. Note the different functionality of each below. Before going live, you can test each promoter to find the one that works best for the goals of your PathFactory experience.
Header feature with the Sign Posts and Bottom Bar promoters.Header is used to add additional branding to your content track.Flow, Sign Posts, and Bottom Bar cannot be used together. Choose 1 of the 3.
End Promoter, Exit, and Inactivity promoters can be used in conjunction with either the Flow, Sign Posts, or Bottom Bar promoters.
Call-to-action (CTA) buttons encourage further engagement from your visitors within your Content Tracks. CTAs can be added to any Target or Recommend Content Track. These CTA buttons can link to either a form or a URL.
Create a CTA
CTAs under User Experience.Add CTA button.Watch a demo.WIP form as your CTA.utm_source=pathfactory&utm_medium=cta-name)Save.Form strategy is used on content tracks to collect data from unknown visitors. This is done by "gating" an asset within a track or by creating a track rule with an engagement threshold (example: spent at least 60 seconds in the track and viewed 2 assets). Not all content tracks will or should have form strategy turned on - it depends on the goal of your campaign. Form strategy should only be used when a track entry point is a direct link from a digital ad bypassing a webform or gated landing page. Please bypass from strategy entirely when linking to PathFactory from emails since we are sending to known users. In the event the recipients (known users) forwards the emails to unknown users, we chose to forgo capturing their information for better user experience.
Please Note: PathFactory activity is tied into the MQL scoring model. This means that you do not need to add form strategy to a content track if entry point is from a landing page.
GDPR Considerations: When using time-based form strategy, aim for at least 15-30 seconds in order for the user to have plenty of time to accept the cookie consent pop-up prior to filling out the form.
On.View Form Strategy located below the Add Content button.Content Rules; for form strategy on the entire content track, you'll choose Track Rule.Form strategy by asset:
Add Rule in the Content Rules row.General Form (2074) LIVE form unless otherwise required according to campaign needs. Do not select a form marked [WIP].Display Behavior, click the dropdown and choose the assets where you want the form to show. (Please Note: only assets that you have added to the content track will show in the dropdown. If you want the form to show on an asset that is not in the track, you will need to add it first.)10 seconds is the default selection.Show to unknown users. This prevents forms being shown to users who are already known in Marketo. However, if you are using the form on the web or other channels, you'll want to select Show to unknown users only.Show to Known Visitors is toggled off.If submitted, allow form to show again toggled off.allow visitors to dismiss the forms if it is not crucial to its use to have them submit their info.Keep promoters active when form is shown is up to the Author. For example, if the Flow promoter is used on a content track, they will still be able to see the sidebar of avialable content while the form is shown to them. If this option is toggled off, the visitor will not be able to click on any content in the sidebar until they fill out the form.Form strategy for content tracks:
Add Rule in the Track Rule row.General Form (2074) LIVE form unless otherwise required according to campaign needs.Display Behavior you can choose to serve the form based on the number of content assets viewed or the total time spent on the track.? (there should only be one immediately after the end of the URL).& when appending UTMs.When a track is LIVE (in use):
[LIVE] Name of track.When a track has been archived (no longer in use):
[ARCHIVED] Name of track.[LIVE] content track.[LIVE] track can disrupt the user experience for the visitor and activate the #all track or fallback URL (about.gitlab.com) instead of the intended content track. Please ensure that the link to the asset is not being used in any other marketing channels before deleting.DRI for track creation: Campaign Managers
Segment Campaigns (subject to change if the folders get massive - HB to update as needed)[motion]-[stage]-[persona][#] (i.e. ci-awareness-prac1 or vcc-) - see moreON > Start Free SaaS TrialONCI Awareness Practitioner 1, set the end promoter to go to CI Awareness Practitioner 2 to move them to the next stage and continue binging)The forms used in PathFactory are hardcoded Marketo form script. They are added to PathFactory using the Marketo script, but they should also include the PathFactory capture tags and custom parameters to capture additional information behind the form fill. If a new form is created, the PathFactory capture tag and custom paramters must be hardcoded in the script.
To request a new form to use in PathFactory, the form must first exist in Marketo. If one does not exist, first create an issue in the marketing ops project using the form_request.md template. Once the Marketo form is completed, then create an issue in the marketing ops project using the pathfactory_form.md template.
A Capture Tag is a snippet of code added to a Marketo form code itself. The Capture Tag sees the visitor’s email address on submitted form, and sends it to PathFactory. This allows PathFactory to associate the email address of a visitor to their engagement data; the visitor will then be a known visitor rather than anonymous.
We use external forms (added by External URL or Custom HTML generated from Marketo) in PathFactory. The information submitted in the form is sent directly to Marketo. In order for PathFactory to associate the submitted email address with the visitor’s engagement data, you must use a Capture Tag. This is what allows PathFactory to identify the individual as a known visitor.
#all track, which includes all assets uploaded to PathFactory. In a case where the user is not redirected to the #all track, they will be redirected to the Fallback URL which is set to about.gitlab.com.lb_email= parameter when sharing about.gitlab.com links in Marketo emails. This parameter is used on learn.gitlab.com links to identify anonymous track visitors.Get Share URL feature next to the title of the track. Share links are to be used in locations such as the website whereas Email tracking links are only for use in email. Note: If it’s in email, it’s a known audience so don’t gate any assets in the track. Only use share links on the web and those tracks can have gated assets within PathFactory.? already existing in the PF link. Typically there is one. The only time it won't have a ? is when you set a custom URL.?, first add an ampersand & at the end of the PF link, followed by the UTMs.
https://learn.gitlab.com/c/10-strategies-to-red?x=53kuPbhttps://learn.gitlab.com/c/10-strategies-to-red?x=53kuPb&utm_source=email&utm_campaign=test?, first add a question mark ? at the end of the PF link, followed by the UTMs.
https://learn.gitlab.com/c/10-strategies-to-redhttps://learn.gitlab.com/c/10-strategies-to-red?utm_source=email&utm_campaign=testMarketo links
& at the end of the PF link, followed by the UTMs.
https://learn.gitlab.com/c/devops-explained-git?x=GVFK3F&lb_email={{lead.Email Address}}&utm_source=email&utm_campaign=test? (there should only be one immediately after the end of the URL).&.PathFactory links behind a form fill on a landing page
https://learn.gitlab.com/c/gcn-dev-sec-ops-how-?x=XOIXTl&lb_email=
Using a content track with a custom URL
? in a different location than with content tracks that don't have a custom URL.
https://learn.gitlab.com/c/gcn-dev-sec-ops-how-?x=XOIXTl&lb_email= (x=XOIXTl = content track ID)https://learn.gitlab.com/cicd/cloud-ci-tools-matur?lb_email={{lead.Email Address}}*Note: for simplicity in tracking, we strongly urge you to use a custom URL slug on all tracks. Video regarding custom URL slugs
PathFactory’s custom query string manager allows you to manage and append query strings when sharing a link to a content track or explore page.
Organization Settings in the dropdown menu in the top right corner.Custom Query Strings tab.Share button or icon.Note: Do not delete or edit the default query string for Marketo as that query string is an important way to integrate with PathFactory.
PathFactory’s Microsite Builder enables marketers to display multiple types of Content Tracks within a custom-designed landing page or multi-page microsite with navigation. Microsites should be used when you want to educate users about a specific topic or topics. Microsites are NOT a catchall nor a replacement for other types of landing pages. If you are unsure whether a Microsite is right for your campaign, please free to reach out in the #mktgops slack channel.
Microsite builder expands on how Explore Pages are used and improves on Explore Pages with a more robust and advanced feature set.
With Microsite builder you can:
You can request a new microsite, or an update to an existing microsite via this issue.
Microsite templates:
[Template] Partner Custom MicrositeExplore pages allow your visitors to quickly view all content assets in a content track. Each explore page you create is built on top of an existing target or recommend content track.
Before you make an explore page ensure that you have already built a content track (target or recommended) that you will use as the base.
Explore from the left navigation.Create Explore Page button.Create Explore Page. Please follow the hierarchy of folders by dept. from the content tracks.Appearances. Select your desired appearance from the left navigation in your explore page under Page Settings.Page Settings, ensure that the Search Engine Directive is set to No Index, No Follow.Layout Settings.Content Settings.Why can’t I change the background color behind my cover image?
The cover background color only shows when the cover image is set to "Fixed Width." Because of this, the color selection square is only available when "Fixed Width" has been selected.
I don’t want this header on my Explore page, how do I get rid of it?
The header is applied to an Explore experience from the base content track you chose for the explore page. If you don’t want the header on your explore page, go to the base content track and turn the header off.
I don’t like the order that my content is arranged on the Explore page; how do I move my content around?
All changes to the content in an explore page has to be done in the base content track that the explore page is built from. This includes the order of your content, so if you want to reorder your content you have to do so in the base content track.
Can I create a custom hero for a header on my page?
Yes! You can add a custom hero image by navigating to Appearances Configuration and selecting the appearance you would like to modify. Then click on the Explore tab and select cover image for Hero layout and upoad your custom image under Hero Image. Make sure you click save on both the explore image upload and then again to save the appearance edits you have made (recommended size for a hero image is 1600x500).
Appearances allow you to control the look and feel of your content tracks. By creating different appearance groups you are able to quickly and easily apply different colors, fonts, and logos to content tracks without having to configure them each time you build a new track. Appearance settings allow you to control how your promoters look, select favicons for your tracks, and configure the appearance of your cookie consent messaging.
You are able to change the appearance of the following components of a content track:
Video walkthrough of appearances (Nook login required)
Create a new appearance group
Appearances from the drop-down menu.Add Appearance.B button to bold the text. Click on the A buttons to change the text size.Add Appearance.Appearance groups, you can apply this styling to any of your content tracks. Simply select the appearance group from the drop-down menu under Experience Settings.The Languages feature gives you complete control over the text displayed to visitors on your promoters within content tracks and on website promoters. This feature also allows you to create language groups for languages other than English, and to customize the text that will be displayed for those languages.
There is no native integration between Smartling and PathFactory. To create a new language configuration in PathFactory and submit the default English source text available in PathFactory's language configuration menu, you must create a CSV. You can only include/exclude columns for translation in CSV. See the help center article for more info on formatting CSV files to submit for translation.
Languages.Languages under User Experience.Add Language button in the top right or in the left sidebar under the other language configurations.Webhooks allow PathFactory to automatically connect with a third party system and send data every time someone visits or interacts with a PathFactory experience. There are 3 types of PathFactory webhooks (form capture, visitor session, visitor activity).
We currently use the Visitor Session Webhook to connect to Marketo. The Visitor session webhook is triggered off of session data. A visitor session begins when a visitor arrives on a content track and ends when that visitor has stopped engaging with content for thirty minutes. This webhook is triggered when a visitor session ends. This means that the webhook will trigger and send data to Marketo thirty minutes after the visitor has finished engaging with content. The data sent though this webhook provides an overview of the level of engagement the visitor had with your content track and the content assets inside them during the session.
PathFactory applies a score to a person based on how much time they spent viewing an asset by its content type. The PathFactory score is incorporated into the Behavior score in Marketo.
| Content Type | Content Engagement Score | Engagement Time Threshold (seconds) |
|---|---|---|
| Analyst report | 1 | 120 |
| Assessment | 1 | 60 |
| Case Study | 1 | 45 |
| Data sheet | 1 | 45 |
| Demo | 1 | 60 |
| Infographic | 1 | 15 |
| Landing page | 1 | 45 |
| Presentation | 1 | 120 |
| Pricing | 1 | 30 |
| Product Article | 1 | 60 |
| Research report | 1 | 120 |
| Solution Article | 1 | 90 |
| Technical Blog Post | 1 | 60 |
| Testimonials | 1 | 30 |
| Thought leadership Blog Post | 1 | 60 |
| Topic Article | 1 | 120 |
| Video | 1 | 60 |
| Webcast | 1 | 600 |
| Whitepaper | 1 | 60 |
| eBook | 1 | 60 |
There are 2 external forms in PathFactory with apply Bizible touchpoints using JavaScript.
MOps: Form Submit-Bizible: Applies a Bizible touchpoint upon form submit within a PathFactory trackMOps: Bizible-Met Threshold: Applies a Bizible touchpoint when a visitor to a track has met the engagement thresholdThere are custom PathFactory fields available in Salesforce and Marketo.
| Field Name | Purpose |
|---|---|
| PathFactory Asset Type | A tag to help categorize types of content (whitepaper, video, eBook, etc) |
| PathFactory Assets Viewed | Cumulative number of assets viewed. This is not associated to time consumed! See Content Count for difference |
| PathFactory Content Count | Cumulative count of assets consumed. Example: if person consumes 2 whitepapers, 1 video and blog post for minimum of 20 seconds each in a single session this field would show 4. |
| PathFactory Content Engagement Threshold | The engagement threshold time setting (in seconds) of the content asset. |
| PathFactory Content Journey | Shows users path through a PathFactory experience (next asset viewed from previous asset based on slug) |
| PathFactory Content Language | The language of the content asset. |
| PathFactory Content List | Cumulative list of each assets content id/slug for each asset consumed. |
| PathFactory Content Slug | The custom slug of the content asset. |
| PathFactory Content Source URL | The URL of the underlying source content of the content asset. |
| PathFactory Content Title | The public title of the content asset. |
| PathFactory Content URL | The current public URL of the asset being rendered in the content track. |
| PathFactory Engagement Score | Each asset in content library can be assigned an engagement score; this score is passed from PF to SFDC and used to determine meaningful engagement with content. |
| PathFactory Engagement Time | Cumulative time a person spends consuming assets in session. |
| PathFactory Experience Name | The PathFactory track name - more details |
| PathFactory External ID | A non-unique ID that can be added to tracks &/or assets, which can be leveraged to organize content and configure it in Marketing Automation Platform (i.e Marketo) |
| PathFactory Funnel State | Each asset is tagged with stage of funnel most applicable to asset - Top of Funnel, Middle of Funnel or Bottom of Funnel |
| PathFactory Query String | Returns any values captured by a query string which you have added to the content experience URL. |
| PathFactory Query String Value | The value of a key in the query string. |
| PathFactory Topic List | Assets are tagged by topic. This is manually set & aligns with the tracking content list. |
| PathFactory Track Custom URL | The custom URL of the content track. |
| PathFactory Track ID | The automatically generated PathFactory ID of the content track. |
There are a variety of analytics and reports available in PathFactory that show the overall effectiveness of content. See more info here.
An iframe, or inline frame, is a tag <iframe> </iframe> that is used to embed an HTML document inside another HTML document on a website. The iframe HTML element can be used to insert content from another source, such as an advertisement, into a web page.
PathFactory uses iframes to serve content inside content tracks. Some web pages have restrictions that prevent their content from displaying in an iframe.
The Google Chrome Extension for PathFactory lets PathFactory users share content tracks and explore pages via Gmail. This functionality lets you embed content thumbnails and titles when sending emails using Gmail. See FAQ in The Nook.
Send button.Insert in the bottom right.Copy Link next to the content track or content asset. Close the modal to return to the email, select the text you want to link from, click the Insert Link button, then paste the copied link.Only Admins can enabled content tracks in the organization settings for use in the Chrome extension. Open an issue in the marketing operations project if you would like a specific content track enabled.
The PathFactory Google Chrome Extension will only de-anonymize users who view content sent in emails if the following is true:
Access protection protects content and events so only a select group of people can access it, based on them having a valid email address or email domain based on an allowed list. This allows you to share more confidential information with prospects, customers and employees in a content track or a VEX Event without the worry of someone viewing it who shouldn’t be.
Access Protection.Add Email to save. You can edit or delete these values at any point.Note: Anyone who has an email address in the Domains list or the Email Address list will be able to access the content.
Languages.Access Protection.Note: These messages willl apply for all users who use access protection in PathFactory. Ensure the messages are generic to apply to all use cases.
Appearances tab.General tab, configure the styling that will apply when someone is trying to access the content track. The fonts and colors will apply to messages within the windows that appear while trying to gain access to the content track, and the logo configured here is also displayed in the first message someone sees when they try to gain access.support@pathfactory.com) with the link to access the content track.You can use Drift within your PathFactory tracks to incorporate a "white glove" experience on a high-value campaign. For available Drift playbooks, see the Drift handbook page.
To set up Drift on your PathFactory track:
MOps: Drift external code snippet on the External Code field within your track settings.Update.PathFactory issue label and cc @MihaiConteanu.