GA4 for SaaS: How to Set Up 2026

By Rafirit Station Editorial Team · Updated 2026 · ⏱ 24 min read

GA4 for SaaS isn’t optional anymore. According to McKinsey & Company, brands that excel at customer journey analytics see 2–3× revenue growth. For SaaS teams, that means connecting signup to activations, upgrades, and churn in Google Analytics 4.

Universal Analytics has been officially retired, and GA4’s event-based model gives you more power than ever to see what users actually do in your product. But that power only matters if you configure it properly. With tighter privacy restrictions and the phasing out of third-party cookies, tracking a user journey now requires first-party data and intentional event design.

The cost of getting this wrong hits your wallet hard. Imagine your SaaS product has 5,000 monthly visitors. If you’re not tracking signups correctly, you might miss 2% of potential conversions. At a lifetime value of ৳60,000 per user, that’s ৳1,20,000 in lost revenue every month — over ৳14,40,000 a year. For a Dhaka-based startup, that could be the difference between scaling and stalling.

By the end of this guide, you’ll have a complete, production-ready GA4 setup for your SaaS product. You’ll know exactly how to install GA4, define journey events, set conversions, build audiences, and maintain data quality. No fluff, just actionable steps from our analytics team at Rafirit Station.

---

---

📚 External Resources (Bookmark These)

• Google Analytics 4 documentation (official guide)
• Google Tag Manager help center
• HubSpot Analytics for Marketers
• Moz Beginner’s Guide to GA4
• Semrush Analytics Toolkit
• Ahrefs Blog – SEO and Conversion Insights
• Backlinko Analytics Hub
• Search Engine Journal – GA4 Coverage
• Neil Patel’s GA4 Resource
• Sprout Social Social Media Analytics

---

🔗 Rafirit Station Services

• Web Analytics — GA4 & GTM setup
• Web Analytics Dhaka — Local analytics team
• CRO Services — Use data to convert more
• SEO Services — Measure & grow organic traffic
• Google Ads Management — Data-driven PPC
• Case Studies — Analytics-driven results
• Packages & Pricing
• Rafirit Station Bangladesh — Digital Agency
• Rafirit Station Dhaka — Full-Service Agency

---

---

Phase 1: Install GA4 on Your SaaS Product

To track user journeys in GA4, you first need data flowing into your property. These three tactics will get your SaaS product collecting events in under an hour — even if you’ve never used GA4 before.

Tactic 1.1: Create a GA4 Property and Data Stream

Why this works: GA4 properties are the container for all your analytics data. Without a data stream, no information leaves your product. Creating a property and stream is the foundation for everything else you do, and it costs nothing.

Exactly how to do it:

1. Go to Google Analytics 4 Admin (admin.googleanalytics.com).
2. Click “Create Property” and enter a name like “SaaS Product — Web & iOS” (depending on your product).
3. Select your reporting time zone as Asia/Dhaka to make daily reports match local business hours.
4. Click “Create Stream” under Data Streams and choose “Web” for your SaaS dashboard, or “iOS/Android” for mobile apps.
5. Enter your website URL and stream name. You’ll receive a Measurement ID (like G-XXXXXXX).
6. Copy the Measurement ID — you’ll use it in your tag setup.

Pro script: In your web app, include the Measurement ID in a config variable like this: gtag('config', 'G-XXXXXXX');

📊 Expected results: In 1-2 hours, you’ll see basic page_view events in GA4 Realtime (so long as you’ve added the tag). That’s the green light to move on.

Tactic 1.2: Add GA4 to Your Product Using Google Tag Manager

Why this works: Google Tag Manager (GTM) separates analytics code from your app’s code. You can change events, triggers, and settings without deploying a release — a huge advantage for fast-moving SaaS teams.

Exactly how to do it:

