Analytics and event setup

Package scope • One existing website and one platform: Yandex Metrica or Google Analytics 4. • Up to five agreed events on existing website elements, with basic enquiry-source parameters where available. • One counter or property in the client’s account and one available implementation method. What you receive • An installed counter and configured events. • An event table covering the action, event name, trigger and verification method. • Examples of event verification in an available diagnostic interface and a short handoff. What we need to begin • The website address, the actions to measure and working website and analytics-account access. • An agreed analytics notice or consent approach already exists on the website; collection settings are confirmed with the owner. Timing Usually 2–3 business days after scope confirmation and receipt of working access. Completion criteria A controlled trigger is demonstrated for each agreed event without duplicate firing in the reviewed scenario. Blocking tools, browser settings and visitor choices may limit collection. Not included • Ecommerce measurement, cross-channel attribution, CRM, advertising accounts, BI dashboards and server-side tracking. • New forms, website architecture changes and legal assessment of data-processing rules. • Advertising spend, paid plans and ongoing support. Quantity and payment One unit covers one agreed package for one website or project. Multiple units do not automatically expand the scope of one package. This is a one-time service with a fixed scope, paid in advance. Before work starts, we agree on the website or project, scope, technical compatibility, required material and start date. Third-party licenses, subscriptions and additional work are charged separately only if agreed; they are not purchased automatically.