User Subscriber Status
This article details the steps to implement your site's user subscriber status data into Chartbeat by adding a few lines to our standard tracking tag.
Last updated
This article details the steps to implement your site's user subscriber status data into Chartbeat by adding a few lines to our standard tracking tag.
Last updated
If you allow users to login to your site, or provide subscriber-only content, add the below configuration to your Chartbeat tag to enable traffic data segmentation by user-type in our tools. First, you'll need to declare a global _cbq variable with the following code:
Then, based on what type of user is currently browsing your site, push the following array elements that constitute a key-value pair to the _cbq array:
Always push _acct as the first element in the array, with that representing the key of a key-value pair. The second element in the array represents the value of the key-value pair. For the user_type value, please use one of the three standardized values below:
Generally, it's best practice to declare _cbq and perform your _cbq.push() right after your _sf_async_config setup. For example, if you wanted to push a user type of paid, your implementation might look like this (see lines 11 & 12):
It's up to your team to create the custom logic to automatically pass in one of our three user-type values each time our tag is loaded, based on the current user's status in your site's user tracking mechanism.
Tip: If your user subscriber status data only becomes available later in the page load, you can load the Chartbeat tag lower in the page HTML instead of placing our tag in the page's header. However, if your site will utilize our Headline Testing integration where some of our code is required to load before the closing <head> tag, we suggest using our two snippet solution detailed in the next page of this guide.
You've learned about our JavaScript tag and tracking script, how to customize your pageview tracking settings with our configuration variables, tracking virtual pageviews, and user subscriber status. Now review our options for alternative integrations of our website tracking code in the next page of this guide to see if any of these options apply to your setup.
Subscriber Status
user_type Value
Guest
anon
Registered
lgdin
Subscriber
paid