Connector

Collect Open Holidays calendars in Google BigQuery

Load public holiday calendars by country from Open Holidays into your own BigQuery project with OWOX Data Marts, then join the dates to your orders and ad spend to tell a real drop in demand from a calendar effect. Read it from BigQuery.

Open HolidaysConnectedPublic Holidays
Data MartPublishedone definition
Google BigQueryDateIdNameDaily 09:00
Refreshed on a schedule. No exports, no copy-paste.

Get started free

Hand this to your AI

Someone asks why Monday's orders dropped, and the answer is a public holiday that isn't in Google BigQuery.

Paste this into your AI assistant. It loads Open Holidays calendars by country into Google BigQuery as a Data Mart, so a join on date shows whether a dip fell on a holiday.

The prompt

load the Open Holidays calendar for our countries into Google BigQuery and show which of last quarter's sales dips fell on a public holiday

Endpoints

Open Holidays Endpoints

Documentation

1 Open Holidays endpoints you can import. Each lands in its own table in your data warehouse.

S00 · Why

Why keep a holiday calendar next to your sales and ad spend

A dip in the week of a public holiday looks like lost demand until someone checks the calendar. With the dates in your data warehouse, the check is a join, not a guess. The calendar sits in your own BigQuery project, beside your own tables.

  • Flag every order and ad day that fell on a holiday
  • Separate a national holiday from a regional one with one field
  • Compare a dip with the calendar before anyone calls it a trend
Open HolidaysHoliday dates
Shop ordersSales by day
Ad platformsSpend by day
Your data warehouseBigQueryDateHolidaySalesJoined by idSales dip on a weekdayExplained by a holidayOne join on date shows whether a dip fell on a holiday.

S01 · Step 1

Step 1: Connect Open Holidays and pick the fields

Create a Data Mart, choose Open Holidays as the data source and tick the fields you need. The source needs no credentials, so there is no token or service account to set up.

  • One endpoint, Public Holidays, with 7 fields to choose from
  • A time series: every holiday row carries its date, ready to filter in BigQuery
New Data MartChoose a sourceShopifyOpen HolidaysGoogle AdsAuthorizeConnectedEndpointPublic Holidays
Public Holidays7 fieldsiddatenametyperegionalScopenationwide

S02 · Step 2

Step 2: Load Open Holidays calendars into a BigQuery table

The dataset and table in your data storage are pre-filled, and you can change them. Run it and the first load lands in your own BigQuery project.

  • Each row is one holiday with its date, name, type and scope
DestinationBigQueryDatasetopen_holidaysTablepublic_holidaysRun
Run HistoryPendingRunningSuccessIncremental load
Tableopen_holidays.public_holidays

S03 · Step 3

Step 3: Read the output schema in plain words

After the first run you get the output schema: every field with a plain description. Your data quality checks can read it too.

  • name is the holiday's name in the language you requested
  • nationwide is true or false, so a regional holiday cannot pass for a national one
open_holidays.public_holidaysOutput schemaFieldDescriptionidUnique identifier for the holidaydateDate of the holidaynameName of the holiday in the…typeType of holiday (public…regionalScopeRegional scope of the holidaynationwideWhether the holiday is nationwide

S05 · Step 5

Step 5: Schedule the refresh and backfill history

Set it once. A scheduled refresh keeps your BigQuery table current, and a manual backfill loads any past period.

  • Backfill a custom start and end date to cover the periods you want to explain
  • Run History shows every load into your BigQuery dataset
ScheduleRun on a scheduleDaily 09:00
BackfillRun backfill
Run HistoryDaily scheduleManual backfillDaily schedule

S06 · Step 6

Step 6: Reuse the same calendar everywhere

One BigQuery table feeds your data model, spreadsheets, dashboards, AI assistants like Claude and ChatGPT, and scheduled AI insights in Slack or email.

  • Every report flags holidays the same way, so the totals agree
  • Ask an AI assistant whether last week's dip fell on a holiday and get an answer from the table
Open Holida…Data MartPublished
Holiday flags
Google Sheets
Data Studio dashboards
Claude, ChatGPT
Slack, email

Recent updates

Why OWOX

Why OWOX for Open Holidays in BigQuery

Someone checking each dip against a holiday list by hand gets an answer once. OWOX keeps the calendar in the table where your orders and ad spend already are, so every report can check it.

  • In your own project. Your BigQuery project holds the table, so your existing access rules, billing and queries apply to it.
  • Your SQL, your project. Analysts reach the table with the BigQuery SQL they already write, and the join lives in the Data Mart.
  • Calendar by country. The holidays come from Open Holidays by country, with their regional and temporal scope.
  • History you can use. Backfill past years, so last year's dip can be explained too.
  • Ready for a data model. The date is what the join runs on, so linking holidays to orders and ad spend is one line in your model.

Book a callGet started free

Trust

The Data Partner You Can Trust

users

175K Source: Internal OWOX data as of 2026-11-11

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

171K3

In Open Source We Trust

Customers