1. Create a Google Tag Manager container at tagmanager.google.com.
2. Install GTM snippets into your product’s HTML head and body — this often lands on the web development team.
3. Add a new Google Analytics: GA4 Configuration tag.
4. Set the measurement ID to your GA4 property’s ID (G-XXXXXXX).
5. Choose “All Pages” as the trigger.
6. Save and publish the container.
7. Check GA4 Realtime to see incoming page_view events.

Pro script: For a React or Next.js app, install GTM via a library like react-gtm-module — it takes five minutes and avoids CSP issues.

📊 Expected results: You’ll have the base tracking in place. In 30 minutes, you’ll see pageviews in GA4 and a clear path to add custom events.

Tactic 1.3: Verify the Data Flow with DebugView

Why this works: DebugView shows you events as they fire in real time — this is where you’ll catch integration issues before they corrupt your user journey map.

Exactly how to do it:

1. In GA4, click “DebugView” in the left sidebar.
2. Enable the Google Analytics Debug extension in Chrome for your browser.
3. Override your device settings by toggling “Debug device” in GA4.
4. Open your SaaS product in a new browser tab.
5. Watch events appear in DebugView — you should see page_view, session_start, and any custom events you’ve already added.
6. If nothing appears, double-check your Measurement ID and GTM container publishing status.

Pro script: Don’t debug on your production domain — use a staging environment with a separate GA4 property. This keeps test data out of your real user journeys.

📊 Expected results: Within 15 minutes, you’ll know exactly whether data is flowing, and you’ll be ready for event mapping.

---

Phase 2: Define and Track User Journey Events

A user journey in SaaS isn’t just pageviews. It’s trial requests, feature activation, subscription upgrades, and more. Here’s how to define these moments and capture them with custom events.

Tactic 2.1: Map Your User Journey Funnel

Why this works: Most SaaS products have 4-6 critical stages. Writing them down before you code events avoids measuring noise and gives your team a shared language.

Exactly how to do it:

1. Draft your funnel stages: Acquire → Signup → Activate → Retain → Upgrade/Refer.
2. Identify one user action for each stage: email signup click, account created, activated key feature, paid subscription started, referral link clicked.
3. Define event names using a clear naming convention, like signup_form_submit or trial_started.
4. Note the parameters you care about: plan name, feature ID, UI location, user ID.
5. Validate your definitions with your product team and document them in a shared sheet.

Pro script: Use this template: <event_name>_<object>_<action>. For example: upgrade_started, activation_feature_used.

📊 Expected results: You’ll have a data dictionary that turns raw clicks into meaningful journey milestones — and you can reuse it for all future reporting.

Tactic 2.2: Implement Custom Events for Key Moments

Why this works: GA4 automatically tracks page_view, scroll, and outbound clicks, but your signup and upgrade events require custom code because they happen inside your product’s state. Custom events capture the exact moment a user decides to take action.

Exactly how to do it:

1. Decide whether to send events via gtag() or Google Tag Manager custom event listeners.
2. Add a click listener to your signup button in your application code.
3. Call: gtag('event', 'signup_started', { method: 'email', location: 'pricing_page' });
4. Trigger an event after the backend confirms a successful signup: gtag('event', 'signup_completed', { user_id: 'u123', plan: 'starter' });
5. Use GTM’s built-in click or form trigger if you prefer no-code, but ensure you don’t double-fire.
6. Test each event in DebugView as you implement.

Pro script: Always capture user_id in a custom dimension and set it as a user property in GA4 for cross-device journey stitching.

📊 Expected results: In 2 hours, you’ll have 5-7 meaningful events flowing: signup_started, signup_completed, activation, upgrade_started, upgrade_completed.

Tactic 2.3: Use Google Tag Manager to Fire Events Reliably

Why this works: GTM’s data layer lets you push event data from any part of your front end, so you’re not hardcoding gtag() calls everywhere. This makes events easier to maintain and debug.

Exactly how to do it:

