Every platform TagPipes connects to, in one place: where your events can go, where your data can come from, and which tag and consent platforms we speak natively.
Echo routes consent-compliant events to every major ad and analytics platform through their official server-side APIs, plus TagPipes Lens or any HTTP endpoint you control. Consent, Global Privacy Control and bot filtering are applied per destination before dispatch. All destination types are included on every Echo plan, with no per-destination fees.
Lens builds unified tables, boards and shareable reports from analytics platforms, ad accounts, event streams, files, warehouses and storage you own. Three of the seventeen are composite types that build a table out of tables you already have. Platforms without a dedicated connector, Meta and TikTok among them, come in through the REST API source or Airbyte.
AutoTag generates GTM tags, triggers, and consent settings for the platforms below, including pre-built templates for common e-commerce and restaurant stacks. Auditor validates pixels from all major platforms, and any conversion pixel beyond them.
TagPipes ships its own consent management platform in Shield, and works with the vendors below where you would rather keep the one you have. AutoTag wires consent settings for each of them, Echo reads consent state per destination before any event leaves the server, and Pulse validates that your banner's promises match your site's behavior.
Echo's custom destination reaches any HTTP endpoint, and Lens's API source can poll any JSON REST endpoint. If your stack is unusual, tell us about it.