HubDB page not tracking

Marketing & Content Hub Blog, Website & Page Publishing
1

This morning I published a new product page by adding a row to a HubDB table. When I began creating a report for web traffic to this new page, I saw that nothing was showing up (which is impossible).

There was a previous instance where this happened, and I was able to fix it by duplicating the row in HubDB and deleting the original. However, when I tried that same approach this time, it didn’t work. When I view the page details, it shows a truncated URL instead of the full page URL.

For example, if the page should be example.com/category/subcategory/page-name, the page details are showing example.com/category instead.

Has anyone experienced this issue with HubDB-generated pages not tracking properly in reports? Any suggestions on what might be causing this or how to resolve it?

2

Hi @MNold21 , yes, I’ve seen this a few times with HubDB-driven pages, and the symptoms you’re describing line up with how HubSpot resolves dynamic URLs and analytics behind the scenes.

What usually causes this is a mismatch between the HubDB row state and the page’s dynamic routing. When HubSpot can’t fully resolve the row slug to a canonical page URL, analytics falls back to the parent path, which is why you’re seeing something like example.com/category instead of the full dynamic URL. When that happens, page views technically exist, but they’re attributed to the wrong path, so your report looks empty.

This tends to happen after edits to the table schema, slug column, or page template, even if the page renders fine in the browser (Build dynamic pages using HubDB - HubSpot docs )

A few concrete things to check. First, confirm the column used as the dynamic page slug hasn’t changed type or internal name, and that the row is published. Even small changes there can break the internal mapping. Second, open the page template settings and make sure the HubDB table and slug column are still correctly selected. I’ve seen cases where duplicating or editing templates silently resets that connection. Third, check the page’s canonical URL and indexing settings in the page editor. If HubSpot thinks the page is canonicalized to a higher-level URL, analytics will follow that logic

(Understand HubSpot's traffic sources in the web traffic analysis tool )

(Analyze your site traffic with web traffic analytics )

The reason duplicating the row sometimes “fixes” it is that it forces HubSpot to regenerate the dynamic page record. When that doesn’t work, the more reliable fix is to republish the HubDB table, then republish the page template itself, not just the row. That usually forces analytics to rebind the full URL correctly.

If after that the page details still show a truncated path, I’d open a HubSpot support ticket and include the table ID, row ID, and template ID. This is one of those cases where support can see the broken mapping directly on the backend. Hope this helps you narrow it down.