---
title: "Tracking"
description: "See how your tracking apps work, choose how Google tags behave before a shopper consents, and read what your store sent to ad and analytics tools."
url: "https://docs.poltura.com/en/settings/tracking/"
lang: en
alternates:
  en: "https://docs.poltura.com/en/settings/tracking/"
  hu: "https://docs.poltura.com/hu/settings/tracking/"
---

# Tracking

See how your tracking apps work, choose how Google tags behave before a shopper consents, and read what your store sent to ad and analytics tools.

- Where: Settings → Tracking

The Tracking page brings your tracking apps together: Google Tag Manager, the pixels of ad platforms and the conversion codes of price comparison sites. It shows whether each one runs, how its server events went in the last 24 hours and what the shopper agreed to. Each app's own settings, such as a pixel ID, stay on its app page.

![The Tracking page with a card for each tracking app and its status, and the Consent, Checkout tracking and Debug mode panels on the right](https://docs.poltura.com/screenshots/en/settings/tracking.webp)

_Apps you have not installed yet show Not installed and an Add link._

## What the page shows

- **Tracking apps**: one card per tracking app. A card says whether the app runs in the shopper's browser and whether it sends server events. It then counts the last 24 hours: sent, skipped (mostly because the shopper did not allow that kind of cookie) and failed. The last problem is written out in plain words. Apps you have not installed show as cards that open the App Store.
- **Latest events**: the five newest events the server handled, each with what every app did with it.
- **Consent**: whether the cookie banner of your theme is shown, and the Google Consent Mode.
- **Checkout tracking**: how tags run on the checkout and order pages.
- **Your Tag Manager container**: what Poltura found in your published Google Tag Manager container.
- **Debug mode**: keeps the exact requests your apps sent, for 24 hours.

## Test an app

Apps that send server events have two buttons on their card:

- **Test connection** checks the app's ID and token with the provider.
- **Send a test event** sends one event the provider marks as a test. Some providers, such as Meta, show test events only with the code from their test events tool. Paste that code into **Test code** first.

## Consent and Google Consent Mode

Tags load only for the cookie categories a shopper allows in the cookie banner. If you switch the banner off in the [Customizer](https://docs.poltura.com/en/online-store/customizer/), no tag loads, because no one can give consent.

**Google Consent Mode** decides what Google tags do before the shopper chooses:

- **Basic** (the default): no tag loads until the shopper chooses.
- **Advanced**: Google tags load straight away with consent denied and send Google cookieless pings. No other tag loads early.

> **Warning**
>
> Data protection authorities in the EU do not agree that advanced mode is lawful (EDPB Guidelines 2/2023). Turn it on only if your legal adviser says it fits your store.

## Checkout tracking

Your tracking apps run on every page, checkout included. On checkout and the order pages a strict security policy lets each app reach only its own services, so no other script can load where shoppers pay.

Google Tag Manager runs there too. On checkout and the order pages your Custom HTML tags and custom JavaScript variables do not run, while Google's tags and tags made from templates do. See [Google Tag Manager](https://docs.poltura.com/en/apps/gtm/#checkout).

## Your Tag Manager container

With the Google Tag Manager app on, the page reads your published container once a day. **Read again** reads it now.

- **Tags your apps can run**: the Google Analytics, Google Ads, Meta and TikTok IDs in your container. **Use in the … app** puts an ID into an app that is on but has none yet. Nothing changes until you select it. If an app runs the same ID, the page warns you, because the tag then counts twice. Remove it from Tag Manager, or send the data layer's `event_id` as its event ID.
- **Custom HTML tags that do not run on checkout and the order pages**: your Custom HTML tags, named by the pixel they run or the services they load from, since Tag Manager does not publish tag names.

If the container cannot be read, the page says so and shows nothing else.

## Event log

1. Open **Settings**, choose **Tracking** and click **Event log**.
2. Narrow the list by outcome (**Sent**, **Waiting**, **Skipped**, **Refused**), by event or by app.
3. Click a row to open the event. It shows what each app did with it and why, the consent at the time and the event data. Customer data appears only as "hashed email ✓", never as the address itself.

The log keeps the last 24 hours. Only server events are in it. Events a tag sends from the shopper's browser are not.

## Debug mode

While **Debug mode** is on, each event in the log also keeps the exact request every app sent, hashed customer data included. It turns itself off after 24 hours. **Turn off** stops it earlier.