I would like to use the Cookie Keeper powerup. I have a Wordpress site myself, which is why I can integrate the Stape Server Side plugin.
However, since I use a cookie banner solution (Cookiebot) to request user consent before I load anything, I do not want the Google Tag Manager to be integrated on the website via the Stape Wordpress plugin. I load the GTM script myself via Cookiebot. I have already implemented the custom loader. I have adapted the Tag Manager script accordingly (this worked).
But now the Cookie Keeper is to be implemented and I would like the Stape plugin to simply generate a corresponding master cookie or reference the correct one so that the Cookie Keeper powerup works.
My question: Can I still use the Wordpress plugin for the Cookie Keeper without integrating the Tag Manager via the plugin? If so, what exactly do I have to set? Or do I have to set the MasterCookie myself in my backend in some way?
Yes, you can still use the WordPress plugin for the Cookie Keeper powerup without integrating GTM via the plugin. To do so, you’ll need to adjust the plugin settings so that it handles only the master cookie without injecting the GTM script.
What You Need to Do
Disable GTM Injection in the Plugin:
Navigate to your WordPress Dashboard → Settings → Stape Server-Side.
Look for an option like “Inject GTM Script” or “Enable GTM” and disable it. This ensures that your custom GTM loader via Cookiebot isn’t overridden by the plugin.
Enable Cookie Keeper:
In the same settings area, enable the Cookie Keeper powerup.
With this enabled, the plugin will take charge of creating (or referencing) the master cookie needed for Cookie Keeper functionality.
Verify the MasterCookie:
After configuration, check your browser’s Developer Tools (usually under “Application” or “Storage” → “Cookies”) to ensure that the master cookie (often named something like _stape_mc) is present and persists correctly.
Hey, thanks for your quick answer. I tried to configure the plugin but i don´t see a cookie with the name stape or similar. This is my wordpress configuration:
WordPress Plugin: Double-check that the Cookie Keeper powerup is enabled in your Stape plugin settings. Make sure any option for GTM injection is disabled as per your configuration.
Stape Account: Confirm in your Stape account that the Cookie Keeper for WordPress is active and properly configured.
2. Consent-Dependent Loading
Since you’re using Cookiebot, ensure that the cookie-setting script isn’t being blocked until after consent. The cookie may only be created once the user has accepted tracking. Test by giving consent and then checking for the cookie.
3. Check the Cookie Name
The cookie might not be labeled exactly “stape.” It could be named something like _stape_mc or a similar variation. Look carefully in your browser’s Developer Tools (under Application → Cookies) for any new or unfamiliar cookies that might correspond to this functionality.
4. Examine Custom Loader Impact
Your custom GTM loader might be affecting the initialization of the Cookie Keeper. Review your custom script to ensure it doesn’t inadvertently prevent the Stape plugin’s script from executing. Also, check your browser console for any JavaScript errors that might indicate a conflict.
5. Review Caching & Security Plugins
Sometimes caching or security plugins can interfere with cookie creation. If you have any such plugins active, try temporarily disabling them to see if the cookie appears.
6. Testing Environment
Incognito/Private Window: Try testing in an incognito window to avoid interference from cached data or previous cookie settings.
Console Logs: Enable or check for logging within the plugin if available, to verify that the cookie-setting process is being executed.
In this case, you need to set your master cookie and use it in the Cookie Keeper script’s Cookie Keeper settings.
Here you can find the requirements for the master cookie (make sure it is not set via JS):
