metrion

Sync set-up & information

Understanding Syncs

Creating a Sync

Sync settings

Conversion goals

The Flow tab

Reading Sync logs

Backfilling a Sync

Deleting a Sync

Subscription

Your subscription

Comparing plans

Managing billing details and invoices

General information

General description of the Metrion platform

What is Metrion

How Metrion is organized

The Launchpad dashboard

Understanding Installations

Understanding Reporting

Filtering report data

The conversion detail panel

Front-end and server-side tracking statuses

Workspace details

Team members

Switching between workspaces

Destinations

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

Installation set-up & information

Creating an installation

Installation settings - Generic

Choosing your CMP

Choosing your CMS

The Installation key and secret

Managing domains

The domain filter

Connecting a destination

Managing destinations

Deleting an installation

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

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.