Common questions
Q: Is Code Cube GDPR compliant? What data is stored?
A: Yes, Code Cube is fully GDPR compliant and built with privacy by design. We don’t store personal data like names or emails. Instead, we only log technical metadata (e.g. which tag fired and when). Any potentially sensitive values in the dataLayer are automatically masked or replaced before storage.
Q: How easy is the integration of Code Cube? Do I need developer time to implement?
A: Code Cube is extremely easy to implement and configure. No developer is needed. You just add a small snippet in your tag manager and we or you can configure your settings in our dashboard.
Q: Do I need to trigger checks manually, for example after a major release?
A: No, Code Cube runs automatically and continuously. It detects changes in your tag setup or dataLayer without you having to trigger anything. Manual checks are no longer needed as Code Cube is always on without any human interaction.
Q: How will we (or our agency) be alerted?
A: You can receive alerts via email, Slack, Teams, or WhatsApp, and assign different contacts from within- and outside your organisation. This allows you to alert internal stakeholders as well as for example your agency.
Q: Can alerts be limited, for example to one overview per day or per week?
A: Yes, you control how often and how detailed alerts are. Choose between real-time notifications or daily/weekly summaries.
Tag Monitor
Q: How many and which pages will be monitored?
A: We monitor a representative subset of pages that covers your key templates and conversion paths, including all page types and the complete funnel. Monitoring every single page isn’t necessary; we focus on those that impact your marketing and tracking most. New or updated pages are automatically detected and added.
Q: Which tags do you monitor, can you also monitor a local vendor?
A: All tags are monitored by default, you don’t need to enumerate them manually: Whether it’s Google Ads, Facebook, a local/regional vendor tag, or a completely custom tag, Code Cube will monitor it. If you want, you can explicitly exclude certain tags from monitoring. This gives you visibility across the full spectrum of your tracking setup, even for niche or custom tags.
Q: Does the Tag Monitor work within our app too?
A: Yes, as long as your mobile app uses Google Tag Manager for mobile apps, our Tag Monitor can be configured to track tag activity in your app as well. This ensures coverage across your web and mobile presence.
Q: Are issues checked in real-time or based on scans with an interval?
A: The monitoring is real time, meaning tag behaviour is evaluated continuously. If real-time alerts are not ideal for you, we can also switch to a sampled or scheduled approach (e.g. every few minutes/hour).
Q: Some tags (e.g. from third parties) slow down my site. Can I exclude them so I’m not alerted?
A: Yes. You can exclude specific tags from monitoring or create custom alert thresholds for them. For example: Ignore a known slow-loading tag from a partner; Set looser thresholds so that only major deviations trigger alerts. If you want help optimising or mitigating slow tags, we can connect you with technical agency partners who can help (e.g. implementing server-side tags, deferred loading, etc).
Q: Do I need to take action if tags or triggers are added/removed in the Tag Manager?
A: No. Once Code Cube is installed, it dynamically adjusts. Any new tags or triggers you publish in your tag manager will be picked up automatically by Code Cube, no additional configuration needed.
Q: Does the Tag Monitor influence the site speed?
A: Very minimally. Here’s how we keep performance impact extremely low: A small script is required in the tag manager container, but we execute it only for a random sample of your traffic (often just 5–10 %). The extra request size is about 400 bytes, comparable or smaller than standard third-party tags (e.g. Facebook ~700 bytes, Google Ads ~602 bytes) Code Cube.
DataLayer Guard
Q: We don’t use a dataLayer, can you still help us monitoring?
A: Yes. DataLayer Guard monitors your entire frontend. We named it “DataLayer Guard” because the dataLayer is the most widely known term for the frontend JSON object. Even if your site doesn’t use a dataLayer, our solution can still replicate a full user visit, simulating any possible scenario just like a real visitor would.
Q: Does the DataLayer Guard distinguish between mobile/desktop and different browsers?
A: Yes. You can configure it to monitor based on device type and browser, so you can detect data layer behaviour that varies across platforms (e.g. mobile vs desktop, or between Chrome, Safari, Firefox).
Q: Are interaction events also monitored with the dataLayer Guard?
A: Yes. This unique feature allows you to monitor user interactions (like form submissions, cart updates, checkout steps) by simulating scenarios and verifying that correct data is pushed to the dataLayer. That helps validate end-to-end flows, not just page loads.
Q: Is it possible to check for specific ranges, values, or whether a date is correct?
A: Yes, DataLayer Guard supports regex-based validations, so you can set conditions such as: Value ranges (e.g. price between 0 and 999.99); Date formats or correct date ranges; Pattern matching (e.g. order numbers following a certain format); Existence or absence of fields. This gives you precise control over what constitutes correct vs incorrect data.
Q: Can I make changes myself to the setup in case the dataLayer blueprint changes?
A: Absolutely. You (or your marketing/dev team or agency) can update rules, field names, or validation logic via the Code Cube portal. You don’t need to contact support or wait, changes are under your control.
Q: Does the dataLayer Guard influence the site speed?
A: No, the design of DataLayer Guard ensures minimal performance impact: It does not inject JavaScript or pixels into your site pages. Instead, it uses a backend agent/browser to simulate visits and observe dataLayer events entirely separate from your user-facing site runtime. This simulation runs off-site (i.e. through our infrastructure), so your actual page speed and user experience remain unaffected.