PPL Tracking & Privacy

PPL Tracking & Privacy for Magento gives merchants a consent-aware signal and privacy foundation for PPL Search Intelligence and other future PPL modules that need storefront behavior data. After installation, the extension adds an admin area under PPL Hub > Tracking & Privacy and a matching configuration section where teams can turn the PPL signal collector on or off per scope, decide whether explicit consent is required, honor Do-Not-Track, redact personally identifiable query data, limit stored query length and set a raw-event retention window. This module does not add a second consent banner: when consent is required, it reuses Magento's Cookie Restriction Mode acceptance state through the `user_allowed_save_cookie` cookie, or an explicit PPL analytics-consent grant from a connected consent-management workflow. The customer-facing storefront does not receive a visible marketing widget or its own reporting dashboard. Instead, when the PPL collector is enabled and consent/configuration allow it, the module records search terms and zero-result searches, result counts, product impressions, clicked products and positions, search-originated add-to-cart, wishlist and compare actions, attributed orders and returns, revenue, store and customer-group context, timestamps, hashed session references and optional customer IDs when configured. A frontend collector loaded through Magento layout reads the catalog search result page and the decoupled PPL Search Intelligence ppl_search:interaction event, while Magento event observers add server-verified cart, wishlist, compare, order and credit-memo signals. Cron then aggregates the raw events into query and per-query product statistics - searches, zero results, impressions, clicks, add-to-carts, orders, returns, revenue, CTR, conversion rate and behavior score, that PPL Search Intelligence or later companion modules can consume.

Features

• Consent-gated behavioral collector for search, impression and click signals, with fixed-window rate limiting, event de-duplication and Do-Not-Track support, so behavioral data is only captured when consent allows.
• Server-side purchase and return signals plus scheduled behavior, query and query/product aggregation, turning raw events into usable statistics without rebuilding the query by hand.
• Configurable raw-event retention window with a daily purge, so data is kept only as long as your retention policy defines.
• GDPR/DSGVO-oriented consent recording and an append-only consent audit trail, giving you a defined record of how consent was handled.
• Configurable PII redaction plus data-subject export and erasure tooling, supporting deletion and access requests from one place.
• The module does not send the behavioral data it collects to PPL or to a bundled third-party analytics service; storage and processing stay in the merchant's Magento-controlled environment, subject to the merchant's own hosting, integrations, consent setup, and retention policy.

What data is collected and produced

The raw event layer stores only the allowed tracking events, plus the context needed to make those events useful: store ID, customer group, hashed session reference, optional customer ID, query and normalized query, event type, product ID, result position, result count, trusted revenue/order attribution, limited metadata, and timestamps. Query PII redaction and maximum query length can be configured before events are stored. The aggregation cron turns those raw events into two practical outputs: query statistics for demand and zero-result analysis, and per-query product statistics for product scoring. Those aggregates expose searches, zero-result counts, impressions, clicks, add-to-carts, orders, returns, revenue, click-through rate, conversion rate, last-seen dates and a behavior score.

How it connects to Magento

The PPL collector has its own module-level enable switch and its own tracking endpoint, but it relies on Magento's existing cookie-consent state instead of creating a separate storefront consent UI. The browser collector sends only untrusted search, result-impression, result-click and zero-result beacons to that endpoint. It cannot inject purchases, returns or revenue. Search-originated add-to-cart, wishlist and compare actions are recorded server-side through Magento events when the request is marked as coming from a search surface. Orders and returns are also recorded server-side from Magento order and credit-memo events, and only when they can be attributed back to a previous consented search interaction for the same product and session or customer. Cooperating PPL modules then read the aggregates through loose event bridges, so PPL Search Intelligence can use behavior, product and zero-result signals without Tracking depending on Search Intelligence.

Why merchants use it

In a standard Magento setup, the platform does not provide a dedicated, consent-aware signal layer for shopper searches, result clicks, purchases and returns. The usual workarounds mean either sending behavioral data to an external platform or writing one-off collection logic that is slow to build and easy to get wrong. PPL Tracking & Privacy closes that infrastructure gap: a consent-gated collector records the signals, a scheduled job aggregates them into behavior, query and query/product statistics, provider events expose the aggregates to PPL Search Intelligence and future consumers, and CLI tooling supports export or erasure of a data subject's data on request. Teams get the tracking and privacy foundation needed for behavior-aware features without building the collection, retention, redaction and data-subject workflows themselves. The module supports these privacy workflows; meeting GDPR/DSGVO obligations still depends on your own configuration, policies and legal review.

Common use cases

• Feeding PPL Search Intelligence with consent-aware behavior, product and zero-result signals.
• Preparing a privacy-controlled signal layer for future PPL modules without adding another external tracker.
• Responding to a data-subject access or deletion request by exporting or erasing that subject's behavioral data through the provided CLI tooling.
• Enforcing a retention policy by letting the daily purge drop raw events past your configured retention window.
• Capturing and auditing shopper consent so behavioral collection only runs when consent and Do-Not-Track settings allow.

What you get

• The extension package for Magento with the admin configuration under PPL Hub > Tracking & Privacy.
• ACL/menu integration through PPL Hub.
• The data-subject-rights CLI commands.
• The aggregation and purge cron jobs.
• Translation files for 12 locales: de_DE, en_US, es_ES, fr_FR, it_IT, ja_JP, nl_NL, pl_PL, pt_BR, ru_RU, tr_TR, zh_CN, giving international teams a ready localization baseline while still allowing normal Magento theme and project translation overrides.
• Documentation for installation, first setup and expected empty states.

Compatibility

Designed for Magento Open Source and Adobe Commerce 2.4 environments, with the PHP and Magento/PPL package versions declared in composer.json. Requires the PPL foundation module PPL Hub as its key PPL dependency. It remains independent of PPL search and filter modules; optional consumers such as PPL Search Intelligence can use the neutral behavior, product and zero-result signal events, but Tracking does not depend on them.

Ideal for

Stores that need a consent-aware behavioral signal and privacy foundation for PPL Search Intelligence, future PPL consumers and EU/DE data-subject-rights workflows, with clear control over consent, privacy and retention.