Skip to content
BonicBD
বাংলা হোম Sign in Get Started
Documentation · Task guide

Get started with BonicBD server-side GTM

Follow the documented setup path from prerequisites to event validation. Exact container values and snippet URLs are shown in your BonicBD account.

Before you begin

  • A domain you control and access to its DNS settings.
  • A Google Tag Manager account with Web and Server containers.
  • Access to the BonicBD dashboard for the container you are configuring.

1. Choose a plan and create a container

Choose a plan based on your expected monthly request volume. The current free trial is limited to 5,000 requests and can be used to check the setup before choosing a paid plan.

Review plans and request limits

2. Prepare the GTM Server container

Create or select the Server container for this setup. Use the container configuration and field values provided in your BonicBD dashboard; do not copy settings from another client or an old guide.

3. Connect your tracking domain

Choose a subdomain on a domain you control, then create the CNAME record shown in the custom-domain guide. Wait for DNS verification in the dashboard before continuing.

Configure the custom domain

4. Install the generated snippets

After the domain is verified, open Dashboard → Setup Guide and copy the snippets for this container. The current guide describes a head snippet, a body noscript snippet, and an integrated tracker script.

  • Place the head snippet at the top of the site’s <head>.
  • Place the noscript snippet immediately after the opening <body> tag.
  • Install the integrated tracker script as directed by the dashboard.
Note: Use the generated snippets for the intended container. Do not publish credentials, access tokens, or customer data in a public page or support message.

5. Validate the event path

Check each stage separately so a collection issue is not confused with a destination-platform reporting delay.

  1. Use GTM Preview to confirm the expected web tags fire.
  2. Check BonicBD real-time analytics to confirm the request reaches the server container.
  3. Use the destination platform’s event diagnostics or DebugView to check forwarding.

Open the missing-events troubleshooting guide

Reviewed against the BonicBD documentation source on 2026-10-22. Dashboard labels can change; follow the current setup guide shown in your account.