This message was deleted.
# experimentation
w
This message was deleted.
f
ya, I think setForcedVariations wont fire the tracking callback
you can fire the tracking callback manually
or use a custom attribute for assignment
p
If I fire the tracking manually, will it be able to see the reporting in Growthbook?
f
yes
p
ok awesome!
Thanks!
f
you can customize how growthbook finds the exposure events
but it basically just need an event name, like 'experiment_viewed', the experiment id/tracking key, the variation id that was seen, and a date exposed
p
yup, I can manually fire that no problem. Just wasn't sure if Growthbook would pick that up even if it wasn't fired by GB. but makes sense that it would just rely on that event so all I need to to is fire the event
f
ya, many users just use growthbook for experiment reporting
its quite modular
p
So if I just want to do reporting. Whats the best way to setup the experiment in GB? Should I use a dummy Feature, or is there a better way?
Is there any Doc's that Im missing about setting that up?
f
you don't need a feature at all
just go to experiment, click on new experiment, and enter the info and go
if you have some data there already, you can click on the 'import existing experiment'
you don't have to join it to a feature flag
p
Oh! I was stuck on the warning
But now I see start anyway!
f
what was the task?
p
The add a feature, redirect or visual
f
I see
p
So I can just skip that and then start reporting manually? Thats amazing
f
yes, you can
when you select 'import' it will skip those steps