If events are not arriving, check these in order. Most problems are one of the first four.
1. Is the container running?
The status badge should read Running. If it says Awaiting config, link the container to Google Tag Manager from its Container tab, or paste the config there (how). If it says Suspended, read the banner for the reason.
2. Is the config the right value?
If you linked the container with Connect Google, Taglinko builds the config itself. Choose Refresh from Google on the Container tab after you reset the environment in Tag Manager or switch containers. If you pasted it by hand, it must be the long provisioning string from the server container's Container Settings, not the short GTM-XXXXXXX ID.
3. Does your website point at the right URL?
The server_container_url in your web container must match a URL shown under Tagging Server URLs, including https://.
4. Did you publish the web container?
Changes in Tag Manager only apply to visitors after you publish.
5. Custom domain not working?
Confirm the CNAME points to the address shown in your container's Domains tab and has propagated. Taglinko refuses to attach the domain until DNS resolves correctly. See the domain guide.
6. Getting HTTP 400 responses?
See Debugging HTTP 400 Errors.
7. Are you out of requests?
Check the Monthly Requests card (details).
8. Ad blockers
Enable the Custom Loader power-up and use your own subdomain so your tracking requests look like normal first-party traffic.
Still stuck?
Email hello@taglinko.com with your container name, the time you tested and what you expected to see.
Still stuck?
Open a support ticket from your dashboard and include the container name.