TagPipes + Google Analytics 4
Bring GA4 reports into Lens next to your ad and order data, and send server-side events to GA4 with Echo.
Lens: GA4 reporting
Lens reads reports from your GA4 property through the GA4 Data API and stores them as tables in your own workspace. It does not change anything in GA4.
How you set it up
- Add the TagPipes service account as a Viewer on your GA4 property. The setup screen shows the address to add.
- In Lens, open Data Tables, click + New Table and choose GA4.
- Enter the GA4 property and pick the dimensions and metrics you want.
- Set the sync schedule.
| What it reads | Any GA4 dimensions and metrics, including your property's custom dimensions and metrics, with optional filters. |
|---|---|
| Grain and history | Daily, or hourly by adding the hour dimension. Each sync re-reads the last 7 days. The first backfill goes back up to 400 days, within GA4's own data retention. |
| Limits | Up to 9 dimensions and 10 metrics per table (a GA4 API limit). GA4 thresholding and sampling apply as they do in GA4. For event-level or unsampled data, use the BigQuery source on your GA4 export. |
| Plan | Included with every Lens plan. Hourly schedules need Enterprise or the hourly sync add-on. |
Documentation: Create a table · Sync data
Echo: GA4 Measurement Protocol
Echo sends events server-side to your GA4 property through the Measurement Protocol, alongside or instead of browser tags.
How you set it up
- Create a Measurement Protocol API secret in GA4 admin.
- Store the Measurement ID and API secret as a connection in Settings > Security & Access.
- In Echo, open Destinations, click Add Destination and choose GA4.
| What it sends | Events with the GA4 client ID and session ID from the visitor's GA cookie, page fields, ecommerce fields and items, and the visitor IP for location. |
|---|---|
| Consent | Consent signals go into GA4's consent fields, which you can switch off per destination. Bot traffic and events without the consent you require can be held back. |
| Limits | Events without a GA4 client ID are dropped, because GA4 needs it to join the session. GA4 accepts Measurement Protocol hits whether or not it records them, so a successful send is not proof GA4 counted the event. GA4 parameter limits are reported, not enforced. GA4 sends are not retried immediately; failures are held and replayed. |
| Plan | Included with every Echo plan. Counts as one destination. |
Documentation: Echo destinations · Consent and bot gating
What every Echo destination does
- A per-destination event filter decides which events are sent.
- You choose the consent categories an event needs before it is sent. Global Privacy Control signals and bot traffic are handled per destination.
- Failed sends are retried, then held and replayed automatically.
- There is no "send a test event" button yet, and Echo does not yet compare what it sent with what the platform recorded.
More on the module: Echo product page.
How your data is handled
- Credentials you add are stored in Settings > Security & Access, and you can remove them there at any time.
- Each company sees only the data from the accounts and sources it connected.
Read the Privacy Policy and the Terms of Service.
TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.
Put GA4 next to your ad spend and orders.
Sign up and add your GA4 property in Lens, or ask us for a walkthrough first.
Already have an account? Log in.