metrion

Cookies

In order to track sessions and conversions on your website, the Metrion plugin places two first-party cookies on your domain. These cookies distinguish the sessions and users on your website. 

Since these cookies will be new to your Consent Management Platform (CMP), these should be acknowledged in the Cookiebot setup. Below are the instructions on how to acknowledge these cookies.

Add Metrion cookies to Cookiebot (by Usercentrics) setup

Channels

Before adding the Meta destination in Metrion, ensure that you remove or deactivate any existing tags or integrations that send data to the same Meta Pixel you intend to use. If multiple sources send the same events to the Pixel (e.g., both Shopify's native integration and Metrion), it can result in duplicate event firing, leading to inaccurate or inflated reporting.

Metrion’s Meta destination includes both the Meta Pixel and Conversions API, which allows Meta to deduplicate events only if both signals are sent from the same source and include the necessary event identifiers (like event_id). However, if multiple platforms send the same event independently, Meta cannot reliably deduplicate them, and this may degrade your ad performance and attribution accuracy.

Add a Meta destination

Before adding the TikTok destination in Metrion, ensure that you remove or deactivate any existing tags or integrations that send data to the same TikTok Pixel you intend to use. If multiple sources send the same events to the Pixel (e.g., both Shopify's native integration and Metrion), it can result in duplicate event firing, leading to inaccurate or inflated reporting.


Add a TikTok destination

Before adding the Google Ads destination in Metrion, note that Metrion creates new conversion actions in your Google Ads account. This means you don’t need to remove or deactivate existing Google Ads tags or integrations — they can safely coexist. Each Metrion destination will send events to its own unique conversion actions, preventing any overlap or duplicate event reporting.

Add a Google Ads destination

Getting started

Welcome to Metrion — your all-in-one platform for managing server-side tracking across channels. With Metrion, you can seamlessly connect user data from your domains (like websites or online stores) to destinations such as Google Ads, Meta Ads, and more. Our platform gives you full control over how your data is collected, synced, and monitored — all within a structured workspace system.

In Metrion, an installation is the core unit that connects your data ecosystem. It represents a specific setup combining:

One or multiple domains (the source of your user data — e.g., your website). One or more destinations (like Google Ads or Meta Ads). Each workspace can have multiple installations — for example, if you're managing multiple clients or projects, each can live in its own installation for clean separation and control.

Create an installation

Getting started with Metrion doesn’t require choosing a subscription right away. When you sign up, you’re automatically placed on our free subscription, which allows you to fully configure your setup and sync up to 100 conversions to your chosen marketing channel. This means you can create an installation, add domains and destinations, and even set up a sync before committing to a paid subscription — giving you the flexibility to explore the platform and see how everything works.

Choose a subscription

To make integration easy, we offer dedicated plugins for popular e-commerce platforms like Shopware, Shopify, Magento, Lightspeed, and WooCommerce. Installing the right plugin allows Metrion to capture accurate data directly from your server, ensuring better tracking, privacy compliance, and performance.

Depending on the platform you use, follow the relevant instructions below to access your plugin.

How to find and install your Metrion plugin


A sync is the connection that sends your conversion data from your website (or other domains) to a destination like Google Ads or Meta Ads. It links the data you've collected with the channels where you want that data to be used — for example, to improve ad performance, reporting, or attribution. Each sync defines what is being sent, where it’s going, and how it should be handled. You can create as many syncs as needed, depending on your domains, destinations, and the goals you’re tracking.

Create a sync

This glossary provides clear definitions of key terms used throughout our articles and documentation. It is designed to help readers—whether new or experienced—understand specific terminology, abbreviations, and concepts relevant to our work. Each entry includes a concise definition along with any relevant context to aid comprehension.

Glossary of Terms and Definitions

To ensure accurate and reliable conversion tracking in your campaigns, your Google Ads account must be correctly configured. This includes enabling auto-tagging, accepting customer data terms, and applying settings for server-side tracking, lead conversions, and more. In this article, we’ll guide you through all the essential Google Ads configurations required to make your tracking setup fully compatible with our platform—so you can measure results with confidence and optimize performance effectively.

Essential Google Ads configuration for accurate conversion tracking

More information about installing plugins into your website or store.

External Plugins

To get started, Metrion will need collaborator access to your Shopify store.
If you're using Shopify's updated checkout extensibility features, our code should be implemented through a custom pixel within the Customer Events section.

Providing access to Shopify's Customer Events

To get started, BigCommerce needs the Metrion app. You can find this in the BigCommerce apps and integration page. 

Installing Metrion on a BigCommerce store

Google Analytics

A Google Analytics 4 (GA4) Data Stream is the source of incoming data from your website or app into your GA4 property. Creating a web Data Stream allows you to collect website activity and access your Measurement ID.


Create a Google Analytics datastream

In Google Analytics, an API secret is required when using the Measurement Protocol (v2) to send data directly to GA4. This secret is part of a security mechanism that ensures only authorized sources can send data to your property. It helps protect your analytics data from unauthorized or malicious input, ensuring that only systems with access to your API secret can submit valid tracking events. Essentially, it's like a password that secures your data pipeline.