Analytics Tracking Issues: No Title Found – Contently

Overview

This guide explains how to address issues with Contently’s analytics tracking by properly implementing the JavaScript tracker. Accurate analytics require the tracker to be installed directly on all individual story pages to ensure the system collects the correct data.

The Contently Analytics tracking code enables clients to track user engagement for their online content (“stories”). Like website tracking codes from providers such as Google Analytics and Omniture, this JavaScript tracker must be installed on all live content pages. Installing the tracking code is a prerequisite for accessing content performance data within the Contently platform.

For the system to function:

Websites must be publicly accessible via a browser (e.g., not behind a firewall).
Each story page must have a unique URL that doesn’t rely on query parameters like
?id=unique-title.

Issue

Redirects or incomplete setups, such as placing the tracker only on general landing pages, are often behind issues like "No Title Found" errors in analytics reports.

One common cause of missing analytics data is the incorrect placement of the Contently Analytics tracking code. It is essential to note that the Contently Analytics tracking code is a small JavaScript snippet that should be inserted on all content pages (not just a homepage or landing page) just above the closing </body> tag.

Solution

1. Confirm Proper Placement of the Tracking Code

The tracker must be placed directly on each page containing articles or stories. This includes all individual story pages within your site. Merely placing it on a general landing page, such as a homepage or section overview, is insufficient.

Example:

Correct: www.website.com/unique-article
Incorrect: www.website.com/homepage

2. Verify and Update the URL Properties

Ensure the property in Contently Admin matches the URLs for the individual story pages. If URLs have changed or redirect (e.g., abcd.com redirects to abcde.com), update the Contently Analytics property to reflect the final destination URL.

3. Test After Updates

After implementing the tracking code on all story pages, allow time for the data to propagate (typically 24-48 hours). Use Contently’s Admin tools to verify that the updated pages are reporting data correctly.

Special Considerations for Video Tracking

If your site includes embedded videos, Contently’s tracker can monitor video engagement. Ensure you append specific parameters to iframe src URLs for platforms like YouTube (?enablejsapi=1) and Vimeo (?api=1).

Key Insights

Improper Code Placement: Without the tracker on individual story pages, analytics will not function correctly.
URL Matching: The tracker must be configured for the exact URLs where content resides, especially if redirects are involved.
Validation: Always test after setup to ensure the tracker is collecting data.

If you have additional questions or need further assistance, contact Contently Support or refer to the Analytics Tracker FAQ.