Write the event taxonomy
A naming convention, an event list and the properties each event carries, agreed with product and marketing before any code changes.
4.9 / 5PostHog setup built around your real questions.
A PostHog setup that starts with the decisions you need to make, then tracks exactly what answers them.
Selected work, in motion.
The experiences behind the journeys teams measure.Autocapture is not a plan.
Most teams switch PostHog on, collect thousands of events and still cannot answer a basic question.
BeforeAfter
Thousands of autocaptured clicks, no clear signup countA short list of named events tied to decisions
Marketing site and app counted as separate peopleOne person profile from first visit to paid account
Ad blockers hiding part of your trafficEvents routed through your own subdomain by a reverse proxy
Nobody sure which numbers are rightEvery event checked against the plan before launch
What's included
The foundation, done once.
Implementation decides the quality of every report you will build later. We treat it that way.
Install across site and app
posthog-js on the website, SDKs in the product and backend, with person profiles and group analytics set up where accounts matter.
Route around ad blockers
A reverse proxy on your own subdomain, so blockers do not drop PostHog requests and your counts stay close to reality.
Validate the data
Each event tested in the live events view and against the plan, with gaps fixed before any dashboard is built on top.
Security, by consideration.
Trust is part of the build.
For your PostHog project, we consider event collection, personal data, workspace access and ingestion endpoints as part of one connected build.
See our approachConnected systems. Considered safeguards.
Changes you can trace.
GitHub workflows, peer review and dependency checks bring decisions into the release process.
Protected in transit.
Certificate configuration, HTTPS and secure headers help protect the path between your users and your systems.
Intelligence with limits.
Scoped tool access, validated inputs and human approval where automated actions carry consequences.
Plan first. Then install.
Nothing gets installed until the tracking plan is signed off.
- 01
Map the questions
We list the decisions your team needs data for and turn them into events and properties.
- Question list
- Event taxonomy
- Tracking plan
- 02
Install and configure
Snippet, SDKs, reverse proxy, identity calls and consent settings set up on every surface.
- PostHog project setup
- Reverse proxy
- Consent configuration
- 03
Validate and train
We check live data against the plan and show your team where the answers live.
- Validation report
- Starter dashboards
- Team training
Built for what’s next.
Built to driveMore memberships.
Built to driveBetter-qualified leads.
Built to driveMore qualified candidates.
Built to driveMore enquiries.
Built to driveMore qualified demos.
Built to driveMore workplace demos.
Built to driveMore business accounts.
Built to driveMore free trials.
Built to driveMore building owners.
Built to driveMore free sign-ups.
Private Villas Mexico
Built to driveMore direct bookings.
Built to driveMore committed players.
Built to driveMore returning customers.
Built to driveMore meaningful demos.
Built to driveBetter talent connections.
Built to driveMore course creators.
Built to driveMore product discovery.
Built to driveMore sign-ups.
Trusted across our practice
Working together. In their words.
Independent reviews. Long-term working relationships.
“After a website (re)launch, they are also always accessible and happy to help. I highly recommend everyone who is looking for a new and more stable website in Webflow, to work with Stega!”
“We’ve been working with Stega & Gabriel for the last two years. Cannot recommend them enough. They’re responsive, professional & an asset.”
“Stega Creative team not only understood our needs and vision for the websites, but they also came up with improvements.”
PostHog implementation questions.
A few things worth discussing before your PostHog setup takes shape.
Should we use PostHog autocapture or custom events?
Use both, with custom events for anything a decision depends on. PostHog autocapture is useful for exploring clicks and pageviews you did not plan for. Signups, purchases and key product actions deserve named custom events with fixed properties, because autocaptured element names break when the design changes.
How do we set up PostHog with cookie consent?
PostHog can wait for cookie consent before storing anything in the visitor's browser. We connect your consent banner to PostHog's opt-in and opt-out calls, or keep its storage in memory until consent is given. The right setting depends on where your visitors are and what your legal team approves.
Does PostHog need a reverse proxy?
PostHog does not need a reverse proxy to work, but most setups benefit from one. Ad blockers drop requests sent straight to PostHog's domain, which can hide a noticeable share of events. A proxy on your own subdomain keeps those events, and we set it up on Cloudflare, Vercel or your existing hosting.
How long does it take to write a PostHog tracking plan?
A marketing site with a handful of conversion events sits at the short end. A product with several apps, a backend and group analytics for B2B accounts takes longer, mostly in the tracking plan and validation steps.
Revamp today.The 
way.
Your ambition. Our collective craft.
Strategy, design and technology, working as one.