Set up Google Tag Manager
0/6Every tag after this one goes through Tag Manager, so the site's code is touched once and the tags are changed without a developer.
Create the account under the company's Google login
If the account belongs to a freelancer or an agency, you lose your tracking when they leave.
- Sign in to Tag Manager with the company's Google account.
- Click Create Account. Account Name: the company. Country: yours.
- Container name: your domain. Target platform: Web. Click Create, then Yes to accept the terms.
- Close the install window for now (the next check uses it). Click Admin > User Management > + > Add users.
- Enter a teammate's email, set Account permissions to Administrator and Container permissions to Publish. Click Invite.
Where: Tag Manager > Admin > User Management
You should see: two people with Administrator, at least one of them on your team, and the company account as the owner.
If it isn't there- You created it while signed in to a personal Gmail. Create a new account under the company login and move on from there.
- The invite is still pending: the teammate has to accept it from the email.
Install the container on every page
Tag Manager only works on pages that load it, so it goes in the layout every page shares.
- In Tag Manager, click Admin > Install Google Tag Manager. It shows two snippets.
- Paste the first snippet as high in the <head> of your site's shared layout as you can.
- Paste the second snippet right after the <body> tag opens.
- Webflow: Site settings > Custom code > Head code and Footer code. Framer: Site Settings > General > Custom Code, Start of <head> and Start of <body>. Then publish the site.
GTM-XXXXXXXWhere: Tag Assistant > Add domain > your URL > Connect
You should see: your container ID (GTM-…) connected on the homepage, then on pricing, a blog post and a landing page as you click through.
If it isn't there- The snippet was added to one page, not the shared layout or the site-wide custom code.
- The site wasn't published after pasting the snippet.
- The container ID in the snippet is from another container.
Remove tags hard-coded next to Tag Manager
A tag in the site's code and again in Tag Manager fires twice, and every number it sends doubles.
- Open your homepage and view its source: Cmd + Option + U on a Mac, Ctrl + U on Windows.
- Press Cmd + F (Ctrl + F) and search for each line below. Note every one you find.
- Recreate each found tag in Tag Manager (Tags > New), then delete it from the site's code or custom code settings.
- Publish the site and the container on the same day, so nothing runs twice or not at all.
googletagmanager.com/gtag/jsfbq("init"_linkedin_partner_idWhere: The page source, and Tag Assistant's list of tags
You should see: only the Tag Manager snippet in the source, and in Tag Assistant each tag firing once per page.
If it isn't there- A Webflow or Framer integration (like the GA4 field in site settings) still adds a tag. Clear the field.
- A WordPress or Shopify plugin adds its own Google tag. Turn its tracking off.
Send events from the code with dataLayer.push
A trigger that watches a button's design breaks the day the design changes. A named event from the code doesn't.
- Ask your developer to add the line below at the moment the action succeeds, such as after the form is sent.
- No developer: skip this check and use the thank-you page method in the lead check further down.
- In Tag Manager, click Triggers > New > Trigger Configuration > Custom Event and type the same event name.
- Name the trigger after the moment it catches, such as Trigger - Demo form sent, and click Save.
- Click Variables > User-Defined Variables > New > Data Layer Variable, enter form, name it DLV - form and save.
dataLayer.push({ event: "generate_lead", form: "demo" })Where: Tag Manager > Preview, then do the action on your site
You should see: generate_lead in the left column of the Preview window, and form: demo under its Data Layer tab.
If it isn't there- The push runs before Tag Manager loads, or is written as data.push or datalayer.push (it's case-sensitive).
- The page reloads right after the push (a full-page form submit), so the event never reaches Tag Manager. Push it on the thank-you page instead.
Name tags, triggers and variables by one rule
Six months in, nobody remembers what Tag 14 does.
- Click Tags, open each one, click its name at the top and rename it Platform - Event - What.
- Click Triggers and rename each one Trigger - the moment it catches.
- Click Variables and rename each user-defined one by its type, then what it reads.
GA4 - Purchase - Pro planTrigger - Pro plan purchaseDLV - valueVariables start with their type, so you know what each one reads: a constant, custom JavaScript or a part of the URL. Where: Tag Manager > Tags, Triggers and Variables
You should see: every name following the rule, sorted so each platform's tags sit together, as in the tag list at the top of this block.
Test in Preview, then publish a named version
Preview shows every tag that fires before visitors see it, and a named version is one click to roll back to.
- Click Preview at the top right, enter your URL and click Connect.
- On your site, do what the new tags track: send the form, book the call.
- In the Tag Assistant window, click each event in the left column and check the tag is under Tags Fired, once.
- Back in Tag Manager, click Submit. Version Name: what changed. Click Publish.
Add generate_lead to GA4 and Google AdsWhere: Tag Manager > Versions
You should see: the newest version at the top with your name and Live next to it.
If it isn't there- You clicked Preview but never Submit, so visitors still get the old version.
- Two people edited the same workspace; Tag Manager asks you to resolve the conflict before publishing.
Install Google Analytics (GA4)
0/7GA4 shows where your visitors come from and feeds conversions and audiences straight into Google Ads. It's free, and it's the analytics Google Ads reads.
Create a Google Analytics (GA4) property for the site
The property holds the site's data, and its web stream gives the Measurement ID that Tag Manager sends to.
- Sign in to Google Analytics with the company's Google account.
- No account yet: click Start measuring and name the account after the company. Otherwise click Admin > Create > Property (Admin is the gear, bottom left).
- Property name: your domain. Set the reporting time zone and the currency you charge in. Click Next.
- Pick your industry, business size and goals, click Create and accept the terms.
- Choose platform: Web. Enter your domain, Stream name: your domain. Click Create & continue.
- Copy the Measurement ID at the top right of the stream's page. The next check pastes it into Tag Manager.
G-XXXXXXXXXXWhere: GA4 > Admin > Data collection and modification > Data streams
You should see: one Web stream with your domain and its Measurement ID.
If it isn't there- The property was created under someone's personal account. Move it: Admin > Property details > Move property.
- The currency is wrong: it can't be changed for past data, so fix it now under Admin > Property details.
Add Google Analytics (GA4) through Tag Manager
One Google tag on every page, set up once in Tag Manager.
- In Tag Manager, click Variables > User-Defined Variables > New > Variable Configuration > Constant.
- Value: your Measurement ID. Name it GA4 - Measurement ID and click Save.
- Click Tags > New > Tag Configuration > Google Tag. Tag ID: click the brick icon and pick GA4 - Measurement ID.
- Triggering: Initialization - All Pages. Name it GA4 - Configuration and click Save.
- Click Preview, open your site, then Submit and Publish.
Where: GA4 > Reports > Realtime overview, and GA4 > Admin > Data display > DebugView while Preview is on
You should see: yourself in Realtime within a minute, and in DebugView a timeline with page_view and session_start.
If it isn't there- The container isn't published: Preview shows your workspace, visitors only get what you Submit.
- The Tag ID has a typo: it starts with G-, not GTM- or UA-.
- The old GA4 field in Webflow or Framer is also filled, so page views count twice. Clear it.
- An ad blocker hides you from Realtime. Check in a normal browser.
Turn off GA4's automatic form events
Enhanced measurement's form tracking misreads many forms and counts form_submit when nothing was sent. Your own events from the next block replace it.
- In GA4, click Admin > Data collection and modification > Data streams > your stream.
- Under Enhanced measurement, click the gear icon.
- Turn off Form interactions. Keep Page views, Scrolls, Outbound clicks and File downloads on. Click Save.
Where: GA4 > Admin > Data streams > your stream > Enhanced measurement
You should see: Form interactions off and the other measurements on; within a day, no new form_start or form_submit events from GA4 itself.
Filter out your own team's visits
The team opens the site every day and inflates every number.
- From the office, search Google for "what is my IP" and copy the address.
- In GA4, click Admin > Data collection and modification > Data streams > your stream > Configure tag settings > Show more > Define internal traffic.
- Click Create. Rule name: Office. Keep traffic_type as internal. Match type: IP address equals. Paste your address and click Create.
- Click Admin > Data collection and modification > Data filters. Open Internal Traffic, set the filter state to Active and click Save.
Where: GA4 > Admin > Data collection and modification > Data filters
You should see: Internal Traffic with the state Active, and your own visits gone from Realtime once it's on.
If it isn't there- The filter is still Testing, which only labels your visits and removes nothing.
- The office IP changes every day. Filter by a VPN's fixed IP, or add each teammate's home IP.
- Once Active, a filter can't be undone for that data, so check the IP before you switch it on.
Keep Google Analytics (GA4) data for 14 months, not 2
GA4 keeps detailed data for 2 months unless you change it, so a comparison with last year comes back empty in Explore.
- In GA4, click Admin > Data collection and modification > Data retention.
- Set Event data retention to 14 months.
- Click Save.
Where: GA4 > Admin > Data collection and modification > Data retention
You should see: Event data retention: 14 months.
If it isn't there- The change only keeps data from now on; anything older than 2 months is already gone from Explore.
Stop your own tools taking credit for leads
A visitor who goes to Stripe or Calendly and comes back counts as a new visit from them, so the lead is credited to Stripe instead of the ad that brought it.
- In GA4, click Admin > Data collection and modification > Data streams > your stream > Configure tag settings > Show all.
- Click List unwanted referrals. Match type: Referral domain contains. Add one condition per domain below and click Save.
- If your app is on another domain, go back and click Configure your domains, add it and click Save.
checkout.stripe.comcalendly.comapp.yourdomain.comWhere: GA4 > Reports > Acquisition > Traffic acquisition, a week later
You should see: no rows for stripe.com or calendly.com under Session source.
If it isn't there- Old visits keep their source: the change only applies from the day you save it.
- Calendly opens in a new tab instead of an embed, so the visitor's next session starts fresh. Embed it on your page.
Link Search Console to Google Analytics (GA4)
GA4 then shows which Google searches bring each landing page its visitors, next to what they did on the site.
- In GA4, click Admin > Product links > Search Console links > Link.
- Click Choose accounts, tick your Search Console property and click Confirm, then Next.
- Click Select, pick your web stream, click Next, then Submit.
- In Reports > Library, open the Search Console collection and click Publish, so it shows in the left menu.
Where: GA4 > Reports > Search Console > Queries
You should see: your Google searches with clicks and impressions, a day or two after linking.
If it isn't there- You're not an owner of the Search Console property, so it isn't in the list. Ask the owner to add you under Settings > Users and permissions.
- The Search Console property is for http or www while the site runs on another version. Use a Domain property.
Track revenue and key events in Google Analytics (GA4)
0/7A handful of events, one per step that matters, each with the money it is worth where there is money.
Write the event list before building any tag
Anything not on the list doesn't get built, so the container stays small.
- Download the tracking plan below and open it in Google Sheets (File > Import > Upload).
- Delete the rows your business doesn't have, and fill in the page or URL each event fires on.
- Share it with whoever builds the tags and keep it next to the container.
generate_lead: form, value, currencydemo_bookedpurchase: value, currency, transaction_idDownload the tracking plan (CSV)Where: Your tracking plan, against Tag Manager > Tags
You should see: one tag in Tag Manager for every row marked built, and no tag that isn't on the plan.
Fire generate_lead when the form succeeds, not on click
A click on Submit also counts the forms that failed and the people who clicked twice.
- No developer: send people to a thank-you page after the form. Webflow: Form settings > Redirect URL. Framer: the form's Redirect setting. Then in Tag Manager, Triggers > New > Page View > Some Page Views > Page URL contains /thank-you.
- With a developer: have them push the line below when the form shows its thank-you message, and create a Custom Event trigger for generate_lead.
- Name the trigger Trigger - Lead form sent.
- Click Tags > New > Google Analytics > Google Analytics: GA4 Event. Measurement ID: GA4 - Measurement ID. Event Name: generate_lead.
- Under Event Parameters add form, value and currency (with a developer, as Data Layer Variables). Triggering: Trigger - Lead form sent. Name it GA4 - Lead - Demo form. Save, Preview, Publish.
- In GA4, click Admin > Data display > Key events > Create event (or New key event), type generate_lead and save.
dataLayer.push({ event: "generate_lead", form: "demo", value: 50, currency: "USD" })Where: GA4 > Admin > Data display > DebugView with Preview on, and Admin > Data display > Key events
You should see: generate_lead in DebugView with its form parameter, marked with the key event flag, and generate_lead in the Key events list.
If it isn't there- The container isn't published: Preview shows your workspace, visitors only get what you Submit.
- The trigger's event name differs by one letter or a capital from what the site pushes.
- An ad blocker or a privacy browser blocks Tag Manager. Test in a normal Chrome window.
- The consent banner hasn't been accepted, so tags that wait for consent are held back.
- The thank-you page can be opened without sending the form (from search or a bookmark). Hide it from search with noindex.
- Key event reports take up to 24 hours; DebugView is the only live check.
Booking tool
Send the Calendly booking as an event
You can't add tags to Calendly's own site, but its embed tells your page when someone books.
- Embed the Calendly booking on a page of your own site (Calendly > Share > Add to website > Inline embed), not as a link to calendly.com.
- In Tag Manager, click Tags > New > Custom HTML and paste the code below. Triggering: All Pages. Name it Calendly - Booking listener.
- Click Triggers > New > Custom Event, Event name: demo_booked. Name it Trigger - Call booked.
- Click Tags > New > Google Analytics: GA4 Event, Event Name: demo_booked, fired on Trigger - Call booked. Name it GA4 - Lead - Call booked.
- Preview, book a test call, Publish. In GA4, add demo_booked as a key event (Admin > Data display > Key events).
<script>window.addEventListener("message", (e) => { if (e.origin === "https://calendly.com" && e.data.event === "calendly.event_scheduled") dataLayer.push({ event: "demo_booked" }); });</script>Where: Tag Manager Preview, then GA4 > Admin > Data display > DebugView
You should see: demo_booked in Preview's left column right after the confirmation screen, and in DebugView.
If it isn't there- Calendly is a popup widget opened from another script, or a plain link: only the embed sends the message.
- The listener isn't on the page with the embed, because its trigger isn't All Pages.
- You cancel test bookings in Calendly, but the event still counted. Filter internal traffic (Install GA4 block).
Send purchase with the amount, currency and order ID
GA4's revenue reports add up the purchase event's value; the transaction ID stops a refreshed thank-you page counting the sale twice.
- In Tag Manager, click Triggers > New > Page View > Some Page Views > Page URL contains your product's success page, such as /success/pro. Name it Trigger - Pro plan purchase.
- Click Variables > New and make one for the order ID: URL (Query, for an ?order= in the address), Data Layer Variable, or Custom JavaScript, whichever your checkout gives.
- Click Tags > New > Google Analytics: GA4 Event. Measurement ID: GA4 - Measurement ID. Event Name: purchase.
- Event Parameters: value (the price, or the checkout total when amounts vary), currency (USD) and transaction_id (the order ID variable). Fire it on the new trigger.
- Name it GA4 - Purchase - Pro plan. Preview, buy once with a test card, check it fires once, then Publish.
dataLayer.push({ event: "purchase", ecommerce: { transaction_id: "cs_123", value: 150, currency: "USD" } })One trigger per product, each firing on its own success page. When the site can't push an event, the success page's URL is the next most reliable signal. Where: GA4 > Admin > Data display > DebugView, then the next day GA4 > Reports > Monetization > Overview
You should see: purchase in DebugView with value, currency and transaction_id, and the next day the same revenue as Stripe shows for that day.
If it isn't there- Revenue shows 0: currency is missing or value is text ("$150") instead of a number (150).
- Revenue is double: the success page was refreshed and transaction_id was empty or changes on every load.
- Nothing at all: the success page lives on the payment provider's domain, so set the success URL to a page on your site.
Payments
Send a refund when money goes back
Without it, GA4 keeps counting refunded sales as revenue.
- When you refund in Stripe, send refund to GA4 with the same transaction_id as the purchase and the amount refunded.
- No code: in Zapier or Make, trigger on Stripe's charge.refunded and send it with GA4's Measurement Protocol (see the server check below).
- With a developer: send it from your Stripe webhook the same way.
{ name: "refund", params: { transaction_id: "cs_123", value: 150, currency: "USD" } }Where: GA4 > Reports > Monetization > Overview, the next day
You should see: Total revenue down by the refund for that day, and refund listed under Admin > Data display > Events.
If it isn't there- The transaction_id differs from the purchase's, so GA4 can't match them.
Subscriptions or sales calls
Send renewals and closed deals from the server
The browser never sees month two of a subscription or a deal closed on a call, so your server sends those to GA4.
- At signup, save the visitor's GA4 client ID on the lead or account: the last two numbers of the _ga cookie (see below).
- In GA4, click Admin > Data collection and modification > Data streams > your stream > Measurement Protocol API secrets > Create. Name it Server and copy the secret.
- When Stripe sends invoice.paid, send a purchase event with the saved client ID and the secret.
- When a deal is marked won in the CRM, send close_convert_lead with its value the same way. Zapier or Make can do both without code.
123456789.1700000000Where: GA4 > Reports > Monetization > Overview, with the comparison set to First user source
You should see: renewals adding to revenue each month, credited to the channel that first brought the customer.
If it isn't there- The client ID was never saved at signup, so server events land as a new, unknown visitor.
- The secret belongs to another stream or property.
- Events sent more than 72 hours late are dropped.
Google Ads
Send the same events to Google Ads
Ads bids for more of whatever you count as a conversion, so it should count leads and sales, not clicks.
- In GA4, click Admin > Product links > Google Ads links > Link > Choose Google Ads accounts, pick yours, Confirm, Next, Submit.
- In Google Ads, click Goals > Conversions > Summary > + New conversion action > Import > Google Analytics 4 properties > Web > Continue.
- Tick generate_lead and purchase and click Import and continue, then Done.
- In Tag Manager, click Tags > New > Conversion Linker, Triggering: All Pages. Name it Google Ads - Conversion Linker and publish.
- In Google Ads, click Goals > Settings > Enhanced conversions, turn it on and choose Google tag as the method.
Where: Google Ads > Goals > Conversions > Summary
You should see: generate_lead and purchase with the status Recording conversions, a day or two after the first ones happen.
If it isn't there- You imported from GA4 and also added Google Ads conversion tags for the same events, so every lead counts twice. Keep one.
- Status says Inactive: no key event has happened since linking. It changes after the first real one.
- The GA4 and Google Ads accounts are under different logins, so the link isn't offered. Add the same Google account to both.
Track the funnel on your main landing pages
0/6For the few pages that get the traffic: where people drop between landing and becoming a lead, by page and by source.
List the 3 to 5 pages that matter
The pages your ads, posts and search traffic land on, each asking for one action.
- In GA4, click Reports > Engagement > Landing page.
- Set the date range at the top right to the last 90 days and sort by Sessions.
- Write the top 3 to 5 pages that ask for an action into your tracking plan. Usually the homepage, pricing and the top landing pages.
Where: GA4 > Reports > Engagement > Landing page
You should see: the pages you wrote down taking most of the sessions.
If it isn't there- (not set) at the top: those are sessions that started without a page view, often from a tag firing before the Google tag. Check Initialization - All Pages on GA4 - Configuration.
Use the same four steps for each page
The same steps on every page make the pages comparable.
- Write the four events below in your tracking plan, for each main page.
- Mark which ones the site already sends. The next two checks add cta_click and form_start.
page_viewcta_clickform_startgenerate_leadWhere: GA4 > Admin > Data display > Events
You should see: all four events listed, each with a count from the last day.
If it isn't there- An event shows 0: it's built but not published, or its trigger never matches. Test it in Preview.
Send cta_click with which button it was
Knowing it was the hero's button and not the footer's tells you what to move.
- Give each main button an ID: hero-cta, pricing-cta, footer-cta. Webflow: select the button > Element settings > ID. Framer: the button's ID field.
- In Tag Manager, click Variables > Configure and tick Click ID and Click URL.
- Click Triggers > New > Click - All Elements > Some Clicks > Click ID contains -cta. Name it Trigger - Main button clicked.
- Click Tags > New > Google Analytics: GA4 Event. Event Name: cta_click. Event Parameters: cta = {{Click ID}}, page = {{Page Path}}. Fire it on the new trigger.
- Name it GA4 - Click - Main button. Preview, click each button, Publish.
Where: Tag Manager Preview, then GA4 > Admin > Data display > DebugView
You should see: a Click event in Preview with GA4 - Click - Main button under Tags Fired, and cta_click in DebugView with cta: hero-cta.
If it isn't there- The click lands on the text or icon inside the button, which has no ID. Use Click - All Elements with Click Element matches CSS selector [id$="-cta"], [id$="-cta"] *.
- The button opens a new page so fast the event is lost. Keep the trigger on Click - All Elements, not Just Links with Wait for tags off.
Send form_start on the first field someone types in
The people who start a form and give up are the ones to win back.
- In Tag Manager, click Tags > New > Custom HTML and paste the code below. Triggering: All Pages. Name it Form - Start listener.
- Click Triggers > New > Custom Event, Event name: form_start. Name it Trigger - Form started.
- Click Tags > New > Google Analytics: GA4 Event. Event Name: form_start, parameter form = a Data Layer Variable for form. Fire it on Trigger - Form started.
- Preview, click into a form field, Publish.
<script>(function(){var s=false;document.addEventListener("focusin",function(e){var f=e.target.closest&&e.target.closest("form");if(f&&!s){s=true;dataLayer.push({event:"form_start",form:f.id||f.name||"form"});}});})();</script>Where: Tag Manager Preview, then GA4 > Admin > Data display > DebugView
You should see: form_start once per page view, the first time you click into any field, with the form's name.
If it isn't there- The form is in an iframe (HubSpot, Typeform), where the page's listener can't see it. Use the form tool's own events instead.
- It fires twice: GA4's own form events are still on. Turn off Form interactions (Install GA4 block).
Tag every link you share with one UTM rule
LinkedIn, linkedin and li show up as three channels.
- Copy the rule into a shared doc: lowercase only, utm_source is the site, utm_medium is the type, utm_campaign is the name.
- Build every link with Google's Campaign URL Builder.
- Add hidden fields to your forms named utm_source, utm_medium, utm_campaign and gclid. Most form tools have a hidden field type; in Webflow, add them inside the form with an Embed element.
- Fill them from the page's URL (many form tools do this for fields with these names; otherwise a small script) and map them to the lead in your CRM.
?utm_source=google&utm_medium=cpc&utm_campaign=brand?utm_source=linkedin&utm_medium=social&utm_campaign=launch?utm_source=newsletter&utm_medium=email&utm_campaign=2026-11Where: GA4 > Reports > Acquisition > Traffic acquisition, and a test lead in your CRM
You should see: one row per channel, and a test lead sent through a tagged link carrying the same utm values in the CRM.
If it isn't there- The same source in two spellings: fix the links, old visits keep their spelling.
- UTMs on links between your own pages restart the visit and steal credit. Use them only on links from outside.
Build the funnel and read it every week
The step with the biggest drop is the one to fix first.
- In GA4, click Explore > Funnel exploration.
- Under Steps, click the pencil. Add four steps: page_view with page_location contains your page, then cta_click, form_start, generate_lead. Click Apply.
- Drag Landing page from Dimensions into Breakdown, or Device category to compare mobile with desktop.
- Rename the exploration after the page. Every week, note each page's biggest drop and fix that step first.
Or let the 3DAY Agent read PostHog, Stripe and Search Console for you and report every MondayWhere: GA4 > Explore > your funnel exploration
You should see: bars for all four steps with a share at each, as in the screenshot at the top of this block.
If it isn't there- A step shows 0 users: the event name in the step differs from what's sent, or it's newer than the date range.
- Everyone drops at step 2 because people may skip it: turn on Make open funnel.
PostHog for session recordings, heatmaps and funnels
0/8Once GA4 counts leads and revenue, PostHog shows what people do on the way: session recordings of real visits, heatmaps of where they click and scroll, every step of a funnel, who comes back, and A/B tests. The tool for CRO and product work, free up to a million events a month.
Add PostHog and identify people at signup
PostHog follows one person across visits, so their visits before signing up join their account.
- Sign up at PostHog. Pick EU Cloud if your data has to stay in the EU; you can't move it later.
- In PostHog, click Settings > Project > General and copy the Web snippet.
- In Tag Manager, click Tags > New > Custom HTML and paste the snippet. Triggering: Initialization - All Pages. Name it PostHog - Configuration. Save and publish.
- Signup and login happen in your app, so a developer adds the two lines below there: identify when someone signs up or logs in, reset when they log out.
- Sign up on your site with a test account.
posthog.identify(user.id, { email: user.email })posthog.reset()Where: PostHog > People and groups > People
You should see: your test account by email, and under its Activity the page views from before you signed up.
If it isn't there- The snippet is in Tag Manager and in the app's code, so every event counts twice. Keep one.
- An ad blocker blocks PostHog's domain. PostHog's docs explain a reverse proxy through your own domain.
- The person shows up twice: identify was called with an email once and an ID another time. Always use the same ID.
Filter out your own team's visits
The team opens the site and the product every day and inflates every number.
- In PostHog, click Settings > Project > Filter out internal and test users. You need to be a project admin.
- Add a filter: email does not contain your company's domain.
- Turn on Enable this filter on all new insights.
Where: Any PostHog insight: the Filter out internal and test users toggle
You should see: the toggle on by default, and your own sessions missing from a trend when it's on.
If it isn't there- Your visits from before signup have no email yet, so they still count. Add a second filter on your office IP.
Turn on session recordings
A funnel shows where people drop; a recording shows why.
- In PostHog, click Settings > Project > Replay and turn on Record user sessions.
- Keep input masking on, so nothing anyone types is recorded.
- Open your site in another browser and click around for a minute.
Where: PostHog > Session replay
You should see: your test visit a few minutes later, playing back what you clicked.
If it isn't there- Recordings are cut by the project's sample rate or minimum duration. Check Settings > Project > Replay.
- The site's content security policy blocks PostHog's recorder. Your developer adds PostHog's domains to it.
Turn on heatmaps for your main pages
A heatmap shows where people click, how far they scroll and what they never reach, page by page.
- In PostHog, click Settings > Project > Autocapture and turn on heatmaps.
- Wait a few days for visits to come in.
- Click Toolbar > Add authorized URL for your domain, then Launch on one of your main pages.
- In the toolbar on your page, click Heatmap. Switch between clicks and scroll depth.
Where: The PostHog toolbar on your page > Heatmap
You should see: colored spots where people click, and in scroll mode the share who reach each part of the page.
If it isn't there- The toolbar doesn't open: your domain isn't in Authorized URLs.
- No spots yet: heatmaps only collect from the day you turn them on.
Send PostHog the same events GA4 gets
The same names in both tools, so a funnel in PostHog and a report in GA4 count the same thing.
- In Tag Manager, click Triggers and note the ones you made for GA4: Trigger - Lead form sent, Trigger - Call booked, Trigger - Form started.
- For each, click Tags > New > Custom HTML and paste the line below with that event's name. Fire it on that trigger.
- Name each one PostHog - Event - What. Preview, then Publish.
<script>posthog.capture("generate_lead", { form: {{DLV - form}} })</script>Where: PostHog > Activity
You should see: each event a few seconds after you do it on the site, with its properties.
If it isn't there- posthog is not defined: the PostHog tag fires after this one. Keep PostHog - Configuration on Initialization - All Pages.
Name your main buttons for PostHog's click tracking
PostHog records clicks by itself; a name on each button tells you it was the hero's and not the footer's.
- Add the attribute below to each main button with its name. Webflow: select the button > Element settings > Custom attributes > +. Framer: the button's Attributes.
- Name: data-ph-capture-attribute-cta. Value: hero, pricing or footer.
- Publish and click a button on your site.
data-ph-capture-attribute-cta="hero"Where: PostHog > Activity, the autocaptured click
You should see: the click with the property cta: hero.
If it isn't there- Autocapture is off: Settings > Project > Autocapture.
Stripe
Connect Stripe so PostHog sees revenue
PostHog reads payments, renewals and refunds straight from Stripe, so revenue sits next to the funnel that earned it.
- In Stripe, click Developers > API keys > Create restricted key, with Read access, and copy it.
- In PostHog, click Data pipelines > Sources > New source > Stripe and paste the key.
- Make sure people in PostHog and customers in Stripe share an email or ID, so revenue joins the right person.
- After the first sync, open Revenue analytics.
Where: PostHog > Revenue analytics
You should see: the month's revenue matching Stripe's dashboard.
If it isn't there- The key lacks read access to one resource the sync needs. PostHog's Stripe page lists them.
- Revenue isn't tied to people: the email in Stripe differs from the one you identify with.
Build the funnel and watch who drops
The step with the biggest drop is the one to fix first, and the recordings show why.
- In PostHog, click Product analytics > New insight > Funnels.
- Step 1: Pageview, filtered to Current URL contains your page. Add form_start and generate_lead, or the steps inside your product.
- Click Save, then duplicate it for each main page.
- Every week, click the bar with the biggest drop and choose to watch recordings of the people who dropped off.
Or let the 3DAY Agent read PostHog, Stripe and Search Console for you and report every MondayWhere: PostHog > Product analytics > your funnel insights
You should see: bars for each step with the conversion between them, as in the screenshot at the top of this block.
Get it all as a Monday report in Slack
0/3The 3DAY Agent reads your analytics, payments, Google search and Google Ads every week and posts one report in Slack: visitors, goals and revenue with what changed, where people drop off, and up to three next steps you approve in the thread. Built by 3DAY.STUDIO™, in a closed beta.
@channel Acme · 2026-10-12 to 2026-10-18 · See every number and what to do next (log in with you@acme.com)
Scaling phase · 2,840 visitors a week
Overview PostHog, Google, Stripe, Gmail · main goal: booked a demo
| Item | This week | ± W | ± M |
|---|---|---|---|
| Unique visitors | 2,840 | ▲ +13% | ▲ +19% |
| MRR (month ago) | 12,480.00 USD | ▲ +6% | ▲ +7% |
| Conversions (Booked a demo) | 41 · 1.4% | ▲ +0.1 pts | no change |
| Google Ads spend | 386.20 USD | -4% | +8% |
| Google Ads CPC | 0.94 USD | ▲ -8% | ▼ +1% |
| Google Ads CAC, 90 days | 224.29 USD · 21 customers | - | ▲ -4% |
| Google Ads LTV:CAC (healthy 3x) | 3.2x | - | ▲ +4% |
± W (vs previous week), ± M (vs the previous 4-week period)
Improvements
CRO-5 Most visitors who open the demo form leave before booking.
118 started it this week and 41 booked, so 77 left on the way.
Action: cut the form to name, email and company.
SEO-8 "cookieless analytics" slipped to place 11.2 on Google.
It is shown 1,310 times a week, and the first page brings most of the visits.
Action: add a comparison section to the cookieless page.
ADS-3 Google Ads cost per demo fell from 33.54 USD to 22.72 USD.
The shorter demo form shipped on 13 Oct.
Action: keep the budget and watch it for another week.
Content idea
CONTENT-12 Search answer A comparison page for "webflow vs framer for startups".
People search for it and Google shows a guide where a comparison page would fit. Google showed the site for it 44 times in 28 days, at place 23.5; done well, it could bring 1 to 2 more clicks a month.
Action: Write a comparison page for the search, and link to it from the page Google shows today (acme.com/blog/webflow-tips today).
See six more content ideas in the app.
1. Conversion
Conversion funnel PostHog
| Item | This week | ± W | ± M | CR | ± W |
|---|---|---|---|---|---|
| Visitors | 2,840 | ▲ +13% | ▲ +19% | 100% | - |
| Saw the pricing | 690 | ▲ +15% | ▲ +17% | 24% | ▲ +0.3 pts |
| Started the demo form | 118 | ▲ +23% | ▲ +22% | 4.2% | ▲ +0.3 pts |
| Booked a demo | 41 | ▲ +8 | ▲ +7 | 1.4% | ▲ +0.1 pts |
Site health: 9 visits with rage clicks, 4 visits that hit an error. See them →
A visit worth watching PostHog · typed text is hidden
| Recording | Why it matters | Link |
|---|---|---|
| 3 min 34 s of activity | Got furthest this period: reached "Booked a demo" | Watch |
Website updates · 3 changes, touching sign-up and how Google sees the site ⚑. See what shipped →
2. Revenue
Revenue Stripe
| Item | Count | This week | ± W | ± M |
|---|---|---|---|---|
| Payments, last 4 weeks | 238 | 16,310.00 USD | - | - |
| MRR (month ago) | - | 12,480.00 USD | ▲ +6% | ▲ +7% |
| New paying customers | 14 | 1,106.00 USD | ▲ +27% | ▲ +23% |
| New subscriptions | 11 | 869.00 USD | ▲ +22% | ▲ +22% |
| Trials converted (of 9 ended) | 6 | 474.00 USD | ▲ +50% | - |
| Cancelled subscriptions | 4 | 316.00 USD | ▲ -20% | - |
| At risk: past due | 3 | 237.00 USD | ▲ -25% | - |
| Failed payments | 7 | 553.00 USD | ▼ +40% | ▼ +33% |
| Refunds | 2 | 158.00 USD | ▲ -33% | - |
| Disputes lost | - | n/a | - | - |
What went wrong · 7 causes, 1,027.00 USD; first: Dispute, product not received, reply by 28 Oct. See every cause and what to do →
Where a row has a count and money, ± is the change in money; MRR's ± W is against a month ago. Failed payments were 10.3% of all payment attempts this period. ⚠ n/a: not tracked yet, or no data this period.
3. Organic traffic
Where free visitors come from Search Console, PostHog
| Item | This week | ± W | ± M |
|---|---|---|---|
| Visitors from Google search | 612 | ▲ +13% | ▲ +11% |
| Visits from branded Google searches (trust) | 205 | ▲ +9% | ▲ +10% |
| Visitors from AI assistants | 38 | ▲ +11 | ▲ +13 |
| Times shown on Google | 18,400 | ▲ +9% | ▲ +9% |
| Clicked when shown (CTR) | 3.3% | ▲ +0.1 pts | ▲ +0.1 pts |
| Average place on Google | 8.2 | ▲ 0.7 places | ▲ 0.8 places |
Visitors from AI assistants · 38 from ChatGPT 24, Perplexity 9, Gemini 5; most land on acme.com/pricing. See where they land →
Your searches on Google Search Console, DataForSEO · this week
| Search | Searches a month | Your place | ± W | Visits | ± W | Google's AI answer |
|---|---|---|---|---|---|---|
| website analytics tool | 2,900 | 6.4 | ▲ 1.5 | 88 | ▲ +27 | not checked |
| privacy friendly analytics | 1,000 | 4.1 | ▲ 0.2 | 52 | ▲ +3 | not checked |
| cookieless analytics | 1,600 | 11.2 | ▼ 0.6 | 14 | ▼ -3 | not checked |
| analytics for b2b saas | 390 | 9.3 | ▲ 8.5 | 11 | ▲ +10 | not checked |
| gdpr compliant analytics | 480 | 12.4 | new | 3 | - | not checked |
| plausible alternative | 720 | 14.1 | ▲ 7.5 | 2 | ▲ +2 | not checked |
| product analytics tool | 4,400 | 12 | - | - | - | links to others |
| funnel analysis software | 880 | 6 | - | - | - | links to you |
Your place: 1 is the first result, ▲ means higher up; place and visits from Search Console, searches a month and the AI answer from DataForSEO. Google's AI answer is the summary above the results: when it links to you, people who read it see your name.
Pages worth adding or improving · 7 searches: 3 pages to improve, 2 pages to create, one of them in CONTENT-12. See them →
Where to show up DataForSEO · lists, threads and directories that rank for what you sell
| Item | What to do | For | Place | AI answer cites it |
|---|---|---|---|---|
| Best Product Analytics Software | Ask to be added | product analytics tool | 1 | yes |
| Mixpanel alternatives that don't cost a fortu… | Write a comment | mixpanel alternative | 1 | no |
A list of the best ranks and gets cited by Google's AI answer: getting onto it puts you in front of buyers and in AI answers.
Reviews · G2 0, Capterra 4 (4.8). See where to add reviews →
Links · 58 sites link to you, the strongest producthunt.com; 2 link to your competitors and not to you. See them →
4. Paid ads
Google Ads spend and results Google Ads, PostHog
What changed in Ads: 3 changes, by 3DAY, you and Google. See every change →
| Item | This week | ± W | ± M |
|---|---|---|---|
| Spent on Google Ads | 386.20 USD | -4% | +8% |
| Clicks from Google Ads | 410 | ▲ +4% | ▲ +7% |
| Cost per click (CPC) | 0.94 USD | ▲ -8% | ▼ +1% |
| Booked a demo from Google Ads | 17 | - | - |
| Booked a demo, as Google Ads counts them | 17 | - | - |
| Share of them Google Ads saw | 100.0% | no change | - |
| Cost per goal from Google Ads, last 28 days | 26.08 USD | - | - |
| CAC, 90 days | 224.29 USD · 21 customers | - | ▲ -4% |
| LTV:CAC (healthy 3x) | 3.2x | - | ▲ +4% |
| Top keywords | Clicks | ± W | Booked a demo | ± W | Cost each |
|---|---|---|---|---|---|
| website analytics tool | 142 | ▲ +11 | 9 | ▲ +3 | 18.71 USD |
| cookieless analytics | 88 | ▼ -4 | 5 | ▲ +1 | 19.42 USD |
| gdpr analytics | 61 | ▼ -9 | 2 | - | 29.15 USD |
Climbing keywords: 2, most "analytics without cookies" with 24 clicks. See them →
New keyword ideas DataForSEO · not in your account · estimated volume and cost per click
| Item | Searches a month | Est. cost per click | Close to |
|---|---|---|---|
| product analytics for startups | 480 | 14.20 USD | product analytics tool |
| funnel tracking software | 390 | 16.90 USD | funnel analysis software |
5. Mentions and emails
Mentions this week Google News, Hacker News, web search · new since the last report
Emails you sent · 1,221 emails delivered, clicked a link 12.1%, 23 replies. See them →
Emails worth reading Gmail · replies and new emails, sender hidden
Join the waitlist
The agent is in a closed beta, and new projects join from the waitlist.
- Open the waitlist and enter your work email.
- We email you when there's a place, with a login to app.3day.studio.
Connect your sources once
The agent reads PostHog, Stripe, Search Console, Google Ads, your email tool and your inbox, with read-only access. GA4 and other tools are set up on request.
- In app.3day.studio, open your project and add each source from its block.
- Follow the numbered access steps for each one; nothing is saved until every step is done.
- Someone from 3DAY checks the access by hand within one working day.
Read the report every Monday and approve the next steps
The numbers are computed in code and checked a second way; the report says how many matched.
- Every Monday at 08:00 your time, the report arrives in your Slack channel.
- Read the numbers and what changed, then the next steps under them.
- Approve or skip each step in the thread. Every change we ship shows up in the reports, dated.
Set up EU GDPR cookie consent in Tag Manager
0/5If people from the EU visit, set this up before the tags above go live. This is not legal advice.
Install a consent banner from Google's certified list
A certified banner passes the visitor's choice to Google's tags the way Google Ads expects.
- Pick a banner from Google's certified list, such as Cookiebot, CookieYes or Usercentrics, create an account and add your domain.
- Copy the banner's ID from its dashboard (Cookiebot: Domain group ID; CookieYes: Website key).
- In Tag Manager, click Tags > New > Tag Configuration > Discover more tag types in the Community Template Gallery. Search your banner's name and click Add to workspace.
- Paste the ID into the tag. Triggering: Consent Initialization - All Pages. Name it Consent - Banner. Save and publish.
Where: Your site in a private window, then Tag Manager Preview
You should see: the banner on first visit, and in Preview Consent - Banner fired first, on Consent Initialization.
If it isn't there- The banner also comes from a script in the site's code, so it shows twice. Remove the code one.
- The banner's dashboard doesn't list your domain yet, so it stays hidden.
Deny everything by default with Consent Mode v2
Google needs ad_user_data and ad_personalization to measure and remarket to EU visitors in Google Ads.
- Open the Consent - Banner tag and find its default consent settings.
- Set the four types below to denied for the EU, EEA, UK and Switzerland (or everywhere).
- Click Admin > Container Settings > Additional Settings and tick Enable consent overview. Save.
- Preview and publish.
ad_storage: denied, analytics_storage: denied, ad_user_data: denied, ad_personalization: deniedWhere: Tag Manager Preview > Consent tab, before and after clicking Accept
You should see: On-page Default: Denied for all four, then On-page Update: Granted after Accept.
If it isn't there- Default shows Granted: the banner's region setting doesn't cover where you're testing from. Set it for everywhere while testing.
- No Consent tab: Enable consent overview isn't ticked.
Make every other tag wait for consent
Google's own tags read Consent Mode by themselves; PostHog, LinkedIn and Meta fire before anyone says yes unless told to wait.
- In Tag Manager, click Tags and click the shield icon (Consent overview) at the top right.
- Tick every tag that isn't Google's and click the edit icon.
- Choose Require additional consent for tag to fire and add analytics_storage, or ad_storage for ad pixels. Save.
- For PostHog in the app's code, start it opted out and opt in after Accept (the lines below). Publish.
opt_out_capturing_by_default: trueposthog.opt_in_capturing()Where: Tag Manager > Tags > Consent overview
You should see: no tag left under Consent Not Configured.
If it isn't there- The consent banner hasn't been accepted, so tags that wait for consent are held back.
Check no cookie is set before Accept
The test a regulator would run, in two minutes.
- Open your site in a private window. Don't click the banner.
- Open the developer tools (Cmd + Option + I on a Mac, F12 on Windows) > Application > Cookies > your domain.
- Check there is no _ga cookie, no ph_ cookie and no ad cookie (_fbp, _gcl_au).
- Click Accept all and reload. The cookies should appear now.
Where: Chrome DevTools > Application > Cookies, in a private window
You should see: only the banner's own cookie before Accept, then _ga and the others after it.
If it isn't there- _ga is set before Accept: the Google tag fires outside Consent Mode, often from a copy left in the site's code.
- PostHog's cookie is set before Accept: it's loaded outside Tag Manager or without opt_out_capturing_by_default.
On this page
- 01Why set up website analytics at all?
- 02What do you actually need to know?
- 03Which analytics tool should you use?
- 04How do you set up Google Analytics (GA4)?
- 05How do you count leads?
- 06How do you see which channel brings customers?
- 07How do you get revenue into Google Analytics (GA4)?
- 08What if people sign up for a product?
- 09How much will you miss?
- 10Website analytics checklist: why are your numbers wrong?
- 11What should you look at every week?
- 12Questions founders ask
- 13Other free tools
Why set up website analytics at all?
To know which of your efforts bring customers. Without it, every marketing decision is a guess. Say your site had 1,000 visitors last month, 20 leads and 4 new customers:
| What you see | Without tracking | With tracking |
|---|---|---|
| Visitors | 1,000 | 1,000 |
| Where the customers came from | unknown | 3 from LinkedIn posts, 1 from Google search |
| What Google Ads brought | 400 visitors | 400 visitors, 0 customers |
Same site, same month. Only the second view tells you to stop paying for those ads and post more on LinkedIn.
What do you actually need to know?
Three things, in this order:
- How many people visit, and from where. Google, ads, LinkedIn, referrals.
- How many of them become leads. A booked call, a trial, a sign-up.
- Which channel brings the leads that pay. This is the one that decides your budget.
Most setups stop at the first. The money is in the third.
Which analytics tool should you use?
| Tool | Best for | Price to start | Watch out for |
|---|---|---|---|
| Google Analytics 4 | Traffic sources, and Google Ads if you run them | Free | Hard to read; needs a consent banner in the EU |
| PostHog | Product analytics: funnels, retention, session replays and A/B tests, per person | Free up to 1M events a month | More than a simple site needs |
| Plausible or Fathom | A clean visitor count without cookies | From about $9 a month | Counts visits, can’t follow a lead to a customer |
Most tech startups end up with GA4 for traffic and ads, and PostHog once they need to see what people do: where they drop in a funnel, who comes back, what a session looked like. A simple site with no ads is fine on Plausible alone.
How do you set up Google Analytics (GA4)?
- Create a GA4 property at analytics.google.com and add a web data stream for your domain.
- Add the tag to every page: in your site’s head, through your builder’s setting (Webflow and Framer both have one), or with Google Tag Manager.
- Open the Realtime report and visit your site. You should see yourself within a minute.
- Mark the sent form or booked call as a key event.
- Filter out your team’s visits, and set data retention to 14 months.
That answers question 1: who visits and from where.
How do you count leads?
Track the few moments that matter, one per step from the first visit to the money:
| Event | When it fires | Key event |
|---|---|---|
page_view with UTM source |
Every page | No |
pricing_viewed |
The pricing page loads | No |
generate_lead, demo_booked or sign_up |
The form is sent or the call is booked | Yes |
qualify_lead |
Sales marks the lead as a fit, from the CRM | Later |
close_convert_lead or purchase |
The deal is won, from the CRM or billing | Later |
That answers question 2. Add a row only when a question you actually ask needs it.
How do you see which channel brings customers?
Save the source on the lead itself. Add hidden fields to your forms that carry the UTM values and the gclid from the landing URL into your CRM. Analytics tools lose track of people long before a deal closes, so this is the only reliable link between a channel and revenue. That answers question 3.
Two things often break it: a booking tool on its own domain (embed Calendly on your page and send demo_booked when it confirms), and an app on a subdomain taking the credit (add it to GA4’s list of unwanted referrals).
How do you get revenue into Google Analytics (GA4)?
Send the money as an event, so GA4 can show which channel earns, not just which one brings leads. GA4 builds its revenue reports and Google Ads its return on ad spend from the purchase event’s value and currency. How you send it depends on how you get paid:
| How you get paid | What to send | From where |
|---|---|---|
| Checkout on your site (Stripe Checkout, Paddle) | purchase with the amount, currency and order ID |
Your success page, through Tag Manager |
| Monthly subscription | purchase for every renewal |
Your server, when Stripe sends invoice.paid |
| Deals closed on a call | close_convert_lead with the deal’s value |
Your CRM, when the deal is marked won |
On the success page, push the sale once, with the Checkout session’s ID as transaction_id, so a refreshed page never counts it twice:
dataLayer.push({
event: "purchase",
ecommerce: { transaction_id: "cs_123", value: 150, currency: "USD" },
});
The browser never sees month two of a subscription or a deal signed after a call. Those go from your server to GA4’s Measurement Protocol. It needs the visitor’s GA4 client ID, so save it on the lead or the account at signup, from the _ga cookie, next to the UTMs:
const url = "https://www.google-analytics.com/mp/collect"
+ `?measurement_id=G-XXXXXXXXXX&api_secret=${SECRET}`;
await fetch(url, {
method: "POST",
body: JSON.stringify({
client_id: lead.gaClientId,
events: [{
name: "purchase",
params: { transaction_id: invoice.id, value: 150, currency: "USD" },
}],
}),
});
Read server-sent revenue by First user source, the channel that first brought the customer: these events arrive outside a visit, so a session report shows them without a source. Once a week, compare GA4’s revenue with Stripe’s for the same days. Within a few percent is right; a big gap means a sale fires twice or not at all. Send a refund with the same transaction_id when money goes back.
That answers question 3 in money: which channel brings the customers who pay, and how much.
What if people sign up for a product?
Follow them into it. In PostHog, call identify with the user’s ID at sign-up, so the visits before it join the new account. If you sell to teams, group events by company, so you see accounts, not just people.
How much will you miss?
More than you’d guess. Many EU visitors decline cookies, and Google only fills that gap with modeled data on sites far bigger than a startup’s. Developer audiences also block trackers. Load the Google tag before the cookie banner and let the banner pass the choice (advanced Consent Mode), and serve PostHog through your own domain. Then treat the CRM, not analytics, as the record of leads.
Website analytics checklist: why are your numbers wrong?
- The main goal isn’t marked as a key event.
- The tag fires twice on some pages, or a conversion triggers twice.
- Your team’s visits and staging sites count as real traffic.
- The booking tool or app domain takes the credit for the lead.
- UTMs don’t follow one naming rule, so one channel shows up three times.
- Lead counts in GA4 and the CRM differ by more than about 15%.
What should you look at every week?
Five numbers, one person, once a week: visitors by channel, leads, leads by channel, qualified leads and won deals. A short list someone reads beats a dashboard nobody opens.
Questions founders ask
01What is a tracking plan, and what goes in a template?
A tracking plan is the list of events your site sends, written down before anyone installs a tag: each event's exact name, when it fires, its properties, which tools receive it and whether it is a key event. Segment and Amplitude both publish empty templates for it. The hard part is not the sheet but knowing which five to eight rows your site needs; the table above is the starting set for a B2B site.
02Which GA4 events should a B2B website track?
Fewer than most lists suggest: one event per link of the chain. Page views carry the source, one event shows real interest (the pricing page), one is the key event (generate_lead, demo_booked or sign_up), and two come back from the CRM or billing: qualify_lead and close_convert_lead, or account_activated and purchase. Google's recommended lead events use exactly these names, and its reports read them. Bounce rate, scroll depth and time on page answer none of a founder's questions.
03What is a key event in GA4, and how many should I have?
Every interaction GA4 records is an event. A key event is one you mark as important to the business, and Google Ads conversions are imported from key events. Google renamed conversions to key events in 2024. A standard property allows 30, but a B2B site needs one to three: the lead or signup, then the qualified lead and the won deal sent back from the CRM, once Google Ads should import them. A click or a page view should never be one.
04How do I audit my GA4 setup for free?
Check the things that make numbers wrong, in this order: the main goal is marked as a key event, the tag fires once per page (Tag Assistant shows it), your own team's visits are filtered, the booking tool sends its event to your page and the app's domain is excluded as a referral, the consent banner controls the tags, UTMs follow one naming rule, and data retention is 14 months instead of the default 2. The list above is that checklist, and each no names the number it breaks. No account connection needed.
05PostHog or GA4: which should a startup use?
GA4 if Google Ads is a real channel, because it feeds key events and audiences straight into Ads. PostHog for deeper product analytics, because it follows one person from the first visit and runs funnels, retention, session replays, A/B tests and feature flags in one place. Many B2B startups run both: GA4 for channels and Ads, PostHog for what people do on the site and in the product. The CRM stays the source of truth for leads and money either way.
06Is there a Google Analytics alternative without cookies?
Plausible and Fathom count visits without cookies, so on their own they need no consent banner, and they load fast. The trade-off is that they count visits, not people: they can't tell you which lead turned into a customer. Keep one for traffic, save the UTMs on each lead in your CRM, and add PostHog (which can also run cookieless) when you need the steps after the visit. This is not legal advice.
07Why is GA4 cross-domain tracking not working with Calendly or my app?
You can't put your GA4 tag on calendly.com, so cross-domain settings don't help there. Embed the booking tool on your own page and send the event when it confirms: Calendly posts a calendly.event_scheduled message to the page. An app on a subdomain shares GA4's cookie by default; add the app and checkout domains to the list of unwanted referrals, so your own app and Stripe never get the credit as a traffic source.
08What is the difference between a tracking plan and a measurement plan?
A measurement plan starts at the top: the business goals, the questions you need answered and the numbers that answer them. A tracking plan is the bottom half: the exact events and properties that produce those numbers. Agencies often deliver the first and leave the second to a developer. Start from the questions, then keep only the events that answer one.
Sources (19)
- Google Analytics Help: Recommended eventsLead generation events: generate_lead, qualify_lead, close_convert_lead, and the reports that read them
- Google Analytics Help: About key eventsEvent, key event and Google Ads conversion
- Google Analytics Help: Configuration limits30 key events per standard property
- Google Analytics Help: Event naming rulesLetters, numbers and underscores, 40 characters, reserved names
- Google Analytics Help: Data retention2 months by default, 14 at most on standard properties; affects explorations and funnels
- Google Analytics Help: Filter out internal trafficDefine internal traffic, then activate the data filter
- Google Analytics Help: Set up cross-domain measurementConfigure your domains; subdomains share the cookie by default
- Google Ads Help: About auto-taggingThe gclid Google Ads adds to every click, so its clicks need no UTMs
- Google Tag Manager Help: Consent mode for EEA trafficConsent Mode v2 signals and when they are required
- Google for Developers: GA4 Measurement ProtocolSending CRM and payment events from a server
- Google Ads Help: Enhanced conversions for leadsQualified leads from the CRM matched back to ad clicks
- PostHog: PostHog vs GA4What each tool is built for, by team type
- PostHog Docs: Product analytics best practicesTrack growth events first; custom events over autocapture for key steps
- PostHog Docs: Controlling data collectionCookieless mode, always and on_reject
- Twilio Segment: How to create a tracking planStart from goals, few events, add only what is missing
- Amplitude: Create a tracking planStart with a handful of key events
- Calendly Developer: Notifying the parent windowcalendly.event_scheduled when a meeting is booked in the embed
- Advance Metrics: Cookie Behaviour Study25.4% accept all, on international B2B sites (service, industry, retail), H1 2023; no sample size given (the 2018 run: 1.2M users)
- Plausible: Google Analytics and ad blockersOne site, August 2021, 50,947 visitors from Hacker News and Reddit: 58% blocked GA