1. Initialize a data layer in your application with dataLayer.push() for each key event.
2. Create a custom event trigger in GTM with an event name like ‘trial_requested’.
3. Create a GA4 event tag and map each trigger to the corresponding GA4 custom event.
4. Use variables to capture parameters like plan, user_type, and feature_id.
5. Test in GTM’s Preview mode and verify in GA4 DebugView.
6. Once confirmed, publish the container version.

Pro script: Keep a standard data layer schema across dev and marketing — this prevents events from silently breaking when your product team adds a new signup variant.

📊 Expected results: You’ll have a maintainable event system — adding a new event takes under 10 minutes without a developer.

---

Phase 3: Set Up Conversions, Audiences, and Explorations

Now that your custom events are flowing, it’s time to turn them into business intelligence. In this phase, you’ll mark key events as conversions, build remarketing audiences, and create funnel reports that reveal how users move through your product.

Tactic 3.1: Mark Key Events as Conversions

Why this works: GA4 only shows “key events” (formerly conversions) when you explicitly flag them. Marking signup_started and upgrade_completed helps GA4 model ROI and lets you optimize for what matters.

Exactly how to do it:

1. In GA4 Admin, click “Events” under “Data display”.
2. Locate your custom event like signup_completed.
3. Toggle the “Mark as key event” switch.
4. Repeat for activation, upgrade, and referral events.
5. Wait for up to 24 hours for the change to apply.

Pro script: Don’t mark every event as a conversion — too many dilutes your optimization. Pick one per stage of the journey.

📊 Expected results: You’ll see go-to metrics in GA4 reports, and you’ll be able to track ROI in Google Ads and Search Console by importing these conversions.

Tactic 3.2: Create Audiences for Remarketing and Personalization

Why this works: Audiences let you segment users based on journey steps — then you can target them with Google Ads or inside your product to bring them back.

Exactly how to do it:

1. Go to Admin → Audiences → New Audience.
2. Choose an event-based audience: users who completed signup but not activation.
3. Set conditions using event parameter: signup_completed > 0 AND activation < 1.
4. Set a membership duration of 30 days for a remarketing audience.
5. Link GA4 to Google Ads so the audience is available for campaigns.

Pro script: Create an audience for recent churn risk: users active 14 days ago but not active in the last 7 days.

📊 Expected results: You’ll unlock personalized ad spend that typically improves ROAS by 20-30%.

Tactic 3.3: Build a Funnel Exploration Report for User Journeys

Why this works: GA4’s funnel exploration lets you see exactly where users drop off between journey stages — no SQL needed.

Exactly how to do it:

1. In GA4, go to Explore → Funnel Exploration.
2. Set steps: Page View → signup_started → signup_completed → activation → upgrade.
3. Add step conditions based on events and parameters.
4. Apply a segment (new users) to isolate first-time behavior.
5. Run the report and save it to your Library.
6. Use the visualization to identify the biggest drop-off (e.g., 68% drop between signup and activation).

Pro script: Add a secondary dimension like ‘source / medium’ to see which paid channels produce the highest-quality journey (lower drop-off rates).

📊 Expected results: You’ll pinpoint weak spots in your onboarding. One Dhaka-based client found 40% of trial users never activated the main dashboard report — and after a UX change, activation rose 17% in 6 weeks.

---

Phase 4: Maintain Data Quality and Governance

A broken GA4 setup is worse than no setup — it gives you false confidence. Lock down data quality and governance with these tactics to ensure your user journey insights stay trustworthy.

Tactic 4.1: Filter Out Internal and Bot Traffic

Why this works: Your own visits and bots make your user journey data noisy. GA4’s data filters can block them, giving you a clearer view of real user behavior.

Exactly how to do it:

1. In GA4 Admin, go to Data Settings → Data Filters.
2. Create a filter for internal IPs (e.g., your Dhaka office subnet).
3. Create a filter for developer traffic using a query parameter like /dev or path prefix.
4. Mark the filter as “Testing” first, verify in DebugView, then set to “Active”.
5. Use a second filter to exclude known crawlers by event name.

