Uploading a Document Asset

Modified on Fri, 06 Oct 2023 at 02:32 AM

To Upload a Document Asset, follow the steps below:

  1. From the Left Nav Menu, click Assets.   
  2. On the Assets page > Upload Asset.    
  3. From the Create Asset pop-up window, select the Asset Type, Document. 
  4. In the Create Asset pop-up window, enter the Name of the Document Asset, and the Title auto-populates. You can edit the Title if you wish.
    Important: When the Name of an Asset reflects the content, it makes content categorization and selection easy. The user sees the Title when engaging with the Asset.

     
  5. Click on Choose under Folder to select a Folder for the Asset. To learn more about Folders, click here.

  6. Choose the appropriate Asset type by selecting an option from the Type drop-down list. Hushly offers a wide range of over 12 content types to choose from. Select the type that best matches the added Asset, whether it is an Article, EBook, Brochure, or any other relevant format.
     
  7. English is selected by default. You can select another language from the drop-down list.    
  8. By default, the Ungated button is set to No. However, if you want to make all the pages in the document visible to the user, toggle the button to Yes.      
  9. When the Ungated button is set to Yes, the Allow Anonymous Download button is displayed. By default the toggle is set to No, however, if you wish, you can toggle it to Yes.   
  10. The Upload option is the default choice for uploading a document Asset. However, you can select the External URL option to upload an asset from an External URL. To learn more about Uploading a Document Asset from an External URL you can refer to this document.    
  11. Click Select File To Upload. The file explorer opens.
     
  12. Navigate to the appropriate folder and select the file to upload. Alternatively, if the file explorer is already open, you can drag and drop the file into the Select File To Upload box.

  13. Click Save. You are redirected to the Setup tab of the Asset.

    On the Setup tab, define information about the Asset and its content.


    The mandatory information fields of the Setup tab, Name, Title, and Type are prepopulated with the values you configured for the Asset using steps 1 through 12 above. However, you can edit or change all of them.

    Important: All the fields in the above window are grouped into sections, as per usage namely,
    • Metadata: Name, Title, Description, Type, Language, Fulfilment URL, and Tags. 
    • Options: Ungated, Preview Pages, Opt-in Message, Hidden, Email Template and Enable Content Conversation. 
    • SEO: SEO Title, Canonical URL, and SEO Description.  
    • Thumbnails: Thumbnail 1 and Thumbnail 2.
    • If you define custom or catalog fields using Setup > Field Management, the fields for the Asset show up in the Setup tab above.

  14. An Excerpt gets automatically generated from the content uploaded providing a glimpse or sample of the content. It is limited to 200 characters.
    Note: Excerpt is effective only on the V3 hub.

  15. Enter a Description.

    Note: The maximum character length for the description is 2000.

     
  16. Enter the Fulfillment URL. The fulfillment URL hosts the ungated Asset.
    • If the Fulfillment URL is configured, the user is redirected to the URL.
    • If the Fulfillment URL is not configured, the user views the entire Asset, and any related content, hosted on a Hushly domain, app.hushly.com/asset.

  17. Enter the Tags you want to associate with the content. You can define a tag by typing the tag name. Use tags to group related Assets. 
  18. In the Options section, If the Ungated button is set to No, enter the page numbers you want to showcase in a content preview. By default, pages 1-3 are shown in the preview. However, if your document has more than 3 pages, you can showcase:
    • Pages 1, 5, and 10 (individual pages)
    • Pages 1-5 (a range of pages)
    • Pages 1, 3-5, 10 (individual pages and a range of pages)

      NoteYou can use a maximum of a hundred pages in a preview.

      When you want to make the entire document available through the preview, such as infographics, charts, tables, outlines, and how-to information. Set the Ungated button to Yes, the Preview Pages to enter the page numbers would not be displayed as the entire content is shown to the user. 
  19. When the Ungated button is set to Yes, the Anonymous Download button is displayed, and set to No, you can set it to Yes to allow the anonymous download to take place.

     

  20. Enter an Opt-in Message. The user sees this message above the opt-in form used for providing the business email. The default message is shown below: 
  21. Optionally, click Tokens to use them in the opt-in message. Use the {{asset.name}}, {{asset.type}}, and {{asset.content.type}} tokens to refer to the Asset information dynamically. 
    Using tokens helps to prevent typos in Asset names, saves time, and reflects changes in the Asset information.
     
  22. The Enable Content Conversation option tracks the conversations between the user and the Mitab of the asset.

    By default, the Enable Content Conversation button is set to NoHowever, toggle the button to Yes to enable the content conversation. 
    Note: To view the conversations, click the View Conversations link.         
  23. By default, the Hidden button is set to No. However, toggle the button to Yes if you want to hide this Asset in Hubs.

    Note: If the asset is set to be hidden, it will not be visible on any Stream.

     
  24. You can attach a specific Email Template to the Asset. When a user submits the opt-in form with a business email for this Asset, the email template configured here will be sent to the user. Click Preview to view the Email Template.
     
  25. In the SEO section, enter the SEO title. The content of this field appears as the title in search engine results. This title is relevant when you are deploying Hubs. 
  26. Enter an SEO description. The content of this field appears as the description in search engine results. This description is relevant when you are deploying Hubs.
    Important: When the SEO Title is not given, the search results show the Asset name as the Asset title.

    In Google Search Results
     
  27. You can also use the Ask Mitab (SEO Title and Description) beta link to automatically recommend an option that is most suitable for your asset as its SEO Title and Description, click here to learn how.  
  28. Enter a valid URL in the Canonical URL field. 
    Note: Search engines would crawl each page's content to compile a massive index of all the words it sees and their location on each page. In addition, they process information included in key content tags and attributes, such as <title> tags and alt attributes. To prevent Search engines from crawling these duplicate versions of the same page, we can configure a Canonical URL.

  29. Thumbnail 1 (500x272 pixels) is auto-generated when you upload an Asset. However, you can also upload Thumbnail 2 (500x660 pixels), which can be set to view at the Stream level on the Hub. Click here to learn more about Thumbnails.
     
  30. Click Preview in the top-right corner. 
    Hushly shows a full preview of the Asset.  
  31. If you notice that the content is not displayed correctly, click Regenerate Previews in the Asset Preview window.
    If the preview is good, click the X button at the upper-right corner to proceed with the setup.
     
  32. Click Update First Page to update or customize the first page only.

    Select an image to replace the first page of your document. Hushly updates and shows the preview of the first page.
    Note: PNG, JPEG, JPG, and GIF formats are all supported.
     
  33. If you have defined custom or catalog fields using Setup > Field Management, you can select the fields to associate with the Asset. 
  34. Click Save.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article