Tracking and installation

Recording specific pages

Control which pages are recorded by installing the snippet selectively or using page targeting rules.

Updated Jun 19, 20262 min read

Why record specific pages

You may not need to record every page on a website. Recording specific pages helps focus analysis, reduce session usage, and avoid sensitive areas.

Common examples:

  • record marketing pages but not account pages
  • record pricing and signup pages during a campaign
  • record checkout only after privacy masking is verified
  • avoid member-only pages
  • track landing pages separately from the main site

Install the snippet only where needed

The simplest way to record specific pages is to install the UserTrail snippet only on those pages or templates.

For example, add the snippet to:

  • landing page templates
  • public marketing templates
  • product page templates
  • selected campaign pages

Do not add it to sensitive templates if those pages should never be recorded.

Use tag manager rules

If you use Google Tag Manager or another tag manager, configure triggers so UserTrail loads only on selected page paths.

Example trigger patterns:

  • page path contains /pricing
  • page path starts with /landing
  • page path equals /checkout
  • page URL contains a campaign parameter

Tag manager rules are useful when you do not want to edit website templates.

Use exclusions for sensitive pages

If the snippet is installed globally, use page exclusions or consent logic to avoid sensitive areas.

Consider excluding:

  • login pages
  • payment pages
  • account settings
  • private dashboards
  • support conversations
  • pages with personal records

Verify page targeting

After changing page targeting:

  1. Visit a page that should be recorded.
  2. Visit a page that should not be recorded.
  3. Check Sessions after processing.
  4. Confirm only intended pages appear.
  5. Check Heatmaps for the target pages.

Common mistakes

Common targeting issues include:

  • installing the snippet globally by mistake
  • tag manager triggers firing on all pages
  • testing the editor preview instead of the live page
  • forgetting mobile or alternate templates
  • route changes in single-page apps not matching expected paths

Review a few test sessions after setup to confirm the targeting behaves as expected.