---
title: 'CallRail: Static vs Dynamic Number Strategy'
type: article
created: '2026-02-24'
updated: '2026-02-24'
source_docs:
- raw/2026-02-24-weekly-call-w-sebastian-124924068.md
tags:
- callrail
- call-tracking
- client-communication
layer: 2
client_source: null
industry_context: null
transferable: true
---

# CallRail: Static vs Dynamic Number Strategy

## Overview

When implementing CallRail for a client, there are two primary approaches to number assignment: **static numbers** (fixed tracking numbers assigned to specific channels or campaigns) and **dynamic number insertion (DNI)** (numbers that swap on the page based on the visitor's traffic source). The choice between them has real implications for customer experience and client trust.

## Recommendation

**Start with static numbers.** Unless there is a specific, pressing need for session-level attribution via DNI, begin with static tracking numbers and introduce dynamic swapping only after the client is comfortable with the setup.

## Rationale

Dynamic number insertion can confuse or alarm customers in certain contexts:

- Customers who have previously called or saved a number may see a different number on return visits, creating distrust.
- Some clients and their customers have a strong preference for a single, consistent phone number that represents the business.
- The attribution benefit of DNI may not outweigh the friction it introduces, particularly for local service businesses where phone trust is high.

Static numbers still provide meaningful tracking — you can assign unique numbers per channel (e.g., one for Google Ads, one for organic, one for a print ad) without any on-page swapping behavior.

## When to Revisit DNI

Dynamic numbers become more valuable when:

- The client has high call volume and needs granular session-level source attribution.
- The client's audience is less likely to notice or be bothered by number changes (e.g., transactional, high-frequency service categories).
- You need to tie specific calls back to individual ad clicks for conversion reporting in Google Ads or GA4.

## Client Context

This guidance was applied to [[wiki/clients/cordwainer/index|Cordwainer]], where the decision was made to start with static CallRail numbers to avoid potential confusion among their senior care audience — a demographic particularly likely to notice and be unsettled by a changing phone number.

## Related

- [[wiki/clients/cordwainer/index|Cordwainer Client Overview]]
- [[wiki/knowledge/google-ads/optimization-score-below-80.md|Google Ads Optimization Score]]