Google Tag Manager logo

Google Tag Manager

Data and analyticsIntegration

About Google Tag Manager

Google's tag container. Bask loads your container on your patient portal, Studio sites and flows, and older questionnaires and landing pages. Flows and older questionnaires also push step and checkout events to its dataLayer, so you manage tags in Google rather than in Bask.

How Bask works with Google Tag Manager

  • Bask loads your container on every published page once the integration is connected.
  • Intake flows push a step_viewed event to the dataLayer on each screen, with flow_slug, step_slug and step_id as top-level fields.
  • A completed purchase pushes a purchase event with flow_slug and event_id, plus transaction_id, currency, value and items under ecommerce.
  • Bask clears the previous ecommerce value before each purchase event and drops any field whose name starts with a dollar sign.
  • The purchase event_id matches the ID Bask sends directly to Meta and TikTok, so a browser tag that passes the same ID lets each sale be counted once.

Set up Google Tag Manager

  1. Open App Store in your Bask sidebar, choose Google Tag Manager, then choose Connect.
  2. Paste your container ID from the top of your Tag Manager workspace. It starts with GTM- followed by 6 to 8 letters or numbers.
  3. Choose Connect in the save bar. Bask asks for the ID only and does not import a container file or template.
  4. Create your tags and triggers in Tag Manager and publish them. Connecting does not create any tags.
  5. Open Tag Manager preview against a published site and go through an intake flow to confirm that step_viewed appears.
  6. Complete a test purchase and check its ecommerce details before you publish tags that report sales.

What you need for Google Tag Manager

Your container ID (GTM-XXXXXX). Tags are created and published in Tag Manager, not in Bask.

Good to know

  • Use a Data Layer Variable such as step_slug to read the current step, and ecommerce.value to read the purchase amount.
  • Events do not all carry a session ID or patient ID, so build triggers around the event name and the fields each event provides.
  • Disconnecting stops Bask loading the container. The container stays in Tag Manager, and a container you installed separately in custom code has to be removed there.

Who it is for

Usually set up by a marketing agency or developer with permission to manage integrations in Bask. Tag Manager lets your agency add website tools without a separate Bask connection for each one.

How it installs

Installed with keys you paste in