If you are using NinjaCat's New Interface Design watch the linked video for a major landmark tour!

All of our efforts go into accessing, aggregating, and delivering your data in the most helpful way we can. For this effort, we maintain an always growing number of direct connections to data source providers. Inside these direct connections, data is requested and delivered through APIs (Application Programming Interfaces) These APIs are created and managed by the data source developer and leveraged by us to gather your data from them.

Not all APIs are created equal. While using NinjaCat you may be interacting with multiple data sources in a single template. Maybe even in a single widget! Pulling data from multiple APIs leads to inconsistent experiences in data display. In order to increase consistency across data source behavior and in data display, NinjaCat employs a data warehouse strategy across all of our data sources.

Section Links

Expected Behavior

Change the Default Refresh Hour

Manually Trigger Data Refresh

Expected Behavior

In brief, to supply data to the Template Builder, Reports, and Dashboards, NinjaCat:

A) At a default time, every morning receives data from

APIs for direct data source connections
Server connections like SQL, FTP, and Amazon S3 for custom data
Data sources that we don't have API connections for via URL, automated Email, and Google Sheets

B) Warehouses that data in our own data warehouse

C) Delivers the warehoused data when requested in:

The NinjaCat Template Builder
Reports
Dashboards

Depending on the time of day you’re analyzing your reports, you may notice slight variations in NinjaCat’s data and what’s showing in the direct provider’s UI. Google Ads, for example, may display an increased number of clicks or conversions than NinjaCat, but that’s simply because NinjaCat’s Data warehouse refresh happened before these adjustments. By the next day, however, any minor discrepancies will have auto-corrected.