Skip to content
Integrations · Google Tag Manager

The least advanced of the four, and said as such.

Today you can connect a Google Tag Manager account to Plireo, with a permission that can neither edit nor publish anything. Reading the published container comes next. This page sets out where the integration stands and where it is going.

Four steps, in order

From a connection to a publication, each step earns the next.

A tag container runs on every page of a site. A mistake there is seen by every visitor, which is why the order below is not negotiable.

  1. 01Connect, read-onlyThe account connects with a permission that cannot edit, publish or manage users. An approver assigns one container to the advertiser.In progress
  2. 02Read the published versionThe version live on the site, turned into a map of the measurement tags: what fires, on what, and what is sent. In development.In progress
  3. 03Prepare a change, with approvalA tag change, written as a before and after and approved, as for an advertising change. Planned for the first version.
  4. 04Publish, with a separate approvalPutting a version live is a second decision, approved separately. Planned for the first version.

The two last steps have no status because they are not in Plireo's capability registry yet: nothing of them exists.

Why read a container at all

The conversion you optimise for is defined in a place nobody looks at.

The figure a bidding strategy optimises towards starts as a tag: a piece of configuration that decides when a conversion is sent, with which value, to which platform. In most organisations the people who decide budgets have never opened it.

Reading the published container lets an analysis say more than “conversions fell”: which tag sends the purchase event, whether it still exists in the live version, and when that version was published.

Custom code in a container can contain anything. Plireo's reading is designed to look in it for calls to advertising pixels only, and then to keep a fingerprint and a length, not the code.

Where this stands today

  • Google Tag ManagerAccount connectionIn progress
  • Google Analytics 4Measurement configuration and event countsIn progress
  • ApprovalsApproval bound to the exact change, with a written reason when a warning is openIn progress

Every capability and its status →

Early access

Be among the first to use Plireo.

Plireo is in pre-launch. Request early access to be told when it opens, or apply to take part in private testing. Access opens gradually, so a request does not mean immediate access.

Paid plans open once the Google Ads, Meta, GA4 and GTM integrations are operationally validated.

Request early access