Manage the static and web resources, such as images and cascading style sheets (CSS) that are used in your applications and are included in replay.
Start by uploading replay assets from the Company Settings page. When you upload replay assets (Templates, Hybrid asset package, Static / Web resource package) from Company Settings, the extracted folder structure and its contents are added to the Experience Analytics file system. You can then use Asset Manager to view, upload, delete, and download individual files on the Experience Analytics file system. You cannot use Asset Manager to upload replay assets in bulk.
Use static and web resources for session replay
Static assets and web assets include files, such as images and cascading style sheets, that are used in your application. To replay sessions, Experience Analytics (Tealeaf) needs to be able to access these resources quickly to render screen views. Normally, static and web resources are dynamically retrieved from the originating server. However, sometimes you can't retrieve the resources from that server. In these situations, you can either manually upload the resources to the Experience Analytics Content Management System (CMS), or you can use the Content Retrieval Service to upload the resources to the Experience Analytics CMS automatically.
Manually uploading static and web resources
- Content and structure of a static or web package
A static or web package is a .zip or .tar file containing the resources that are required for replay. The folder structure in that file must duplicate the structure of the website, and the name of the first-level folder must be the name of the host server. For example, if you have a file that is called
logo.jpgthat is on your website here: http://www.site.com/assets/images/home/logo.jpg, it must reside in the folder structure of the static or web package file here: \www.site.com\assets\images\home\logo.jpg.
- Tagging a static or web package with site and time frame
When you upload a static package to the CMS, it must be tagged with information that includes a domain name (Tag 1) and a date range (Tag 2).
The domain name in Tag 1 is matched to host name in the requests that are made by the replay server during session replay. For a static resource package, the date range is matched to the date when the replayed session was captured.
When you want to upload a web package to the CMS, you can upload it using static package link in Company Settings, but you must tag the package with a domain name (Tag 1) and an empty Tag 2. When you tag the package this way, you can use the Web Replay Asset tab of the Asset Manager to manage individual Web Replay assets.
After you upload the resources, you can then use the
GetStaticAssetsreplay rule to instruct the replay server to use the resources in CMS.
In the fall of 2017, a company decides to change the graphical layout of their website (www.site.com). The change introduces new versions of site images and style sheets. The new site will be rolled out on January 1, 2019.
The data analytics and marketing teams are concerned about the fidelity of session replay because the server wont' be able to retrieve resources that were available before the change. Remember, visitors saw previous versions of site images, but replay server can download only the new versions.
By using a static package, you can assure the data analytics and marketing team that sessions that were captured before the change but replayed after will accurately reflect what visitors see. The static package contains all static assets that were used by the previous version of the website, which won't be accessible after the roll out of the new website is complete.When you upload the static package, the value for Tag 1 must match the host name
www.site.com, and the value for Tag 2 must match the time frame when the uploaded resources were part of the website. So, for this example, the time frame is before January 1, 2019 and is entered as
- Note: In addition to uploading to the CMS, you need to create a relevant
GetStaticAssetsreplay rule for each uploaded static package (each
Tag 2values) that instructs the replay server to use resources in the uploaded file. In this example, a host profile must exist in replay rules with the name equal to
Tag 1and a
GetStaticAssetsrule with the SessionDateRange equal to the value for
<HostProfile name="www.site.com"> <GetStaticAssets name="CMSFIRST" SessionDateRange="-01/01/2019" urlList=".*"/> </HostProfile>
- Note: In addition to uploading to the CMS, you need to create a relevant
About uploading static resources automatically using the content retrieval service (CRS)
You can use the CRS to upload the resources to the Experience Analytics CMS automatically.
For information about CRS, see Retrieve static content from URLs captured in sessions with the content retrieval service (CRS).
Find a static or web resource package
To upload, change, or download a static or web package, you must first use the Find Static Package function. You must perform this step before you click Edit on the Company Settings page.
To find the static or web resource package, complete the following steps.
- From the menu bar, click your user login name and select Admin.
- Select the Settings tab.
- Scroll to the Static Resource Package section.
- Enter the host name in the Tag 1 field.
- Enter the date range in the Tag 2 field.
If you are working with a web resource package, leave Tag 2 blank.
- Click Find Static Package.
Tag 1 and Tag 2 also serve as the two tags that are associated with the static assets (bundled in a .tar or .zip file) to be uploaded.
Upload static resources that do not exist in the CMS
Use this task to upload a static or web resource package that does not yet exist in the CMS. If you clicked Find Static Package and got a message similar to Static Resource Package (tag_1/tag_2), then the static or web package is not in the CMS. You must upload the .tar or .zip file first by completing the following steps.
- On the Company settings page, click Edit in the lower right corner.
- Click Upload file.
The Choose a TAR/ZIP file from your local file system dialog displays.
- Browse to select the file on your local machine.
- Click Upload.
Select a different static or web resource package
If the values that you entered for Tag 1 and Tag 2 correspond to a package in the CMS, the package name is displayed as a link in the Static Package (/) field, as follows:
Static Resource Package (tag_1/tag_2) <size><upload_date>
To change to a different static resource package, complete the following steps.
- On the Company settings page, with the package name displayed in the Static Package (/) field, click Edit in the lower right corner.
- Click Change the file.
- Browse to select the replacement file on your local machine.
- Click Upload to upload the replacement file to Acoustic Experience Analytics (Tealeaf).
When the upload completes, the Static Package (/) field changes to display the package name of the replacement file.
- Click Save to save the replacement file to Acoustic Experience Analytics (Tealeaf).
Download static or web resources for replay
- Click the link in the Static Resource Package (/) field.
- Select Save File.
- Click OK to save the .zip or .tar file package.
What to do next
To retrieve the static resources from CMS during replay, you must enable the
GetStaticAssets replay rule in the
ReplayServerProfile.xml file. See Using the GetStaticAssets replay rule to retrieve static resources from a remote host in Replay rules and replay rule configuration for more information.