Importing historical data
Learn how to import your past YouTube analytics data for comprehensive trend analysis.
Quick Answer
TubeAnalytics enables users to import historical data like video performance, subscriber history, and revenue for comprehensive analysis beyond automatically pulled data. Users can import CSV, Excel, Google Sheets, or JSON files manually or via Google Sheets integration, mapping columns to TubeAnalytics fields for detailed historical reports and trend analysis.
Importing Historical Data
While TubeAnalytics automatically pulls data from your connected channel, you can also import historical data for deeper analysis.
What Data Can Be Imported?
- Video performance data (views, watch time, engagement)
- Subscriber history
- Revenue data (if monetized)
- Custom metrics you've tracked elsewhere
Supported Import Formats
- CSV: Most common format
- Excel: .xlsx files
- Google Sheets: Direct import
- JSON: For developers
Import Methods
Method 1: Manual Import
- Go to Settings > Data Import
- Click Import Data
- Select your file
- Map columns to TubeAnalytics fields
- Preview and confirm
Required columns: Date (YYYY-MM-DD format), Video ID or URL, At least one metric (views, watch time, etc.).
Method 2: Google Sheets Integration
- Connect your Google Sheets account
- Select the spreadsheet with your data
- Choose the sheet and range
- Map columns automatically
- Set import frequency (one-time or recurring)
Data Mapping
When importing, you'll map your columns: Your Column maps to TubeAnalytics Field (Video URL -> Video ID, Views -> Views, Watch Time (minutes) -> Watch Time, Likes -> Likes, Comments -> Comments, Subscribers -> Subscriber Change).
After Import
Data appears in: Historical reports, Trend analysis, Comparison tools, Export functions. Data does NOT appear in: Real-time dashboards, Live video monitoring, YouTube API sync.
Tips for Successful Imports
- Clean your data first: Remove duplicates, fix dates
- Use consistent formats: Same date format throughout
- Start small: Test with a single month's data
- Document sources: Note where data came from
Limitations
- Starter plan: 1,000 rows per import
- Pro tier: 50,000 rows per import
- Agency tier: Unlimited
Data older than 3 years may have reduced accuracy due to YouTube API limitations.
How to manage YouTube channel owners and managers →
Export your YouTube Studio data directly from studio.youtube.com under Analytics > Advanced Mode > Export. This gives you a clean CSV that maps well to TubeAnalytics import fields.
Frequently Asked Questions
What types of historical data can I import into TubeAnalytics?
You can import various historical data, including video performance (views, watch time, engagement), subscriber history, revenue data (if monetized), and custom metrics you've tracked elsewhere.
What file formats does TubeAnalytics support for historical data imports?
TubeAnalytics supports several common file formats for importing historical data, including CSV, Excel (.xlsx), Google Sheets (direct integration), and JSON, catering to different user needs and technical proficiencies.
What are the two main methods for importing historical data into TubeAnalytics?
The two main methods are Manual Import, which involves uploading a file and mapping columns in Settings > Data Import, and Google Sheets Integration, where you connect your Google Sheets account, select a spreadsheet, and set an import frequency. Both methods require careful column mapping.
Where does imported historical data appear within TubeAnalytics?
After a successful import, your historical data will appear in various analytical sections such as historical reports, trend analysis, comparison tools, and export functions. However, it will not be displayed in real-time dashboards, live video monitoring, or YouTube API sync.
Are there any limitations to importing historical data into TubeAnalytics?
Yes, import limitations vary by plan tier: Starter allows 1,000 rows, Pro allows 50,000 rows, and Agency offers unlimited rows per import. Additionally, data older than three years may have reduced accuracy due to YouTube API limitations.
Was this article helpful?