Integration QA Steps: AMP
Steps to QA your integration of Chartbeat code on AMP pages.
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
To access your Implementation Review:
Sign in to your Chartbeat account.
Navigate to Settings from the menu top right-head
Implementation Review pages on the left side menu
Navigate to the Platform Audit and Traffic Audit Tabs
Tip: If you cannot access the Implementation Review, verify with your organization if your account has the required Admin role.
Once you're able to access the dashboard, here are some useful QA steps to ensure proper tracking:
Platform Audit
Navigate to the Platform Audit Tab to view the Implementation Summary Table
Locate the "AMP" column and corresponding cell for the site and platform of interest
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.
Traffic Audit
Select a site and verify the timezone and snapshot date.
Summary table: reference Web pageviews breakdown to validate snapshot counts
Device breakdown by platform: section selects "AMP" 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 corresponding pageviews across all platforms
If data in the Implementation Review snapshots are as expected, your site is implemented correctly for AMP. If more QA or troubleshooting is needed please continue with the additional QA steps below to assess your implementation.
Check your Real-Time Dashboard
Upon a successful Chartbeat integration with your AMP pages, a new AMP filter will appear in the left-hand side of your Real-Time Dashboard (screenshot below).
Select the AMP filter in your Real-Time Dashboard to perform the following data QA checks:
Under 'Top Pages':
Page titles are populating as expected
Hover over page titles in this list to view the canonical paths received from these pages. Alternatively, click into the article view and right-click the title to copy the link address
Check for duplicate page entries in this list, and identify the discrepant paths being received from these pages to determine the fix in your configuration settings
Open the section & author drop-down filters to ensure section & author data is populating as expected
Tip: Once again, the page property metadata (sections, authors, path, title, and content type) configured to send from your AMP pages should match exactly the data we receive from those same pages on your non-AMP website via our standard JavaScript tag, and stay consistent across all of your other Chartbeat tracked platforms. Check to ensure the page data being sent from your AMP pages to Chartbeat aligns precisely with the data we receive from those same pages across your other Chartbeat-tracked platforms.
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.
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 QSP fields that are important to check for in your review.
QSP/Key
Description
h
The site, or "host" where your site's traffic data will appear in your Chartbeat account. This string is pulled from the value assigned to the domain variable in our AMP code block.
p
The page's path. This string should match your page's canonical URL path, or whatever you're passing into the canonicalPath variable in your AMP code block.
d
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.
g
Account ID, pulled from the value assigned to the uid variable our AMP snippet.
g0
A comma-delimited list of sections received from the page via the sections variable in our snippet.
g1
A comma-delimited list of authors received from the page via the authors variable in our AMP snippet.
i
Page title. Only appears in the very first ping from each unique page session on your site.
r
Will carry the referring URL of the current pageview if the referrer value is an external site.
t
Unique identifier for the page-session. Each unique t-key value represents a separate pageview in your Chartbeat data.
Limitations
Because Google restricts the use of JavaScript in its supported AMP partners' analytics scripts, we are currently unable to measure Visitor Frequency for your AMP page visitors. All AMP page visitors will be tracked as "Unclassified" users under the Visitor Frequency metric in your Chartbeat tools. The restricted use of JavaScript also means that AMP pages using infinite scroll are not compatible with Chartbeat's AMP code at this time.
Chartbeat video tracking for AMP pages is also unsupported at this time, as well as user subscriber status tracking.
Up next
Choose your next integration.
Google AMP Tracking✅
Last updated
