Reddit Pixel Integration: setup and help

Follow the steps in Quick start.

Set these in Modules -> Reddit Pixel -> Configure.

• Enable Reddit Pixel. Turns browser Pixel tracking on or off; default: 0.

• Pixel ID. Stores your Reddit Pixel ID from Reddit Ads Manager -> Events Manager; default: "". It must contain only letters, numbers, underscores, and dashes, with 4 to 128 characters.

• Exclude employee browsing. Stops tracking when a logged-in back-office employee browses the storefront; default: 1.

• Respect marketing consent. Loads Reddit tracking only after marketing consent when mprcookiesrevolution or mprcookiebanner is active; default: 1.

• Track PageVisit. Sends a general page visit event on tracked storefront pages; default: 1.

• Track ViewContent. Sends product view events on product pages when product data is available; default: 1.

• Track AddToCart. Sends cart addition events after a confirmed successful quantity increase; default: 1.

• Track AddToWishlist. Sends wishlist addition events from acknowledged successful wishlist additions; default: 1.

• Track InitiateCheckout. Sends checkout entry as a Reddit custom event named InitiateCheckout; default: 1.

• Track Search. Sends search events on search-related pages when a query is present; default: 1.

• Track Purchase. Sends purchase events on order confirmation with order value, currency, products, transaction ID, and conversion ID; default: 1.

• Track SignUp. Sends a sign-up event on the next page load after customer account creation; default: 1.

• Track custom events. Enables your JSON custom event rules for browser Pixel tracking; default: 0.

• Custom event rules. Stores the JSON array used for click, URL, controller, and DOM-event rules; default: "".

• Enable Conversions API events. Queues eligible events server-side and sends them to Reddit with matching conversion IDs where the transport supports them; default: 0.

• Conversions API access token. Stores the Reddit Conversions API token generated in Reddit Ads Manager -> Events Manager; default: "".

• Events testing ID. Enables Reddit test mode for CAPI payloads when filled; default: "".

• Queue batch limit. Controls how many queued conversion events are processed per run, from 1 to 100; default: 20.

• Persist consent withdrawals. Default: 0. Enables a durable veto for previously accepted purchase and contact-form events. Enable it if you need that withdrawal persistence.

Click Save after changing the form.

The current form also exposes these settings. All signal switches default to No. Enable only the actions you intend to observe.

Shared thresholds are three gallery views, one variant change, one detail click, a 45-second dwell, and a 1500 ms option throttle. Gallery, variant, and detail counts are bounded to 1 through 20. Dwell is bounded to 5 through 600 seconds. Throttle is bounded to 250 through 60000 ms. For example:

{"min_gallery_views":3,"min_variant_changes":1,"min_detail_clicks":1,"dwell_seconds":45,"option_throttle_ms":1500}

You can also provide gallery_selectors, variant_selectors, and detail_selectors. Keep defaults unless your theme needs different selectors. These optional signals require consent, employee-policy, and tracking-ownership checks just like commerce events.

Keep the consent and employee-exclusion settings enabled during initial setup. Test from a normal visitor browser that is not marked as an employee. A logged-in Back Office session, an internal-traffic rule, or a visitor opt-out can suppress tracking.

The shared consent layer supports MPR consent integrations and additional CMP adapters. It must obtain a usable marketing decision for the destination. An unknown, stale, or refused decision can hold events. The module does not supply a cookie banner. A legacy consent preference does not override a live refusal from a detected CMP.

The module must own the configured destination in the shared tracking coordinator. Missing, ambiguous, or conflicting ownership can hold browser and server delivery. Remove duplicate theme tags or resolve the owner when another MPR module manages the same account.

Production sending also follows the outbound policy. An event shown in demo or preview mode is not necessarily delivered to your advertising account. Purchases and server form events are sent only with the consent the buyer gave at the time; a later cron run cannot supply that consent.

Your storefront header provides cache-safe configuration. The module loads https://www.redditstatic.com/ads/pixel.js after its checks pass. You do not get a normal storefront widget. The module supports displayHeader, displayOrderConfirmation, actionValidateOrder, actionCustomerAccountAdd, displayFooter, and displayBeforeBodyClosingTag.

With the relevant switches enabled, page visits send PageVisit; product pages send ViewContent; query pages send Search; acknowledged cart and wishlist additions send their matching events. Checkout entry sends Reddit Custom with customEventName=InitiateCheckout. Account creation is marked for SignUp on the next eligible page load.

Purchases include the available order items, quantities, value, currency, transaction ID and conversion ID. Server and browser purchases share the same purchase identity where available. Cart and wishlist additions need confirmation of a real addition; a browser event alone is insufficient.

