KnowledgeTree allows you to add assets in multiple ways.
Does it make a difference? The answer is, of course, it depends. It depends on what you’re trying to accomplish. So we will lay out the the pros and cons of each.
|Preview Available in SFDC||Displays for Prospects on KT Landing Page||KT Analytics Gathered||Ease of Updating|
|URLs (Blogs, Marketo landing pages)||No||No||Share, View||If link address changes, must create new asset in KT Manager|
|URLs to specific assets (ending in .pdf, .doc)||Yes||
|Share, View, Download||If link address changes, must create new asset in KT Manager|
|Asset via Repository (Box, Dropbox, Google Drive)||
|Share, View, Download||Update at the repository level. KT will show newest version real time. **|
If you are aiming to gather more analytics via other marketing tools, such as Marketo, you may want to consider using a URL. This will send the prospect to the link and your settings for that page will take effect just as if KnowledgeTree weren’t involved.
The benefit to adding the URL to KnowledgeTree for Sales users to create a share link, is that you will get the share and view activities to allow for analytics of what is shared and viewed. You will then get your further analytics with your secondary tool from their analytic methods.
In order for URL's to be shareable to prospects, they must be publicly accessible, e.g. not behind a company log in or firewall. The URL will function in KnowledgeTree the same as it does without KnowledgeTree.
Also, click here for more about integrations using KnowledgeTree activities generated in Salesforce.
Asset Via Repository Notes:
If one of your goals is ease of updating content, you will want to add your assets via a repository. When the current version is updated to the latest, KnowledgeTree will render the most recent version.
Currently, KnowledgeTree supports direct integration with Box, Dropbox, Google Drive, OneDrive, Alfresco, FTP, Sharepoint (Office365 & On-Premise), Salesforce Content Libraries, and WebDAV.
**If you delete or move an asset from your repository, you will break the link with KnowledgeTree. You will need to add the asset again to KnowledgeTree and unpublish the original KnowledgeTree asset.