Every time someone views a page, Conversion Bridge records that page view so it can build conversion journeys. Normally that small request loads all of WordPress, every plugin and your theme, only to save one row in your database. Fast page view tracking records the page view without loading all of that, which is much lighter on your server, especially on busy sites.
Where to find the setting
Go to Settings → Conversion Bridge → Options and scroll to the Performance section. Check Record page views without loading all of WordPress and save your settings.
It's off by default, and once you turn it on there's nothing else to set up.
What changes when it's on
Your visitors won't notice anything, and your reports look the same. The only difference is how much work your server does for each page view.
With the setting off, each page view goes through the same route as the rest of WordPress, so your whole site starts up in the background every time. With it on, the page view goes to a small file inside Conversion Bridge that starts only the parts of WordPress it needs: the database and your settings. It then saves the page view using the exact same code as before, with the same privacy rules. For example, ad click IDs like gclid are still only saved when the visitor has allowed marketing cookiesA small piece of data stored in a user’s browser that helps websites remember user activity, preferences, or sessions across visits..
If you get a lot of traffic, or you're on a host that limits how much your site can run at once, this can make a real difference.
What still works the normal way
Only the automatic page view uses the fast route. Everything else stays exactly as it was:
- Conversions like form entries, purchases and signups always go through the normal route, because they need your other plugins and your ad platform connections.
- Server-side sends to ad platforms are unchanged.
- Your cookie banner is respected the same way as before.
When Conversion Bridge doesn't use it
Even with the setting checked, Conversion Bridge sends page views the normal way when the fast route can't handle them the same way. That happens when:
- Track Conversion Journeys is off and no platform needs page views. In that case Conversion Bridge doesn't send a page view request at all, so there's nothing to speed up.
- An ad platform sends page views from your server. Meta, Pinterest, Snapchat and OpenAI Ads can send page views server-side, and that needs the normal route.
- Server logging is on. While you're debugging, page views take the normal route so every one of them shows up in the log.
- Another plugin changes Conversion Bridge's tracking. Some plugins hook into how Conversion Bridge records events. Those hooks only run on the normal route, so Conversion Bridge keeps using it.
- Your site is a multisite network. Fast page view tracking isn't available on multisite.
When one of these applies, the Performance section shows Not in use with the reason, so you always know which route your page views are taking.
If your host blocks it
Some hosts and security plugins block files inside the plugins folder from being opened directly. WP Engine does this, and some Wordfence setups do too. If that happens, Conversion Bridge notices right away, sends that page view the normal way, and keeps using the normal way for the rest of the visit. You don't lose any page views, you only miss out on the speed boost.
The Performance section also tells you when this happens, with a message that your host blocks it and that page views are being recorded the normal way. If you'd like to use fast page view tracking on a host like that, ask your host whether they can allow requests to wp-content/plugins/conversion-bridge/track-pageview.php.
Frequently Asked Questions
Will I lose any data by turning this on?
No, page views are saved by the same code with the same rules, and if the fast route doesn't work on your host, Conversion Bridge falls back to the normal one on its own.
Does this make my pages load faster for visitors?
Not directly, because the page view is sent in the background and visitors don't wait on it either way. What it saves is work on your server, which helps your whole site stay quick when traffic is high.
Do I need this on a small site?
You don't have to turn it on, but it doesn't hurt. The savings grow with your traffic, so busy sites and sites on smaller hosting plans get the most out of it.