DialPerPage
Assign replacement phone numbers to specific pages without editing themes, templates, or content.
Use with caution
DialPerPage works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.
- Tested with the latest WordPress (7.1)
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where DialPerPage stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| call tracking | >100 |
| dynamic number insertion | #43 |
| landing pages | >100 |
| phone | >100 |
| telephone | >100 |
About DialPerPage
From the official readme · v1.1.1Description
DialPerPage replaces one configured source phone number with page-specific numbers on exact WordPress URLs.
Replacement runs on the final HTML response, so the plugin can update shared headers and footers, page-builder output, modal windows, visible text, tel: links, WhatsApp links, and phones whose characters are split across nested HTML elements.
Only the configured source number is changed. Other numbers and pages remain untouched.
Features
- Assign a different replacement number to each page.
- Accept full URLs or relative paths.
- Update visible numbers,
tel:links, and phone-based messenger URLs. - Preserve the original phone mask, including spaces, non-breaking spaces, parentheses, dots, and hyphens.
- Handle phone digits split across nested
spanorsmallelements. - Search, validate, add, and remove rules from a responsive settings screen.
- Support international phone numbers containing 10 to 15 digits.
- Follow the standard WordPress locale and WordPress.org language-pack system.
- Make no changes to post content, theme files, or templates.
- Purge supported page caches after activation, upgrades, and settings changes.
- Restore managed phone links if a call-tracking script changes them in the browser.
- Send no data to external services and include no tracking.
Performance
The plugin resolves the current request path with an exact array lookup. Output buffering, HTML processing, and the small browser guard start only when that path has a valid replacement rule. AJAX, REST, JSON, feeds, cron, WP-CLI, XML-RPC, robots, favicon, HEAD, and non-HTML responses are skipped.
Admin CSS and JavaScript load only on the plugin settings screen. Settings and the active rule are cached for the current request.
Privacy
DialPerPage does not collect, transmit, or share personal data. It makes no external requests and stores only its configuration in the WordPress options table.
Installation
- In WordPress, open Plugins > Add New Plugin > Upload Plugin.
- Upload
dialperpage.zip, install it, and activate DialPerPage. - Open Settings > DialPerPage.
- Enter the source phone currently displayed on the site.
- Add a page URL or path and its replacement phone.
- Save the settings. DialPerPage clears supported WordPress page caches automatically; clear any hosting or CDN cache that is managed outside WordPress.
Frequently asked questions
Does the plugin modify content in the database?
No. Replacement is applied to the final HTML response. Posts, page-builder data, theme files, and templates are not changed.
Does it run on pages without a rule?
The plugin performs one exact path lookup. When no rule matches, output buffering does not start and the HTML is not scanned or copied.
Will unrelated phone numbers be replaced?
No. Only the configured source phone is matched. For 11-digit Russian phones, 7 and 8 prefixes are treated as equivalent.
Is the original phone format preserved?
Yes, when source and replacement numbers contain the same number of digits. Only digits change; separators and HTML spacing entities remain in place. Compact tel: values remain compact.
Does it support phones split into many HTML tags?
Yes. Inside a matching tel: link, the plugin can replace digits distributed across nested span and small elements while retaining their tags, styles, classes, and microdata.
Can I use a full URL?
Yes. Both https://example.com/service/ and /service/ are accepted. Query parameters are ignored, and matching uses the normalized path.
Why is the old phone still visible?
Saving settings automatically purges Hyper Cache, WP Super Cache, WP Rocket, W3 Total Cache, Cache Enabler, and LiteSpeed Cache when their public purge APIs are available. After updating from an earlier DialPerPage release, clear any remaining hosting or CDN cache once. Then test the page in a private browser window and confirm that the saved path exactly matches the page path.
What if a call-tracking script changes the number after the page loads?
On pages with an active rule, DialPerPage marks managed tel: links and loads a lightweight browser guard in the document head. If a third-party script such as a dynamic call-tracking service changes a marked link later, the guard restores its configured number before interaction. Unmanaged links and pages without rules are not observed.
How are translations handled?
DialPerPage follows the current WordPress locale. Community translations are managed and delivered through the standard WordPress.org language-pack system.
Changelog
1.1.1
- Moved plugin translations to the standard WordPress.org language-pack system.
- Removed the plugin-specific language selector so the interface follows the WordPress locale.
1.1
- Added automatic cache purging after activation, upgrades, and settings changes.
- Added an active-page-only browser guard for phone links changed by third-party scripts.
- Ensured page caches receive the already-replaced HTML response.
1.0
- Initial public release.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best DialPerPage alternatives
All call tracking plugins →
FAQ
DialPerPage: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 4, 2026
Is DialPerPage free?
Yes. DialPerPage is free to download and use from the official WordPress.org plugin directory.
Is DialPerPage safe to use in 2026?
DialPerPage works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.
How many websites use DialPerPage?
DialPerPage is active on <10 WordPress websites and has been downloaded 130 times since it launched in August 2026. It was downloaded 66 times in the last 30 days.
Does DialPerPage work with WordPress 7.1?
Yes. The developer has tested DialPerPage up to WordPress 7.1.2, the latest release. It requires WordPress 6.0 or newer.
What PHP version does DialPerPage need?
DialPerPage requires PHP 8.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was DialPerPage last updated?
The latest version, 1.1.1, was released on August 25, 2026 (1 month ago).
Who makes DialPerPage?
DialPerPage is developed and maintained by codeverse.
What are the best alternatives to DialPerPage?
The most popular alternatives to DialPerPage are CallRail Phone Call Tracking (10K+ installs), WhatConverts (7K+ installs) and CallTrackingMetrics (3K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
