Connecting Concrete CMS to TikTok Events API

TikTok visitors land in the in-app browser, and on a Concrete CMS site that first request is often served from full page cache, so any PHP that reads ?ttclid= from the URL never runs. Capture ttclid with a small script into a first-party cookie, then read that cookie when the commerce add-on creates the order and store it as an order attribute, alongside the _ttp cookie value and the order's email and phone.

Send CompletePayment from the add-on's order-completed event through the Events API, with the order number as event_id and the same event_id on any browser CompletePayment so TikTok can deduplicate. Value and currency come from the add-on's order totals. Because Concrete commerce runs on your own domain, the in-app browser usually holds the session through checkout, unless your payment gateway redirects off-site. Check which gateway your add-on uses: a PayPal or hosted-gateway redirect out of TikTok's in-app browser is exactly where TikTok orders go missing, and the server event is what recovers them.

For Concrete sites that only take enquiries, send SubmitForm when the Express form entry is saved, with the ttclid copied into a hidden field. The TikTok pixel itself can go in Concrete's Tracking Codes setting, but exclude it from cached confirmation pages for the same reason as the order hook: a cached page replays stale values. The order hook name differs by add-on and version, so confirm it rather than copying code from another Concrete site.