COLLABORATIVE ASSET GENERATION AND COMMUNICATION SUMMARY OF THE INVENTION This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The technology described herein allows a sender to initiate generation of a collaborative asset, which may be a video generated by merging videos provided by a group of users. The technology can facilitate the generation and collection of digital assets, such as video, images, and audio recordings from a group of users designed by the sender. The collaborative asset may be associated with a tangible object using a unique identifier located on the tangible object. The collaborative asset may be stored in computer memory on a user- experience server and associated with the unique identifier. When the unique identifier is provided to the user-experience server by a recipient of the tangible object, the collaborative asset can be retrieved and output to the computing device that provided the unique identifier. Thus, a user can initiate generation of a collaborative asset. The tangible object may be a greeting card, gift card, ornament, and the like. A unique identifier, such as a QR code, may be located on the tangible object and used to associate the tangible object with the collaborative asset. In one aspect, the collaborative asset is stored in a cloud data store and indexed with an identifier linked to the QR code or other unique identifier. Upon scanning the QR code with a visual sensor (e.g., camera) on a computing device, such as a smart phone, an application on the device may retrieve the collaborative asset and output it to the user. In one aspect, the collaborative asset is a customized video generated by multiple users. For example, the customized video may be a collection of users wishing a recipient of a greeting card happy birthday. Generation of the collaborative asset may be originated by a sender of the greeting card, or other tangible object, by the sender scanning a unique identifier located on the greeting card. The sender may purchase the tangible object with the unique identifier located on it. The unique identifier may be obscured by packaging, a removable portion of the tangible object (e.g. flap), a moveable portion of the tangible object, and the like. The sender may need to remove packaging or manipulate the portion of the tangible object obscuring the unique identifier in order to scan the unique identifier. Thereafter, the system may associate the unique identifier with the collaborative asset. Scanning the unique identifier can cause the collaborative asset application to display the collaborative asset to a recipient and/or a sender for editing, approval, or viewing. The video may be intended for viewing by the recipient of the tangible object. Scanning the unique identifier may cause a customized video application on the phone to be opened. The collaborative asset application may be provided by a collaborative asset service. The collaborative asset service may edit and join groups of videos provided by multiple users into a single video. Returning to the collaborative asset application, the sender may be asked to login to an existing account or create an account for the customized video service. Other persons contributing content to the collaborative asset may also need to log in. The unique identifier is then stored in computer memory on a user-experience server. The user-experience server can associate the unique identifier with a digital asset, such as an image or video, designated by the user. The tangible object can then be communicated to a recipient. For example, a greeting card can be mailed from a sender to a recipient. The collaborative asset application can work with a service that allows the sender to invite others to contribute to the collaborative asset. The service may allow the sender to enter email addresses, phone numbers for texts, social media identifiers, or other means to contact potential collaborators. The service can track invites sent and whether content was contributed by invitation recipients. The sender may receive notifications when new content is added. The service may combine the videos of multiple people into a single collaborative asset. The sender may be able to approve and edit the collaborative asset before allowing it to be viewed by the recipient. BRIEF DESCRIPTION OF THE DRAWING The present disclosure is described in detail below with reference to the attached drawing figures, wherein: FIG. 1 is a diagram of a QR code located on a tangible object, in accordance with aspects of the technology described herein; FIG. 2 is a diagram of sender scanning a QR code located on a tangible object, in accordance with aspects of the technology described herein; FIG. 3 is a diagram of a digital asset selection interface that a sender uses to associate a digital asset with the tangible object, in accordance with aspects of the technology described herein; FIG. 4 is a diagram of a recipient scanning the QR code on the tangible object, in accordance with aspects of the technology described herein; FIG. 5 is a diagram of a recipient viewing the collaborative asset through the recipient’s user device, in accordance with aspects of the technology described herein; FIG. 6 is a block diagram of an exemplary computing environment suitable for use in implementing embodiments of the present disclosure; FIG. 7 is a block diagram illustrating an exemplary collaborative asset system in which some embodiments of the present disclosure may be employed; FIGS. 8A-G illustrate actions taken by a sender during generation of a collaborative asset, in accordance with aspects of the technology described herein; FIGS. 9A-F illustrate actions taken to invite others to contribute content to the generation of a collaborative asset, in accordance with aspects of the technology described herein; FIGS. 10A-G illustrate actions taken to edit and finalize a collaborative asset, in accordance with aspects of the technology described herein; FIG. 11 is a block diagram that illustrates an exemplary computing device; FIGS.12A-C illustrate actions taken to view a collaborative asset, in accordance with aspects of the technology described herein; FIGS. 13A-D illustrate a greeting card with an obscured unique identifier that is linked to a collaborative asset, in accordance with aspects of the technology described herein; FIG. 14 illustrate a greeting card with an obscured unique identifier that is linked to a collaborative asset, in accordance with aspects of the technology described herein; FIG. 15 illustrate a method of generating a collaborative asset, in accordance with aspects of the technology described herein; and FIG.16 illustrates a method for printing a greeting card with an obscured unique identifier, in accordance with aspects of the technology described herein. DETAILED DESCRIPTION OF THE INVENTION The subject matter of the present disclosure is described with specificity herein to meet statutory requirements. However, the description itself is not intended to limit the scope of this patent. Rather, the inventors have contemplated that the claimed subject matter might also be embodied in other ways, to include different steps or combinations of steps similar to the ones described in this document, in conjunction with other present or future technologies. Moreover, although the terms “step” and/or “block” may be used herein to connote different elements of methods employed, the terms should not be interpreted as implying any particular order among or between various steps herein disclosed unless and except when the order of individual steps is explicitly described. Each method described herein may comprise a computing process that may be performed using any combination of hardware, firmware, and/or software. For instance, various functions may be carried out by a processor executing instructions stored in memory. The methods may also be embodied as computer-usable instructions stored on computer storage media. The methods may be provided by a standalone application, a service or hosted service (standalone or in combination with another hosted service), or a plug-in to another product, to name a few. The technology described herein allows a sender to initiate generation of a collaborative asset, which may be a video generated by merging videos provided by a group of users. The technology can facilitate the generation and collection of digital assets, such as video, images, and audio recordings from a group of users designed by the sender. The collaborative asset may be associated with a tangible object using a unique identifier located on the tangible object. The collaborative asset may be stored in computer memory on a user- experience server and associated with the unique identifier. When the unique identifier is provided to the user-experience server by a recipient of the tangible object, the collaborative asset can be retrieved and output to the computing device that provided the unique identifier. Thus, a user can initiate generation of a collaborative asset. The tangible object may be a greeting card, gift card, ornament, picture frame, clothing, pottery, decoration, accessory, and the like. A unique identifier, such as a QR code, radio-frequency identification tag (RFID), and/or unique design, may be located on the tangible object and used to associate the tangible object with the collaborative asset. As an alternative, the unique identifier may be located on a tag (hanging tag) or decal associated with tangible object. As yet another alternative, the unique identifier may be within a box or otherwise obscured by packaging and/or integrated into packaging. As used herein, a unique identifier may include a unique machine-readable number and/or alphanumeric sequence encoded by the unique identifier. The unique identifier allows an associated tangible object to be differentiated from all of other similar tangible objects even among the same model of tangible object. For example, a first instance of a generic birthday card with a first design has a first unique identifier and a second instance of same generic birthday card has a second unique identifier that is different than the first unique identifier. In one aspect, the collaborative asset is stored in a cloud data store and indexed with an identifier linked to the QR code or other unique identifier. Upon scanning the QR code with a visual sensor (e.g., camera) on a computing device, such as a smart phone, an application on the device may retrieve the collaborative asset and output it to the user. In one aspect, the collaborative asset is a customized video generated by multiple users. For example, the customized video may be a collection of users wishing happy birthday to a recipient of a greeting card. Generation of the collaborative asset may be originated by a sender of the greeting card, or other tangible object, by the sender scanning a unique identifier located on the greeting card. The sender may purchase the tangible object with the unique identifier located on it. The unique identifier may be obscured by packaging, a removable portion of the tangible object (e.g. flap), a moveable portion of the tangible object, and the like. The sender may need to remove packaging or manipulate the portion of the tangible object obscuring the unique identifier in order to scan the unique identifier. Thereafter, the system may associate the unique identifier with the collaborative asset. Scanning the unique identifier can cause the collaborative-asset application to display the collaborative asset to a recipient and/or a sender for editing, approval, or viewing. The collaborative asset (e.g., video) may be intended for viewing by the recipient of the tangible object. Scanning the unique identifier may cause a customized video application on the phone to be opened. The collaborative asset application may be provided by a collaborative asset service. The collaborative asset service may edit and join groups of videos provided by multiple users into a single video. In an aspect, the first time the unique identifier is scanned the collaborative asset building interface is opened. The second time the unique identifier is scanned the viewing interface is opened. In other aspects, the interface asks whether the user is a sender or receiver and the appropriate interface is then shown. In an aspect, the viewing interface is not available until after the collaborative asset is finalized. Once finalized, the next scan may result in the application opening the viewing interface. Returning to the collaborative asset application, the sender may be asked to login to an existing account or create an account for the customized video service. Other persons contributing content to the collaborative asset may also need to log in. The unique identifier is then stored in computer memory on a user-experience server. The user-experience server can associate the unique identifier with a digital asset, such as an image or video, designated by the user. The tangible object can then be communicated to a recipient. For example, a greeting card can be mailed from a sender to a recipient. The collaborative asset application can interact with a service that allows the sender to invite others to contribute to the collaborative asset. The service may allow the sender to enter email addresses, phone numbers for texts, social media identifiers, or other means to contact potential collaborators. The service can track invites sent and whether content was contributed by invitation recipients. The sender may receive notifications when new content is added. The service may combine the videos of multiple people into a single collaborative asset. The sender may be able to approve and edit the collaborative asset before allowing it to be viewed by the recipient. In some aspects, a collaborative asset may be configured for playback and/or interaction at one or more different timepoints. For example, to incorporate both time- constrained, and free-time playback options, one or more features may be incorporated into the user experience for playback of the collaborative asset, such that the asset recipient (e.g., a greeting card recipient that is gifted a card having a code that retrieves the particular collaborative asset) and potentially one or more of the asset contributors (e.g., the greeting card purchaser and any other contributor to the recorded digital content compilation) may interact at any time or at a particular timepoint with the digital content, and potentially with the card recipient. In some aspects, an asynchronous “party” may be created where the collaborative asset recipient is invited to join and interact with the collaborative asset contributors. The greeting card recipient may scan a unique identifier to retrieve the collaborative asset, and at the same time, an invitation to each collaborative asset contributor may be provided, so that contributors can see and/or interact with the recorded content of the other contributors, and the contributors themselves. In this embodiment, attendees to the “asynchronous” party could participate at any time, given that the card recipient is invited to view the content and interact with the dedications within the recorded content at any time. In other embodiments, the card recipient may be invited to view the content and interact in real time with the recorded segments of content from each contributor. In further aspects, a video greeting card creator/purchaser, may be able to monitor if a card contributor has viewed, opened, or responded to the video content of the collaborative asset. In some aspects, each of the content contributors may be able to view each of the other contributions to the entire collaborative content, while in further aspects, collaborators/contributors to the content may be further able to invite additional contributors/attendees to the asynchronous party platform, by inviting the participants to socialize/view the recorded content. In another embodiment, contributors may assist in editing or creating the final collaborative asset content, while in further embodiments, the greeting card recipient may be able to respond back to all of the contributors to the collaborative content. In some aspects, an “event” date may be determined for engaging each of the digital collaborators, providing a reminder of different timepoints, such as the date/time to submit digitally recorded content to the collaborative asset, and a date/time to rejoin the card recipient to view the collaborative content together. In further aspects, the unique identifier printed within the greeting card may be able to initiate recording by the greeting card purchaser, retrieve the collaborative recorded content for viewing by the greeting card recipient, and initiate subsequent engagement and/or interaction between the greeting card recipient and at least one of the collaborative asset contributors after delivery of the greeting card to the recipient. In an aspect, the tangible object includes two obscured unique identifiers. One of the two obscured unique identifiers may be removable from the tangible object. In this way, the sender may keep the second unique identifier, while the first unique identifier remains attached to the tangible object. In one aspect, the item (e.g., removable tab) obscuring the permanent unique identifier includes a second copy of the unique identifier. Initially, both the first and second copy are obscured. FIGS. 1-5 illustrate the use of the technology with a greeting card. However, aspects of the technology described herein are not limited to use with a greeting card. The example of FIGS.1-5 describes the transfer of a greeting card between a first user and a second user. The first user is described as the sender and the second user is described as the recipient. The use of a QR code is one example of a unique identifier that may be suitable. Turning now to FIG.1, the greeting card 100 includes a happy birthday message 105 and a QR code 110. Though not shown, the greeting card 100 could also include stock- keeping unit (“SKU”) identifiers. The SKU identifies the greeting card model, but not the individual greeting card. In other words, all greeting cards of the same model may have the same SKU. The SKU may be used to identify a fiducial mark pattern associated with the card model. Different card models may include different fiducial marks, different arrangements of fiducial marks, and different amounts of fiducial marks, among other differences. In aspects, the SKU and/or card design could be used to identify the card in combination with the QR code 110 or other identifiers. Turning now to FIG. 2, the sender opens a collaboration interface of a greeting card application running on a mobile device 120 and takes a picture of the QR code 110 with the mobile-device’s camera. The collaboration interface may provide instructions that ask the user to capture the portion of the greeting card including the QR code 110. In other words, the portion of the tangible object captured by the camera should include the QR code 110. When the SKU is included on the tangible object, then the instruction may request that the SKU also be included in the image. In this case, instructions could indicate that the QR code 110 should be captured along with the SKU and possibly other card design features. In aspects, multiple images may be requested. For example, when an SKU is located on the back of a greeting card and the QR code is located on the front. The collaboration interface and/or greeting card application can perform a quality check on the image. If the QR code 110 and/or other requested card features are not within the captured image, then the sender may be prompted to capture a second image. Alternatively or additionally, the quality check can be performed in real time through analysis of the video being received through the camera and instructions provided to adjust the camera location as needed. If the QR code 110 and other features are within the field of view, then the greeting card application instructs the user to capture an image, for example by tapping the screen. Turning now to FIG. 3, the sender 114 selects one or more digital assets to associate with a collaborative asset that is associated with the greeting card 100 through the unique identifier. The digital assets may be identified through a collaboration interface provided by the greeting card application. The digital assets can include assets located on the mobile device, such as existing pictures and videos. The digital assets can include assets located on a server, such as publicly or privately available pictures and videos. The digital asset may also be created by the collaboration interface. For example, the collaboration interface can facilitate the user recording an audio or video message that becomes part of the collaborative asset. Back-end services, such as the user-experience server 702, associate collaborative assets with unique identifiers. The unique identifier is then stored in association with a reference to the collaborative asset. The unique identifiers may be used to retrieve the collaborative assets and output those assets to a recipient of the greeting card. The greeting card application can include an interface through which others are invited to contribute content. The content provided by others can be combined to form a collaborative asset. Turning now to FIG.4, the recipient of the greeting card 100 opens the greeting card application in the recipient’s mobile device 130 and scans the greeting card. As before, the greeting card application may provide instructions to the recipient to scan an adequate portion of the tangible object. Turning now to FIG. 5, the greeting card application then uses the image captured by the recipient to retrieve the unique identifier using the QR code 110 and/or other identifiers. The unique identifier is then sent to the user-experience server with instructions to retrieve any collaborative asset associated with unique identifier. The collaborative asset 132 is then provided to the recipient’s mobile device 130 and output to the recipient. Turning now to FIG. 6, a block diagram is provided showing an operating environment 600 in which some embodiments of the present disclosure may be employed. It should be understood that this and other arrangements described herein are set forth only as examples. Other arrangements and elements (e.g., machines, interfaces, functions, orders, and groupings of functions, etc.) can be used in addition to or instead of those shown, and some elements may be omitted altogether for the sake of clarity. Further, many of the elements described herein are functional entities that may be implemented as discrete or distributed components or in conjunction with other components, and in any suitable combination and location. Various functions described herein as being performed by one or more entities may be carried out by hardware, firmware, and/or software. For instance, some functions may be carried out by a processor executing instructions stored in memory. Among other components not shown, operating environment 600 includes a number of user devices, such as user devices 602a and 602b through 602n; a number of data sources, such as data sources 604a and 604b through 604n; server 606; user 603, and network 610. It should be understood that environment 600 shown in FIG. 6 is an example of one suitable operating environment. Each of the components shown in FIG. 6 may be implemented via any type of computing device, such as computing device 1100, described in connection to FIG. 11. These components may communicate with each other via network 610, which may include, without limitation, one or more local area networks (LANs) and/or wide area networks (WANs). In exemplary implementations, network 610 comprises the Internet and/or a cellular network, amongst any of a variety of possible public and/or private networks. It should be understood that any number of user devices, servers, users, and data sources may be employed within operating environment 600 within the scope of the present disclosure. Each may comprise a single device or multiple devices cooperating in a distributed environment. For instance, server 606 maybe provided via multiple devices arranged in a distributed environment that collectively provide the functionality described herein. Additionally, other components not shown may also be included within the distributed environment. User devices 602a and 602b through 602n may comprise any type of computing device capable of use by a user 603. For example, in one embodiment, user devices 602a through 602n may be the type of computing device described in relation to FIG. 11 herein. By way of example and not limitation, a user device may be embodied as a personal computer (PC), a laptop computer, a mobile device, a smartphone, a tablet computer, a smart watch, a wearable computer, virtual reality headset, augmented reality headset, a personal digital assistant (PDA), an MP3 player, global positioning system (GPS) or device, video player, handheld communications device, gaming device or system, entertainment system, vehicle computer system, embedded system controller, a camera, remote control, a bar code scanner, a computerized measuring device, appliance, consumer electronic device, a workstation, or any combination of these delineated devices, or any other suitable device. User devices 602a and 602b through 602n can be client devices on the client- side of operating environment 600, while server 606 can be on the server-side of operating environment 600. Server 606 can comprise server-side software designed to work in conjunction with client-side software on user devices 602a and 602b through 602n to implement any combination of the features and functionalities discussed in the present disclosure. This division of operating environment 600 is provided to illustrate one example of a suitable environment, and there is no requirement for each implementation that any combination of server 606 and user devices 602a and 602b through 602n remain as separate entities. Each user device 602a and 602b through 602n can be associated with one or more users, such as user 603. The users can include sender and recipients as described herein. Some user devices can be associated with multiple users, such as a family PC, game console, meeting room PC, electronic white board, and such. Similarly, a single user can be associated with multiple devices, including shared devices. A user sign in identification can be used to determine the user operating a user device at a point in time and to associate actions taken with a user record. Data sources 604a and 604b through 604n may comprise data sources and/or data systems, which are configured to make data available to any of the various constituents of operating environment 600, or collaborative asset system 700 described in connection to FIG. 7. For instance, in one embodiment, one or more data sources 604a through 604n provide (or make available for accessing) digital assets that can be combined in a collaborative asset and associated with unique identifiers. The digital assets can be uploaded from user devices 602a and 602b through 602n and/or from server 606. Turning now to FIG. 7, a block diagram is provided illustrating an exemplary collaborative asset system 700 in which some embodiments of the present disclosure may be employed. The collaborative asset system 700 includes network 610, which is described in connection to FIG. 6, and which communicatively couples components of collaborative asset 700. The components of collaborative asset system 700 may be embodied as a set of compiled computer instructions or functions, program modules, computer software services, or an arrangement of processes carried out on one or more computer systems, such as computing device 1100 described in connection to FIG. 11. In one embodiment, the functions performed by components of collaborative asset system 700 are associated with one or more applications, services, or routines. In particular, such applications, services, or routines may operate on one or more user devices (such as user device 602a), servers (such as server 606), may be distributed across one or more user devices and servers, or be implemented in the cloud. Moreover, in some embodiments these components of collaborative asset system 700 may be distributed across a network, including one or more servers (such as server 606) and client devices (such as user device 602a), in the cloud, or may reside on a user device such as user device 602a. Moreover, these components, functions performed by these components, or services carried out by these components may be implemented at appropriate abstraction layer(s) such as the operating system layer, application layer, hardware layer, etc., of the computing system(s). Alternatively, or in addition, the functionality of these components and/or the embodiments of the disclosure described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc. Additionally, although functionality is described herein with regard to specific components shown in collaborative asset system 700, it is contemplated that in some embodiments functionality of these components can be shared or distributed across other components. The collaborative asset system 700 generally operates to identify a unique identifier on a tangible object, such as a greeting card. The unique identifier is used to associate a digital asset, such as a video, with the greeting card. The digital asset can be retrieved when the recipient of the card scans the unique identifier. As briefly mentioned above, each component of the collaborative asset system 700, including the user-experience server 702, first user device 720, second user device 730, third user device 750, fourth user device 752, and storage 790 and their respective subcomponents, may reside on a computing device (or devices). The user-experience server 702 is responsible for providing the server-side of the user experience. Using the greeting card as an example, the user-experience server 702 will receive a unique identifier and a designated digital asset from the sender’s user device. For the purpose of illustration, the first user device 720 is described as the sender’s user device and the second user device 730 is described as the recipient’s user device. The third user device 750 and fourth user device 750 are collaborating devices. The user-experience server 702 will associate the unique identifier and the digital asset together within a data store as a seed for a collaborative asset. The invitation management component 716 sends invitations asking potential collaborators to submit content for the collaborative asset. Invitations may be tracked and follow ups provided until content is received or a deadline is reached. Progress notifications may be provided to the sender. The collaborative asset builder 718 edits the original digital asset provided by the sender and the additional assets received from collaborators to build a collaborative asset. When the unique identifier is provided to the user-experience server 702 by the recipient of the tangible item, then the collaborative asset can be retrieved and communicated to the computing device that provided the unique identifier the second time. Optionally an address, such as a URL, where a digital asset can be found can be communicated instead of the digital asset itself. The user-experience server 702 includes sub-components, such as digital asset management component 712, collaborative asset manager 714, QR code tracker 713, invitation manager 716, and collaborative asset builder 718. These components work together to provide the experience described above. The digital asset management component 712 manages digital assets and the association of the digital asset with a unique identifier. Managing the digital asset can include storing the digital asset. For example, pictures, videos, and audio recordings provided by the sender or collaborators may be stored by the digital asset management component 712. The digital assets provided by a particular sender could be stored in storage 790 and associated with a user profile 740 of the particular sender. In the example shown, the media pairs 748 include a digital asset 748a and an identifier 748b associated with it. A particular user, such as the sender, may be associated with multiple media pairs. In instances where the digital asset is already stored in association with a video provider, such as a social media platform, the digital asset 748a could be a link or reference to the digital asset. Any method of storing or identifying the digital asset in such a way that it may be retrieved in the future are suitable for use with the technology described herein. Storing the media pairs in association with the user profile 740 can allow the user to modify the association. For example, a user that initially established the pairing may choose to delete the content, modify the content, etc. The first user device 720 and the second user device 730 are provided. As mentioned, the first user device 720 can correspond to a user device used by a sender, while the second user device can be used by recipient. Both devices can include exactly the same components, but these components may perform different functions depending on whether the device is a sender or recipient. The user-experience application 722 can perform functions on behalf of the sender and receiver. The functions performed by the user-experience application 722 working on behalf of the sender are explained in conjunction with the user-experience application 722. Functions performed by a recipient are explained subsequently in association with the description of the user-experience application 732. The user-experience application 722 could be a cloud-based experience provided through a web browser. The user-experience application 722 could be a specialized application that runs on the first user device 720 and communicates with a back end service. The user-experience application 722 can initiate generation of a collaboration interface by the collaboration interface component 726. The collaboration interface can provide instructions asking the user to scan a unique identifier on the tangible object. The instructions can use a combination of textual explanation and images. The image capture component 724 captures an image of the unique identifier and optionally an SKU. The image capture component 724 can then send the image to the user- experience application 722 for further use. The digital asset collection component 725 can provide an interface that allows the user to select a digital asset to associate with the tangible object as a seed for a collaborative asset. The digital assets can include assets located on the mobile device, such as existing pictures and videos. The digital assets can include assets located on a server, such as publicly or privately available pictures and videos. The digital asset may also be created by the collaboration interface. For example, the collaboration interface 726 can facilitate the user recording an audio or video message that becomes the digital asset. The unique identifier and the digital asset and/or identification information for the digital asset are communicated to the user-experience server 702. The user-experience server 702 maintains an association between digital assets and unique identifiers. The unique identifiers may be used to retrieve the collaborative assets after digital assets are combined and output those collaborative assets to a recipient of the greeting card. The second user device 730 is used by the recipient of the tangible object. For example, a sender associated with the first user device 720 could mail a greeting card to the user of the second user device 730. The second user could then open the user-experience application 732 and follow instructions provided to retrieve a collaborative asset associated with the tangible object by the first user. The user-experience application 732 could be a cloud- based experience provided through a web browser. The user-experience application 732 could be a specialized application that runs on the second user device 730 and communicates with a back end service. The user-experience application 732 can generate a collaboration interface 736 that instructs the user to take a picture of the QR code on the greeting card or other tangible object. The image capture component 734 can capture an image QR code and communicate the image or code extracted from the image to the user-experience application 732. The image or code can then be communicated to the user-experience server 702. The user-experience server 702 analyzes the code and identifies the collaborative asset associated with the unique identifier generated by analysis of the image. The digital asset collection 735 can perform functions that allow the collaborative asset to be output to the user through the second user device 730. User profile 740 includes user accounts and activity data 742, user device information 744, user preferences 746, and media pairs 748. User account(s) and activity data 742 generally includes user data related to the sending and receiving of tangible object using the user-experience server. In particular, user account(s) and activity data 742 can include data regarding user emails, texts, instant messages, calls, and other communications; social network accounts and data, such as news feeds; online activity; calendars, appointments, or other user data used by components of the system. Embodiments of user account(s) and activity data 742 may store information across one or more databases, knowledge graphs, or data structures. As discussed hereinabove, user device information 744 may include identification information for devices used by a single user. The user device information can be used for security reasons to validate a user, maintain a secure session, and for other purposes. User preferences 746 can include various permissions, such as how long digital assets and the association between the digital assets and the unique identifier should be maintained. The user preferences can include opt-in and opt-out selections for the sharing and collection of personal information. FIGS. 8A-G illustrate actions taken by a sender during generation of a collaborative asset, in accordance with aspects of the technology described herein. Turning now to FIG. 8A, shows a starting interface 801 for the collaboration asset generation process. The interface 801 may be shown after the user logs into the collaborative asset generation system. The interface 801 allows the sender to designate a recipient by name by entering the recipient’s name in the text box 802. The sender may also select a theme (not shown), background music through a music drop down interface 803, and/or other creative aspects to be used when generating the collaborative asset. The user may be asked to select from stock content provided by the collaborative asset service. The stock content may match the theme. Selecting the continue button 804 brings the user to the next interface. Turning now to FIG. 8B, shows an asset-upload interface 805, in accordance with aspects of the technology described herein. The asset-upload interface 805 allows the user to generate a video and/or upload pre-existing content, such as a video, photograph, or audio file to act as a seed for the collaborative content. Selecting the preview video button 806 will play the current version of the collaborative asset video. The user may start the process of uploading a video or photo by selection the video upload button 807. In an aspect, the digital asset selection interface 809 is opened in response to selecting the video upload button 807. Selecting the invite a friend link 808 will open an interface through which friends may be invited to contribute content to the collaborative asset. In an aspect, selecting the invite a friend link opens the invitation interface 901 of FIG. 9A. In one aspect, the asset is a digital gift card or other holder of monetary value. The digital gift card may not be provided in or viewable within the collaborative asset. Instead, it may be displayed in the interface used to view the collaborative asset. It could also be separately communicated in electronic form to the recipient upon the recipient scanning the unique identifier. Turning now to FIG. 8C, a digital-asset selection interface 809 is shown, in accordance with aspects of the technology described herein. The digital-asset selection interface 809 gives the user the choice of creating content by selecting the record-a-video button 810 or selecting content from a library by selecting the choose-from-a-library button 811. Pressing the cancel button 812 may return the user to the digital asset-upload interface 805. Turning now to FIG.8D, a video creation interface 813 is shown, in accordance with aspects of the technology described herein. The video creation interface 813 allows a user to create a custom video. The video may be created using the front-facing camera on a smartphone or tablet. Alternatively, a webcam may be used. The smartphone interface may provide helpful instructions, such as reminding the user to look at the camera on the phone, rather than the screen, with a look-here arrow 815. The user may start recording by selecting the tap-to-record button 814. Once a video is recorded, the user may preview the video and then uploaded it if satisfied. Otherwise the user may attempt to record a second video and may repeat this process until the user is satisfied with the video created. Turning now to FIG. 8E, a photo or video selection interface 820 is shown, in accordance with aspects of the technology described herein. The photo or video selection interface 820 allows a user to select pre-existing photos or videos. As can be seen, a filter 822 allows either photos or albums to be selected to help the user navigate to the desired content. The selection interface 821 may show thumbnails of the content to help the user identify the correct asset to upload to the collaborative asset service. A search box 823 is provided for the user to enter a search query meant to return a relevant video or photo. Turning now to FIG. 8F, a confirmation interface 830 is shown, in accordance with an aspect of the technology described herein. The confirmation interface 830 shows thumbnails (834, 835, and 836) of the uploaded content and a successful upload message 831. The confirmation interface 830 allows the sender to upload additional content through the upload video button 837 and to invite others to upload content through the invite others button 838. Selection of the invite others button 838 may take the user to the screen shown in FIG. 9A. Selection of the edit video control 833 enables the user to edit the associated video. The editing can include deleting all or part of the associated video. The collaborative video may be previewed by selecting the preview button 832. Turning now to FIG. 8G, a content management interface 840 is shown, in accordance with an aspect of the technology described herein. The content management interface 840 allows the user to edit the order of content, add content, or delete content from the collaborative asset project. In one aspect, the added content is library content that can be placed anywhere within the collaborative asset. The library content may be provided by a service that facilitates generation of the collaborative asset. The library content could include a celebrity greeting, animation, or other type of content. FIGS. 9A-F illustrate actions taken to invite others to contribute content to the generation of a collaborative asset, in accordance with aspects of the technology described herein. Turning now to FIG. 9A, an invitation interface 900 is shown, in accordance with aspects of the technology described herein. The invitation interface 900 is used by the sender to identify collaborators to which invitations to collaborate will be sent. In one aspect, the application may use a text system, social media application or email application on a smart device to send the invitation to the potential collaborators. In this way, the invitation appears to be a text or email sent from the sender to the collaborator. In another aspect, the email address, social media ID, or phone number are provided by the user and the system generates a text, email, or social media message that is sent from the system to the potential collaborator. Either way, the invitation will provide a link for the collaborator to follow if the potential collaborator chooses to participate. A customized message to potential collaborators can be entered in text box 902. The message provided may be included in the body of an automatically generated message (e.g., text, email, social media post) to a potential collaborator. An automatically generated email invitation can be generated using the email invite button 904. An automatically generated text invitation can be generated using the text invite button 906. The link button 908 causes a link to be displayed that may be copied and pasted into a social media post, email, text, messaging application, and the like. Turning now to FIG. 9B, a collaboration management interface 910 is shown, in accordance with aspects of the technology described herein. The collaboration management interface 910 provides a notification 912 when a collaborator uploads content. The collaboration management interface 910 shows videos provided by collaborators. The videos can be viewed individually by selecting the video thumbnails (915, 917, and 919). The collaboration management interface 910 may allow the user to arrange the order in which the collaborative videos will be seen in the final collaboration asset. Videos may also be deleted or shortened. The collaboration management interface 910 may provide an automated system that allows the sender to thank the collaborator for providing content. The collaboration management interface 910 also provides a link 839 for additional invitations to be sent to additional potential collaborators. Turning now to FIG. 9C, a collaboration asset editing interface 920 is shown, in accordance with aspects the technology described herein. The editing interface 920 allows the user to view the automatically created collaboration asset by selecting a preview screen 922. The automatically created collaboration asset may be created by the collaboration asset system described in FIG. 7. The collaboration asset may start with an introductory video provided by the collaboration asset system that is tied to the tangible object on which the QR code is located. The introductory video is an example of stock content. For example, the introductory video may include a message related to a message on the tangible object, such as a birthday wish, holiday wish, expression of sympathy, or the like. The digital assets provided by the sender and collaborators may be stitched together to form a video that is then concluded with content provided by the collaboration asset service. The terminal content may be stock content tied to the theme on the tangible object and complement the introductory content provided by the collaboration asset service. The terminal content and introductory content may match the theme on the card. The theme may be occasion based. Example occasions include, but are not limited to, an anniversary, birthday, holiday, graduation, get well, condolences, and the like. The theme may also be aesthetic, such as using the same art, colors, fonts, and the like. Once satisfied with the collaborative asset the sender may finalize it by selecting the finalize button 924. If the user is not satisfied, then selecting the back-to-editing button 926 will return the user to collaboration management interface 910 through which the video may edited. A digital link may then be sent to the recipient for electronic viewing. The recipient may also access the collaborative asset by scanning the QR code on the card. This provides two means of access for the collaborative content. In aspects, digital links to the collaborative content may be sent to the collaborators who provided content. In this way, the collaborators may view the collaborative asset sent to the recipient. Turning now to FIG. 9D, a confirmation interface 930 is shown in response to the user selecting the finalize button 924. If the user does not confirm that the collaboration asset is finalized by selecting the done button 934, then the user is taken back to the collaboration asset editing interface 920 for further editing. Pressing the cancel button 936 also causes the user is taken back to the collaboration asset editing interface 920 for further editing. Otherwise the collaborative asset is finalized upon receiving confirmation. Turning now to FIG. 9E, a sharing interface 940 is shown, in accordance with an aspect of the technology described herein. The sharing interface 940 allows the sender to view the collaborative asset by selecting the preview screen 941. The sharing interface 940 also allows the user to designate email addresses 944 or phone numbers 942 through which a link to the collaborative asset may be shared. The sender may select any user they wish to share the collaborative asset with. This can include the intended recipient, collaborators, friends, or anyone else they choose to share the collaborative asset with. The sharing interface 940 also includes a link generation button 946 that allows a link to the collaborative asset to be copied easily into social media, a webpage, or some other communication medium. FIGS. 10A-G illustrate actions taken to edit and finalize a collaborative asset, in accordance with aspects of the technology described herein. Turning now to FIG. 10A, a text invitation interface 1000 is shown, in accordance with aspects of the technology described herein. The communication means used to send an invitation to a collaborator can include text, email, and social media. These methods may be selected by the sender initiating the generation of a collaborative asset. The collaborative asset application on a sender’s device may have access to the sender’s contact list and select the text numbers from the list of designated collaborators. A single collaborator could be contacted through multiple communication means. For example an email and text could be sent to the same collaborator. The text invitation 1002 can include a link 1004 that the user may select. In response to selecting the link 1004, a collaboration interface through which content can be uploaded may be opened. The collaboration interface may be the upload interface 1020. Turning now to FIG. 10B, an email invitation interface 1010 is shown, in accordance with aspects of the technology described herein. As with the text invitation, the email invitation interface 1010 provides a link 1012 the user can select to access a collaboration interface. Turning now to FIG. 10C, a digital asset upload interface 1020 is shown, in accordance with aspects of the technology described herein. The digital asset upload interface 1020 provides an upload button 1022 for the user to upload content. The content can be uploaded from the user’s device or from some other source, such as cloud storage. In an aspect, one button allows the user to create content by recording a video. A second button allows the user select previously created content. In one aspect, a link to example collaborative asset video is provided to help the receiver think of a relevant and appropriate content to upload. Turning now to FIG. 10D, a digital asset selection interface 1030 is shown, in accordance with aspects of the technology described herein. The selection interface 1030 gives the user record video button 1032 to facilitate creating content or a selection button 1034 to select existing content from a library. The user may press cancel 1036 to return to a previous interface. Turning now to FIG. 10E, a photo or video selection interface 1040 is shown, in accordance with aspects of the technology described herein. The photo or video selection interface 1040 allows a user to select pre-existing photos or videos. As can be seen, a filter 1042 allows either photos or albums to be selected to help the user navigate to the desired content. The selection interface 1040 includes a thumbnail interface 1046 to help the user identify the correct asset to upload to the collaborative asset service. The search box 1044 allows the user to search for existing content by name or other feature. Turning now to FIG. 10F, a video creation interface 1050 is shown, in accordance with aspects of the technology described herein. The video creation interface 1050 allows a user to create a custom video. The video may be created using the front-facing camera on a smartphone or tablet. Alternatively, a webcam may be used. The smartphone interface may provide helpful instructions, such as reminding the user to look at the camera on the phone, rather than the screen, with a look-here arrow 1052. The user may start recording by selecting the tap-to-record button 1054. Once a video is recorded, the user may preview the video and then uploaded it if satisfied. Otherwise the user may attempt to record a second video and may repeat this process until the user is satisfied with the video created. Turning now to FIG. 10G, an upload confirmation interface 1060 is shown, in accordance with aspects of the technology described herein. The confirmation interface 1060 provides a confirmation message 1062 that confirms to the collaborator that the content has been uploaded and no further actions are required on behalf of the collaborator. It should be noted that while the selection of videos and photos is illustrated, the content can also include an audio file, and animation, and the like. A browse video greetings button 1064 allows the recipient to start a new collaborative asset. FIGS.12A-C illustrate actions taken to view a collaborative asset, in accordance with aspects of the technology described herein. Turning now to FIG. 12A, a text reception interface 1201 for a collaborative asset is shown, in accordance with aspects of the technology described herein. The text reception interface 1201 includes a link 1202 for the recipient to follow in order to access the collaboration asset, which may be opened in a web browser or other application. Turning now to FIG.12B, an email reception interface 1210 for a collaborative asset is shown, in accordance with aspects of the technology described herein. The email reception interface 1210 includes a link 1212 for the recipient to follow in order to access the collaboration asset, which may be opened in a web browser or other application. Turning now to FIG.12C, a collaborative asset viewing interface 1220 is shown, in accordance with aspects of the technology described herein. The viewing interface 1220 may be shown in a web browser or other application after the user selects a link in an email or text. The viewing interface 1220 may also be accessed by selecting a QR code on a greeting card or other tangible object. The viewing interface 1220 includes a player 1222 for the collaborative asset. The viewing interface 1220 includes a thank you interface. The thank you interface allows the recipient to send a text message or email to the sender and/or one or more collaborators with a thank you message. In aspects, the selection of either the text message button 1225 or email link 1226 will cause an email application or text application to open and be populated with the address or phone number of a sender or collaborator. Template message content may also be provided in the text or email. The thank you text or email can also include a link to the collaborative asset to allow the sender or collaborator to easily view the collaborative asset again. A browse video greetings button 1228 allows the recipient to start a new collaborative asset. FIGS. 13A-D illustrate a greeting card with an obscured unique identifier that is linked to a collaborative asset, in accordance with aspects of the technology described herein. Turning now to FIG. 13A, an unconstructed greeting card 1300 with an obscured unique identifier is shown. Generally, in the first embodiment, the greeting card 1300 a cover panel 1302, an intermediary panel 1304, and an end panel 1306. Alternate embodiments are contemplated, with more or fewer panels, different fold lines, different securement mechanisms or couplings, and different positioning of the obscured unique identifier. The embodiments are not limited to those described in the figures. Referring now to FIG. 13A, a front perspective view of a first embodiment of a unconstructed greeting card 1300 is depicted, in accordance with an aspect of the present invention. The first embodiment of the greeting card 1300 is formed from a single piece of card stock that is die cut and folded to provide three panels, namely, a cover panel 1302, an intermediary panel 1304, a and an end panel 1306. It should be noted that the term "die cut" should be interpreted broadly to cover all types of cutting the shape out of a piece of material or stock (e.g. laser, scissors, etc.). Similarly, while "card stock" is identified in the described example, the invention is not so limited. The phrase "card stock" should be interpreted broadly to cover other types of material, such as plastics, synthetic paper, etc. The cover panel 1302 has a first side 1308 and a second side 1310 and is coupled to the intermediary panel 1304 along a first fold line 1303. It should be noted that the term "fold line" as used herein should be interpreted broadly to cover all types of bends, scores, rules, creases, perforations, etc. The intermediary panel 1304 has a first side 1312 and a second side 1314 and is coupled to the end panel 1306 along a second fold line 1305. The end panel 1306 has a first side 1316 and a second side 1318. The panels 1302, 1304, and 1306 may be folded together such that they are in a stacked arrangement, with the first side 1308 of the cover panel 1302 positioned as a first front outside surface of the greeting card 1300 and the second side 1318 of the end panel 1306 positioned as a rear outside surface of the of the greeting card 1300. Additionally, in this stacked arrangement, the second side 1319 of the cover panel 1302 and the second side 1314 of the intermediary panel 1304 are facing each other and are preferable coupled together (e.g., by adhesive) in an abutting relationship. Further, in this stacked arrangement, which is illustrated in FIGS. 13C and 13D, the first side 1312 of the intermediary panel 1304 and the first side 1316 of the end panel 1306 may be facing each other. This arrangement presents the appearance of a standard two panel greeting card that can be opened and closed. By forming the greeting card 1300 from a single unitary piece of card stock, the die-cut card stock may be run through a printer prior to being folded to print a design, coloring, a pattern, sentiment or other indicia on one or both sides of the greeting card 1300. For printing, the greeting card 1300 may lie flat and is in a flat, unfolded configuration, such as just after the die-cutting process. This arrangement and use of three panels allows the die cut blank to be passed through a single sided printer, yet still provide printing on all three surfaces of the greeting card 1300 when it is formed. The intermediary panel 1304 includes a removable tab 1334 defined by a perforated edge 1332. The removable tab 1334 is centered in the middle of the intermediary panel 1304. Embodiments may include removable tabs located elsewhere. As shown in FIG. 13D, the opening created by removing the removable tab 1334 makes a QR code, or other unique identifier, printed on the back side 1310 of the cover panel 1302 visible to a user. In embodiments, the removable tab 1334 may include a second copy of the QR code on the back side. The greeting card 1300 may be sold with the removable tab 1334 attached. A purchaser may then remove the tab to expose the QR code and start the process of building a unique collaborative asset. The removable tab 1334 deters a person from scanning the QR before purchasing the card. Referring now to FIG. 13B, a back perspective view of a first embodiment of an unconstructed greeting card 1300 is depicted, in accordance with an aspect of the present invention. The cover panel 1302 has a first side 1308 and a second side 1310 and is coupled to the intermediary panel 1304 along a first fold line 1303. It should be noted that the term "fold line" as used herein should be interpreted broadly to cover all types of bends, scores, rules, creases, perforations, etc. The intermediary panel 1304 has a first side 1312 and a second side 1314 and is coupled to the end panel 1306 along a second fold line 1305. The end panel 1306 has a first side 1316 and a second side 1318. The panels 1302, 1304, and 1306 may be folded together such that they are in a stacked arrangement, with the first side 1308 of the cover panel 1302 positioned as a first front outside surface of the greeting card 1300 and the second side 1318 of the end panel 1306 positioned as a rear outside surface of the of the greeting card 1300. Additionally, in this stacked arrangement, the second side 1319 of the cover panel 1302 and the second side 1314 of the intermediary panel 1304 are facing each other and are preferably coupled together (e.g., by adhesive) in an abutting relationship. Further, in this stacked arrangement, which is illustrated in FIGS.13C and 13D, the first side 1312 of the intermediary panel 1304 and the first side 1316 of the end panel 1306 may be facing each other. This arrangement presents the appearance of a standard two panel greeting card that can be opened and closed. The intermediary panel 1304 includes a removable tab 1334 defined by a perforated edge 1332. Though shown as a rectangle, the removable tab 1334 could be any suitable shape, such as a triangle, oval, circle, trapezoid, and the like. The removable tab 1334 is centered in the middle of the intermediary panel 1304. Embodiments may include removable tabs located elsewhere. As shown in FIG.13D, the opening created by removing the removable tab 1334 makes a QR code 1340, or other unique identifier, printed on the back side 1310 of the cover panel 1302 visible to a user. In aspects, a human readable version (not shown) of a unique number and/or alphanumeric sequence encoded in the unique identifier may be printed above the unique identifier 1340. The human readable rendition of the information encoded within the unique identifier 1340 can assist with a quality check during manufacturing of the greeting card. In embodiments, the removable tab 1334 may include a second QR code 1335 that is identical to the QR code 1340. The second QR code 1335 would be obscured when the panels are in a stacked arrangement. The greeting card 1300 may be sold with the removable tab 1334 attached. A purchaser may then remove the removable tab 1334 to expose the QR code and start the process of building a unique collaborative asset. The sender could keep the removable tab 1334 and use the second QR code 1335 to access the collaborative asset. The removable tab 1334 deters a person from scanning the QR before purchasing the card. Turning now to FIG.13C, a view of the greeting card 1300 is shown in a formed and semi-open configuration, in accordance with an aspect of the present invention. The panels 1302, 1304, and 1306, are folded along the fold lines 1303 and 1305 to bring the panels 1302 and 1304 and 1306 together into a presentation arrangement. The unique identifier is obscured behind the removable tab 1334. The perforations on the perforated edge 1332 and finger slot 1350 make removal of the removable tab 1334 a simple task for a sender or purchaser of the card. The view show in FIG. 13C is of the inside of the card after opening. The removable tab 1334 provides instructions to remove the removable tab 1334 and scan the QR code. A birthday message is on the right side of the card 1355. Each card may include printed content associated with a theme (e.g., occasion, occasion/recipient, event, event/recipient). The theme may be specific or generic. For example, a generic birthday card vs. niece birthday card. Turning now to FIG.13D, shows the same greeting card 1300 as shown in FIG. 13A, but with the removable tab 1334 removed and the QR code 1340 exposed. The QR code 1340 may encode a unique identifier, a URL for the collaboration asset service, and a SKU for the greeting card. In combination, the SKU and unique identifier may form a unique identification for the specific card. The SKU can be used by the collaborative asset service to select book-end content for the collaborative asset. For example, a video introduction with aesthetics and a message that complements a message on the greeting card may be selected. For example, a greeting card with a happy birthday message may be paired with introductory video with an audio of the happy birthday song along with graphics and animation that are similar to the design on the card. The example shown, a dancing bottle with the word cheers on may sing happy birthday to be paired with the bottle on the greeting card. Concluding art or content may also be used to and the video or other collaborative asset. For example, an ending message of have a great birthday could conclude the collaborative video. Thus, a collaborative video could start with an introduction that is provided by a content provider. The video could be aesthetically and thematically linked to the greeting card or other tangible object on which the QR code is located. The video could continue with custom birthday videos created by the sender and other collaborators and then conclude with content provided by the collaboration service that is tied to the theme and aesthetics of the greeting card. In aspects, content is provided by the collaboration service in between the various messages. The intermediary content can serve as introductions to the different sections of the video. The introductions could tie the theme of the tangible object and to a particular collaborator. For example, the intermediary content could communicate that “grandmas are special” or “grandma loves you” and introduce a video from grandma to a grandchild. Thus, both the tangible object and stock content in the collaborative asset may have the same theme. Unique stock content may be provided for each model of tangible object. For example, a specific greeting card model (e.g., SKU) may have unique stock content available. Thus, the same template stock content may be used for all models of the same SKU and may be unique to the model. Alternatively, template stock content may also be used on multiple card models (e.g., SKUs) with similar themes. For example, the same stock content may be used for multiple birthday card models. In this way, different unique identifiers may be pre-linked (e.g., at printing) to stock content that matches the theme of the card on which the unique identifier is printed. In some aspects, the “code” printed within the greeting card may be decorative, having both a visual appearance for a card recipient and scannable features for a computing device. In further embodiments, the code may be visible to the card purchaser upon viewing an exposed surface of the greeting card, while in other embodiments, a code may be partially and/or temporarily obstructed from view. For example, a scannable unique identifier code may be printed on a particular surface of a greeting card such that, during manufacturing, the unique code may be printed on a manufacturing-accessible surface. Upon further processing, including one or more of cutting, folding, gluing, or taping, the greeting card may be configured in such a way to obscure the code-printed surface and protect the code from being scanned by anyone other than the card purchaser. In some aspects, the greeting card may include an integrated element, such as a die-cut, sticker, tear-away, peel-off, or other perforated or manipulated element of the card structure that reveals the code for scanning by the card sender in establishing the collaborative content, and scanning by the card recipient in retrieval of the contributed digital compilation. In further aspects of the invention, based on having a plurality of unique scannable codes associated with a single SKU of manufactured tangible items, a system for uniquely printing a distinct code onto each of the tangible items may include a batched variable print data server that is coupled to the printing system that, upon receipt of individual print jobs, manufactures a series of uniquely identifiable greeting cards, each having common SKU card content with at least one item of uniquely different, printed content. In some aspects, both a unique scanning code and a unique user-readable code may be printed onto each individual card from a particular batch of unique greeting cards. In further aspects, a unique print job for a unique identifier on a particular greeting card may include identifying a particular print region within a greeting card design, orienting the printing of the unique identifier in context of the surrounding greeting card design, and printing the unique code onto the properly oriented portion of the greeting card. In some aspects, based on the printing of a batch of unique identifiers onto a batch of commonly designed greeting cards, the system for manufacturing uniquely identifiable greeting cards may produce similar SKU card designs with variable scanning code features corresponding to variable customization zones within each card. Retail Display Turning now to FIG. 14, an exemplary collaborative asset preview experience may be provided in a retail environment. The preview experience may be provided as part of a tangible item product display having a scanning feature for generating a collaborative asset preview. Upon scanning a unique machine-readable code, a preview of the digital content included with the collaborative asset experience may be displayed prior to purchasing the greeting card. In one aspect, an example collaborative asset is shown to the user. In one embodiment, the tangible item is a greeting card (not shown), and the product display may include a retail merchandizing component featuring a unique machine- readable code 1406 that a consumer could scan. The retail merchandizing component may be an insert 1400 that sits behind greeting cards (and envelopes) in a greeting card slot within a greeting card rack. The insert 1400 may have a lower portion 1408 that is obscured by the greeting cards and envelopes in the card slot. In contrast to the lower portion 1008, the upper portion 1402 is, at least partially, visible above the greeting cards and envelopes. The upper portion 1402 may include a card description 1404 or category and a machine-readable code 1406. In this example, the machine-readable code is a QR code. Each unique card may have card-specific collaborative asset stock content. Accordingly, each insert 1400 may include a unique machine-readable code 1406 to enable a potential purchaser to view the specific stock content and/or example collaborative asset built with the specific stock content. In further aspects, because the unique identifier code (non-preview) is obscured within at least a portion of the greeting card structure so that the card purchaser is unable to preview the digital content accompanying the tangible greeting card product, the product information display may provide an indication of the type of digital contentment associated with that tangible item being sold at retail. In the example of the greeting card, the unique indicator preview may be represented as a triangle-shaped scannable code or QR code on the sample product information display (PID) insert 1400. In this example, prior to purchasing the greeting card displayed adjacent to this particular PID, the consumer may determine whether the tangible item features both physical and digital characteristics of a greeting card that they wish to purchase and eventually present to their card recipient. As such, the complete and/or non-preview version of the unique identifier may be present in and potentially obscured from view (e.g., behind a tab) or protected from access by all potential purchasers. The unique identifier preview code 1406 may be scanned by a potential card purchaser to launch a preview of the digital component of the corresponding greeting card. In further aspects, at least a portion of the unique identifier code for each tangible product SKU may be imbedded within a PID icon for Video Greetings-enabled products, such that scanning the embedded code sample launches a video preview of the digital component (animation, music, theme, etc.) accompanying the specific tangible item. As mentioned, a different theme may be used for stock content (e.g., music, starting video, end video, banners, side bars, stickers, wallpaper, or other creative/editorial content) may be provided for different SKUs. For example, birthday theme may be associated with a birthday card and a graduation theme associated with a graduation card. Providing a preview identifier for each SKU (or group of SKUs with the same theme) allows an SKU specific theme to be viewed by the purchaser prior to purchase. Example Methods Referring now to FIG. 15, a flow diagram is provided depicting a method 1500 for generating a collaborative asset, in accordance with aspects of the technology described herein. The method 1500 comprises a computing process that may be performed using any combination of hardware, firmware, and/or software. For instance, various functions may be carried out by a processor executing instructions stored in memory. The methods may also be embodied as computer-usable instructions stored on computer storage media. The method may be provided by a standalone application, a service or hosted service (standalone or in combination with another hosted service), to name a few. In addition, method 1500 is described, by way of example, with respect to the features of FIGS. 1-12. However, these methods may additionally or alternatively be executed by any one system, or any combination of systems, including, but not limited to, those described herein. At step 1510, the method 1500 includes obtaining from a first user device a unique identifier located on the tangible object. At step 1520, the method 1500 includes receiving an instruction to associate the unique identifier with the collaborative asset. At step 1530, the method 1500 includes receiving a first digital asset from a first user of the first user device. At step 1540, the method 1500 includes receiving a second digital asset from a second user of a second user device. At step 1550, the method 1500 includes using the first digital asset and the second digital asset to build the collaborative asset. At step 1560, the method 1500 includes associating the unique identifier and the collaborative asset together within a data store. Referring now to FIG. 16, a flow diagram is provided depicting a method 1600 for printing a tangible object with an obscured unique identifier, in accordance with aspects of the technology described herein. At step 1610, the method 1600 includes printing a unique identifier on a first surface a first card panel of a greeting card body. A unique identifier, such as a QR code, radio-frequency identification tag (RFID), and/or unique design, may be located on the tangible object and used to associate the tangible object with the collaborative asset. As used herein, a unique identifier may include a unique machine-readable number and/or alphanumeric sequence encoded by the unique identifier. The unique identifier allows an associated tangible object to be differentiated from all of other similar tangible objects. The unique identifier may be assigned to a card model during or before the printing process. In an aspect, the computerized printing system may select from unique identifiers allocated to a particular SKU when printing. Alternatively, the unique identifiers are randomly chosen and the unique identifier is scanned after printing and associated with the SKU that is also printed on the card. The scanning may occur prior to folding the card stock into the stacked position described with reference to FIG.13. At the conclusion of the printing process, the printing system/collaborative asset system knows what card SKU is associated with each unique identifier. The unique identifier may then be associated with appropriate stock content within the collaborative asset system. The user is then able to see the correct stock content when creating the collaborative asset without providing additional details about the greeting card model. The stock content can include and introduction, transitions, and terminal content. The stock content can match the content on the greeting card. At step 1620, the method 1600 includes applying a cut to a portion of a second card panel of the greeting card body to form a perforated tab. A perforated tab has been described with reference to FIG. 13, for example, with the removable tab 1334. At step 1630, the method 1600 includes folding the greeting card body to cause the perforated tab to at least partially obscure the unique identifier. The stacked arrangement of panels has been described with reference to FIG. 13 and serves to obscure the unique identifier. Example Computing Environment With reference to FIG. 11, computing device 1100 includes a bus 1110 that directly or indirectly couples the following devices: memory 1112, one or more processors 1114, one or more presentation components 1116, one or more input/output (I/O) ports 1118, one or more I/O components 1120, and an illustrative power supply 1122. Bus 1110 represents what may be one or more busses (such as an address bus, data bus, or combination thereof). Although the various blocks of FIG. 11 are shown with lines for the sake of clarity, in reality, these blocks represent logical, not necessarily actual, components. For example, one may consider a presentation component such as a display device to be an I/O component. Also, processors have memory. The inventors hereof recognize that such is the nature of the art and reiterate that the diagram of FIG. 11 is merely illustrative of an exemplary computing device that can be used in connection with one or more aspects of the present technology. Distinction is not made between such categories as “workstation,” “server,” “laptop,” “handheld device,” etc., as all are contemplated within the scope of FIG. 11 and with reference to “computing device.” Computing device 1100 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by computing device 1100 and includes both volatile and nonvolatile media, removable and non- removable media. By way of example, and not limitation, computer-readable media may comprise computer-storage media and communication media. Computer-storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVDs) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 1100. Computer storage media does not comprise signals per se. Communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above should also be included within the scope of computer- readable media. Memory 1112 includes computer storage media in the form of volatile and/or nonvolatile memory. The memory may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard drives, optical-disc drives, etc. Computing device 1100 includes one or more processors 1114 that read data from various entities such as memory 1112 or I/O components 1120. Presentation component(s) 1116 presents data indications to a user or other device. Exemplary presentation components include a display device, speaker, printing component, vibrating component, and the like. The I/O ports 1118 allow computing device 1100 to be logically coupled to other devices, including I/O components 1120, some of which may be built in. Illustrative components include a microphone, joystick, game pad, satellite dish, scanner, printer, wireless device, etc. The I/O components 1120 may provide a natural user interface (NUI) that processes air gestures, voice, or other physiological inputs generated by a user. In some instances, inputs may be transmitted to an appropriate network element for further processing. An NUI may implement any combination of speech recognition, touch and stylus recognition, facial recognition, biometric recognition, gesture recognition both on screen and adjacent to the screen, air gestures, head and eye tracking, and touch recognition associated with displays on the computing device 1100. The computing device 1100 may be equipped with depth cameras, such as stereoscopic camera systems, infrared camera systems, RGB camera systems, and combinations of these, for gesture detection and recognition. Additionally, the computing device 1100 may be equipped with accelerometers or gyroscopes that enable detection of motion. The output of the accelerometers or gyroscopes may be provided to the display of the computing device 1100 to render immersive augmented reality or virtual reality. Some aspects of computing device 1100 may include one or more radio(s) 1124 (or similar wireless communication components). The radio 1124 transmits and receives radio or wireless communications. The computing device 1100 may be a wireless terminal adapted to receive communications and media over various wireless networks. Computing device 1100 may communicate via wireless protocols, such as code division multiple access (“CDMA”), global system for mobiles (“GSM”), or time division multiple access (“TDMA”), as well as others, to communicate with other devices. The radio communications may be a short-range connection, a long-range connection, or a combination of both a short-range and a long-range wireless telecommunications connection. When we refer to “short” and “long” types of connections, we do not mean to refer to the spatial relation between two devices. Instead, we are generally referring to short range and long range as different categories, or types, of connections (i.e., a primary connection and a secondary connection). A short-range connection may include, by way of example and not limitation, a Wi-Fi® connection to a device (e.g., mobile hotspot) that provides access to a wireless communications network, such as a WLAN connection using the 802.11 protocol; a Bluetooth connection to another computing device is a second example of a short-range connection, or a near-field communication connection. A long-range connection may include a connection using, by way of example and not limitation, one or more of CDMA, GPRS, GSM, TDMA, and 802.16 protocols. EMBODIMENTS Embodiment 1. A greeting card customization system comprising: a unique code generator configured to dispense a single code for a single greeting card print job, wherein each single greeting card print job comprises a card design and card dimensions. The system also comprising a customization zone template configured to receive the single code and the single greeting card print job. The customization zone template is configured for: 1) accessing by a printing component to facilitate placement of the single code within a printable template zone corresponding to both the card design and the card dimensions; and 2) accessing by a finishing component to facilitate one or more of folding, die-cutting, gluing of the greeting card structure in relation to the printable template zone such that the single code is printed and protected from each process of the finishing component. Embodiment 2. A method for associating a sample digital asset with a tangible object. The method including obtaining a sample portion of a unique identifier for a digital asset corresponding to a particular tangible object. The method also including associating the sample portion of the unique identifier and a product information display for a merchandiser of a plurality of the particular tangible object, wherein the sample portion comprises at least a first video segment of curated content from a digital asset theme of the particular tangible object. Many different arrangements of the various components depicted, as well as components not shown, are possible without departing from the scope of the claims below. Embodiments of the present disclosure have been described with the intent to be illustrative rather than restrictive. Alternative embodiments will become apparent to readers of this disclosure after and because of reading it. Alternative means of implementing the aforementioned can be completed without departing from the scope of the claims below. Certain features and sub-combinations are of utility, may be employed without reference to other features and sub-combinations, and are contemplated within the scope of the claims.