Context

When using website visitor reveal functionality, you may want to exclude certain website paths (like career pages or other non-intent pages) from consuming reveal credits. This helps optimize credit usage by focusing on visitors showing genuine buying intent.

Answer

Yes, you can control which pages trigger visitor reveals by selectively implementing the website tracking tag. Instead of adding the tracking code to your entire website, you can choose to add it only to specific pages where you want to identify visitors.

Temporarily Pausing All Reveals: If you need to temporarily pause all visitor reveals without removing tracking code, you can toggle Unify Reveal off:

1. Go to Settings → Web & Product Data → Settings

2. Toggle “Unify Reveal” off

This will pause credit usage while keeping your tracking implementation in place. Toggle it back on when you're ready to resume reveals.

To implement selective tracking:

Alternative Credit Optimization Strategies:

Beyond selective page tracking, you can also optimize credit usage through:

• External API Integration: Connect your Clearbit or 6Sense API keys to de-anonymize website traffic without using Unify credits. Unify Intent (0.1 credit per visitor) will only be consumed if these external services fail to identify the visitor.

• ICP-Focused Filtering: Use Unify's built-in filters to focus on qualified companies based on attributes like company size, employee count, and industry type.

• Dynamic Audiences: Set up audiences that automatically filter website visitors based on your ICP criteria, such as page views, employee count, or account ownership.

1. Identify the pages where you want to track and reveal visitors

2. Remove the website tracking tag from your global header/footer if present

3. Add the tracking tag only to the specific pages you want to monitor

4. Consider also removing the tag from product/app pages and customer login areas to avoid consuming credits on existing customer sessions

Important: Credits are consumed per identified visitor session, not per unique person. This means:

The same visitor returning multiple times will consume 0.1 credits for each sessionCurrent customers logging into your product/app will consume credits on each login if the tracking tag is presentMany teams remove the tracking tag from product, app, and login pages to avoid paying for active customer sessionsFocus the tag on high-intent marketing pages (pricing, product info, demo requests, etc.) where identifying visitors provides the most valueYou can monitor your credit consumption through the Usage Dashboard in your account settings. Consider combining selective page tracking with ICP filtering and external API integration for maximum credit efficiency.