Tracking, pixels and cookie consent

• Google Analytics 4: Measurement ID (G-…) and, for server-side purchases, the Measurement Protocol API secret (GA4 → Admin → Data streams → your stream).
• Google Ads: Conversion ID (AW-…) and Purchase conversion label.
• Meta Pixel & Conversions API: Pixel ID, Conversions API access token (Events Manager → your pixel → Settings), optional Test event code (Events Manager → Test events; clear it after testing).
• TikTok Pixel & Events API: Pixel ID, Events API access token, optional Test event code.
• Tokens and secrets are stored encrypted and never shown again ("Saved — leave blank to keep"). Send test event (GA4, Meta, TikTok) sends one test event with the saved settings and shows the platform's response — save first.
• Server-side conversion events (Pro plans and above): purchases are also sent from the server when an order is paid (or placed with an offline payment); customer details are hashed; shoppers who rejected tracking are skipped.
• Cookie consent: Ask first (opt-in) — banner with Accept/Reject, pixels load only after Accept (EU/UK); Notify, allow opting out — pixels load, notice with Reject; No banner. Optional banner text (empty = standard text in every storefront language). Google Consent Mode v2 starts denied until accepted.
• Recent server events: last 30 days of server sends with platform, event, order, Sent/Failed and the error; filter by status and platform.

Product feeds are in Marketing → Sales channels.