high-dusk-7074
10/02/2022, 8:55 PMmost-pizza-11069
10/03/2022, 3:51 PMfaint-portugal-8257
10/03/2022, 5:59 PMcareful-machine-67313
10/03/2022, 11:09 PMcareful-machine-67313
10/03/2022, 11:21 PMbrash-raincoat-88597
10/04/2022, 1:00 AMhandsome-library-89124
10/04/2022, 7:40 AMbillions-arm-13894
10/04/2022, 8:53 AMbrief-traffic-36675
10/04/2022, 4:19 PMnarrow-yacht-43459
10/04/2022, 10:58 PMripe-pencil-68147
10/05/2022, 10:24 AMwooden-nest-76199
10/05/2022, 6:05 PMrhythmic-insurance-43078
10/06/2022, 5:55 AMAssignments Table
- user_id
- timestamp
- date(partition)
- hour (partition)
- experiment_id (partition)
- variation_id
- browser
- country
Events Table
- user_id
- timestamp
- date (partition)
- hour (partition)
- value
Dimension Table
- user_id
- value
Questions:
1. Do we create per metric events table ? For example, Revenue Events Table, Impressions Events Table
2. Is it okay to have one big assignments table ?
3. I'm assuming we have many dimension tables of the format mentioned above ?
could you please provide guidance on this as I'm doing this for the first time ?brief-traffic-36675
10/06/2022, 6:29 AMquaint-pharmacist-3914
10/07/2022, 7:35 AMFetch error GET <https://cdn.growthbook.io/api/features/{key}>
TypeError: Failed to fetch
Has anyone faced this? What could be the reason?bland-vegetable-68187
10/08/2022, 12:12 AMswift-beach-91166
10/10/2022, 8:37 AMbroad-continent-77439
10/10/2022, 4:53 PMid
for growthbook (in setAttributes
) to match the segment one? I tried to send the ajs_anonymous_id
/ ajs_user_id
as an id. but the problem is those segment cookies are set after growthbook config initialization!
Thanks.broad-continent-77439
10/11/2022, 8:22 AMexperiment_id
column in your data source" and as in the React SDK I am sending the event as
trackEvent("Experiment Viewed", {
experimentId: experiment.key,
variationId: result.variationId,
});
do I need to change experimentId
to experiment_id
so it can track? Thanks.some-planet-44104
10/11/2022, 1:31 PMCAST(e.timestamp as DATETIME) as conversion_start,
But what I’m trying to achieve is having conversion_start date to be different from the experiment exposure date. Namely, I want a delayed conversion start so that I can calculate retention (which is visiting the app 7 days after experiment exposure). So that the user is considered converted if they logged in on 7th day after the exposure.
Maybe there’s a more proper way to go about this?brave-pager-50062
10/12/2022, 3:29 AMfuture-caravan-57043
10/12/2022, 11:11 AMbrash-raincoat-88597
10/13/2022, 9:17 AMExperiment Auto-Update Frequency
setting also apply to the numbers calculated for Dimensions in the Experiment Result section?cold-greece-95487
10/13/2022, 10:37 AMnutritious-waiter-93215
10/13/2022, 12:56 PMeager-rainbow-87882
10/13/2022, 2:07 PMbetter-magician-65629
10/17/2022, 7:08 PMenough-kangaroo-252
10/19/2022, 2:20 PMrhythmic-chef-84815
10/20/2022, 7:21 AMuserRegistrationDate
that stores a unix timestamp, you could make a New vs Existing
dimension like this"most-jackal-23578
10/20/2022, 8:18 AMid
, that is currently in use by features, will those continue to work?
We have replaced the attribute with another, and want users to start using the new one, but we don’t want to break existing features. From my quick test, I see that the attribute is still part of the configuration payload, so based on that, I assume things will continue to work as before, but it will not be possible to select the attribute on new features (which is what we want).