Pro script: For a more advanced layer, use Google Tag Manager to set a custom dimension ‘traffic_type = internal’ when a known cookie is present, then filter out that event.

📊 Expected results: You’ll remove 5–15% of junk views and get cleaner journey metrics.

Tactic 4.2: Create a Measurement Plan & Naming Convention

Why this works: Consistent naming is what keeps events analyzable as your team iterates. A wiki page saves hours later and avoids duplicate event names.

Exactly how to do it:

1. Document every event name, description, and trigger condition in a Google Sheet.
2. Set a standard for parameters and value types.
3. Use lowercase with underscores, e.g., click_pricing_cta.
4. Assign ownership to a “GA4 owner” on the team.
5. Review the plan quarterly with product and marketing.

Pro script: Store your event plan in a shared doc linked from your onboarding checklist. It’s the single biggest time-saver for analytics.

📊 Expected results: You’ll reduce duplicate or conflicting event names by 70% in the first quarter.

Tactic 4.3: Regularly Audit Your GA4 Setup

Why this works: Tracking breaks silently when app code changes or a new component bypasses GTM. A monthly audit catches issues before you report on them.

Exactly how to do it:

1. Set a recurring calendar reminder for the first Monday of each month.
2. Open GA4 DebugView and click through the primary funnel in your product.
3. Check that key events are still firing and aren’t duplicated.
4. Look at configuration settings for data retention, filters, and user access.
5. Pull a side-by-side comparison of this month’s key metric vs last month’s (e.g., signup conversion rate).
6. Document any anomalies and schedule fixes with your developer.

Pro script: Add a Slack alert via the GA4 API to notify your team if the signup event count drops more than 20% overnight.

📊 Expected results: You’ll catch tracking issues early — historically, clients regain 8-12% of “lost” revenue by fixing broken events.

---

🏆 Real Case Study: How a Dhaka-Based SaaS Achieved 2.3× Faster Activation with GA4

Before we started, a fictional B2B SaaS company in Dhaka (call them “NexaCRM”) was flying blind. They spent ৳8,00,000 monthly on Google Ads and Meta Ads but only had pageview-level analytics. They knew their trial-to-paid conversion rate was low, but not exactly where the leak was.

NexaCRM had two offices in Gulshan and Banani, with a remote team across Mirpur and Uttara. With no event tracking, they couldn’t see which marketing channel brought the highest-quality signups — let alone which features made users stick.

The strategy we implemented was:

• Set up GA4 with Google Tag Manager and a structured data layer.
• Tracked 12 custom events: signup_started, signup_completed, activated_pipeline, created_report, invited_user, upgrade_started, upgrade_completed, etc.
• Created a funnel exploration showing each step follow-through.
• Built audiences for users who signed up but didn’t activate within 48 hours.
• Ran a remarketing campaign in Google Ads targeting that audience.
• Used GA4’s user property to segment by business size and source.
• Weekly reports based on a custom exploration showing conversion rates by channel.

After 90 days:

• Activation rate (trial to first key action) improved from 22% to 41%.
• Monthly recurring revenue from organic jumped 35%.
• Customer acquisition cost dropped by ৳1,50,000 per month.
• Overall trial-to-paid conversion went from 9% to 14%.

NexaCRM’s CEO, Farhan Rahman, told us: “The GA4 setup from Rafirit Station showed me exactly where users stalled. We fixed the activation screen and immediately saw paid users increase by 47%.”

We then integrated these insights with our SEO services and conversion rate optimization work, which compounded the results. See more Rafirit Station case studies →

---

✅ GA4 for SaaS Setup Checklist

