TsadaLabs Explore admin demo

Google Tag integration

Google Tag connects Google Analytics, Google Ads, and other Google marketing tools to the public casino website.

Tsada stores only the public Google Tag identifier in the admin panel. When the Google Tag provider is enabled, the frontend injects the Google Tag script into server-rendered public pages automatically.

Platform role

Within Tsada, Google Tag is used to:

  • Load the Google Tag script on public casino website pages.
  • Connect the website to Google Analytics or Google Ads.
  • Keep the public Tag ID configurable from the admin panel.
  • Avoid manual code changes for basic tag activation and deactivation.

The platform does not store Google account secrets or custom HTML snippets for this integration.

Before you start

Make sure the operator has:

  • Admin panel access.
  • Access to the relevant Google Analytics or Google Ads account.
  • The Google Tag identifier for the property or ads account.
  • Permission to update provider settings in the admin panel.

Valid Tag ID formats include:

G-XXXXXXXXXX
AW-XXXXXXXXXX
DC-XXXXXXXXXX

Do not paste the full Google Tag HTML snippet. The admin panel expects only the identifier.

Where to find the Tag ID

In Google Analytics, open:

Admin -> Data streams -> select the web stream -> Measurement ID

In Google Ads, open:

Tools -> Data Manager / Google tag -> Tag ID

Use the exact identifier shown by Google.

Admin configuration

Open:

Admin Panel -> Providers -> Google Tag

If Google Tag is not listed under providers, the technical team should check the latest deployment and provider seeders.

To enable Google Tag:

  1. Open the Google Tag provider.
  2. Enter the Tag ID.
  3. Enable Provider enabled.
  4. Save the provider.
  5. Wait up to 1 minute for the public bootstrap cache to refresh.

After the cache refreshes, the frontend injects the Google Tag script into public website pages.

Disabling the integration

To disable Google Tag:

  1. Open the Google Tag provider.
  2. Disable Provider enabled.
  3. Save the provider.
  4. Wait up to 1 minute for the public bootstrap cache to refresh.

The Tag ID can remain saved. While the provider is disabled, the frontend does not inject the Google Tag script.

Verification

Browser check

Open the public casino website, then use browser developer tools to check the Network tab after a page reload.

Search for a request like:

https://www.googletagmanager.com/gtag/js?id=<Tag ID>

If the request is present, the tag has been added to the page.

Google tools check

The setup can also be checked with:

  • Google Tag Assistant.
  • Google Analytics realtime reports.
  • Google Ads diagnostics.

If Google Tag Assistant does not detect the tag immediately after saving, wait 1 minute and reload the page with browser cache disabled.

Operational notes

  • The admin panel stores only the public Tag ID, not a secret key.
  • One active Google Tag provider controls one Tag ID.
  • Configuration changes are not instant because the public bootstrap API is cached for 60 seconds.
  • If the Tag ID is incorrect, the frontend may still inject the script, but Google will not receive events correctly.
  • Full custom HTML snippets and additional scripts are not supported through the Tag ID field.

When to involve the technical team

Contact the technical team if:

  • Google Tag is missing from the Providers section.
  • The tag does not appear in page HTML or network requests after more than 1 minute.
  • Google Tag Assistant reports an installation error.
  • Multiple independent Google tags need to be connected at the same time.
  • Consent mode, enhanced conversions, or custom ecommerce events need to be configured.