Troubleshooting¶
Start with the container status under Server GTM → Contêineres. In most cases it already points at the cause.
Provisioning¶
| Situation | What it means | What to do |
|---|---|---|
| Stays in Pendente or Provisionando | The server is being created. | Wait a few seconds and refresh. Nothing needs to be restarted. |
| Stays in Erro | Provisioning failed. | The error message on the card says why. Fix it and create the container again. |
| "A configuração do contêiner GTM é obrigatória" | The configuration field is empty. | Paste the string following How to get the configuration string. |
| "A configuração é muito longa" | More than 64 KB were pasted. | Copy only the configuration field again, with no surrounding text. |
| Provisioning fails right after creating | The string was altered during the paste. | Copy again without editing and create a new container. |
| You cannot find "Provisionar servidor de tags manualmente" | The container in GTM is not a server-type container. | Create a server-type container in GTM first. |
Traffic and status¶
| Situation | What it means | What to do |
|---|---|---|
| Bloqueado status | The plan request limit was reached. | Upgrade or talk to support. See Usage, limits and billing. |
| Suspenso status | The container is temporarily disabled. | Talk to AdPulse support. |
| Error 403 when accessing the container | The container is Bloqueado, Suspenso or not Ativo. | Check the status under Server GTM → Contêineres. |
Error 404 on the /c<id>/ path |
The ID in the URL does not match an existing container. | Copy the URL again from the container page. |
| The site receives requests but the dashboard does not count them | The counters sync every 5 minutes. | Wait for the next sync before concluding anything. |
GTM¶
| Situation | What it means | What to do |
|---|---|---|
| GTM does not connect to the server | The tag server URL is wrong. | Review How to get the tag server URL. |
| Error 404 when opening the tag server URL | The /c<id>/ path is incomplete or wrong. |
Copy the full URL from the container page, including the trailing slash. |
| The Visualizar mode does not open | The problem is on the preview server. | See Using the tag server Preview. |
| Tags fire in the browser but not on the server | The tag is on the web container, not on the server. | Make sure you are editing the server-type container. |
Custom domain¶
| Situation | What it means | What to do |
|---|---|---|
| Stays in Verificando for a long time | The DNS has not propagated yet or the record is wrong. | Confirm the CNAME points to cdn.turbo-ssl.com. |
| "O DNS não foi confirmado em 48 horas" | The verification window expired. | Fix the record and click verify again. |
| "Informe um hostname, por exemplo trk.seusite.com.br." | The hostname is empty. | Type the full hostname. |
| A subdomain warning appears before the domain | You typed the root domain. | Use a subdomain — the root domain is not supported. |
| "O domínio X pertence à AdPulse e não pode ser conectado." | The hostname is under a reserved domain. | Choose a hostname on a domain you own. |
| "Conectar domínios personalizados exige um plano que inclua o recurso." | The current plan does not include the feature. | Talk to support. |
| Infinite redirect on the hostname | The hostname is behind a proxy with SSL in Flexible mode. | Use Full (strict) or turn off the proxy at your provider. |
The full walkthrough is in How to connect a custom domain.
WordPress¶
| Situation | What it means | What to do |
|---|---|---|
| "Plugin is enabled but no Container ID is set." | The plugin is on, but with no ID. | Enter the Container ID under AdPulse → Settings. |
| The GTM script does not load | The plugin is disabled or the proxy path changed. | Enable the plugin and regenerate the link rules. |
| The server responds slowly or times out | The wait time is too short. | Raise Proxy Timeout, up to 60 seconds. |
The step-by-step is in How to install and configure the WordPress plugin.
When none of this helps¶
Before contacting support, write down:
- The container ID and the current status.
- The error message shown in the dashboard, in full.
- The affected hostname, if it is a custom domain.
- What you have already tried.
These details already answer most of the initial questions and avoid a back-and-forth loop.