Hi GrowthBook team, We are experiencing some unexpected behavior with our GrowthBook experiments and would appreciate your input. Issue summary: • The

experiment_started

event is being triggered on random pages across our site, not just on the intended experiment page(s). • The experiment is configured to run only for registered users, but it is also being triggered for leads (unregistered users). Questions: • Is it possible for GrowthBook to trigger the

experiment_started

event on pages outside of the specified targeting rules, or for users who do not meet the targeting criteria (e.g., leads)? • Or does this indicate a misconfiguration on our end, and such behavior should not be possible if GrowthBook is set up correctly? We want to make sure we are not missing anything in our setup. Any guidance or clarification would be greatly appreciated! Thank you!

Hi Vitally, this is likely a misconfiguration, but maybe we're missing some context to answer your question. How have you set up your targeting, what SDK are you using and where are you using it, and what is the evidence you have that it is running for unregistered users? The last issue is likely one where your experiment hash attribute is available even for unregistered users.

Hi @helpful-application-7107 Thank you for the quick response! Here full setup information: SDK Setup • SDK:

<@U052WVA1MH6>/growthbook-react

version

1.5.1

• Environment: React SSR application with Node.js backend • API Host:

<https://growthbook-api.scentbird.com>

User Attributes Configuration We set the following attributes in our GrowthBook instance: await gb.setAttributes({ growthBookUid, // Hash attribute loggedIn, // Boolean: true for registered users, false for leads id: personalInfo?.id, // User ID (only for logged-in users) email: personalInfo?.email, // Email (only for logged-in users) country, // User country isE2ETest, // Testing flag ...personalInfo?.analyticsMetadata || {}, // Additional metadata }) Targeting Configuration For the problematic experiment `queue-page-rudder-stack`: - Targeting condition: subscriptionStatus = PAYING - URL targeting: No URL restrictions set - Traffic allocation: 50% (A) 50% (B) - Hash attribute: userId

The attributes in

await gb.setAttributes({
  growthBookUid,           // Hash attribute
  loggedIn,               // Boolean: true for registered users, false for leads
  id: personalInfo?.id,   // User ID (only for logged-in users)
  email: personalInfo?.email, // Email (only for logged-in users) 
  country,                // User country
  isE2ETest,             // Testing flag
  ...personalInfo?.analyticsMetadata || {}, // Additional metadata
})

Need to match those being used in the targeting. Your hash attribute is

id

, so it should only use those for whom

id: personalInfo?.id

exists, but I don't see

subscriptionStatus

being set in the attributes.