TikTok Pixel Tracking Pro module for PrestaShop

Features and benefits of the TikTok Pixel module for PrestaShop

• Implement TikTok Pixel from the PrestaShop panel: simply enter the TikTok Pixel ID in the module configuration; there is no need to manually paste the Pixel code into theme files.
• Support for the purchase journey: the module records the ViewContent, Search, AddToCart, InitiateCheckout, AddPaymentInfo, Purchase, and CompleteRegistration events wherever the corresponding store data is available.
• Control over the purchase event: Purchase is queued after the order reaches the status marked by PrestaShop as paid, not when the payment process itself is started.
• Protection of cart data quality: AddToCart is sent after a successful cart update, and the product data for this event is retrieved from the current server state.
• Matching the TikTok catalog: for product events, you can choose product ID, product ID with combination, reference, EAN-13, or UPC, and apply a shared identifier prefix.
• Optional TikTok Events API: the module can also send paid purchases from the server, without disabling standard tracking by TikTok Pixel in the browser.
• Shared event identifier: browser-side and server-side Purchase use the same deterministic event_id to support deduplication across both delivery channels.
• Per-store configuration: in multistore, each store can have its own Pixel ID, Events API token, product identifier type, prefix, and consent settings.

Key functionalities

• Pixel launch and page call: once the configuration and consent conditions are met, the module loads the TikTok Pixel library and calls page.
• ViewContent on the product page: the event includes the selected product identifier, price, currency, quantity, and item data prepared from the current product.
• Search on the search page: for a non-empty phrase, the module passes the search query to the Search event.
• AddToCart after cart change confirmation: the script reacts to a successful PrestaShop cart update and retrieves the event data through the module’s protected endpoint.
• InitiateCheckout and AddPaymentInfo: the module creates InitiateCheckout on supported checkout pages, and AddPaymentInfo after a change to the standard payment method selection.
• CompleteRegistration: after account creation, the module queues the registration event and sends it on the next supported customer page.
• Purchase on the confirmation page: the module uses paid order data, including items, value, and currency, and assigns a deterministic event_id to the event.
• CRON endpoint for Events API: when Events API is configured, the module provides a token-protected URL for retrying temporary delivery errors of server-side Purchase.

Marketing consent and Advanced Matching

• Optional consent gate: when the marketing consent requirement is enabled, the Pixel is not loaded until the integration of the consent manager in use calls the module’s provided JavaScript function or event, or until a PD Cookie Pro decision is recognized.
• Integration with PD Cookie Pro: the module recognizes the signed decision from an active PD Cookie Pro version 1.1.1 or later. The “all” consent grants the module permission for tracking and Advanced Matching, while the Advanced Matching feature itself still requires enabling in the configuration; custom groups require the ad_storage value for tracking and ad_storage and ad_user_data for Advanced Matching.
• Advanced Matching disabled by default: once enabled and after marketing consent is obtained, the module can send the valid email address and the phone number saved in the delivery address of the logged-in customer, if the number is already in E.164 format.
• Data in Events API: in server-side Purchase, email and phone are normalized and hashed with SHA-256 only when Advanced Matching is enabled and marketing consent has been recorded.
• Technical scope: the module helps control Pixel operation according to the consent state, but it does not replace cookie banner configuration, the privacy policy, or the assessment of the store administrator’s legal obligations.

TikTok Events API and delivery reliability

• Optional server-side connection: the TikTok Events API access token is optional; without it, event tracking through the browser-side TikTok Pixel still works.
• Paid Purchase only: Events API does not send the full list of browser events; server-side delivery applies exclusively to the paid purchase.
• Handling transport issues: temporary errors can be retried via CRON, while rejected data or invalid credentials are not resent indefinitely.
• Secure administrator settings: saving a new Events API token can resume deliveries stopped after a credential error, and the switch allows removing the token and stopping server-side delivery only.

Product identifiers and the TikTok catalog

• Choice of content_id source: available options are product ID, product ID with combination, reference, EAN-13, and UPC.
• Identifier prefix: one optional prefix is added to every identifier sent in product events.
• Catalog compatibility: the selected identifier and prefix should exactly match the values used in the TikTok product catalog. If a value is missing for the selected reference, EAN-13, or UPC, the module skips that item instead of replacing it with another identifier.

Compatibility and multistore

• PrestaShop: the module declares compatibility with PrestaShop from version 1.7.0.0 to 9.99.99.
• Multistore: configuration requires selecting a specific store, so tracking settings are not accidentally shared between stores.
• Themes and checkout: the module uses PrestaShop front-office hooks, supports the standard checkout, and recognizes the one-page checkout controllers indicated in the code, including TheCheckout, SuperCheckout, and OnepageCheckout.