Self-Storage Reporting: Combine Website, Search and Booking Data in One Dashboard
The most complete, up-to-date view of your website, marketing and booking data, all in one place.
contents
Google Analytics tells you how many people visited your site. Search Console tells you which searches brought them there. Your storage software tells you who actually booked. None of them, on their own, tells you which channels or search terms are actually producing paying customers rather than just traffic.
Answering that needs all three data sets in one place. This post covers a practical way to do it: Zapier pulling data from each source into a shared Google Sheet, and Data Studio turning that sheet into an actual dashboard.
The Zapier automations post covers event-based automation; this is a different pattern, pulling periodic reports rather than reacting to single events.
If you haven’t read An Introduction to APIs yet, start there.
What "combining via API" means in practice
Analytics tools like Google Analytics and Search Console expose their data through an API, same as your storage software does. The difference here is what you’re pulling: not individual events as they happen, but periodic reports, a day’s sessions by channel, a week’s search queries, a month’s bookings.
Zapier sits in the middle for all three. On a schedule, it asks each source for its latest report and writes the result into a shared Google Sheet, using a consistent set of columns (date, source, metric, value) so the data can actually be compared side by side rather than living in three separate formats.
How the pieces fit together
- Google Analytics 4 exposes a “run report” action through Zapier, letting you pull sessions, channel and conversions for a given date range.
- Google Search Console exposes a search traffic action, letting you pull queries, impressions and clicks for the same period.
- Your storage software exposes leads, bookings and revenue through its own API, polled on a schedule like any other Kinnovis Connect-style integration.
- A scheduled Zap (using Zapier’s built-in Schedule trigger) runs each of these periodically, typically daily, and writes a row into a shared Google Sheet for each source.
- Data Studio connects to that Sheet as its data source and does the actual visualising: joining the rows by date so you can see traffic, search performance and bookings on the same timeline.
What data actually moves and what it's for
| Data type | What it becomes in the sheet | Used for |
|---|---|---|
| Sessions and conversions by channel (Google Analytics) | A row per day and channel | Seeing which channels bring visitors, and how many convert on-site |
| Queries, impressions and clicks (Search Console) | A row per day and query or page | Seeing which searches actually bring people to the site |
| Leads and bookings (your storage software) | A row per day, and by channel if UTM data is captured | The number that actually matters: which of the above turned into paying customers |
Setting up the Zaps
- Create a Schedule by Zapier trigger for each source, running daily (or weekly, depending on how granular you need the data).
- For Google Analytics, use the Run Report for a Property action, specifying the metrics and date range you want.
- For Search Console, use the equivalent search traffic action, specifying the site and date range.
- For your storage software, poll its API for new bookings and leads over the same period, the same pattern used throughout this Academy.
- Each Zap’s final step writes a new row to the same Google Sheet, using consistent column names across all three so Data Studio can treat them as one data set.
- Connect Data Studio to that Sheet and build the actual report: a timeline blending traffic, search performance and bookings side by side.
The column consistency in step 5 matters more than it sounds. If “date” is formatted differently across sources, or channel names don’t match, Data Studio won’t be able to join the rows cleanly, and the whole point of combining the data is lost.
What the reports can show
Cost or effort per booking, by channel. Blending traffic-by-channel with actual bookings shows which channels are worth the time, not just which bring the most visitors.
Which search queries actually convert. Search Console shows what people searched for. Combined with booking data, you can see which of those queries led to an actual customer, not just a click.
Facility-level dashboards. For multi-location operators, blending local site engagement with occupancy by facility gives a clearer read on where marketing effort is and isn’t working.
What you need to set this up
Access to your Google Analytics 4 property and your verified Search Console property.
A Zapier account with those two apps connected, plus Google Sheets.
An API key from your storage software, scoped to read-only, since this only needs to pull data out.
Data Studio, free, connected to the shared Sheet as its data source.
Where this has limits
Data Studio’s connection to Google Sheets has its own refresh frequency and row-count considerations, worth checking against how much historical data you’re keeping in the sheet.
Joining the data cleanly depends on consistent naming, particularly UTM parameters, across your website, your ads and your storage software. If a channel is labelled differently in each system, the numbers won’t line up without manual cleanup.
This is daily or weekly reporting, not real-time. It’s the right tool for spotting trends and comparing channels, not for anything that needs to be current to the hour.
How this looks with Kinnovis Connect
If you’re a Kinnovis customer, the booking and lead side of this pulls from Kinnovis Connect the same way as the rest of the Academy: filter[createdAt] on bookings for new activity in the reporting period, polled on whatever schedule matches your reporting cadence. An API key scoped to read-only (reader_api) is sufficient, since this integration only reads data out.
This isn’t a hypothetical pattern. Operators already connect BI tools, including Power BI and Data Studio, directly to the Kinnovis Public API for their own operational reporting, without needing Zapier or a Sheet in between. Reports built this way typically cover:
Reservations over time, to track booking volume and spot seasonal patterns
Top customers by spend, to see who your highest-value accounts actually are
Customers plotted on a map, useful for understanding where your customer base sits relative to each facility
Churn analysis, tracking how many customers don’t renew, and over what period
Occupancy rates by unit type, showing which sizes fill fastest and which sit empty longest
Overdue payments, surfaced as a live list rather than something someone has to check for manually
If you’re a Kinnovis customer, we can set up reporting like this for you directly, at no cost, with your data populated automatically and no Zapier account needed on your end. Get in touch through our contact page to request it.
Frequently Asked Questions (FAQs)
The Zapier and Google Sheets side is largely no-code. Getting UTM tracking consistent across your website and ad platforms, so the data actually joins up cleanly, is the part most worth getting a developer or marketer experienced with analytics to check.
Data Studio can connect to Google Analytics and Search Console directly for their own data. The Sheet exists specifically to bring in your storage software’s booking data alongside them, since Data Studio doesn’t have a native connector for most PMS platforms.
Daily is typical for most operators. Weekly is often enough if you’re mainly looking at trends rather than day-to-day performance.
Yes. Ad platform spend is a common next addition, from your Google, Bing or Meta ads.
API Academy
Access Control Integrations for Self-Storage
Zapier Automations Self-Storage Operators Actually Use
Mailchimp Segmentation for Self-Storage: Message the Right Customers
Get Started today
Unlock the true potential of your
self-storage facilities
Kinnovis. Designed to make facility management simple.
