Using the tag server Preview¶
The Google Tag Manager preview mode is how you test tags before publishing. On server-side containers it depends on a preview server — a service separate from your container.
AdPulse runs that preview server in a shared way. You do not need to configure anything: it is already available.
Preview server address
The shared preview server is https://edge.turbo-ssl.com. You never enter that address anywhere — the container receives it automatically. It differs from the tag server URL, which lives at https://cdn.turbo-ssl.com/c<id>/.
AdPulse dashboard in Portuguese
The AdPulse dashboard interface is only available in Portuguese. The labels quoted in the steps below are exactly what you see in the product.
How to open¶
- Open Google Tag Manager.
- Select the server-type container.
- Click Visualizar (Preview) in the top bar.
- Enter your site's URL when prompted.
GTM connects to the preview server, opens the debug panel and shows the events and tags firing in real time.
Visualizar comes from GTM, not from the AdPulse dashboard
The button lives in Google Tag Manager. The AdPulse dashboard has no equivalent preview button — it shows the container status and usage.
Why the preview is a separate server¶
Your container serves production traffic: the requests from your site, the events, the published tags. The preview, instead, serves the debugging session — a separate conversation between GTM and the server, with test tags that do not affect real traffic.
That is why the two addresses are different and must not be swapped:
| Purpose | What to do |
|---|---|
| Serve your site's traffic | URL do servidor de tags in the container settings |
| Debug tags in test mode | Nothing to configure — the GTM Visualizar uses the preview server automatically |
If you paste your container URL in the wrong place, debugging stops working while production traffic continues normally — the symptom is confusing precisely because of that.
What the debug panel shows¶
With the connection open, you see:
- The events arriving at the server.
- Which tags fired for each event.
- The data sent by each tag.
- Firing errors, when there are any.
It is the same GTM debug panel as always — the difference is that execution happens on the server, not in the browser.
Troubleshooting¶
| Situation | What it means | What to do |
|---|---|---|
| Preview mode does not connect | The container is not yet Ativo, or the GTM setup is incomplete. | Check the status under Server GTM → Contêineres. |
| The preview opens but no tag fires | The tags are not published on the server container. | Publish the container in GTM and try again. |
| Tags fire in the browser but not on the server | The tag is installed on the web container, not on the server. | Make sure you are editing the server-type container. |
| The preview works and the site receives no events | The tag server URL in GTM is wrong or the site was not updated. | Review How to get the tag server URL. |
| The debug shows someone else's events | You opened the preview with another session's debug link. | Open a new preview mode from GTM. |