Set Meta, Google and TikTok in SmootifyUserOptions.analytics and remove them from Webflow's integrations and your custom code, so each waits for the visitor's consent.
The symptom. Tracking starts before the visitor has accepted cookies.
Why. A pixel added in Webflow’s integrations or in custom code loads at once and sends its page view before any consent. Smootify finds that copy and uses it, but cannot take back what it has already sent.
The fix. Remove the pixels from Webflow’s integrations and your custom code, and set their ids in window.SmootifyUserOptions.analytics. Smootify loads each one after the consent it needs. On .webflow.io, the debugger points out a copy still on the page.