How to Implement User Segmentation for Targeted Content in FlutterFlow

Open FlutterFlow's Firestore panel and add the following fields to your users collection schema: explicitSegment (String — set during onboarding, e.g., 'freelancer', 'student', 'enterprise'), behaviorSegment (String — set by Cloud Function, e.g., 'power_user', 'at_risk', 'new_user'), abGroup (String — static assignment, e.g., 'A' or 'B'), interests (String Array — user-selected topics), and segmentUpdatedAt (Timestamp). Having separate explicit and behavior fields lets you combine them for targeting logic: show a feature to users who are both 'enterprise' segment AND 'power_user' behavior.

Build an onboarding flow in FlutterFlow with 2-3 screens that ask the user about their role and interests. Use a single-select Button Group for role ('Freelancer', 'Startup', 'Enterprise', 'Student') and a multi-select chip grid for interests ('Marketing', 'Development', 'Design', 'Finance'). Store selections in page state variables. On the final onboarding step, use FlutterFlow's Update Document action to write explicitSegment and interests to the user's Firestore document. This runs once at account creation — users can update it from a Profile > Preferences screen later.

Create a scheduled Cloud Function that runs every night, reads user activity for the past 30 days, and assigns a behaviorSegment label. Define your segment criteria: 'power_user' = opened app 20+ times and has non-zero purchases; 'at_risk' = was active 60 days ago but has not opened app in 14+ days; 'new_user' = created account in the last 7 days; 'engaged' = everything else. The function queries your activity or sessions collection, evaluates each user against the criteria in priority order, and batch-updates the behaviorSegment field. This function runs server-side so the logic is consistent and cannot be spoofed by clients.

1// functions/updateSegments.js
2const { onSchedule } = require('firebase-functions/v2/scheduler');
3const { getFirestore, Timestamp } = require('firebase-admin/firestore');
4const { initializeApp } = require('firebase-admin/app');
5
6initializeApp();
7
8exports.updateSegments = onSchedule('every day 02:00', async () => {
9  const db = getFirestore();
10  const now = new Date();
11  const day14 = new Date(now - 14 * 86400000);
12  const day7 = new Date(now - 7 * 86400000);
13  const day30 = new Date(now - 30 * 86400000);
14  const day60 = new Date(now - 60 * 86400000);
15
16  const usersSnap = await db.collection('users').get();
17  const batch = db.batch();
18
19  for (const userDoc of usersSnap.docs) {
20    const user = userDoc.data();
21    const createdAt = user.createdAt?.toDate() || new Date(0);
22    const lastSeen = user.lastSeen?.toDate() || new Date(0);
23
24    // Count sessions in last 30 days
25    const sessionsSnap = await db.collection('sessions')
26      .where('userId', '==', userDoc.id)
27      .where('createdAt', '>=', Timestamp.fromDate(day30)).get();
28    const sessionCount = sessionsSnap.size;
29
30    let segment = 'engaged';
31    if (createdAt >= day7) {
32      segment = 'new_user';
33    } else if (lastSeen < day14) {
34      segment = 'at_risk';
35    } else if (sessionCount >= 20) {
36      segment = 'power_user';
37    }
38
39    batch.update(userDoc.ref, {
40      behaviorSegment: segment,
41      segmentUpdatedAt: Timestamp.fromDate(now),
42    });
43  }
44  await batch.commit();
45});

In FlutterFlow add content blocks to your home or feed page for each segment variant. For example: a 'Power User' tips banner, an 'At Risk' re-engagement offer card, and a 'New User' onboarding checklist. Stack all variants in the same Column or Stack widget, then configure each block's Conditional Visibility. Click the visibility eye icon > Set Condition. Bind the condition to the authenticated user's behaviorSegment field from Firestore (use the 'Authenticated User > behaviorSegment' path). Set the condition: value == 'power_user' for the tips banner, value == 'at_risk' for the offer card. Only one block will be visible at a time.

For A/B testing, assign users to a static experiment group when their account is created so the group never changes mid-test. In your FlutterFlow account creation flow, after the Create Document action that creates the user profile, add a Custom Function called assignAbGroup that generates either 'A' or 'B' with a 50/50 random split. Write this value to the abGroup field. Because abGroup is assigned once and never updated by the nightly segmentation function, users stay in the same group for the duration of your experiment. Track conversion events in Firebase Analytics using the abGroup value as a user property so you can compare groups in Analytics reports.

1// Custom Function: assignAbGroup.dart
2String assignAbGroup() {
3  final random = DateTime.now().millisecondsSinceEpoch % 2;
4  return random == 0 ? 'A' : 'B';
5}