How to Configure MucaSST Cookie Keeper (ITP Bypass)
Due to Apple's Intelligent Tracking Prevention (ITP) and other privacy-focused browsers (like Safari and Brave), first-party tracking cookies are now automatically restricted to a lifespan of just 1 to 7 days. This severely degrades your ability to track returning customers and accurately measure your ad campaign's Return on Investment (ROI).
The MucaSST Cookie Keeper leverages your Server-Side GTM (sGTM) container and our cloud firewall to intercept these restrictions, seamlessly extending your cookie lifetimes back to 1 year (or your preferred duration).
Follow the detailed steps below to configure this feature.
Step 1: Enable via MucaSST Dashboard
Before configuring Google Tag Manager, you must activate the backend firewall rules from your server infrastructure.
Log in to your MucaSST Client Area.
Navigate to your specific container's Order Details or Instance Management page.
Locate the Cookie Keeper feature and toggle the switch to the ON position.
Note: Activating this toggle instantly applies the necessary response header rewriting rules to your server's backend infrastructure.
Step 2: Import the Template into Server GTM
Next, you need to add our official Cookie Keeper template to your Server container.
Log in to your Google Tag Manager account and open your Server GTM container (Do not use the Web container).
From the left-hand navigation menu, click on Templates.
In the Tag Templates section, click the Search Gallery button.
Search for MucaSST Cookie Keeper in the gallery.
Select the template and click Add to workspace.
Pro Tip: If the template is currently pending official approval in the Community Gallery, you can manually upload the .tpl file provided by MucaSST Support using the Import option.
Step 3: Create the Cookie Keeper Tag
With the template imported, you now need to create the tag that will process your cookies.
Navigate to Tags from the left menu and click New.
Name your tag clearly (e.g., MucaSST - Cookie Keeper).
Click on Tag Configuration and select the MucaSST Cookie Keeper template you just imported.
In the template settings, specify the cookies you want to extend. Common tracking cookies include _ga, _fbp, and _fbc.
Set the Duration to 1 year (or 395 days) to ensure long-term attribution.
Step 4: Configure the Regex Trigger
You must configure this tag to fire on every single request that hits your server so it can actively rewrite the cookie headers.
Scroll down to the Triggering section and click inside the box.
Click the + (plus) icon in the top right corner to create a new trigger.
Click Trigger Configuration and select Custom Event.
In the Event Name field, type exactly: .* (a dot followed by an asterisk).
Check the box labeled Use regex matching.
Name your trigger (e.g., All Events - Regex) and click Save.
Step 5: Publish and Verify
Once your Tag and Trigger are saved, click the blue Submit button in the top right corner of your sGTM workspace.
Add a descriptive version name and click Publish.
Congratulations! Your tracking infrastructure is now resilient against ITP restrictions. Your server will automatically rewrite incoming tracking cookies to ensure maximum data accuracy and attribution lifespan.