Nobase review for Stape Conversion Tracking
Jan. 24, 2026
Be careful when using the Stape Custom Loader via Shopify Custom Pixel. In my setup, the loader injects the Web GTM container 5–8 seconds after page load, which causes serious issues: - First page_view and session_start can be missed - Campaign parameters (gclid / utm) may be lost - Consent Mode v2 default signals are sent too late - Google reports missing ad_personalization - Attribution and remarketing performance is negatively affected Consent Mode v2 requires consent defaults to run before any Google tags initialize, which is not possible with this delayed injection. When I moved GTM back to , all consent and attribution issues disappeared. Recommendation: Load the Web GTM container in and use Shopify Custom Pixel only for checkout / purchase events. Do not rely on Custom Loader for primary container injection if you care about data quality and consent compliance
Thanks for sharing your feedback, and sorry for the trouble this caused. You’re right that there was a bug affecting Custom Loader on checkout pages, and we’ve already fixed it. If you’re willing, please try again and let us know whether everything works as expected now. Regarding consent, the app has nothing to do with consent pushes and does not influence them. If anything still isn’t working properly, please contact our support team. We’ll investigate and help you resolve it as quickly as possible.
