FocusForge. Two weeks live, 18 installs, 0 signups. Here's what I'm learning.
Two weeks since FocusForge launched as product two of the HelixLabs ecosystem. Here's the honest picture.'
18 installs from organic Chrome Store search. 0 signups. 0 revenue. Prompt Helix sits at 103 total installs, 1 weekly active user, also £0 revenue.
The pattern is identical to Prompt Helix's early days where people install and don't create accounts. Which tells me the onboarding experience isn't creating enough urgency to sign up before people get value from the free tier.
The irony is that FocusForge's free tier is genuinely useful on its own. Time tracking, site blocking, grayscale mode, daily reports. all free, no account needed. Which means people install it, get value, and have zero reason to create an account or upgrade.
Sound familiar? It's the exact same mistake I made with Prompt Helix before v1.0.2.
The fix for Prompt Helix was a 25 query daily limit that creates a natural upgrade trigger. FocusForge has the AI coaching and Nuclear Option locked behind Essential at £7/month. But the free tier is still too complete how someone could use it indefinitely without ever feeling the need to upgrade.
What I'm thinking about now is that the problem the free tier being too generous, or is it that people aren't using it enough to hit any wall at all? If someone installs FocusForge and opens it twice then forgets it exists, no conversion trigger matters.
The return behaviour problem is something several founders on my last post flagged. The daily limit only works if they come back to hit it.
Current thinking is I need a re-engagement mechanism. Something that brings people back to the extension in the first 48 hours before they forget it exists. An onboarding sequence, a daily nudge, something.
Still figuring it out. Would love to hear from anyone who's solved the day 1 to day 7 retention problem for Chrome extensions specifically.
Chrome Store: chromewebstore.google.com/detail/focusforge/hdkabchfflgnnonnhffkcmhgbenfoaci
helixlabs.studio
Thanks for sharing this so honestly—it's painful but incredibly valuable to see the raw numbers and the pattern between both your products. The "free tier is too complete" problem is such a classic trap, especially for builders who want to deliver real value upfront. It's easy to forget that generosity doesn't always drive conversion.
What really stands out is your insight about return behavior being the core issue, not just the upgrade trigger. A daily limit doesn't matter if they never hit it.
Here's my question: Have you considered adding a "streak" or "focus score" that only persists if they're logged in? Something like: free tier shows today's focus time, but creating an account saves history, unlocks weekly trends, and lets them compare productivity over time. That way, the value of signing up grows the more they use it, rather than relying on a hard paywall. Do you think that could shift the day 1→7 retention curve?
the streak and focus score idea locked to account is genuinely the best conversion mechanic suggestion I've received. it flips the logic. instead of "sign up to unlock features" it becomes "sign up because your data is worth saving." the value of the account grows with usage rather than being a gate before usage. going to think seriously about implementing this. the weekly trends and history being account-only is a much softer ask than "upgrade to unlock Nuclear Option."
My first reaction is 18 installs is probably way too early to blame the free tier.
If people were hammering it every day and never upgrading, that’s one problem. But if they install it, poke around once, then forget it exists, that’s a completely different issue.
Feels more like a day 1 retention / habit problem than a pricing one.
For this kind of tool . . . getting someone to come back tomorrow probably matters way more than where the paywall sits.
you're right and this is the more honest framing. 18 installs is nowhere near enough data to diagnose a free tier problem. what I actually don't know is whether people are using it daily and not upgrading or installing once and forgetting it exists. with 0 signups I have no visibility into what happens after install at all. that's the real problem. I'm blind to post-install behaviour. the day 1 retention hypothesis feels more accurate than the free tier one. getting someone to come back tomorrow is the actual unlock.
Full disclosure: I'm Avery Lin (avrlin). I've been packaging a Live Agent DFY setup (pair/screen-share install for OpenClaw-style agents) with AI assistance, so take this as adjacent interest, not neutral advice.
Docs alone stall a lot of founders — the unblock is usually someone on a call walking the install, secrets, and first successful run.
Curious — for agent tooling, do buyers finish self-serve, or do they still need a live hand-hold to go live?
That fork you describe — too-generous free tier vs. not enough usage to hit any wall — is the exact one I spent four months on the wrong side of. We kept tightening pricing and adding upgrade triggers, when the actual answer was that our users weren't returning often enough for any trigger to matter.
What finally cut through for me wasn't another pricing experiment — it was looking at the gap between install and day-3 return. If most of your 18 installs aren't opening the extension on day 2 or 3, the wall is irrelevant; you don't have the repeat usage to gate. If they are returning but stopping at the same place, then the free tier is the actual thing.
Worth pulling that one number before you redesign the tier.
The day 1 to day 7 retention problem for extensions is almost always an 'invisible value' problem more than a re-engagement problem. Users who install and don't return usually didn't internalize what the tool was for during installation -- they clicked install on a vague impulse and it's already not top-of-mind by day 2.
The daily limit mechanic works for Prompt Helix because the limit makes the value visible every time you hit it. That's not re-engagement, it's value realization -- the limit forces users to notice what they're getting. FocusForge needs its own version of that signal.
For a focus tool specifically, the 'value realization' moment is usually retrospective: 'I was able to get X done because I wasn't distracted.' The daily reports you mentioned are the mechanism for that, but they have to be seen on a day when the user actually experienced a good focus session. The onboarding optimization isn't a drip sequence -- it's triggering the first meaningful report at the right moment (after a session that hit a block threshold, not after arbitrary time passage).
The underlying question: for the 18 installs, did anyone use the site blocking feature for a full work session, or did they explore the extension and close it? That behavior gap is where the retention answer lives. If nobody used it for a real session, the install converts to session conversion is the bottleneck, not session to signup.
the install to session conversion being the real bottleneck is the reframe I needed. I've been assuming people are using it and not returning when the more likely reality is they explored the popup, didn't set anything up, and closed it before the product did anything at all. the daily report only creates value realisation if a real session happened first. without that it's just empty data. the onboarding question I should be asking isn't "how do I get them to come back" it's "how do I get them to complete one real session before they close the extension for the first time." that's the actual conversion point I've been missing.
The free tier problem you're describing is really a workflow problem in disguise.
People aren't hitting a wall — they're not building a habit first. The upgrade trigger only works if the product becomes part of their daily routine before they see the limit.
For the 48-hour retention problem specifically: the most effective thing I've seen isn't a nudge — it's a "first win" moment. Something that makes the user feel the product worked for them personally in the first session.
For FocusForge, what does that first win actually look like? Is there a moment where the user sees a result that surprises them?
the first win moment for FocusForge is probably the first time the block actually triggers. not the setup, not the report, not the grayscale, the moment where you're about to open Reddit out of habit and the extension stops you. that's the moment where the product becomes real. before that it's just settings you configured. after that it's something that actually changed your behaviour.
the surprise element you're asking about is interesting. right now the daily report shows time saved but if someone only used it for one session there's nothing surprising in it yet. the report needs enough data to feel personal before it creates the "wow this knows me" moment. which means the first win has to come from the block itself not the report.
what does that look like in practice probably a full screen intervention when the block triggers rather than a quiet banner. something that makes the moment feel significant rather than easy to dismiss. the friction of the block is the feature, not a bug to smooth over.
The “free tier too generous vs users not returning enough” distinction feels like the whole game here.
If people install, use it once, and disappear, a paywall won’t fix much. If people are coming back and still not signing up, then it’s probably a packaging problem.
For a focus tool, I’d look for the first moment where the product creates a tiny bit of pain or pride:
Then ask for account creation right after that. Basically: ask when they have something they don’t want to lose.
"ask when they have something they don't want to lose" is the clearest version of the signup trigger I've heard across this whole thread. it reframes account creation completely not as a gate before value but as a way to protect value already created. the first blocked distraction or first "you saved 23 minutes today" moment is exactly when that ask makes emotional sense. right now the signup prompt appears before any of those moments happen which is completely backwards. going to restructure the onboarding flow around this principle . deliver the value moment first, then ask for the account immediately after while the feeling is fresh.
That cohort framing is exactly the right diagnostic lens — "what did day-7 retained users do on day 1 that day-1 churned users didn't?" maps directly to how I think about root cause analysis in BI work. Isolate the population difference, trace it back to the earliest signal.
The feature-level day-0 events will probably surface the answer pretty fast once you have enough volume to segment. My guess is it comes down to whether they hit the blocking feature in session 1 or not — that first tangible value moment is usually the deciding variable.
Once you're structuring the data model for this kind of behavioral tracking, SQL cohort patterns can get complex fast. I documented a bunch of these query patterns in a handbook if useful → https://growthwithshehroz.gumroad.com/l/gwiow
the first tangible value moment hypothesis feels right for FocusForge specifically. for a focus tool the value isn't abstract it's the first time the extension actually blocks you from a site you were about to waste time on. if that doesn't happen in session one the product is just another icon in the toolbar.
the day 0 event I need to track is probably "first block triggered" not "extension opened" those are completely different signals about whether the product did anything useful yet.
"First block triggered" is the right north star event. I'd also instrument the attempted-but-blocked URL as a property — over a few weeks that becomes your best signal for which sites are doing the actual damage, and doubles as a marketing content angle. Plus tracking time-from-install to first block — if that's >24h, your onboarding is probably the leak, not the value.
the time-from-install to first block metric is the one I hadn't considered and it's probably the most actionable signal. if that number is consistently above 24 hours it tells me the onboarding isn't getting people to set up their first block fast enough which means the value never triggers in the window where they're still curious. the blocked URL as a property is smart too. after a few weeks that data tells me exactly which sites are the real problem for my users which reshapes everything from the Chrome Store description to the marketing copy. going to add both to the instrumentation list.
Really insightful additions — the blocked URL as a property is exactly what I was hinting at too. In data work, we call this 'low-cardinality dimensions with high behavioral signal' — a handful of URL patterns that segment your entire user base by actual use case.
Worth tracking blocked URL category (social/news/entertainment) + time-of-day in the same event. You'll likely find completely different engagement patterns for morning users vs evening users, which reshapes when and how you message them during onboarding.
This kind of behavioral segmentation is where early-stage SaaS products find their real retention levers. If you're building out data instrumentation further, I put together a free diagnostic scripts pack with patterns that transfer well to product analytics → https://growthwithshehroz.gumroad.com/l/psmqnx
the time of day angle hadn't occurred to me and it's genuinely useful. morning doomscrollers are a completely different profile from evening ones. different sites, different emotional state, different reason for being there. if the data shows a cluster of evening Reddit users that reshapes everything from when the warning banner appears to what the AI coaching says. blocking URL category plus time of day in the same event is a cheap addition that pays for itself in segmentation clarity later. going to add both properties to the instrumentation plan.
Exactly right — time of day is one of those dimensions that looks obvious in hindsight but almost never gets instrumented upfront. The intent gap between a morning session (quick habit check) and an evening session (deeper distraction spiral) is completely different, which means the right intervention is different too. Once you have that dimension in your events, you can also layer it against which sites trigger the block — late-night social vs. mid-morning news are distinct patterns that deserve distinct messaging. Good that you're baking it in early rather than retrofitting it later.
the late night social versus mid morning news distinction is exactly the kind of segmentation that changes what you say and when you say it. someone doomscrolling Reddit at 11pm needs a completely different intervention than someone checking news at 9am when they should be working. baking time of day in now means that dimension is already clean when there's enough data to act on it. retrofitting it later means rewriting the events schema which is the kind of technical debt that quietly kills product iteration speed.
The event schema point is the one I'd double down on — baking the time dimension in early is one of those decisions that looks trivial now and saves weeks later. The doomscrolling-at-11pm vs productivity-check-at-9am distinction is also a great framing for messaging tests once you have enough data. Two completely different audiences that need completely different copy, and you'll have clean segmentation to act on it.
the schema debt point is real — retrofitting time_of_day means rewriting whatever ETL or event processing pipeline is downstream, and if you've already got aggregated tables, those need to change too.
the broader principle: any dimension that could drive segmentation is worth capturing raw from day one, even if you don't query it for months. device, session depth, acquisition source, time_of_day — they're cheap to log at event creation time and expensive to reconstruct from session timestamps later.
the only counterargument is schema bloat, but that's a much nicer problem to have than missing data when you're finally ready to act on it. worth the early column.
Same boat here. Two weeks in, built a competitor tracker for SaaS founders. Getting installs but converting to signups is a different game entirely.
same problem different product. the install to signup gap is brutal when you can't see what's happening on the other side of it. how are you approaching it for the competitor tracker? curious whether the problem is people don't see the value or they see it but don't want to commit to an account.
the part that jumped out — youre framing it as onboarding/retention but maybe the upstream q is diff: did those 18 installs come from someone with real pain, or from "ooh nice tool" curiosity browsing? bcs no nudge mechanic saves the second group, they forget you exist regardless. on prompt helix the daily limit worked partly bcs ppl already had the habit. would dig into where the 18 came from — what search query, what problem they typed — and see if any came back even once. that signal tells you more than retention tactics imo
this is the question I actually can't answer yet and it's probably the most important one. I don't know what search query brought those 18 people in. Chrome Store doesn't give me that granularity. but your framing is right that if they came from curiosity browsing rather than real pain no retention mechanic saves them. the installs from organic search suggest some real intent but I genuinely don't know. going to try to instrument this better.
yeah chrome store granularity is a black box on intent, basically guessing from rankings. one cheap-ish workaround we used on hosting was a single free-text post-install nudge — "what brought you here today" — no required signup, no other fields. you lose a few installs but the answers you get back are the actual search vocabulary people typed, not your hypothesis about it. even five raw answers usually reshape the listing copy more than a week of analytics would. are you against friction at install in principle, or open to testing it on the next 50?
not against friction in principle. against friction that doesn't pay for itself. a single free text field asking "what brought you here today" with no required signup is low enough friction that I'd test it. the insight is worth more than the installs lost especially at this volume where every data point matters.
the search vocabulary angle is the part that appeals most. I'm essentially guessing what people typed to find Prompt Helix and FocusForge right now. five real answers would probably reshape the Chrome Store descriptions more than anything else I could do. going to add this to the next update for both extensions.
open to testing on the next 50. at 26 FocusForge installs that window is coming up soon anyway.
yeah that's the right filter — friction only worth it if it pays for itself. the next 50 install window is enough for a directional read, not statistical, but qualitative pattern shows up fast tbh. even 10-15 free-text answers usually surfaces the dominant intent buckets. if 60%+ say the same job-to-be-done, thats your search vocab right there. worth keeping the field optional and single line prob — no required submit, no second screen.
nice. one tip when those answers start coming in — group them by whether they mention a specific pain ("cant stop scrolling reddit") vs generic outcome ("want to focus more"). pain-anchored ppl tend to actually come back, outcome-only ones are usually the install-and-forget crowd. also worth tagging which chrome store search term they came from if you can match it via search analytics — that pairing is where the listing copy rewrites pay for themselves. ngl 26 installs is low for stat sig but at this stage qualitative beats quantitative anyway. you planning to show the prompt only on first session, or also on day 2 if they come back?
the pain versus outcome segmentation is the right filter. pain anchored users have a specific moment they're trying to fix. outcome users have a vague aspiration. those are completely different conversion paths and treating them the same is probably why generic retention tactics feel hollow.
on when to show the prompt . planning first session only right now. the logic being that if they come back on day 2 without being asked that's already a signal they found value and the question feels less urgent. but your point makes me reconsider. if they come back on day 2 and still haven't set up a block or defined a goal then showing the prompt again on day 2 with a slightly different framing like "still getting started?" might catch the people who opened it on day 1 out of curiosity but didn't commit to anything. worth testing both.
first session only is the right call imo — anything later and you're prompting people who already self-selected, so the answers skew. ngl the riskier q is what counts as "completed first session" for focusforge — 5 min of focus, or just opening the app? bcs the pain anchored crowd will bounce mid-session if they get interrupted and never see the prompt. maybe trigger on close-of-session regardless of duration, so you catch the bouncers too. 26 installs is small but the qualitative diff between "i used it for X" vs "i tried it and quit at Y" is gold rn.
“Utility before identity” is exactly the diagnosis. Building an AI product right now and hitting the same wall from a different angle — if people never get past the surface layer, they never experience what the product actually is. For us the identity layer is memory and continuity across conversations. For you it’s the AI coaching. Same problem: the feature that creates loyalty is locked behind a step people don’t take.
the memory and continuity angle is exactly the same problem from a different product angle. the feature that creates loyalty is the one nobody reaches because it requires the step nobody takes. for FocusForge the AI coaching is that feature. for you it's conversation memory. both products have their best feature locked behind account creation which is the step most users don't bother with. have you found anything that gets people past that step?
That “open it twice, then forget it exists” line is the real clue. The product isn’t losing because it lacks features, it’s losing because the first step is too easy to ignore. I see the same thing with dictation. If there’s a mode switch or a separate window, people drift away. DictaFlow tries to avoid that by keeping capture as one hold-to-talk action.
the mode switch friction point is real. every extra step between the user and the value is an uninstall waiting to happen. FocusForge has too many steps before it does anything useful like install, open, set up sites, set limits, then wait to get blocked. that's four steps before any value. going to think about how to collapse that down to one.
The install-to-signup gap is a data problem before it's a product problem — you need to know where in the free tier people are dropping off before you can fix the right thing.
A few things I'd instrument immediately if you haven't:
Your "two opens then forget" hypothesis is probably right, but without that segmentation you're guessing which re-engagement lever to pull. If people aren't opening it on day 2, a daily nudge won't save you — you need something at install that locks in a habit immediately (a "set today's focus goal" prompt on browser open is a good pattern here).
The 48-hour window is everything for browser extensions. Most churn happens before the user even forms a mental model of what the product is for.
As a BI consultant who tracks activation data for SaaS startups, I see this pattern constantly — the free tier is too complete, activation is undefined. Worth reading: I put together a free SQL diagnostic scripts pack that covers tracking patterns → https://growthwithshehroz.gumroad.com/l/psmqnx (different domain, same diagnostic mindset)
the day 0 open rate and day 2 return rate are exactly what I'm blind to right now. I have install numbers but zero visibility into what happens after. your segmentation point is right. without knowing which feature has engagement I'm guessing at which lever to pull. the 48 hour window framing is useful. most of the value I need to deliver has to happen in the first two sessions or the user is gone. going to instrument this properly.
Instrumenting properly is the exact right move. The pattern that tends to work: track feature-level events on day 0 (not just installs), then build a simple cohort view — "what did day-7 retained users do on day 1 that day-1 churned users didn't?" That gap tells you which specific feature is the real hook. The 48-hour window framing is spot-on. Once you have that visibility, you'll know whether it's a segmentation problem or an onboarding friction problem — those have very different fixes. Good luck with the instrumentation — the clarity that comes from that data will make every other decision easier. I put together some free SQL Server diagnostic scripts built around the same "observability first" philosophy → https://growthwithshehroz.gumroad.com/l/psmqnx
the cohort view framing is exactly what I need. "what did day 7 retained users do on day 1 that churned users didn't" is the right question and I don't have the answer yet because I don't have the instrumentation to ask it. right now I'm flying completely blind on post-install behaviour. going to prioritise getting basic event tracking in place before anything else. without that data every product decision is a guess. appreciate the observability first philosophy, it's the right order of operations.
That prioritization is exactly right — instrument first, then let the data drive decisions. The sequence that tends to unlock the cohort question fastest:
That third event is usually what separates "this is useful" from "this is a habit" for focus tools. Once you have it, the day-1 vs. day-7 cohort query almost writes itself — and you'll see immediately whether the gap is about onboarding friction or product-market fit.
If you're thinking about how to model the events schema so cohort queries stay clean as you add more events, this covers the data modeling patterns that make that work: https://growthwithshehroz.gumroad.com/l/vgiex
the three event sequence is exactly the right framework. install to first meaningful action, first session to 48 hour return, then the recurring versus ad hoc split at day 7. that third one is the one I haven't thought about clearly enough. ad hoc users who find it useful once are completely different from habit users who build it into their daily routine. and focus tools specifically live or die on habit formation not utility. if someone uses FocusForge three times a week but never sets a recurring schedule they'll probably churn. if they set a daily focus goal on day 1 they're probably retained. that's the cohort question worth asking. appreciate the data modelling pointer. events schema getting messy as products multiply is exactly the problem I'll hit.
FocusForge is clear, but it still sounds like a Chrome extension, not a serious productivity system.
That matters if you want people to create an account and come back daily.
Right now the product gives utility before identity.
Users install it, use the free layer, and mentally file it as “a blocker.”
The bigger opportunity is to make it feel like a personal execution system, not a browser tool.
Xevoa.com would fit that direction better if you expand beyond blocking into AI coaching, daily discipline, and behavior loops. Cleaner, broader, and more durable than FocusForge.
utility before identity is the sharpest diagnosis I've gotten on FocusForge yet. a blocker is something you install and forget. a personal execution system is something you check in with daily. those are completely different products even if the features overlap.
the AI coaching layer is supposed to be the identity piece how you have something that knows your patterns and talks to you about them. but if people never sign up they never experience that layer at all. so the identity angle exists in the product but nobody's reaching it.
on Xevoa. you've been consistent on this. I'm going to look at that domain seriously this week. not committing to a rebrand but I want to understand what you're seeing that I'm not.
That’s exactly the gap I’m seeing.
FocusForge explains the current utility.
Xevoa gives you room to build the identity layer.
If the product stays as blocking, FocusForge is fine.
But if the real product becomes:
AI coaching
behavior loops
daily execution
personal accountability
focus patterns over time
then “FocusForge” keeps pulling perception back to browser-tool territory.
Xevoa feels more like a system people can build a relationship with.
Short, clean, software-native, and not boxed into one feature.
That matters because the account signup has to feel like entering a personal execution layer, not unlocking extra settings in an extension.
That’s why I keep seeing Xevoa here.
It matches the product you’re trying to become, not just the feature people see first.
the distinction between "unlocking extra settings in an extension" versus "entering a personal execution layer" is the clearest version of the signup problem I've heard. right now the account creation screen feels like admin. it should feel like onboarding into something that knows you and gets smarter over time.
the AI coaching layer is supposed to be that something that builds a picture of your patterns and talks to you about them. but if the product is mentally filed as a blocker before anyone reaches that layer then the identity piece never lands.
I've been sitting with the Xevoa argument across multiple conversations now and I think you're pointing at something real. not the name specifically but the category shift from browser tool to personal execution system. that shift has to happen in the product experience before it can happen in the brand.
so the question I'm asking myself is whether FocusForge as it exists today can make that category shift through product changes alone or whether the brand is actively working against it. genuinely not sure yet.
That’s the right question.
I don’t think the issue is whether FocusForge is a bad name. It isn’t.
The issue is whether it keeps forcing people to interpret the product through the first feature they understand: blocking.
If the product experience can make users feel “this knows my patterns and helps me execute daily” before they mentally file it as an extension, then FocusForge can probably stretch.
But if users have already decided “this is a blocker” before they reach the AI coaching layer, the brand is making the product do extra work.
That’s where Xevoa becomes interesting. Not because it explains the feature better, but because it doesn’t trap the product in the feature.
Happy to continue this privately if useful. Easier to think through the rebrand/category question without turning the thread into a naming debate.
LinkedIn:
https://www.linkedin.com/in/aryan-y-0163b0278/
No rush on this.
The reason I suggested taking it private is because this is less about “name preference” and more about whether FocusForge is helping or fighting the category shift you already described.
If you do want to pressure-test Xevoa seriously, LinkedIn is probably cleaner than turning this thread into a naming debate.
appreciate you offering to take this off thread. you're right that it's becoming a naming debate when the real question is about category positioning. will connect on LinkedIn this week and think through it properly there.
That makes sense.
One thing I’d add before we move it to LinkedIn: if Xevoa is genuinely worth pressure-testing, I’d do it sooner rather than “sometime later.”
The reason is simple: time is already moving. Every week you keep shipping, updating onboarding, collecting users, and letting people see FocusForge as the product name, the cost of switching goes up.
So the real decision is not “rename now or never.”
It is:
do you want to keep building under a name that may keep people seeing this as a blocker, or secure a product brand that gives the AI coaching / personal execution layer room to become the main thing?
That’s why I think Xevoa is worth looking at seriously now, while the product is still early enough to change cleanly.
Happy to continue on LinkedIn and keep it practical.
point taken on the timing argument. you're right that switching cost goes up every week and "later" is not neutral. going to connect on LinkedIn this week and actually pressure test it properly rather than keep deferring.
Exactly.
That is the only reason I pushed on timing. Not because the name has to change immediately, but because the window to change cleanly gets smaller with every product update.
Here’s my LinkedIn:
https://www.linkedin.com/in/aryan-y-0163b0278/
Let’s continue there and pressure-test Xevoa properly.
This comment was deleted a month ago
the activation event framing is exactly what's missing. I've been thinking about limits as the trigger but you're right that limits only work if the user has already formed a usage pattern. without a defined activation event there's no moment where the product clicks. going to define that specifically for FocusForge it's probably the first time someone gets blocked from a site and sees their daily report. that's the moment. everything before that is setup not activation. thanks