MetaRouter Server-Side Tag Management

What MetaRouter Server-Side Tag Management is

MetaRouter Server-Side Tag Management collects first-party customer data on the server and routes it to advertising, marketing, and analytics vendors. For common destinations, this can reduce or eliminate client-side tags. A single code library supports page, behavioral, and identity data, including third-party identifier resolution. Before routing, customers can map, transform, and filter incoming parameters. Sync Injector adds addressable cookie-based IDs and URL decorators to event streams for third-party identity resolution. Listed destinations include Google Analytics, Google Ads, Meta, Amazon Redshift, BigQuery, Braze, Salesforce, and Snowflake. Organizations can deploy the service in their own cloud or use a single-tenant MetaRouter-hosted environment on Google Cloud, AWS, or Azure. Self-hosted customers are responsible for infrastructure resource costs, which MetaRouter estimates from expected event volume and integrations. Its custom enterprise plan is scoped to use cases, event volume, and infrastructure footprint, with no per-user or per-profile fees; pricing is on request. The product supports websites, server-side tagging, and consent management. MetaRouter says an independent auditor examined its controls against SOC 2 Type II Trust Services Principles for Security and that it conducts regular third-party security audits.

Who it suits

MetaRouter is aimed at organizations handling first-party customer data across advertising, marketing, and analytics destinations. The company names Fortune 500 enterprises and retail media networks, with marketing technology, IT, engineering, and retail media leaders among buyers.

Limits

The custom enterprise plan is scoped to use cases, event volume, and infrastructure footprint. Self-hosted customers are responsible for infrastructure resource costs.

Getting started

1. Visit the MetaRouter Server-Side Tag Management website.
2. Request pricing for a custom enterprise plan.
3. Choose customer-cloud deployment or a single-tenant MetaRouter-hosted environment.
4. For self-hosting, plan for infrastructure resource costs based on anticipated event volume and integrations.
5. Request an OAuth 2.0 client ID and secret to use the Orchestration API.

Verdict

MetaRouter centralizes server-side collection and routing, with controls for shaping data and options for hosting. Organizations should account for custom pricing and infrastructure costs for self-hosted deployments.