busy-horse-73824
01/14/2025, 4:09 PM,
But a CSV of e.g. user IDs would normally look like this:
user_id
a
b
c
This then turns into a single row in the group - user_idabc
😂
So it should probably at least be putting a comma at the end of each line before removing the linebreaks?loud-hydrogen-50191
01/16/2025, 4:18 AM(e.g. use '{{ startDate }}' instead of {{ startDate }}).
instead of the original
(e.g. use {{ 'startDate' }} instead of {{ startDate }}).
?plain-pharmacist-9564
01/17/2025, 12:27 PMpurple-pharmacist-44666
01/23/2025, 11:27 AMable-tent-93748
01/28/2025, 2:49 PMlemon-airline-30634
02/05/2025, 8:32 AMdry-ambulance-7044
02/05/2025, 3:30 PMrough-park-54233
02/10/2025, 6:22 PM--project
flag on GrowthBook CLI isn't actually implemented.microscopic-ocean-92851
02/13/2025, 9:33 PMSyntax error: Expected ")" but got keyword WHERE at [83:13]
The generated query has two where
keywords instead of an and
FROM
`ga4-explorations`.`analytics_383872824`.`events_*`
WHERE
(
(_TABLE_SUFFIX BETWEEN '20241115' AND '20250214')
OR (
_TABLE_SUFFIX BETWEEN 'intraday_20241115' AND 'intraday_20250214'
)
)
WHERE
customer_type != 'pro'
loud-guitar-35849
02/21/2025, 6:48 PMicy-lamp-84983
02/25/2025, 2:25 PMbillowy-pizza-30300
03/08/2025, 1:19 AMplain-pharmacist-9564
03/20/2025, 10:02 AMQuery execution was interupted. Please try again.
error messages (in the Queries overview and a red warning symbol), but I can see in our query engine that the queries actually ran successfully in a reasonable timeframe and also GrowthBook gives it a tick + shows the data (but also an error message) 🤔
We would really appreciate a fix here as the error messages make stakeholders lose trust in the data 🙏
CC @ripe-tiger-2213thankful-exabyte-82433
03/23/2025, 3:19 PMThis message is hidden because it was posted more than 90 days ago
or View messages and files older than 90 days PRO
, GrowthBook can migrate to Discord which is free forever and it keeps chats for the eternity. Many open source projects migrated to Discord because of that feature. It would be awesome if you guys can consider it.little-balloon-64875
03/28/2025, 5:50 AMclean-city-48510
03/31/2025, 8:21 AMlittle-balloon-64875
04/09/2025, 8:42 AMacoustic-actor-75733
04/11/2025, 5:20 PMquick-greece-27695
04/19/2025, 2:20 AMlate-ambulance-66508
04/24/2025, 1:43 PMlate-ambulance-66508
04/25/2025, 9:41 AMfaint-cat-56200
05/07/2025, 6:08 PMhelpful-glass-76730
05/12/2025, 8:11 AMambitious-apartment-58735
05/16/2025, 6:05 PMWe can write both as follows, where V is the number of tests that are statistically significant but are false positives and R are the number of tests that are statistically significant.
False Discovery Rate=FDR=E[V/(V+R)]
Should be V/R?creamy-magazine-78898
05/26/2025, 7:36 AMlate-ambulance-66508
05/27/2025, 8:31 AMincalculable-ram-43980
06/10/2025, 9:12 PMsalmon-fall-61851
06/11/2025, 8:34 AMm.timestamp >= d.timestamp + INTERVAL '1 hour'
), the conversion_window (e.g. + AND m.timestamp <= d.timestamp + INTERVAL '24 hours'
) is consistently missing, even when clearly configured in the UI and stored in the metric’s JSON (inspected via Web UI).
I’ve tested:
• Updating existing metrics → conversion_window is ignored.
• Creating new metrics via the UI → still ignored.
• Metrics (self-labeled) “in 90d”, “in 48h”, etc. → do not apply a user-relative time cap in the SQL, and we’ve therefore been consistently misreporting these numbers under the assumption that the window was respected.
• Burn-in does work reliably, so this appears to be a partial implementation.
Interestingly, I found one older metric that does apply the conversion window correctly, so it might be related to how/when the metric was created.
Let me know if you’d like reproduction steps or example SQL — happy to share more.
We're using GrowthBook Cloud w/ Build: 3.6.0+2d22835 (2025-06-10)
Thanks in advance!blue-dinner-94596
06/27/2025, 4:54 PMwide-beard-81045
07/07/2025, 11:44 PM