Getting Started & Logging In
Velora is accessed through a web browser. Once the workspace URL is opened, you will land on the login screen.
1.1 Signing in with email and password
- Enter your registered email address (or username) in the Login ID field.
- Enter your password.
- Click Log In.
Your account must already exist in the system for a password login to succeed. If you don't have credentials yet, contact your workspace administrator.
1.2 Signing in with a connected account
The login screen also offers "Continue with" buttons for single sign-on. Depending on what your organization has enabled, you may see:
Selecting one of these redirects you to that provider to sign in, then returns you to Velora already logged in. The first time you sign in this way, an account is created for you automatically using your name and email from that provider — no separate registration step is required.
1.3 Staying signed in / logging out
Once logged in, your session stays active in the browser until you log out or your session expires. Use the Log Out option in the top navigation to end your session. Logging out clears any data you had loaded in that session, so export anything you need first (see Section 9).
1.4 First things you'll see after logging in
On your first successful login, Velora shows a short welcome message and confirms that session security tracking has started. You will land on the Overview page.
Workspace Navigation
Velora is organized into a set of pages, accessible from the side/top navigation menu. Click any page name in the navigation to switch to it — your active page, uploaded data, and generated forecast persist as you move between pages within the same session.
| Page | What it's for |
|---|---|
| Overview | Landing dashboard with headline stats (latest Impressions, Engagements, forecast Sales/Revenue, data quality status) and quick links to the rest of the workspace. |
| Data Quality | Shows the automated Data Quality & Cleansing report for the most recently uploaded dataset: quality score, missing-value summary, outlier summary, drift summary, consistency checks, duplicate detection, and an editable data grid. |
| Forecasting | Displays the generated forecast table (Month, Sessions, Posts, Impressions, Engagements, Engagement Rate, Sales, Revenue, confidence range) and the reference table of all Forecasting Variables the model can use. |
| Charts | Visualizes trends: Impressions Trend, Engagement Trend, Engagement Rate, Seasonality, Impact Multiplier, Forecast Funnel, Sales/Revenue Forecast, Actual vs Predicted, Driver Impact, Correlation, and Feature Importance. |
| Auto Insights | Plain-language, automatically generated observations about trends, drivers, and forecast outlook based on the current dataset. |
| Model Performance | Shows the comparison across all trained models plus a time-based backtest: accuracy, precision, recall, F1, and how each model compares to a naive ("no-change") forecast. |
| Sales Prediction | Converts the Impressions/Engagements forecast into a projected Sales and Revenue figure using assumptions set on the Settings page. |
| Goal Seek | Reverse forecasting: enter a target Sales or Revenue figure and Velora solves for the driver combination needed to reach it. |
| Accuracy Tracker | After uploading real monthly results, compares them against what was forecast: accuracy %, hit/miss, and naive-forecast comparison. |
| SQL and Reports | Push the current forecast to the connected database, run read-only queries, and download the Forecast CSV, Power BI CSV, or a PDF report. |
| Notification Centre | Chronological log of everything that has happened in the session. Admin accounts can also broadcast a message to every logged-in user from here. |
| Settings | Configure the model, forecast horizon, sales assumptions, macro/micro adjustment, and LinkedIn integrations. |
Uploading Your Data
Velora is driven by a monthly CSV file of your marketing/content performance data. Data can also arrive automatically via the LinkedIn integration (Section 10) instead of a manual upload.
3.1 Required columns
Every CSV upload must contain the following nine columns (one row per month). Column names are matched automatically even with different spacing, capitalization, hyphens, or underscores.
| Column | Description | Example |
|---|---|---|
| Month | Calendar month for the row. | Jan-25, 2025-01, 01/2025, January 2025 |
| Sessions | Website sessions driven for that month. | 12500 |
| Posts | Number of posts published. | 18 |
| Creatives | Number of creative assets used. | 24 |
| Likes | Total likes received. | 3400 |
| Comments | Total comments received. | 210 |
| Shares | Total shares received. | 150 |
| Impressions | Total impressions. | 185000 |
| Engagements | Total engagements. | 9200 |
3.2 Optional variables
Beyond the 9 required columns, Velora recognises around 30 additional optional columns. If present, they're automatically picked up as extra inputs to improve forecast quality — you don't need to add them, and their absence never blocks an upload.
| Category | Optional columns in that category |
|---|---|
| Audience Growth | New Followers, Follower Growth Rate |
| Website Traffic (breakdown) | Organic Sessions, Social Sessions, Direct Sessions, Referred Sessions |
| Content Publishing | Posting Days, Posts Per Week, Consistency Score |
| Content Formats | Video Posts, Carousel Posts, Image Posts, Text Posts |
| LinkedIn Live Performance | LinkedIn Live Count, LinkedIn Live Attendees, LinkedIn Live Views |
| Webinar Performance | Webinar Count, Webinar Registrations, Webinar Attendees, Webinar Attendance, Webinar Attendance Rate |
| Employee Advocacy | Employee Posts, Employee Shares, Employee Advocacy Score |
| Paid Marketing | Paid Spend, Boosted Posts, Sponsored Content |
| Content Strategy | Third-Party Posts, Research Posts, Event Posts, Product Posts |
| Business Events | Industry Event Flag, Conference Flag, Product Launch Flag |
3.3 How to upload
- Go to the Overview or Forecasting page.
- Click the Upload / Choose File control and select your .csv file.
- Velora automatically checks the file's data quality (see Section 4) and, if it passes, trains the forecasting models and generates a forecast right away.
A confirmation notification appears (and is logged in the Notification Centre) once the upload and forecast are complete, including how many months of data were loaded.
Data Quality & Cleansing
Every dataset — whether uploaded as a CSV or pulled from LinkedIn — is automatically checked before it is used for forecasting. You don't need to trigger this manually.
4.1 What is checked
- Missing / null values, including runs of consecutive missing months
- Statistical outliers in each numeric column
- Distribution drift between earlier and more recent records
- Consistency checks: required columns present, correct data types, values within expected ranges, and logical checks (e.g. Engagements should not exceed Impressions)
- Duplicate or suspicious records (e.g. two rows for the same month)
4.2 Quality score and status
Each dataset receives a Quality Score out of 100 and a rating: Excellent, Good, Fair, Poor, or Critical. A score of 75 or higher (with no missing required columns) is marked Clean and the forecast proceeds automatically. Anything below that is marked Dirty and the workflow pauses for your review.
4.3 What you can do with a Dirty dataset
- Continue Anyway — proceeds with the data as-is; the forecast is generated but flagged as based on unreviewed data.
- Clean the Data First — Velora automatically fills/adjusts missing or out-of-range values, removes duplicate rows, and re-checks the result.
- Edit Manually — an editable data grid lets you correct individual cell values yourself, after which the file is re-checked.
The Data Quality page also lists specific Recommended Actions and plain-language insights explaining how each issue could affect your forecast.
Page-by-Page Guide
Overview
Headline numbers, current data quality status, and shortcuts into the rest of the workspace. Use "Refresh Stats" to recompute the figures.
Forecasting
Forecast table with projected Sessions, Posts, Impressions, Engagements, Engagement Rate, Sales, Revenue, and confidence range. Includes Rerun Forecast.
Charts
Impressions/Engagement trends, Engagement Rate, Seasonality, Impact Multiplier, Forecast Funnel, Sales/Revenue Forecast, Actual vs Predicted, Driver Impact, Correlation, Feature Importance.
Auto Insights
A running list of plain-language observations generated from your current dataset and forecast.
Model Performance
Compares all models with a time-based backtest: accuracy, precision, recall, F1, and comparison to a naive forecast.
Sales Prediction
Translates the Impressions/Engagements forecast into a Sales and Revenue projection using your Settings assumptions.
Goal Seek
Work backward from a target Sales/Revenue number to the driver levels needed to reach it. See Section 7.
Accuracy Tracker
Tracks forecast accuracy once real results are available. See Section 8.
SQL and Reports
Push data to your database, query it, and export files. See Section 9.
Notification Centre
Session activity log and admin broadcasts. See Section 11.
Settings
Forecast, model, and integration configuration. See Section 6.
Settings
The Settings page controls how forecasts are generated and how external connections are configured.
6.1 Forecast & model settings
| Field | What it controls | Default |
|---|---|---|
| Selected Model | Which algorithm to use: Auto Select Best Model, Ridge Regression, Random Forest Regressor, Gradient Boosting Regressor, Neural Network (MLP), Adaptive Online Learner (SGD), Extra Trees Regressor, or Hist Gradient Boosting Regressor. | Auto Select Best Model |
| Forecast Months | How many months ahead to forecast (1–12). | 3 |
| Forecast Base | Which historical point the forecast builds forward from: Last Historical Month, Historical Average, or Rolling Average (3 months). | Last Historical Month |
| Lead Conversion Rate (%) | Share of engagement that becomes a lead, used in Sales Prediction and Goal Seek. | 2.0 |
| Sales Conversion Rate (%) | Share of leads that convert into a sale. | 20.0 |
| Average Deal Value | Average revenue value of one closed sale. | 5000 |
| Change Rating | Manual sensitivity adjustment applied to the forecast. | 5 |
| Upper / Lower Circuit (%) | Maximum allowed swing above/below the model's raw forecast, keeping the confidence range realistic. | 15 / 15 |
| Next Sessions / Likes / Expected Posts / Creatives | Optional manual overrides for next period's driver inputs, used instead of the model's own projection when supplied. | blank |
| Macro Impact (%) | Manual adjustment for broad external/market conditions, applied as a multiplier on top of the forecast. | 0.0 |
| Micro Impact (%) | Manual adjustment for internal/company-specific factors, applied as a multiplier on top of the forecast. | 0.0 |
After changing any of these, Velora automatically regenerates the forecast using your current uploaded data. You can also trigger this manually with Rerun Forecast.
6.2 LinkedIn integration settings
Covered in full in Section 10.
Goal Seek
Goal Seek answers the question: "What would we need to do to hit a specific Sales or Revenue number?" It works backward from your target using the model that is already trained on your data.
7.1 How to run a Goal Seek
- Open the Goal Seek page (requires an uploaded dataset and a generated forecast).
- Choose the Target Metric: Revenue or Sales.
- Enter the Target Value you want to reach.
- Choose the Month Offset — how many months ahead the target applies to.
- Optionally, lock one or more drivers to a fixed value and let Velora solve for the rest.
- Click Run Goal Seek.
7.2 Reading the result
- The required level for each driver needed to reach your target
- How that compares to your current baseline (percentage change per driver)
- Projected Impressions, Engagements, and the achieved Sales/Revenue value
- A Gap % showing how close the achieved value is to your target
- A plain-language narrative summarizing what would need to change
Accuracy Tracker (Uploading Actuals)
Once real results for a forecasted month become available, upload them to see how the forecast performed.
8.1 How to upload actuals
- Make sure a forecast has already been generated.
- Go to the Accuracy Tracker page.
- Upload a CSV with a Month column plus whichever of Impressions, Engagements, and Sales you have real figures for.
- Velora automatically matches each row to the corresponding forecast month and computes accuracy.
8.2 What you'll see
- Accuracy % for Impressions, Engagements, and Sales for each matched month
- A Hit / Miss classification against a 15% tolerance band
- A comparison against a naive "no-change" forecast
- The confidence level originally attached to that forecast month
SQL, Exports & Reports
The SQL and Reports page is where forecasts leave the workspace — either into your own database or as downloadable files.
9.1 Push to SQL
Pushes the current forecast (and the combined historical + forecast dataset) into your connected database. Each push is stamped with a unique Run ID and scoped to your own login. Pushing also lets your historical data auto-load automatically next time you log in.
9.2 Run SQL Query
A simple query box for running your own read-only SELECT statements against the connected database. Only SELECT statements are permitted from this tool.
9.3 Downloads
| Export | Contents |
|---|---|
| Forecast CSV | The generated forecast table (Month, drivers, Impressions, Engagements, Sales, Revenue, confidence range) as a CSV file. |
| Power BI CSV | A combined historical + forecast dataset formatted for import into Power BI or similar BI tools. |
| PDF Report | A formatted PDF summarizing the forecast, key charts, and headline figures — suitable for sharing outside the workspace. |
Each export is timestamped in its filename so you can keep multiple versions.
LinkedIn Integration
Velora can connect directly to LinkedIn in two distinct ways, configured separately on the Settings page.
10.1 "Continue with LinkedIn" sign-in
Used purely for logging in to Velora with your LinkedIn identity (see Section 1.2). This does not pull any performance data by itself.
10.2 LinkedIn organization statistics
A separate connection authorizes Velora to pull your LinkedIn Page/organization statistics — Impressions, Clicks, Likes, Comments, and Shares — directly from LinkedIn.
- Enter the Client ID, Client Secret, and Redirect URI provided by your LinkedIn developer app under Settings → LinkedIn Stats.
- Save the settings.
- Authorize the connection when prompted; you'll be redirected to LinkedIn to approve access and returned to Velora afterward.
- Use Fetch LinkedIn Stats to pull the latest statistics on demand.
Every LinkedIn pull automatically runs through the same Data Quality check described in Section 4 before the numbers are used anywhere in the workspace.
Notification Centre
A running, timestamped log of everything happening in your session: successful uploads, forecasts generated, data quality warnings, export confirmations, connection errors, and security events.
Use this page any time something doesn't look right — it's usually the fastest way to see exactly what happened and when.
11.1 Broadcast messages (administrators only)
Administrator accounts can push a message that appears in every logged-in user's Notification Centre at once — useful for announcing maintenance windows or workspace-wide updates. A broadcast can be cleared by the administrator once it's no longer relevant.