Traffic Optimizer for visitor tracking
Control which visitors enter live tracking during high traffic and understand why browsing history may be incomplete.
What it is
Traffic Optimizer applies additional admission criteria when a website reaches its configured live visitor threshold. Domain and IP checks also determine which traffic INSIDE accepts. A separate overload safeguard can reduce browsing-history writes during very high page-view activity.
Who uses it and why
Administrators ask Powerfront to tune tracking for busy websites. Developers check that their integration uses the correct website account and allowed page domains.
Where to find it
Powerfront manages Settings › General Settings › Traffic Optimizer and the related admission controls in Settings › General Settings › Admin. Ask Powerfront to change these for you.
How it works
Normal web tracking checks that the website account is available and started, the originating page is allowed and the visitor's IP is not excluded. Maintenance can also stop tracking admission.
The optimiser applies when it is enabled, Optimal Limit is greater than zero and the live web and WeChat mini-program visitor count reaches that limit. It supplies additional traffic conditions and page or time locks. Visitors already online bypass this optimiser in the normal configuration flow. First-party cookie capability is required by that flow while optimisation applies.
Traffic conditions must pass together. An active optimiser with no conditions does not admit new traffic through the browser's condition check.
INSIDE also checks selected Google, Yahoo and Bing crawler identities against network address information. This is limited crawler recognition, not comprehensive bot exclusion.
Separately, Powerfront can configure page-history overload protection. When the applicable rate thresholds are exceeded, some page views may not be written to history. Visitors with an active chat bypass that particular history check.
Configure it
Ask Powerfront to review Enabled, Optimal Limit, traffic conditions, Page Lock and Time Lock (mins) together. Enabling the optimiser with a zero limit does not activate it.
For missing traffic after a website change, ask Powerfront to check Whitelist Domains, Check White List Domains and Visitor IP Blacklist. Include the affected page and time of the test.
Settings
| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Enabled | Settings › General Settings › Traffic Optimizer | website | Off | Powerfront | Enables traffic optimisation once a positive visitor limit is reached. |
| Optimal Limit | Settings › General Settings › Traffic Optimizer | website | 0 visitors; optimisation inactive | Powerfront | Sets the visitor threshold at which traffic optimisation applies; zero does not activate it. |
| Page Lock | Settings › General Settings › Traffic Optimizer | website | 0 page views; no page lock | Powerfront | Sets the page-view lock used to delay further tracking attempts for restricted traffic. |
| Time Lock (mins) | Settings › General Settings › Traffic Optimizer | website | 0 minutes; no time lock | Powerfront | Sets the time lock in minutes used to delay further tracking attempts for restricted traffic. |
| Check White List Domains | Settings › General Settings › Admin | website | Off | Powerfront | Controls checking of the configured allowed website domains. |
| Whitelist Domains | Settings › General Settings › Admin | website | Not set: no domain restriction | Powerfront | Lists the page and origin domains allowed by website admission checks. |
| Visitor IP Blacklist | Settings › General Settings › Admin | website | Off | Powerfront | Enables the configured visitor IP exclusions. |
Limits and good to know
- Live visitor counts need not match website analytics that use different admission rules.
- Admission limits and history-write protection are separate controls.
- A visitor can continue through live processing even when an overloaded history write is omitted.
- Search crawler recognition does not establish that all automated traffic is identified or blocked.
- Cookie restrictions and old unsupported browser behaviour can also prevent normal tracking.
Depends on and works with
View all connections as a list
This feature uses
- Website accounts · managed by PowerfrontRequires
Tracking admission needs an available, active website account.
- Admin settings and feature switches · managed by PowerfrontConfigured by
Powerfront manages domain and visitor IP admission settings.
- Starting, ending and expiring chatsEnhances
Visitors with an active conversation bypass the reviewed page-history overload check.
- Website domain checks for browser requestsConfigured by
Website origin and page-domain checks are part of tracking admission.
- Visitor activity and availabilityEnhances
Visitors already online bypass the active optimiser in the normal tracking configuration flow.
Used by
- Visitor page and product trackingConfigured by
Tracking admission and load limits can affect accepted activity and recorded history.
- Visitor browsing and activity historyConfigured by
Tracking admission and overload protection affect which page views reach history.
FAQ and troubleshooting
Why did a newly added domain stop showing visitors?
Ask Powerfront to check the allowed domains for both the page and its origin.
Why are existing visitors still connected during a busy period?
The normal configuration flow exempts sessions that are already online from the active optimiser.
Why is a page missing from browsing history?
Check admission, the website integration and retention. During overload, history-write protection can also omit page entries.
Does Traffic Optimizer block every bot?
No. The reviewed crawler recognition covers selected search crawlers and does not provide a general bot-blocking guarantee.