Integration

Zembula + Google Analytics

The Google Analytics Data API returns aggregated rows, not single-person records, so Zembula can read item and transaction data for your whole property. Each read is a report on one Analytics property.

It's our business to grow yours

Book a demo

What Zembula can read from Google Analytics

Google Analytics reports users, sessions, ecommerce items and revenue, and Zembula can read four kinds of that data through the Data API. Ecommerce items give views, purchases and revenue for each item, found by item ID inside one property. Ecommerce transactions give the purchase totals for each transaction, found by transaction ID. User metrics give active users and the custom dimensions scoped to a user, found by the property ID.

Traffic source gives the session source and medium. Every read is a report on one property. The reads return aggregates, so the data describes groups of people. It does not describe one person, and no per-person lookup by email appears in the docs.

Your team needs a Google Cloud project, plus a user or service account with access to the property. Quotas apply to the property. Google measures quotas in tokens, concurrent requests and server errors. Daily quotas refresh at midnight PST.

DataDetailLooked up by
Ecommerce item metricsItem views, purchases and revenue for each item.item ID, inside one property
Ecommerce transaction totalsPurchase revenue for each transaction.transaction ID
User metricsActive users and user-scoped custom dimensions.property ID
Traffic sourceThe source and the medium of each session.property ID

How the data arrives

  • API: Zembula can run a report on your property through the Data API, using a user or service account.
  • ESP merge tags: Your email service provider sends the item ID or transaction ID in the image URL.

What you need

  • A Google Cloud project, and a user or service account with access to your property.
  • An API key or a data export from Google Analytics. Zembula sets up the connection for you.
  • An item ID or transaction ID in your email service provider, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
Standard property: 200,000 Core tokens per day, 40,000 per hour, 10 concurrent requests. Analytics 360: 2,000,000 per day, 400,000 per hour, 50 concurrent.Each property has a fixed daily and hourly budget of report tokens.
Daily quotas refresh at midnight PST. Hourly quotas refresh within an hour.A spent quota returns at the next daily or hourly refresh.

Ideas for email

  • Rank your top items by item revenue in a best-seller block.
  • Match the email copy to the session source of your traffic.
  • Show purchase revenue for each transaction in a campaign report email.

Last checked: 19 November 2026.

Performance marketing dials, inside email. For the first time.

See how we do it by booking a demo.