Steps to check that your website integration is working as expected.
Configure QA/staging sites in Chartbeat
If you are adding new Chartbeat code to a website, we recommend first adding our code in a controlled QA/staging environment. The recommended way to handle this is to have the domain value in your Chartbeat tag set to your staging site ID (e.g. staging.mysite.com) when running on staging, and your production site ID (e.g. mysite.com) when in production.
So the production code line would be:
And the staging code would be:
This way, traffic data from your integration QA tests will stay confined in a separate test site in Chartbeat.
Note: The test Site will have to be added to your organization's Chartbeat account to test your data in this sandbox dashboard. If you run into any issues adding this sandbox site to your account, contact [email protected] and we'll get it added for you.
Check your Implementation Review
Our Implementation Review lets Admin users view data snapshots from the latest full calendar day we have on hand.
Please note that a 5-10% difference between platforms is generally expected. If data is not coming through as expected, check out common issues in troubleshooting pageviews and unique discrepancies page.
For details on general use of the dashboard please see our Implementation Review Introduction in our documentation
Locate the "Web" column as your platform of interest and row for the site
If there is a green checkmark in the corresponding cell, that means Chartbeat is receiving significant web traffic from the site at the time snapshot was taken.
Select a site and verify the timezone and snapshot date.
Summary table: reference Web pageviews breakdown to validate snapshot counts
Device breakdown by platform: Select Web as an option in the dropdown to see data on visitors viewing your site across unique device types.
Top Articles by pageviews: View the top 20 canonical paths and pageviews across all platforms
If data in the Implementation Review snapshots are as expected, your site is implemented correctly for Web. If more QA or troubleshooting is needed please continue with the additional QA steps below to assess your implementation.
Check your Real-Time Dashboard
Our Real-Time dashboard lets you see current activity on your site. If this view shows data after adding our tag to your site and loading your webpage in a browser, then your snippet is collecting data and sending it to Chartbeat as expected. This dashboard displays activity for specific pages, so if you haven’t added the snippet to all pages on your site, you can check check to see whether the snippet is sending data from the pages you have tagged.
Check the Device module in the left-hand column to ensure data is tracking for visitors viewing your site across unique device types
Use DevTools to monitor pings
You can use your browser's site inspector tools to monitor network activity from your site, filtering on "chartbeat" to view all chartbeat related scripts loading on the page, or on "ping?" to find requests to URLs beginning with ping.chartbeat.net.
Upon loading a page of your site, you should be able to view the requests here for chartbeat_mab.js (if you've included our headline testing code), chartbeat.js (or chartbeat_video.js), and the subsequent pings to our servers every 15 seconds, carrying most of the data we collect from your site.
Clicking into one of these ping requests to ping.chartbeat.net in DevTools will display a list of the included query string parameters in this call which contain data determined by the configuration variables in your code snippet. Below is a ping key that describes some of these query string fields that are important to check for in your review.
The site id, or "host" where your site's traffic data will appear in your Chartbeat account. This string is pulled from the value assigned to theconfig.domain variable in our snippet.
The page's path. This string should match your pages' canonical URL paths if your snippet sets config.useCanonical = true, or it should match the value assigned to config.path if your site makes use of our custom path variable. Sometimes this value is just the path portion of the URL, and sometimes it includes your domain name as well.
With this key, we collect the actual domain of your page, which may be different from the h-key host/site name in your Chartbeat account. If config.useCanonicalDomain is set to true in your Chartbeat code, this key should carry the domain set in your canonical URL. If that variable is not set to true, we will access the domain from document.location.
Account ID, pulled from the value assigned to config.uid in our snippet.
A comma-delimited list of sections received from the page via the config.sections variable in our snippet.
A comma-delimited list of authors received from the page via the config.authors variable in our snippet.
Page title. Only appears in the very first ping from each unique page session on your site.
Will carry the referring URL of the current pageview IF the referring page is an external site.
Will carry the referring URL of the current pageview IF the referring page is your own site.
Unique identifier for the page-session. Each unique t-key value represents a separate pageview in your Chartbeat data.
We're starting to automatically collect even more metadata about your webpage content to power our next-generation products. Review the final page of this guide to get a head start on what's next for Chartbeat.