Cathy Liu
09/04/2026, 1:11 AMkapa.ai
09/04/2026, 1:11 AMfirst_visit_date falling within the selected date range, you do not need complex MAQL date-comparison logic. In GoodData, metrics automatically evaluate within the context of the date dataset configured for the dashboard date filter [Slack thread].
Here is how you can set this up:
1. Ensure first_visit_date is in your Data Model Make sure first_visit_date is mapped to a Date Dimension in your Logical Data Model (LDM) connected to your player dataset.
2. Create the Metric MAQL COUNT naturally counts unique attribute values [COUNT aggregation]:
SELECT COUNT({label/player_id})
_(Optional)_: If you want this KPI to strictly depend only on the date filter and ignore other parent/attribute filters on the dashboard, you can define it as:
SELECT COUNT({label/player_id}) WITHOUT PARENT FILTER EXCEPT {dataset/first_visit_date}
[Slack thread]
3. Configure the Dashboard Date Filter 1. In your dashboard, add or edit the Date Filter [Date filters].
2. Set the date filter's dimension to your first_visit_date date dataset.
3. Configure the desired preset or relative period (for example, Last 30 days or From 30 to 1 day ago as shown in your screenshot) [Date filters].
Once connected, GoodData will automatically scope the metric to only include players whose first_visit_date falls into whatever range is selected in the date filter. đ 0 button đ 0 button âšī¸ Tip: Mention @kapa.ai in the thread for follow-ups.
đ Our Support team monitors all messages and will jump in if needed.