What it shows
Go to Echo > Dataflow. The Event Flow panel draws the property's pipeline left to right in four lanes. The line under the title counts sources, destinations and how many destinations are gated, for example "1 source into 4 destinations, 3 gated for Demo Shop".
| Lane | What appears | Click it to |
|---|---|---|
| Containers | Each AutoTag project on this property, with its domain and container ID. With no AutoTag project, one node built from the property itself (title, URL and container ID if one is on file) | Open the AutoTag project |
| Sources | Each source that feeds this property, headed "Echo Browser SDK" for a JavaScript source, with the source title, version and app_id (the property ID the SDK stamps on every event) | Open the source |
| Echo Pipeline | One hub node: Echo, Collector and Processor | |
| Destinations | Each destination on this property, with its type and a status dot | Open the destination |
When connections exist, the Sources lane shows only the sources connected to a destination on this property. With no connections, every source in the company is shown, because every source feeds the collector.
Hover a node to highlight its path and fade everything else. Hover a chip on an edge to see that destination's full gate.
Dataflow is built from configuration. Without volume turned on, nothing on it is a measured count. Below 992px wide the lanes stack and the connecting lines are hidden.
Reading an edge
Each edge from Echo to a destination carries a chip and, where a gate applies, glyphs and a dashed line.
| Mark | Meaning |
|---|---|
| All events | The destination has no event filter, so every event reaches it |
| 3 events | The destination forwards only the three event names in its filter |
| Padlock | Consent required |
| No-entry sign | GPC suppresses: events carrying Global Privacy Control are not sent |
| Gear | Bot traffic excluded |
| Dashed line | Gated: at least one of the three rules above applies |
| Grey dot, faded node | The destination is disabled |
The hover card lists the destination title, the events it forwards, the required consent categories (or "none"), GPC ("suppress" or "ignore"), bot traffic ("excluded" or "forwarded") and status. These are read from the same settings Echo deploys, so the diagram matches what is live. See Consent and Bot Gating for how the gate decides.
Show volume
Click Show Volume to add event counts. Pick 24h, 7d (the default) or 30d; click Hide Volume to go back. Volume is a separate page load, so the plain diagram never waits on it.
With volume on:
- The chip shows the number of events sent in the window (UTC), rounded, for example
74.6k. A red figure is events the gate suppressed before sending. - Line thickness is relative to the busiest destination, not an absolute scale.
- The hover card adds "Sent: X of Y received", plus unmatched, errors and suppressed counts by reason when they are above zero.
- An edge reading "-" emitted no counts in the window. That is not the same as zero traffic: counts only exist once traffic reaches the processor.
If the counts cannot be read, a banner says "Volume is unavailable" and the diagram stays configuration only. It never shows zeros in their place.
Limits
- Which container loads which source is set inside the container and is not recorded by TagPipes. With several sources, container-to-source links are drawn as a fan, and a note under the diagram says so.
- When the property has more than one AutoTag project, each container node shows its numeric container ID instead of the public
GTM-ID, because the public ID is recorded per property, not per project. - If the AutoTag lookup fails, the Containers lane falls back to the property node and a note says so.