Heap setup

Heap setup is a one-off implementation project: we connect Heap with autocapture (it collects interactions itself — clicks, submits, views), set up user identification, define key 'defined/virtual events' on top of autocapture, properties, basic funnels, retention and dashboards. Heap's main plus is retroactivity: you can define an event now and analyze it on already-collected data without waiting for new tagging. Honestly about autocapture, this matters: autocapture saves time, but 'everything will count correctly by itself' is a myth; for data to be meaningful key events still need to be defined and named in human terms, otherwise you get a pile of unnamed clicks; the quality of conclusions depends on this tagging (garbage in, garbage out). Honestly about requirements: access to code/the tag manager is needed to install the snippet. Honestly about the essence: this is collection and basic-report setup, NOT product analysis-conclusions and NOT metric growth — Heap shows behavior, conclusions and improvements are yours or your analyst's; the implementation itself does not raise retention or conversion. Honestly about correlation: funnels/retention = what happens and correlations, not a proven cause. Honestly about the platform: Heap has a free tier with limits; full capabilities and volumes are a paid plan, billed directly by Heap, separate from our work; autocapture at high volumes = a lot of data, limits must be watched. Privacy: autocapture may collect too much (field input) — masking settings, consent and a policy are needed; the legal assessment is given by a lawyer, we do not guarantee compliance. Maintenance: when the product changes the event definitions need upkeep. An important boundary: this is Heap setup, not end-to-end web analytics (GA4/Metrica) and not the product analysis itself. For a simple brochure site Heap is overkill. Picture this: instead of 'we did not tag events and now there is no data for the past period' retroactivity lets you analyze behavior even in hindsight. The base price starts from 20,000 ₽ per project; it depends on the number of events and product complexity.

• You do not manage to tag all events in advance and lose data.
• Autocapture is on but events are unnamed and not analyzable.
• There are no meaningful funnels and retention by key actions.
• The web counter does not show product scenarios.

• Installing Heap with autocapture (via code or tag manager)
• User identification
• Defined/virtual events on top of autocapture
• Properties, basic funnels and retention
• Dashboards for key product metrics
• Masking settings for sensitive data
• Verification of tagging meaningfulness
• Handover of access and a short instruction

• Behavior is collected automatically, including for hindsight analysis
• Meaningful named events and funnels
• Retention and cohorts by key actions
• A base for product analytics (conclusions — separately)

• We clarify key scenarios and events; collect access to code/the tag manager
• We install Heap, set up autocapture, events, masking and dashboards
• We verify on real actions, hand over access and an instruction

• Does Heap autocapture remove tagging entirely?

  No. Autocapture collects interactions, but without defining and meaningfully naming key events you get a pile of unnamed clicks. For data to be useful key events still need setup — that is the main part of the work.

• Will Heap raise retention and conversion?

  No. Heap shows behavior, but by itself it does not raise the metrics. Conclusions and product improvements are made by you or an analyst; growth is separate work, not a consequence of the implementation.

• Is the Heap plan included in the price?

  No. There is a free plan with limits; full capabilities and large volumes are a paid plan, billed directly by Heap, separate from our setup. At high volumes autocapture generates a lot of data — we watch the limits.