TagPipes + Google Ads
Report on Google Ads performance next to your website analytics, and send server-side conversions back to Google Ads.
Lens: Google Ads reporting
Lens reads your Google Ads reporting data into tables in your own workspace, where it sits next to your analytics in boards and shareable reports. Lens only reads: it never creates or edits campaigns, ads, keywords or budgets.
One Google connection is shared by several TagPipes modules, so the Google sign-in screen asks for more than reporting access. Lens uses it only to read reports.
How you set it up
- Connect your Google account in Settings > Security & Access (Google sign-in).
- In Lens, open Data Tables, click + New Table and choose Google Ads.
- Pick the ad account, and a manager (MCC) account ID if you use one.
- Pick a predefined report or write a custom Google Ads query (GAQL).
- Set the sync schedule.
| What it reads | Predefined reports for campaigns, ad groups, ad copy and landing pages, keywords, search terms, geography, devices, conversion actions, account settings and campaign budgets. A custom GAQL query covers anything else. |
|---|---|
| Grain and history | Daily rows. Currency and timezone come from the ad account. Each sync re-reads the last 7 days so late conversions settle. The first backfill is 90 days by default and can be set longer. Account settings and budgets refresh in full. |
| Limits | Daily grain only, no hourly. One ad account per table; combine accounts with a Union table. |
| Plan | Included with every Lens plan. |
Documentation: Google Ads source · Create a table · Sync data
Echo: Google Ads conversions
Echo sends your website conversions server-side to Google Ads conversion actions through Google's Data Manager API.
How you set it up
- Connect your Google account in Settings > Security & Access. Connections made before August 11, 2026 need to be reconnected to grant the Data Manager permission.
- In Echo, open Destinations, click Add Destination and choose Google Ads.
- Enter the customer ID, a manager (MCC) ID if you use one, and the conversion action ID.
| What it sends | Conversions with value, currency and order ID. Google uses the order ID to remove duplicates. Events go in batches of up to 500. |
|---|---|
| Match keys | A Google click ID (gclid, gbraid or wbraid) or a user identifier. |
| Limits | Every event needs a click ID or a user identifier, or it is dropped. Echo does not hash email or phone for Google Ads, so those must arrive already hashed. No consent field is sent to Google; consent works by holding events back. |
| Plan | Included with every Echo plan. Counts as one destination. |
Documentation: Echo destinations
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 Google Ads next to the rest of your data.
Sign up and connect Google from Settings > Security & Access, or ask us for a walkthrough first.
Already have an account? Log in.