Cookieless analytics without consent banner

Reach measurement in XICTRAQ Analytics sets no cookies, stores nothing in the browser, does not store IP addresses and creates no persistent user profiles; visits are distinguished by a pseudonymous daily identifier. The exception is automatic customer recognition from the Business plan: it links visits of logged-in customers to their customer number and, where the site provides them, to name or company, and is therefore personal data. Because reach measurement stores nothing in and reads nothing from the browser, consent under § 25 TDDDG is usually not required for it; for the pseudonymous daily identifier, legitimate interest under Art. 6(1)(f) GDPR usually comes into consideration as the legal basis. The specific legal assessment depends on your use case; we recommend review by your data protection officer.

Cookieless analytics captures every pageview -- unlike cookie-based tracking where up to 50% of visitors deny consent. Re-identification beyond the day does not take place in reach measurement (privacy by design): the daily key of the visitor identifier is a random value generated anew each day and deleted once the day is over. The exception is customer recognition from the Business plan, which assigns visits of signed-in customers via their customer number. In return you get reliable aggregate metrics: visits, pageviews, time on page, sources and devices.

For most SMBs, yes. XICTRAQ Analytics provides pageviews, visitor sources, device statistics and campaign tracking. Features like cohort analysis or remarketing lists that rely on personal data are intentionally not included — that is the price for cookie-free and GDPR-compliant.

Yes. Analytics data is collected, processed and stored in our data centre in Nuremberg. Only if you ask the AI assistant for analyses are summarised figures sent to the language model provider in the USA (privacy policy, section 9b).

The XICTRAQ Analytics snippet is around 26 KB Brotli-compressed (around 27 KB gzip, around 94 KB minified) and delivers the complete feature set in return: pageviews, click heatmaps, Core Web Vitals, form analytics, media tracking, custom events and A/B testing. It loads asynchronously, does not block rendering and has no measurable impact on load time or Core Web Vitals.

Yes. All standard UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) are recognized and displayed in the dashboard as campaign reports. This lets you measure the success of your marketing campaigns.

Partly. XICTRAQ classifies known AI crawlers by their user agent (e.g. GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot) and shows in the analytics dashboard which bot accessed how often and when it was last seen. These hits are kept separate from your human visitors and do not distort visitor counts. A crawler is captured once it loads the tracking pixel or runs the script; most AI crawlers do neither, so the figure is a lower bound.

Yes. When a visitor reaches your site via a link from ChatGPT, Perplexity, Gemini, Copilot, You.com or DeepSeek, the AI source is derived from the referrer and surfaced in the dashboard as a dedicated AI referral channel — including its share of total traffic. This shows whether and how AI answers contribute to your reach.

Yes. The analytics overview has a central comparison control: "compare with" previous period, previous year or a custom date range. The chosen comparison applies to every card at once — KPI cards (e.g. visitors, pageviews) show the delta versus the comparison period, breakdown cards a comparison pill in the header. The colour is direction-aware: more visitors or conversions are shown green, a higher bounce rate red. In the backend the compare_mode parameter (previous, year or custom) controls the behaviour.

XICTRAQ detects e-commerce tracking for 25 systems without manual setup, including WooCommerce, Shopify, Shopware 5/6, Magento/Adobe Commerce, PrestaShop, OpenCart, OXID, JTL, Gambio, BigCommerce, Squarespace, Wix, plentymarkets, SAP Commerce/Spartacus and Salesforce Commerce Cloud. Captured events are product view, add to cart, remove from cart, checkout, purchase and refund — each with product name, item no./SKU, variant, price, quantity and category.

Both. The cart snapshot mirrors every line item 1:1 (name, variant, item no., quantity, unit and line price) and provides subtotal, shipping, tax and grand total always net and gross — regardless of whether your shop displays net or gross. Tax mode and currency are carried along so analysis stays comparable across shops.

Via real-user monitoring (RUM) directly in your visitors’ browsers, cookieless and millisecond-precise. It captures TTFB, FCP, LCP, INP, CLS and the full page load, aggregated by page, device and connection. This gives you field data from real usage instead of isolated lab values.

Yes. Logged-in customers are recognised without forced PII: the customer number and type/group are stored and, where the shop provides them, name or company. This works automatically for Shopware, Shopify, WooCommerce/WordPress, PrestaShop, Drupal, Joomla, TYPO3 and BigCommerce. For custom applications there is a generic convention via window.xictraqUser, meta[name=xictraq:user-id] or a data-user-id attribute.

Via a one-line script tag with Subresource Integrity (SRI) and content-hash rotation: <script defer src="https://api.xictraq.com/t.v<hash>.js" data-site="YOUR-SITE-ID" integrity="sha384-..." crossorigin="anonymous"></script>. The integrity hash ensures that only the unchanged file is executed; a noscript pixel fallback additionally captures visitors without JavaScript.

XICTRAQ automatically detects the statistics/analytics consent from 16 common consent management platforms (CMPs) as well as the IAB TCF v2.2 and Consent Mode v2 standards and adopts it as a signal. Cookieless reach measurement runs continuously and independently because it requires no consent. Only consent-required features — currently session recording — start after consent has been granted and stop automatically as soon as it is withdrawn.

A dedicated tab area provides an overview, order history (carts and orders chronologically with status open, abandoned, purchased or refunded), per-product performance (views, cart, revenue), carts, abandonment with rate and lost value, recovery for identified customers with an open cart, finances from gross through discount, net, shipping and tax to refund, revenue sources and customers. AI analyses of funnel, abandonment, products, finances and recovery can be triggered directly in the tab via the AI assistant.

Logged-in customers are linked across days via their external customer number and shown in a dedicated "identified users" view as well as in the visitor detail. Customer number, type (B2B/B2C) or group and — where the shop exposes it in the DOM or in profile/checkout fields — name or company come exclusively from what the shop itself provides; there is no obligation to collect personal data.

In the location breakdowns (cities, regions), XICTRAQ does not list segments with very few visitors individually but groups them into an "Übrige" (other) bucket. A specific city or region is only shown once a minimum number of distinct visitors per row (k-anonymity threshold) is reached. This reduces the re-identification of individual people via rare location combinations and follows the principle of data minimisation. It is a suppression of small cohorts, not a guarantee of anonymity. Your headline metrics remain unaffected.