BluePoint ATM — CallRail WordPress Plugin

Overview

During a December 2025 working session, the Asymmetric team installed the CallRail WordPress plugin on the BluePoint ATM website. The plugin handles tracking script injection automatically, eliminating the need to manually embed a JavaScript snippet in the theme or tag manager.

This approach is the preferred method for WordPress sites: install once, and CallRail's dynamic number insertion (DNI) script is present on every page without touching template code.

Installation

The plugin was installed directly from the WordPress plugin directory during the live session:

Navigate to Plugins → Add New in the WordPress admin
Search for CallRail
Install and activate the official CallRail plugin
The plugin automatically injects the CallRail tracking script sitewide

No API key or manual configuration was required at the plugin level — the script is tied to the CallRail account via the plugin's internal connection.

Note: Because the plugin handles script injection, the "Add JavaScript Snippet" step inside CallRail's number setup wizard can be skipped. Mark confirmed this during setup: "You don't have to add the JavaScript. Because we put the plug-in on already."

What the Plugin Enables

Once active, the plugin supports:

Dynamic Number Insertion (DNI): CallRail scans the page for a configured "swap target" number and replaces it with a tracking number from the pool, keyed to the visitor's session and traffic source.
Static number tracking: Numbers placed directly on the site (footer, office lines) can be replaced with CallRail static numbers that forward to the original destinations while logging and recording calls.
GA4 and HubSpot event firing: The script enables CallRail to send call events to connected integrations.

Known Issue — Dynamic Swap Not Firing

After installation and number pool configuration, the dynamic number swap was not functioning by end of session. The swap target (720-987-5711, Mike Stebbins' main number in the homepage banner) was configured correctly in CallRail, but visiting the site in an incognito window showed the original number rather than a pool number.

Status: Open. Assigned to Mark Hope for troubleshooting.

Possible causes to investigate:
- Page caching serving a cached version without the script executing
- Elementor rendering the number in a way that DNI cannot target (e.g., inside an image or non-standard HTML element)
- Script load order or conflict with another plugin

See ^[1] for full session context.

The plugin underpins all CallRail number tracking on the BPATM site. For the full number architecture configured during this session, see:

^[1] — session overview, decisions, and open action items
^[2] — general DNI concepts and troubleshooting
^[3] — HubSpot contact creation from call events

References

Client: ^[4]
Meeting: ^[1]
Owner: Mark Hope (troubleshooting DNI swap)