Server events go to Reddit's https://ads-api.reddit.com/api/v2.0/conversions/events/PIXEL_ID endpoint with the configured Pixel ID. Which matching data is sent depends on the visitor's original attribution and consent. Browser and server copies share an event ID for deduplication when both are sent, but not every event is sent through both.

Enable Track custom events, paste a JSON array into Custom event rules, and save. Adapt selectors and paths to your shop. Use click, url, controller, or event triggers. A controller rule can also include a modules list. Event names allow letters, numbers, underscores, and hyphens, up to 64 characters. The limit is 15 distinct names. once limits a rule within its current page runtime.

[
  {
    "event": "GalleryBrowse",
    "trigger": "click",
    "selector": ".product-images img,.images-container img",
    "params": {
      "property": "product_gallery"
    },
    "once": false,
    "capi": true
  },
  {
    "event": "LandingView",
    "trigger": "url",
    "contains": [
      "/special-offer"
    ],
    "params": {
      "property": "special_offer"
    },
    "once": true,
    "capi": true
  },
  {
    "event": "ContactView",
    "trigger": "controller",
    "controllers": [
      "contact"
    ],
    "params": {
      "property": "contact_page"
    },
    "once": true,
    "capi": true
  },
  {
    "event": "SizeGuideOpen",
    "trigger": "event",
    "dom_event": "mprreddit:sizeGuideOpen",
    "params": {
      "property": "size_guide"
    },
    "once": false,
    "capi": true
  }
]

Trigger the DOM rule from your theme after tracking has initialized:

document.dispatchEvent(new CustomEvent('mprreddit:sizeGuideOpen'));

Each rule's capi flag sends a server copy through the custom bridge. The bridge accepts Custom with customEventName, checks that the rule is configured, and needs an event ID and the visitor's current consent. Without them, the event is held.

For the click rule, supported data attributes can override value, currency, num_items, and event_id, for example:

<button class="track-reddit-demo" data-reddit-param-value="12.50"
        data-mprreddit-param-currency="EUR">Track custom action</button>

Use a matching click selector in your rule. The older product_id and product_category attribute example is not consumed by the current runtime. A DOM event can supply supported commerce values in detail.params. Put static descriptive parameters in the rule itself.

The task send_reddit_conversions is registered with schedule every:300. It becomes due every five minutes. Your shared MPR cron runner must execute due tasks; the schedule declaration alone does not run a worker. The batch-limit setting caps queue rows per processing run, from 1 through 100, with a default of 20.

The module does not include a standalone cron.php entry point. Use the shared scheduler already configured for your shop. Confirm task execution in that scheduler and check queue timestamps and status on this module's configuration page.

The diagnostics include readiness checks, queue counters, recent rows, Send API probe, and Retry failed events. Resolve the reason for failure before retrying. Returning failed rows to pending does not bypass current consent, employee policy, account ownership, or destination checks.

For Send API probe, enter an Events testing ID and have a real pending event from a buyer who consented. Without a test ID, current consent or a usable queued event, the probe is refused; it never creates a fake purchase. Clear Events testing ID when you are ready for production events.

1. Check required-configuration notices, tracking ownership, and the integrity banner.
2. Use a normal visitor browser and grant marketing consent through your configured CMP.
3. Open a product, search, and complete a successful cart addition. Check SDK loading and the matching event requests in the browser Network panel.
4. Check Reddit's event diagnostics or Pixel Helper, if available in your testing setup.
5. For purchases, use an authorized test flow and inspect the browser event, conversion ID, and queue row.
6. For server delivery, run the configured scheduler and check the queue result. A browser call accepted by your shop has not necessarily reached Reddit.

If no script loads, check Enable Reddit Pixel, Pixel ID syntax, consent state, employee markers, ownership, outbound policy, and script blockers. If cart or wishlist events are absent, inspect successful-operation signals and product data. A click alone is insufficient. Use custom rules for separate interactions, without relabeling a click as a proven purchase or cart addition.

If CAPI rows fail or remain held, check the token, Pixel destination, recorded consent, queue schema, and cron execution. Custom rules need valid JSON and selectors. This version does not provide the former window.mprredditTrack helper.

Turn off the browser and server switches and save if you want to stop tracking while retaining configuration. Uninstall from Module Manager to remove module settings, menu entries, and registered tasks.

Uninstall invokes the shared conversion-queue cleanup. The shared queue table is retained while another conversion module uses it and can be dropped when the last user is removed. Export diagnostics you need before uninstalling. Do not assume uninstall removes events already sent to the advertising platform or clears all browser attribution storage.

Requires PrestaShop 1.6.0.0 or later and PHP 7.1 or later.