Measurement set up properly and then answered in plain conversation: account, property and web stream created, a tag that only fires after the cookie banner is accepted, advertising pixels carrying real lead-conversion events, and matching privacy-notice wording in both languages. Afterwards the owner asks their own assistant how many enquiries came in last month and from where, without opening a dashboard.
What ports as-is
- The full access path (cloud project, admin and data API enablement, consent screen, desktop OAuth client, credential minting, the connector entry written into the agent config)
- The property and tag leaf (account, property and stream creation, the data-sharing options that arrive pre-ticked, time zone and currency defaults, reading the measurement id from real page text, installing the tag behind an existing consent gate)
- The analytics tool set exposed to the agent (standard reports, realtime, funnel, conversions, custom dimensions and metrics, property details, annotations, ads links)
- A troubleshooting table for the failures that actually occur
- A stated read-only boundary
What we build for you
- Their cloud project and OAuth client
- The property
- Stream and measurement id
- Consent banner integration and content-security-policy allowances
- The conversion events that matter to their funnel
- The privacy-notice wording
