← Back
PixelYourSite Professional / General Settings / PixelYourSite Global Settings

PixelYourSite Global Settings

Last updated: February 12, 2026

These settings affect tracking across your whole site: how PixelYourSite stores IDs, handles AJAX/caching, detects user data, attributes reports, and excludes traffic.

External IDs

Use external_id

Creates/stores an external_id value (saved in a cookie called pbid). This helps identify users more reliably across events.

Use transient WP for storage external_id

Stores external_id temporarily in the WordPress database (transients). Useful when cookies are unreliable or you need a short-lived server-side backup.

external_id expire days for cookie

How long the pbid cookie is kept (example shown: 180 days).

Recommendation: keep external_id enabled if you use server-side tracking (CAPI) or want better matching.

Ajax options

Use Ajax when API is enabled, or when external_id’s are used

Keeps event sending stable on cached sites and helps:

  • generate unique event_id values (important for deduplication)
  • ensure external_id is available
  • reduce issues caused by aggressive caching

Recommendation: keep ON if you use any caching plugin/CDN.

Use Ajax for Static events

Sends AJAX requests for events that fire on page load (static events). Helps when the page loads before other scripts finish or when caching interferes.

Use navigator.sendBeacon instead of jQuery.ajax

Uses the browser’s sendBeacon API to deliver events more reliably in the background (especially when the user leaves the page). Falls back to AJAX if not supported.

Recommendation: keep ON (best reliability + performance).

Disable PHP session

Disable PHP sessions

Stops PixelYourSite from creating the PHPSESSID cookie. Can help if sessions/caching conflict, but may reduce accuracy for session-based data (landing page, traffic source, UTMs).

Recommendation: leave OFF unless you’re troubleshooting a session/caching conflict.

Advanced user-data detections

These settings help PixelYourSite detect user fields from forms and URLs to improve matching (email, first/last name, phone).

Forms (field name mapping)

You can list possible field names for:

  • Fn (first name)
  • Ln (last name)
  • Tel (phone)
  • Eml (email)

PixelYourSite uses these to detect and capture user data even when forms use custom field names.

Tip: only add names you actually use to avoid wrong matches.

URL parameters (mapping)

Lets you pull user data from URL parameters (example: [url_utm_term] style placeholders shown in UI).
Useful when you prefill forms from links (email campaigns, funnels, affiliates).

Data persistency

  • Keep the data in the browser for as long as possible (default / best for attribution)
  • Use the most recent data (overwrites older source/UTM info with the latest visit)

Recommendation: keep “as long as possible” if you care about first-touch attribution and long buying cycles.

Reports attribution

Controls how PixelYourSite reports attribute events to sources/UTMs.

First Visit Options

How long to keep “first visit” cookies (example: 60 days).

Last Visit Options

How long to keep “last visit” cookies (example: 60 min).

Attribution model for events parameters

Choose which model is used when attaching source/UTM parameters to events:

  • First Visit
  • Last Visit

Recommendation:

  • Use First Visit if you care about the original acquisition source.
  • Use Last Visit if you optimize around the most recent click/source.

Disable the plugin (exclude traffic)

Disable the plugin for known web crawlers

Stops tracking for bots/crawlers (recommended).

Disable the plugin for these IP addresses

Exclude specific IPs (office, developers, agencies).

Ignore these user roles from tracking

Exclude logged-in roles (admins, shop managers, editors) to keep data clean.

User role permissions

Controls which WP roles are allowed to access/see PixelYourSite plugin settings (example shown: Administrator).

Remove parameters

These options remove URL-like parameters from events to reduce privacy risk.

  • Remove URL parameters from event_source_url
    Recommended ON (helps avoid sending private info in URLs; also required for some CAPI setups).
  • Remove target_url parameters
  • Remove download_url parameters

Recommendation: keep the first one ON by default.

Caches

If you use caching/minification/delay JS features, you may need to exclude PixelYourSite scripts from optimization. The box shows example file paths to exclude (useful for WP Rocket, Autoptimize, LiteSpeed, etc.).

Other stuff

Debugging Mode

Adds extra info to your browser console to help troubleshoot events.

Compress frontend js

Compresses PixelYourSite frontend JS. Can conflict with some cache/minify tools.

Remove the name of the plugin from the console

Hides plugin mentions in console logs (cosmetic/privacy).

Track domains and subdomains together

Unifies tracking across subdomains (useful if you run the same site across www + non-www, or multiple subdomains and want unified source/UTM tracking).

Recommendation: enable only if you really track across subdomains and they’re part of the same user journey.