Hi what happens when customer is matched to one ex...
# ask-questions
o
Hi what happens when customer is matched to one experiment with attrbiute targeting but doesnt have the feature flag? We are releasing the feature flag with the new release. Targeting the experiment would rely on engagement metric. 1. What happens from targeting? Is user going to enter the experiment funnel? 2. I guess it wont impact the journey of the customers since there is no flag, they will have the normal flow without flag. 3. What will happen with experiment viewed event? I guess this is connect to first point. If someone can answer promptly it would be amazing. Best.
h
I think it depends on how you have your flag rules set up. Is the experiment only reachable as a rule in a feature flag, or is there also a non-flagged visual editor or url redirect implementation in the experiment? If the flag is the only implementation of your experiment, and if there are any rules above the experiment that do not pass, then the user will never reach the experiment.
o
Let me check with our eng team. There isnt any targeting in feature flag. Targeting is set in experimentation
It is in mobile, there is no redirect. Simply the old version customers wont have the feature flag in code. But in terms of targeting in the experiment they can enter the experiment because of attribute match
h
could you share your feature flag rules and experiment targeting
o
IMG_8165.png
Feature flag is basic true false embedded to home page which is going to be released with new version of the app
So app version was not available at the moment , that’s why we use sign up date targeting
But the users who have earlier version and newer sign up date would theoretically enter the experiment without having feature flag
h
ah, so the SDK payload is not fetched by the app and must be shipped down with new app releases?
o
If I understood your question correctly yes it was hard coded with new release
h
And you're concerned that users with the old app release will have the old SDK payload hardcoded and will thus enter your experiment based on old targeting logic?
o
Yes , i have a concern that old customer enter experiment which has new hardcoded feature flag because of global attribute targeting in the expeirmentation
h
would it be sufficient to ship down new targeting rules with a new app release, or are you concerned about some users not upgrading their app?
o
Just it was rushed
Normally that was the purpose
So what would happen now
How is the sequence of feature flag and experiment targeting
h
If your app makes any fetches to the GB API, it should be able to pick up the changes for most users. If not, you can hopefully push down an app update with new targeting. If you do nothing and leave the current logic in place, then users will flow into the experiment based on the current
signup_date > 2025-03-30 and total_completed_orders === 0
logic.
the targeting flow is 1. evaluate the
getting-started-sheet-flow
feature flag 2. encounter an experiment rule 3. evaluate the experiment's targeting conditions (
signup_date
,
total_completed_orders
) 4. If that passes, then enroll and bucket the user
o
So experiment flow is as below then Targeting Flow: a. Check Feature Flag: Is getting-started-sheet-flow enabled? (true/false flag) a. Encounter an Experiment Rule: If the feature flag is on, does the user qualify for any experiments? a. Evaluate Targeting Conditions: Apply experiment rules: • signup_date • total_completed_orders a. If all pass: The user is enrolled and bucketed into control or treatment.
It means if feature flag is not available these customer wont enter the experiment right ?
h
Because the experiment is only referenced in the flag as a rule, that means that if the flag is either missing or OFF then the user will never encounter the experiment. It will be as if the experiment does not exist
o
Perfect thanks