Zywave Analytics

What is Zywave Analytics?

Zywave currently uses three third-party tracking solutions to gather analytics from our applications: Heap, Appcues, and Google Analytics. Zywave Analytics bundles these tracking solutions into a single component to simplify the process of adding analytics to your application.

How to use Zywave Analytics

There are three ways to add the analytics scripts to Zywave applications:

1. Use Zywave Shell and it will add the necessary analytics scripts to your application (recommended)

2. If you cannot use Zywave Shell, but your application has single sign-on (SSO) with Zywave or is a Zywave subdomain (*.zywave.com):

   1. You should use Zywave Analytics in conjunction with Zywave API Proxy and

   2. Provide the URL to the Zywave API for your application to the api-base-url attribute:

       <zywave-api-proxy api-base-url="${API_BASE_URL}"></zywave-api-proxy> <zywave-analytics></zywave-analytics>

3. If you cannot use Zywave Shell or Zywave Analytics + Zywave API Proxy:

   1. You must manually add Zywave Analytics to your application and
   2. Include the appropriate attributes and IDs for the analytics solutions you need (more on that below).

When do I use the Zywave API Proxy element <zywave-api-proxy>? Check here.

Installing Zywave Analytics manually

Prerequisites

Before installing Zywave Analytics, check if Heap, Appcues, and Google Analytics scripts are already added to your application.

Do you already have tracking scripts in your application?

If any of these third-party tracking scripts are already in your application, there is a high chance of duplicate script loading/initialization when you install Zywave Analytics. To decrease the chances of duplication, we recommend you to:

1. Remove the third-party tracking scripts
2. Obtain the necessary IDs from Heap, Appcues, and/or Google Analytics, and
3. Follow the installation instructions below to add Zywave Analytics to your application in order to load these scripts instead

Do you not have any tracking scripts in your application currently?

If there are no third-party tracking scripts in your application and you want to add at least one via Zywave Analytics:

1. Obtain the necessary IDs you need from Heap, Appcues, and/or Google Analytics and
2. Proceed with the installation instructions below to add Zywave Analytics to your application in order to load the necessary scripts

Not sure how to obtain the necessary IDs from any of the analytics solutions for your application?

Reach out to the Heap and Appcues group at Zywave.

Installation

Once you've gotten the necessary IDs for any or all of the analytics solutions, it's time to install Zywave Analytics in your application!

Fun fact: Zywave Analytics is a native web component and has no expectations of frameworks/libraries being used.

Step 1: Load the scripts

Add the following script tag to the head of your document in order to register the custom elementin browsers and allow your application to load the analytic scripts.

<script type="module" src="https://cdn.zywave.com/@zywave/zywave-api-toolkit-bundle@latest/dist/bundle.js"></script>

Step 2: Add Zywave Analytics to your page

Add the following HTML (supplying attributes when needed, and removing when unnecessary) to your page:

<zywave-analytics    appcues-account-id="${APPCUES_APP_ID}"    ga-tracking-id="${GOOGLE_ANALYTICS_TRACKING_ID}"    heap-app-id="${HEAP_APP_ID}"    identity="${UNIQUE_GLOBAL_IDENTIFIER}"></zywave-analytics>

This custom element will load the necessary analytics based on the attributes you've supplied.

We'll go over what the attribute identity is in the next step.

Step 3: Add 'identity'

The last thing you need to supply is a unique global identifier to the identity attribute in <zywave-analytics>. With the way the third-party scripts work, we need an identifier to help track a given individual across multiple sessions and devices. identity should be a guaranteed unique global identifier from your system.

For Zywave, we use a combination of profileTypeCode and profileId, separated by a tilde (e.g., identity="B~1234").

Best practices

Identity

identity should be consistent and unique based on the third-party project IDs you are given because we want to reduce conflict between different systems in our analytics solutions—especially in Appcues. If you are given the Zywave Appcues account ID that all Zywave products use, your identity should be identifiable as associated with your ecosystem. For example, Advisen might use "Advisen~{userId}" to not conflict with other systems such as Zywave's identifier "B~1234".

User properties

userProperties (HTML: user-properties) is an optional property and feature of Zywave Analytics. It allows you to supply extra information in the form of a JavaScript object (or, if coming in via HTML, as an HTML safe JSON string) about a user to these scripts. userProperties currently has three standardized fields:

• givenName: Commonly referred to as "first name"
• familyName: Commonly referred to as "last name"
• email: email address

Any extra fields provided are entirely up to you. However, if you use the same Appcues instance as Zywave, it is highly encouraged your field names are confined to your product suite. For example, Advisen might want to supply the name of the agency. It would be recommended they do something like advisenAgencyName: 'Awesome Agency'.

Third party IDs and testing

No one tests in production! Be sure to use the proper IDs when testing this in a test environment. Transform these IDs with production ones when deploying to a production environment. We have a test instance of Appcues and most Heap projects are segmented into environments for this purpose.

Content Security Policy requirements

The third party analytics tools we use come with their own requirements. When using Content Security Policies (CSP), you will need to ensure you configure your policies to support these tools. Click the links below to find relevant documentation:

1. Heap
2. Appcues