Changelog
The plugin was renamed from Brainrune Pixel Manager to Brainrune Pixel Tracking, and its Pro add-on from Brainrune Tracking Pro to Brainrune Pixel Tracking Pro. The versions below cover both names.
Brainrune Pixel Tracking
Section titled “Brainrune Pixel Tracking”- Server events: filter the list by event, destination and status, and show only orders that came from an ad.
- Server events: a Source column on order rows (Google Ads, Meta Ads, organic, direct), read from the click ID, then the stored source and medium, then WooCommerce attribution.
- Fix: the links and the Retry redirect on the server events screen opened the Dashboard.
Security pass on the public endpoints.
- Events from the browser bridge are queued and answered at once, instead of being sent inside the visitor’s request. With the queue off they are sent inline with a four-second timeout.
- The rate limiter counts IPv6 senders per /64, keeps a cap per visitor session, and keeps separate site-wide limits for standard and custom events so one cannot starve the other.
- A custom event never carries the value the browser reports. It carries the value on its definition, under the new Highest value a custom event may carry setting on the Server tab, or none.
- Funnel values are priced for at most twenty units.
- Staff opening an order-received page no longer fire or acknowledge the purchase.
- New: Hold the purchase for unpaid orders until they are completed on the WooCommerce tab. On for new installs, off after an update until the shop turns it on.
- Shop managers see the screens read-only.
- Uninstalling also drops the delivery state and, when data removal is authorised, the plugin’s order meta.
The free plugin on its own. Server delivery for TikTok, GA4, Pinterest, Snapchat and Reddit, additional tags, custom events and the form plugin triggers, the six funnel events beyond the core five, customer value and cohorts, the sources report and the offline export moved to Brainrune Pixel Tracking Pro.
- New: Umami. Cookieless, loaded from the shop’s own Umami server, without waiting for consent unless you ask for it.
- Settings stay in one place. Saving while Pro is off keeps every setting Pro stored.
- The page address sent with page views and funnel events no longer carries the order key or the thank-you page’s order parameters, and is built on the site URL.
- A background run sends only the rows it claimed, so two runs never send the same rows.
- When Brainrune Cookie Consent is off and its cookie is read directly, a choice made under an older policy version counts as no choice.
- An order-received URL with a wrong key is no longer written to the log.
Two security audits, applied in full.
- A custom event can no longer read a password, card or hidden field, nor anything inside a login, checkout or payment form. Only an administrator can change what leaves the site.
- The funnel bridges add up duplicated products, use the shop’s currency and cap every value at the catalogue price. The rate limit counts per IP first, per minute.
- A purchase is checked against the order status again before it is sent. A sent row cannot be sent twice from the retry button, and one row that fails no longer stops the run.
- The attribution cookie waits for marketing consent. The offline export takes only orders with recorded consent. Settings changes have a log of their own.
- WordPress’s privacy tools export and erase what the plugin keeps on orders.
- Credentials are removed on uninstall even when the data is kept.
- The server queue moved into a table of its own. It retries with a growing delay of one minute to twelve hours, stops after the configured number of attempts, and drops sent rows after a week and failed ones after a month.
- New Server events screen: what is waiting, what was delivered and what failed, with the HTTP code, the attempt count and a retry button. Tokens never reach that screen.
- Google Ads enhanced conversions. The hashing happens on the server, so the browser never sees the plain email or phone number.
- Seven platforms added: Microsoft Ads, Pinterest, Snapchat, Reddit, Microsoft Clarity, LinkedIn and OpenAI Ads.
- OpenAI follows its own rules: money in minor units, a closed list of event names, and no phone or name fields.
- The cookie banner moved out into Brainrune Cookie Consent, a plugin of its own. On activation it takes over the banner settings this plugin held.
- Tags ask a chain of consent sources in order: Brainrune Cookie Consent, the WP Consent API, then the cookie left by Cookiebot, CookieYes, Borlabs or Complianz. When nobody answers, the Consent tab decides whether to load or hold; it holds by default. The tab shows which source answered.
- Applying consent to server events and advanced matching moved to the server section, with the same meaning.
- The guided setup no longer stops with a fatal error.
- The tooltip recommendations are in English, like the rest of the screens.
First release.
Brainrune Pixel Tracking Pro
Section titled “Brainrune Pixel Tracking Pro”- A Cookie Consent Pro key turns on the Cookie Consent Pro features only. A Pixel Tracking Pro key turns on both. Keys issued before this keep turning on everything.
- Cookie Consent Pro starts with only the free Cookie Consent installed. Pixel Tracking is needed only for the Pixel Tracking Pro features.
- Cookie scan: browsers of logged-in staff are no longer collected.
- Updates are verified before they are installed: each release is signed and the plugin checks the signature and the checksum of the zip. A package from any other host, or over plain http, is refused.
- The licence is signed for this site; a licence written into the database by hand counts as no licence.
- Consent: blocking, the consent log, regions and automatic scans keep running with the saved settings when the licence is off. Only the Pro tabs wait for it. The admin sees a notice and gets one email when the licence goes off.
Cookie Consent Pro features: automatic blocking of 45 known services, regions, WPML and Polylang texts, an A/B test of two banners, the cost of refusals, the cookie scan as a tab with automatic weekly or monthly runs and a report email, and the consent log CSV export. See the Cookie Consent changelog.
First version: everything above, taken out of Pixel Tracking 1.8.7 and Cookie Consent 1.6.1.