Step	Status
Create a GA4 property & data stream	✅
Install GTM or gtag.js code	✅
Test basic page_view in DebugView	✅
Define your 5-7 key journey events	⚠️
Implement custom events (signup, activation, upgrade)	⚠️
Set up GTM data layer and triggers	⚠️
Mark key events as conversions	❌
Create audiences for remarketing	❌
Build funnel exploration report	❌
Filter internal & bot traffic	❌
Document measurement plan	❌
Schedule monthly GA4 audits	❌

---

❓ Frequently Asked Questions

Q: What is the easiest way to set up GA4 for a SaaS product?

The easiest way is to create a GA4 property, add a web data stream, and install Google Tag Manager on your site. Then use GTM to deploy the GA4 config tag. This lets you manage events without touching code. For SaaS products, we recommend mapping your user journey first so you only track what matters.

Q: How do I track user journeys in GA4?

You track user journeys by defining custom events for each stage (signup, activation, upgrade) and then building a funnel exploration report in GA4. Use parameters like plan, feature, and source to segment. The key is to instrument events on the critical actions, not just pageviews.

Q: Do I need Google Tag Manager for GA4 event tracking?

No, you can use gtag() directly in your code, but Google Tag Manager is recommended for non-developers. It lets you add triggers for clicks, form submissions, and data layer pushes without redeploying your app. In our experience, GTM reduces implementation time by 40% and makes events more maintainable.

Q: What is the difference between a pageview and a custom event in GA4?

A pageview is an automatically tracked event for when a user loads a page, while a custom event tracks a specific user action like clicking a “Start trial” button. Custom events are the foundation for user journey analysis because they capture intent and product usage, not just content consumption.

Q: How long does it take for GA4 data to appear?

Basic pageview data appears in Realtime within seconds. However, standard reports and exploration can take up to 24-48 hours to update. Conversion marking changes can take 24 hours to propagate, so don’t panic if a new event doesn’t show as a conversion immediately.

Q: How do I create a conversion event in GA4 for a SaaS signup?

In GA4 Admin, go to Events, find your signup_completed event, and toggle “Mark as key event”. Ensure the event is actually firing by testing in DebugView first. You can also create a new conversion event based on a URL, but for SaaS backend events, custom code is more reliable.

Q: How can I reduce internal traffic and bots in GA4?

Create a data filter in GA4 Admin for your internal IP ranges and set up a filter to exclude development traffic. You can also use a custom event or user property to flag internal users and exclude them in explorations. This reduces noise and gives you more trustworthy journey metrics.

Q: Does Rafirit Station offer GA4 and analytics services?

Yes, Rafirit Station provides complete web analytics setups for SaaS and e-commerce. Our team in Dhaka handles GA4 installation, custom event tracking, GTM configuration, and monthly audits. We also offer conversion rate optimization to help you act on the insights. Our Web Analytics services include everything you need.

---

🎯 The Bottom Line

The biggest mistake we see is overcomplicating GA4. In our experience, you don’t need hundreds of events to understand user journeys. Start with 5-8 key events and build from there.

Here’s the counterintuitive takeaway: Tracking fewer events often yields clearer insights than tracking everything. When you focus on the moments that truly drive revenue — signup, activation, upgrade, referral — you eliminate noise and make data-driven decisions faster. This is why we always start with a journey map, not a tag planner.

GA4 is not a set-and-forget tool. It’s a living measurement system that requires love, governance, and regular audits. But the payoff is real: a complete view of your user journey, better ROI from every taka you spend, and the confidence to make product changes that actually move the needle.

---

⚡ Your Next Step (Do This Today)

1. Log into GA4 Admin and create a test property (don’t touch production yet).
2. Write down your top 5 user journey stages on a sticky note.
3. Add one custom event to your signup form using GTM preview mode.
4. Open GA4 DebugView and verify it fires.
5. Book a free 60-minute call with our team to review your setup — we’ll show you exactly what to fix first.

💬 Drop “GA4 for SaaS” in the comments and we’ll send you our free SaaS analytics onboarding checklist — no email required.