Frequently Asked Questions
Q: Does this plugin work without WooCommerce?
A: Yes, partially. The traffic attribution tracker, admin dashboard, campaign manager, and all settings work on any WordPress site. WooCommerce is only needed to use the Bulk URL Tagger’s product and category URL fetcher. You can still use the tagger to tag pages and posts on a non-WooCommerce site.
Q: Is this GDPR-compliant?
A: The plugin does not store any personally identifiable information. Visitors are identified by an anonymous SHA-256 hash derived from their IP address and User Agent string — the raw IP is never saved to the database. No data is sent to external servers. You should still mention the use of attribution cookies in your privacy policy. For stricter requirements, you can disable tracking until the user consents by toggling the Enable Tracker setting off and enabling it conditionally via a consent management platform.
Q: What is the difference between a visit and a unique visitor?
A: A visit is every individual page load that is tracked. A unique visitor is a distinct visitor hash — a visitor who lands on five pages in one session counts as one unique visitor but five visits. New visitors are those whose hash has never appeared in the visits table before that visit.
Q: How does the first-touch vs. last-touch attribution work?
A: The frontend tracker stores two cookies: one for the first source the visitor ever arrived from (first touch), and one for the most recent source (last touch). The visit log records the last-touch attribution, which is the standard used by most ad platforms. The cookie duration setting controls how long both cookies remain active.
Q: Can I track visits across subdomains?
A: Yes, with a Pro license. Set the Cookie Domain to .yourdomain.com (with the leading dot) in Settings → Tracking. This shares the attribution cookie across all subdomains so a visitor who discovers you via blog.example.com and purchases on shop.example.com is attributed to the same original source.
Q: Why are some visits not appearing in the dashboard?
A: The most common causes are: the visitor is logged in as an admin or editor (excluded by default), the visitor is a known bot, the IP is in the excluded list, or the visit was rate-limited. Enable Debug Mode in Settings → Tracking, open your browser’s developer console, and reload the page — the tracker will print what it detected. Also check that your page caching plugin is not caching the REST API responses.
Q: My form emails are not showing attribution data. What should I check?
A: Form attribution requires a Business license and the Form Attribution setting to be enabled. The supported form plugins must also be active. The attribution data is injected via JavaScript, so if the form page is loading without JavaScript executing (e.g., due to a JavaScript error), the hidden fields won’t be injected. Open the browser console on the page with your form and look for any errors.
Q: How do I exclude my own traffic?
A: Go to Settings → Privacy & Filtering and either enable Exclude Admins & Editors (if you browse the site logged in) or add your IP address to the Excluded IP Addresses list using the Add to list button next to your current IP. Both require a Pro license for the IP exclusion; admin exclusion is available on all plans.
Q: The data retention setting is locked to 30 days. How do I change it?
A: Data retention control beyond 30 days requires a Pro license. On the free plan, records older than 30 days are automatically removed daily to keep your database manageable. Upgrade to Pro to retain data for 60 days, 90 days, 6 months, 1 year, or forever.