How to install and configure the WordPress plugin

Previous Next

How to install and configure the WordPress plugin

The AdPulse sGTM plugin makes your WordPress site serve the Google Tag Manager scripts from your own domain and forward the requests to the AdPulse tag server. That keeps the loading first-party instead of depending on a third-party domain.

Plugin interface in English

The plugin dashboard is only available in English. The field names quoted below are exactly what appears in WordPress. The AdPulse dashboard, in turn, is only available in Portuguese — its labels are quoted as they appear in the product.

Prerequisites

  • A server container created in the AdPulse dashboard and with status Ativo.
  • The numeric ID of that container — it appears on the container page and in the integration instructions.
  • WordPress 5.8 or higher and PHP 7.4 or higher.

Step by step

  1. In the WordPress dashboard, go to Plugins → Add New → Upload Plugin and upload the ZIP downloaded from wordpress.org/plugins/adpulse — or search for AdPulse sGTM in the directory and click Install Now.
  2. Click Activate.
  3. In the WordPress side menu, open AdPulse → Settings.
  4. Check Enable AdPulse sGTM integration.
  5. In Container ID, enter the numeric ID of your container — for example, 12345.
  6. Click Save Settings.

Where the container ID is

In the AdPulse dashboard: Server GTM → Contêineres → click the container → the ID appears at the top of the page, next to the highlighted ID do contêiner.

What starts happening on your site

With the plugin active, WordPress serves the GTM script at https://<your-site>/c/gtm.js and forwards everything that arrives on /c/ to the AdPulse tag server, on the container you configured.

The settings page itself shows the resulting URL in the Status section, on the GTM URL line.

Configuration reference

Field Default Description
Enable AdPulse sGTM integration disabled Turns on the injection of the GTM scripts into the pages.
Container ID empty Numeric ID of the server-side container in the AdPulse dashboard.
Proxy Path /c/ Path on your site where GTM is served.
Proxy Timeout 15 Maximum time, in seconds (1 to 60), to wait for the tag server response.
Include visitor IP address when consent is granted enabled Sends the visitor's IP to GTM only when consent has been granted.

The Status section on the same page shows the plugin state (Active/Inactive), the installed version, the configured ID and the GTM URL.

Changing the proxy path

If you change Proxy Path, the WordPress URL rules need to be regenerated — they are updated when the plugin is activated and deactivated. After saving the new path, go to Settings → Permalinks and click Save Changes without changing anything, or deactivate and reactivate the plugin.

Troubleshooting

Situation What it means What to do
"Plugin is enabled but no Container ID is set." The plugin is on, but with no container ID. Enter the Container ID in AdPulse → Settings and save.
Warning "Container ID not configured" or a 400/500 error page on the /c/ path The plugin received a request with no container configured. Confirm the ID and save the settings.
The GTM script does not load on the page The plugin is inactive or the proxy path changed without regenerating the rules. Activate the plugin and regenerate the link rules (see above).
The tag server responds slowly or times out The wait time is too short for your region or your theme. Increase Proxy Timeout (up to 60 seconds).
GTM does not appear on certain pages The plugin injects the script into the pages generated by WordPress. Confirm the page is served by WordPress and not by a pre-rendered static cache.
The ID is right but nothing is tracked The container is not yet Ativo in the AdPulse dashboard. Check the container status in Server GTM → Contêineres.

Dashboard URL

The plugin shows a link to the AdPulse dashboard. The current address is app.adpulse.com.br.

Next steps