Overview

Hublify integrates an own Download-Manager, which stores, secures & tracks all configured downloadable files & data.
Each download has a unique 63-char ID.
All downloads are streamed out through a standard url: https://<your Hublify>/hfy/download?id=....
The downloaded content behind a download can be ...
- A Hublify MAM-Asset (any kind of media, office, pdf, etc. file)
- Another remote URL
- ( Hublify Dataset Exports )
Downloads can be secured with an extra password. Of course the password is stored only encrypted.
Executed downloads are always counted with an own counter.
Additionally executed downloads can be tracked with more detailed tracking-infos.
PIM products can be configured to contain prepared downloads. So you can securely sell downloadable content.

PIM: Products with Downloads

One product (-record) can be configured to contain 1 or more downloads.
This is achieved by extending a product via its configurator-extension of type: "Downloads"
The details for these downloads are contained in the usual product-data in the field: prc_configurator_params.
When such a product is purchased (an order is created) then from its download-configuration the final (personalized) downloads are created & enabled in the download-manager.

Example - Product Data

Here an example what a product-record looks like that contains "downloads":

{
    "pcode": "myProductSKU",
    "name": "A Download Package",
    "description": "Buy this and you will get TWO downloadable files!",

    ...                                   // all other product-data properties...

    "prc_configurator_params": {          // ---------------   property "downloads" contains an array of downloads  -------

        "downloads":[
            {                                                     // ----    1st Download   (FREE, A MAM Asset)
                "dlprd_cfg_code": "xH8w22dk",                     // Unique Id for this configured download within
                                                                  // this product. Hublify generates it itself.
                                                                  // In e.g. later "free" downloads you must usually
                                                                  // provide the combi of: pcode & dlprd_cfg_code.

                "dl_acc_mode_person": "free",                     // Defines how/when this download can be accessed:
                                                                  // "free"            - Shop frontend availability (no ORDER).
                                                                  // "account_person"  - The buying person can download it later.
                                                                  // "account_company" - All person of buying company-account can download it later.

                "dl_name": "Download Number #1",                  
                "dl_desc": "This download contains foo bar!",
                "dl_track": "1",
                "dl_save_name": "dl-1.pdf",                       // (optional) This is the filename under wich the download will
                                                                  //            be saved in the user's browser.

                "dl_mb_label":"user-manual-example.2021.pdf",     // This refers to the actual MAM-Asset later downloaded!
                "dl_ref_url":"",

                "dl_cnt_max":"3",                                 // (optional) The download can be executed max. 3 times
                "dl_time_start":"",                               // (optional) Download will be not possible before this dateTime.
                "dl_time_end":"2021-12-31 23:59:59",              // (optional) Download will be not possible after this dateTime.
                "dl_time_start_offset_orderdate":"1",             // (optional) Download will be not possible before these number 
                                                                  //            of days (1) after purchase (relative offset).
                "dl_time_end_offset_orderdate":"",                // (optional) Download will be not possible after these days 
                                                                  //            after purchase (relative offset).

                "teaser_title":"Come on!",                        // (optional) 
                "teaser_content":"You don't want to miss it!"     // (optional) 
            },


            {                                                     // ----    2nd Download   (A streamed other URL)
                "dlprd_cfg_code": "aBc123xz",
                "dl_acc_mode_person": "account_person",           // Downloadable after purchase
                "dl_name":"Second File (#2)",
                "dl_desc":"Your extra file, too!",
                "dl_ref_url":"http:\/\/www.orimi.com\/pdf-test.pdf",   // The url. The downloading user will NOT SEE this!
             }
         ]
    }
}

Accessing downloads (dl_acc_mode_person)

The access of each single download within a product is configured by the field: dl_acc_mode_person.

In a shop frontend template, e.g. on a product-detail-page, you should evaluate this field and display the infos around it correspondingly. The possible values and intentions are:

"free"

Intention: It can/should be possible for the shop frontend user to download this file directly. Without having to purchase this product. Of course, it is up to you in the shop frontend how and whether at all to display this and providing a download link for it!

The standard download link is composed like:

https://<your hublify domain>/hfy/download?pcode=<Product PCode>&dlprd_cfg_code=<Download's dlprd_cfg_code>

Example download link

https://demo.hublify.io/hfy/download?pcode=myProductSKU&dlprd_cfg_code=xH8w22dk

With tracking

In order to track who (registered shop frontend persons) downloaded content later, you can optionally provide the personid as an additional parameter.

The personalized standard download link is composed like:

https://<your hublify domain>/hfy/download?pcode=<Product PCode>&dlprd_cfg_code=<Download's dlprd_cfg_code>&personid=<person-Id>

Attention: Hublify has no possibility to determine the correctness of your provided personid. So, for best detailed tracking results, be sure to display the "correct" (...and personalized) download link to your users.

"account_person"

Intention: After purchasing this product the buying person can download it.

For that personalized download Hublify will generate and provide unique download-id once the order is created / purchased.
How and when the buying person gets (e.g. via email) or sees (e.g. via my-account pages) this id is again up to you!

MORE INFOs soon here!

"account_company"

Intention: After purchasing this product the buying person and all optionally persons of the same company account can download it.