Google Tag Manager

1 Add the template to your container

In Tag Manager open Templates → Tag Templates → Search Gallery, search for Pixelary and click Add to workspace. Or download template.tpl from the template’s repository and import it under Templates → Tag Templates → New → ⋮ → Import.

2 Create the base tag

New tag → Pixelary Conversion Tracking. Choose Load Pixelary (base tag), paste your site key and fire it on Initialization – All Pages. Initialization runs after Consent Initialization, where banners set their defaults, so Pixelary loads early and sees the right consent state.

Tag type   Pixelary Conversion Tracking
Action     Load Pixelary (base tag)
Site key   px_7hq2lm4x
Consent    Pass Google Consent Mode state to Pixelary: on
Trigger    Initialization - All Pages

The base tag loads https://cdn.pixelary.app/s/<site key>.js. Pixelary then tracks what you set up in the dashboard: page views, forms and clicks.

3 Track conversions

Add one more Pixelary tag per conversion with Action set to Send event. Pick a standard event and attach your existing trigger.

You don’t have to fire the base tag first. Each tag adds its command to a queue, and Pixelary runs the queue in order once it loads. If an event tag has its own site key, it also loads Pixelary; the script loads only once per page.

4 Publish and verify

Use Preview first: in Preview the template writes [Pixelary] messages to the browser console when a field is dropped or a tag fails. Then submit the container, open your site and check the Install page in the dashboard. It turns green when the first event arrives.

Send event fields

Send raw user data; don’t hash it. Pixelary normalizes and hashes every value separately for Meta, TikTok and OpenAI, and sends it only when the visitor has granted ad_user_data.

Identify user

Uses the same user data fields and attaches them to every following event on the page. Empty fields are skipped; if all of them are empty the tag sends nothing and still succeeds, so it is safe to fire everywhere.

Consent in Tag Manager

With Pass Google Consent Mode state to Pixelary checked (the default), each Pixelary tag reads ad_storage, ad_user_data, ad_personalization and analytics_storage, sends them before its own command, and keeps them in sync when the visitor changes their choice. Consent sent from GTM takes priority over Pixelary’s own detection of banners.

For the strictest setup, open each Pixelary tag’s Advanced Settings → Consent Settings, choose Require additional consent for tag to fire and add ad_storage. GTM checks consent when the trigger fires, so also fire the base tag on your banner’s “consent updated” event. That is safe: the script loads once.

Example: Purchase from the dataLayer

Your thank-you page pushes the order:

<script>
  window.dataLayer = window.dataLayer || [];
  dataLayer.push({ ecommerce: null });
  dataLayer.push({
    event: "purchase",
    ecommerce: {
      transaction_id: "ORD-1001",
      value: 49.90,
      currency: "USD",
      items: [{ item_id: "sku-1", item_name: "T-shirt", price: 24.95, quantity: 2 }]
    },
    customer: { email: "jane@example.com", phone: "+1 555 010 0000" }
  });
</script>

Create Data Layer Variables for ecommerce.transaction_id, ecommerce.value, ecommerce.currency, ecommerce.items, customer.email and customer.phone, and a Custom Event trigger for purchase. Then add a Send event tag:

• Event name: Purchase; Value, Currency, Content IDs from the variables;
• Order ID and Event ID: the transaction ID, the same one your backend uses if it sends Purchase too;
• User data: email and phone from the variables;
• Trigger: the purchase Custom Event.

Everything from GTM, including PageView

On the base tag check Disable automatic events. Pixelary then sends no page views, forms or clicks of its own on those pages. Add a Send event tag with PageView on All Pages and on a History Change trigger, and send forms and clicks with your own tags. Without this, a PageView tag next to automatic events would count every page twice.

Troubleshooting

What the template can access

The template doesn’t send requests or set cookies itself. Everything goes through the Pixelary script.

Commands the template sends

The template calls the same JavaScript API you can use on your site:

pixelary("source", "gtm", { template_version: "1.0.0" });
pixelary("config", { auto_events: false });
pixelary("consent", { ad_storage: "granted", ad_user_data: "granted", ad_personalization: "denied", analytics_storage: "granted" }, { source: "gtm" });
pixelary("track", "Purchase", { value: 49.9, currency: "USD", content_ids: ["sku-1"], order_id: "ORD-1001" }, { event_id: "ORD-1001", user: { email: "jane@example.com" } });
pixelary("identify", { email: "jane@example.com", external_id: "u_123" });

Consent banner

Pixelary sends nothing a visitor has declined. In the EEA, the UK and Switzerland it waits for the visitor’s yes before any pixel loads or any event leaves the page.

Pixelary reads these on its own, with no extra setup:

• Google Consent Mode v2
• IAB TCF 2.2
• Global Privacy Control
• Cookiebot
• OneTrust
• CookieYes
• Usercentrics
• Complianz
• iubenda
• Termly
• Osano
• CookieFirst
• Didomi (via TCF)
• Framer cookie banner

Another banner can pass its answer with one line of code. Consent & banners