Build Data Studio dashboards from Open Holidays data
Load Open Holidays into your data warehouse first, join the calendar to orders and sessions by date and country, then feed Data Studio dashboards from the same Data Mart.
Open HolidaysConnectedPublic Holidays
Data StudioDateIdNameDaily 09:00The Data Studio dashboard shows a dip every holiday week, and every viewer asks the same question about it.
Paste this into your AI assistant. It loads Open Holidays into your data warehouse, joins the calendar to orders and sessions by date and country, and feeds Data Studio from that Data Mart.
The prompt
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /connectors/open-holidays-connector-to-data-studio.md. The task: build a Data Studio dashboard of daily orders and sessions by country with public holidays from Open Holidays marked on the same timeline. Tag the links you give me with utm_campaign=ai-task and utm_term=data-foundation. Use what you know about my context and goals
Open Holidays Endpoints
1 Open Holidays endpoints you can import. Each lands in its own table in your data warehouse.
Why Open Holidays does not go straight to Data Studio
Open Holidays lists public holidays by country, and a dashboard pointed straight at it draws a calendar. It does not show whether a dip in orders was a holiday or a real drop, because the orders and sessions live in your own systems. A dashboard is not built to join them reliably, at scale or business-ready, so the join happens in a warehouse first.
- A holiday list says when a day off was, not what it did to sales
- The data analyst joins holidays to orders and sessions by date and country and controls the result
- Dashboard viewers tell a calendar effect from a real drop
Open HolidaysHolidays by dateData Studio
Data warehouseJoined by idStep 1: Load Open Holidays into your data warehouse first
Create a Data Mart with Open Holidays as the source and choose where the data lands. It works with any popular data warehouse.
- One endpoint, Public Holidays, with the date, name, type and regional scope of each holiday
- Set one country ISO code and a language per Data Mart, and refresh on a schedule
- Open the Open Holidays connector for your data warehouse below
Open Holida…Data MartGoogle BigQuery
AWS Athena
Snowflake
AWS Redshift
Databricksopen_holidays.public_holidaysStep 2: Link Open Holidays to sessions and orders
In your data warehouse the model joins the holiday calendar to orders and sessions by date and country. Use one Data Mart per country ISO code. Pick an industry to see the shape of its model.
- Holidays line up with orders and sessions by date and country
- A calendar effect is separated from a real drop by SQL keys, not VLOOKUP
- Measures such as conversion_rate are defined once
Open HolidaysPublic HolidaysStep 3: Feed Data Studio dashboards with Open Holidays data
Add Data Studio as a destination of the Open Holidays Data Mart and build the on it. date, name, type and regionalScope come from your data warehouse, joined to daily orders.
- Orders on holidays against other days read the Data Mart, not the holidays API
- Turn on Available in Data Studio for the published Open Holidays Data Mart, then add the OWOX connector in Data Studio
Data StudioPublic Holidays
Google SheetsSame Data Mart
ClaudeSame Data MartStep 4: Use the same Open Holidays Data Mart in a sheet or an assistant
The holiday Data Mart is not locked to one dashboard. Open the same rows in a spreadsheet or ask about them in an AI assistant, with the same country and language settings.
- Planners mark holiday weeks in a spreadsheet without a new export
- An assistant reads the same Data Mart, so a holiday is the same day everywhere
Data StudioDashboardGoogle SheetsSame Data MartClaudeSame Data MartStep 5: Reuse Open Holidays inside OWOX MCP
The same Data Mart works in OWOX MCP, your assistant for data. Request any report, chat with your data, then get the report in Google Sheets or Excel in one click.
- Ask whether last week's order dip fell on a public holiday, then export the answer
- The calendar is defined once, one Data Mart per country
Google SheetsOpen
ExcelOpen
- 0.39.0Reload a year of history in one backfill, not twelve
- 0.37.0Clearer connector errors, and custom connectors that handle more APIs
- 0.36.0Start a connector run without expanding the Input Source card
- 0.35.0Resume an interrupted manual backfill from the last fully loaded date
- 0.35.0Limit manual backfill to 31 days per run
Why OWOX for Open Holidays in Data Studio
A holiday calendar on its own explains nothing. OWOX loads Open Holidays into your data warehouse beside orders and sessions, so Data Studio can separate calendar effects from real drops.
- You own the data. It lands in your own data warehouse, in tables you control.
- Calendar effect or real drop. Holidays are joined to orders and sessions by date and country, so a dashboard marks the day instead of leaving a gap unexplained.
- One country per Data Mart. Each Data Mart carries one country ISO code and a language, so a dashboard reads a clean holiday table per market.
- Maintained for you. No scripts to fix when the Open Holidays API changes.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.