# Implement Tracking

- [Standard Websites](https://docs.chartbeat.com/cbp/tracking/standard-websites.md): A guide to integrating Chartbeat tracking for your website.
- [Adding chartbeat.js to Your Site](https://docs.chartbeat.com/cbp/tracking/standard-websites/our-javascript.md): An introduction to our analytics code snippet for standard web tracking.
- [Customize Tracking Settings](https://docs.chartbeat.com/cbp/tracking/standard-websites/configuration-variables.md): Use our JavaScript configuration variables to fine-tune your pageview tracking and send key page properties to Chartbeat.
- [Tracking Virtual Page Change](https://docs.chartbeat.com/cbp/tracking/standard-websites/single-page-apps.md): This article covers using our virtualPage function to track virtual page change on your site. This implementation is only required for sites that use virtual page changes.
- [User Subscriber Status](https://docs.chartbeat.com/cbp/tracking/standard-websites/subscriber-engagement.md): 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.
- [Alternative Site Integrations](https://docs.chartbeat.com/cbp/tracking/standard-websites/alternative-integrations-web.md): This page details alternative options for implementing our tracking snippet to better fit your site's existing model for loading third-party JavaScript.
- [Integration QA Steps: Website](https://docs.chartbeat.com/cbp/tracking/standard-websites/qa-web-integration.md): Steps to check that your website integration is working as expected.
- [Additional Page Metadata](https://docs.chartbeat.com/cbp/tracking/standard-websites/additional-page-metadata.md): Learn how we're beginning to collect metadata about your content to power our next generation products, and get a head start by configuring this metadata in your page HTML.
- [Google AMP](https://docs.chartbeat.com/cbp/tracking/google-amp.md): A guide to integrating Chartbeat tracking for your Accelerated Mobile Pages.
- [Chartbeat Code for AMP](https://docs.chartbeat.com/cbp/tracking/google-amp/amp-code.md): Instructions to add Chartbeat code to your AMP pages.
- [AMP Configuration Variables](https://docs.chartbeat.com/cbp/tracking/google-amp/amp-configuration-variables.md): Available Chartbeat configurations to be passed into your AMP implementation code.
- [Alternative AMP Integration](https://docs.chartbeat.com/cbp/tracking/google-amp/alternative-amp-integration.md): Alternative options for integrating our code on your AMP pages.
- [Integration QA Steps: AMP](https://docs.chartbeat.com/cbp/tracking/google-amp/qa-amp-integration.md): Steps to QA your integration of Chartbeat code on AMP pages.
- [Mobile App SDKs](https://docs.chartbeat.com/cbp/tracking/mobile-app-sdks.md): A guide to integrating Chartbeat tracking for your native mobile applications for iOS and Android smartphones and tablets.
- [Intro to Mobile App Tracking](https://docs.chartbeat.com/cbp/tracking/mobile-app-sdks/mobile-sdks-intro.md): Review the information in this article before getting started with our integration for native mobile applications. Note that this is an add-on feature, not included in all Chartbeat service plans.
- [Android SDK](https://docs.chartbeat.com/cbp/tracking/mobile-app-sdks/android-sdk.md): Instructions to integrate Chartbeat's Android SDK to your native app.
- [iOS SDK](https://docs.chartbeat.com/cbp/tracking/mobile-app-sdks/ios-sdk.md): Instructions to integrate Chartbeat's iOS SDK to your native app.
- [Integration QA Steps: Mobile Apps](https://docs.chartbeat.com/cbp/tracking/mobile-app-sdks/qa-mobile-sdk-integration.md): Recommended steps to test your mobile app integration for accuracy.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.chartbeat.com/cbp/tracking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.