--- title: "Dashboard Analytics" label: "Dashboard analytics" description: "Monitor live visitors, first-touch channels, country map, and job performance from your built-in Cavuno dashboard." publishedAt: 2025-12-31 updatedAt: 2026-10-29 order: 1 status: "published" faqs: - question: How often does the dashboard update? answer: "Current visitors uses a rolling five-minute activity window and refreshes about every 30 seconds. Traffic trends and other metrics refresh every few minutes." - question: How are channels defined? answer: "Each session is classified once, from its first page view. If that page has a UTM medium, the medium decides the channel (for example cpc becomes Paid search, unless the source is a social site, which becomes Paid social). Otherwise the referrer domain decides Organic search, Organic social, A.I., Referral, or Direct." - question: Can I export dashboard data? answer: "Export directly from the dashboard is not available. For detailed exports and custom reports, connect Google Analytics to your board." - question: Why does a job show applications but few or no views? answer: "Views and apply clicks are counted by the visitor tracker in the job seeker's browser, and ad blockers or privacy browsers can stop it. Applications are counted from the submitted applications themselves. A job can therefore show applications with fewer, or zero, views and apply clicks. This applies to the Jobs list in your dashboard and to the job stats employers see." - question: What counts as a visitor? answer: "Cavuno counts distinct tracked session IDs, not identifiable people. Multiple page views in one session count once for the selected period, while the same person can count more than once across browsers, devices, or new sessions." --- View your job board's performance at a glance. See who is on the board right now, how they arrived, which jobs get attention, and how traffic changes over time. ## Before you begin Publish at least one job before evaluating job-level performance. For a useful traffic comparison, choose a period that includes the campaign, post, or listing change you want to investigate and a comparable period before it. ## Access your analytics 1. Click **Home** in the sidebar 2. Scroll past the Companion prompt to **Your overview** 3. Use the date picker next to **Your overview** to change the time range ## Key metrics ### Current visitors Shown above the Companion prompt as “N people on your board now”: the number of distinct tracked sessions with activity in the previous five minutes. Use it as a near-real-time activity signal, not a count of unique people. Click the count to open a globe of those sessions. The overlay shows your board name and logo, with a Powered by Cavuno badge. Each pin is labeled Visitor N from that country and shows the referrer, device, and page from the latest hit. Pins for the same country are spread inside that country so they do not stack. ### Metric cards **Your overview** shows one card per metric, two to a row, in this order: visitors, apply clicks, Stripe and AdSense revenue when connected, new email subscribers and new candidate profiles when they apply to your board, then page views and average session. Each card shows the total for the selected range, the change from the previous period of the same length with that period's total next to it ("vs 28.6K previous period"), and a chart of the current period (solid line) against the previous one (dashed). The legend under each chart gives both date ranges, and hovering a day shows both periods' values. Compare them with job launches, campaigns, and referrals to investigate what may have changed; a chart alone does not establish the cause. ### Jobs posted Total count of active job listings. Use this as inventory context when interpreting traffic; the count alone does not show whether visitors found the listings relevant. ### Top jobs Most-viewed job listings. Treat views as an interest signal, then compare apply clicks and applications before deciding which roles or employers to prioritize. ### Top companies Companies with the most job views. Use this to identify which employers resonate with your audience. ### Channel, referrer, and campaign Acquisition is first-touch: one channel per session, taken from the first page view. 1. If that page has a UTM medium, the medium decides the channel. Common values: `cpc`, `ppc`, or `paid` become **Paid search**, unless the UTM source is a social site, which becomes **Paid social**. `email` becomes **Email**. `social` becomes **Organic social**. 2. Otherwise the referrer domain decides. Search engines become **Organic search**. Social sites become **Organic social**. Known AI chat domains become **A.I.** Other sites become **Referral**. 3. No referrer becomes **Direct**. The **Referrer** tab lists the raw host. The **Campaign** tab lists `utm_campaign` values from that first page. Rows with no campaign tag are omitted. `GET /v1/analytics/traffic` returns the same first-touch campaigns, one row per `utm_campaign`, `utm_source` and `utm_medium`, with apply clicks. Pass `campaignGroupBy=content` to also split rows by `utm_content` and `utm_term`, for example to compare individual posts in one campaign. Each row then has `content` and `term`, empty when the link had none. ### Apply clicks by job `GET /v1/analytics/apply-clicks` lists apply clicks grouped by job and first-touch channel. Pass inclusive UTC `start`/`end` so scheduled pulls can be incremental (defaults to the last 30 completed UTC days). Join `jobId` to the jobs export `id`. This is apply clicks, not confirmed applications, and not last-click. `GET /v1/analytics/job-visitors` lists unique visitors (sessions) that viewed a job-detail page, grouped by company slug, job slug, and first-touch channel. First-touch UTM campaign, source, and medium are included when the landing URL was tagged. Join `companySlug` + `jobSlug` to the jobs export `company_slug` + `slug` — not `id`. A deliberate slug rename splits visitor history. `visitors` counts unique sessions and will always be lower than `views` in the jobs export; the two are not expected to match. ### Pages and entry page **Pages** ranks paths by tracked sessions in the selected range. **Entry page** is the first path in each session. There is no exit-page report: the tracker does not record the click that leaves your board. ### Map and country Tracked session counts by country, shown as a choropleth and as a table. Each row shows sessions and apply clicks for that country. ### Browser, OS, and device Tracked session counts by browser, operating system, and device type. Each row shows sessions, with a bar for its share of the top row, and apply clicks. ### Google Search Console How your board performs in Google search for the selected date range, compared with the same number of days just before it. It appears once [Search Console is connected](/docs/analytics/connect-search-console). - The four tiles at the top show **Impressions**, **Clicks**, **CTR**, and **Avg. position** for the range, each with the change from the previous period and that period's value. A lower average position is better, so a drop shows as an improvement - Select a tile to chart that metric day by day, current period against previous - **Search queries** lists the queries people searched; **Search pages** lists your pages that appeared in results - Each row shows clicks, impressions, CTR, and average position. Clicks, impressions, and position also show the change from the previous period. **New** marks a query or page with no impressions in the previous period - **Top** sorts by clicks - **Rising** and **Falling** sort by the largest gain or drop in clicks. Falling includes queries that had clicks before and have dropped out of search results - **Striking distance** lists queries whose best page ranks between position 5 and 20 with at least 50 impressions, sorted by impressions, next to the page that ranks. These pages are close to the top of the first results page, so improving them is usually the quickest search win - The search box filters the rows by query or page URL Both periods use only days Google has finished processing, so a comparison never sets complete days against partial ones. Google finishes a day about two or three days later; the card's footer shows the last day included ("Google data through …"). Each view lists its top 250 rows. A search, or sorting by a column, also reaches the other rows the card loaded, up to 1,000 in all. Results refresh at most every six hours. Search Console keeps 16 months of data and the comparison period has to fit inside it, so an all-time range uses about the most recent eight months. ## Per-job performance The Jobs list includes three columns for each listing: **Views**, **Apply clicks**, and **Applications**. Views count page loads on the job detail. Apply clicks count presses on the Apply button. Applications counts native applications submitted through your board; jobs using an external application URL show — instead. Views and apply clicks come from the visitor tracker that runs in the job seeker's browser. Ad blockers, privacy browsers, and tracking protection can stop it, and those views and clicks are then not counted. Applications are counted from the submitted applications, not from the tracker. A job can therefore show more applications than apply clicks, or applications with no views at all. The same is true of the per-job stats employers see in their jobs list. Tracked session counts on **Home** are affected the same way. ## Filter by date Change the time period for your analytics: 1. Click the date picker next to **Your overview** 2. Select a preset: - Today - Last 7 days - Last 30 days - Last 90 days 3. Or choose a custom date range ## Verify the selected period After changing the date range, confirm the date picker shows the period you selected and that the metric cards, the channel, country, and device tables, and the Google Search Console card refresh together. The **Current visitors** count is different: it always uses the previous five minutes, so it should not change when you select a historical range. In the Jobs list, an externally hosted application flow should show **—** under **Applications**, while its **Views** and **Apply clicks** can still increase. ## Example investigation Suppose a newsletter links to three new roles. Select a range covering the send, compare the **Channel** and **Referrer** tabs for newsletter traffic, then inspect those jobs' views and apply clicks. A traffic increase without apply clicks suggests the message earned visits but not enough application intent; it does not identify the cause by itself. ## Automated traffic Visitor and pageview counts leave out automated traffic, on every card and for every date range, including past dates. Cavuno looks at how visitors behave: traffic that loads pages without using them the way people do is left out, and declared crawlers such as search engine bots are filtered with a maintained list. Apply click totals are not affected. New automated traffic is usually left out within an hour of arriving, so today's numbers can drop slightly as the day goes on. ## Troubleshoot unexpected numbers If a visit does not appear, confirm you are viewing the correct board and date range, then allow a few minutes for the dashboard to refresh. Browser privacy controls can prevent a session from being tracked, and when **Require cookie consent** is on, visitors who do not accept the cookie banner are not tracked. If Cavuno and GA4 differ, compare their definitions and consent behavior rather than expecting identical totals: Cavuno reports tracked session IDs, while GA4 applies its own identifiers and processing. ## Understand your analytics ### Traffic spikes When you see traffic increases: - Check what jobs were posted that day - Review any marketing or social posts you published - Note what worked so you can repeat it ### Declining traffic When traffic decreases: - Check if you're posting new jobs regularly - Review your SEO settings for any issues - Consider adding new content or running a promotion ### Popular content Use top jobs and companies to: - Understand what job seekers in your niche want - Guide your outreach to similar employers - Decide which job categories to expand ## Go deeper Built-in analytics are good for daily checks. For detailed analysis, conversion tracking, or search data: - [Connect Google Analytics](/docs/analytics/connect-google-analytics) for detailed traffic reports and user behavior - [Connect Search Console](/docs/analytics/connect-search-console) for search performance and keyword data ## Next steps - Review [Google Analytics setup](/docs/analytics/connect-google-analytics) when you need acquisition or journey reports - Use [Search Console](/docs/analytics/connect-search-console) to investigate search queries and indexed pages