SEED Analytics

Enter the dashboard API token to continue. It is stored in this browser only.

The token is the API_TOKEN value from the server's environment.

Skip to the numbers
SEED Global Education Analytics
→
Overview Visitor activity
    Traffic sources
      Content performance
        Data quality
          API access

            SEED Global Education website report

            Overview

            The headline figures for the dates chosen at the top of this page.

            Visitor activity

            Single visits you can read from start to finish, and the day-by-day totals behind them.

            What people read before they enquire

            One person's trail per visit. Visits that ended in an enquiry come first.

            From Copy reference inside any visit, a form submission, or a browser’s sa_did / sa_sid. A whole URL works too.

            Day by day

            How many people came each day, and how many pages they opened, across the dates chosen above.

            Which actions happened, and how often

            Across the whole site: forms sent, WhatsApp clicks and pages opened all count.

            Where people went when they left

            Links that sent people off the site, counted by where the link goes.

            Where people give up on a form

            Pages with a form: saw the page, reached the form, sent it. Watch the last drop.

            Which question people stop at

            Each question in order. “Reached” answered it; “Stopped here” gave up after it.

            Traffic sources

            What sent people to the site, the page they arrived on, and where in the world they were.

            Where visitors came from

            The site or app that sent them here. Typed and saved-link visits are left out.

            Campaigns you tagged

            Visits from links tagged with a campaign name. Untagged links never appear.

            The page people land on first

            The page each visit started on, over the dates chosen above.

            Where in the world visitors are

            From each person’s internet connection. Known for some only — the first line says how many.

            Content performance

            Which pages held attention, which parts of them people read, and what they were reading on.

            Most-read pages

            The pages opened most often over the dates chosen above.

            Time spent on each part of a page

            Pick a page, then read it top to bottom to see where visitors linger and where they stop.

            Sections on each page

            Built from each page’s data-sa-section markers. The pages as they are now, so the dates don’t apply.

            Phones, tablets and computers

            What they were reading on. A phone and a laptop count as two.

            Data quality

            Automated visits, the gaps in what can be measured, and the live feed.

            Automated visits

            Search engines and AI tools. Kept and marked, and left out above unless the header says otherwise.

            Visits that look like copying, not reading

            Software working through the pages. It lifts visitor counts, but never fills in a form.

            What just happened

            The 100 most recent actions, newest first. Always live, whatever dates are chosen.

            Live

            Adding a page to this report

            Goes in the <head> of every page you want counted.

            
                          
                        
            • Page opens, clicks on links that leave the site, and form submissions are all counted on their own. Add data-no-autotrack to stop that.
            • Count something of your own with seedAnalytics.track('enquiry_submitted', { programme: 'MSc' }).
            • Tie a visit to a record in the CRM with seedAnalytics.identify('lead_1234').
            • People who have turned on Do Not Track in their browser are not counted at all.

            API access

            Keys that let other systems read this data. One key per system.

            API keys

            Every key, what it may read, and when it was last used. Edit or show a key at any time.

            API documentation

            Create a key

            The key value stays the same, so nothing using it needs updating.

            Say which system will use it, so this list still makes sense in a year.

            What it can read
            Permissions

            Personal data is switched off while website addresses are filled in: anyone who opens a web page can read the key inside it.

            One per line, the address only: https://www.seedglobaleducation.com, nothing after it. Only pages at these addresses can use the key.

            More options: sites, request limit, note
            Sites it can read

            Leave every box empty for all sites, including any added later.

            120 suits almost everything. At most 1,200.

            SEED Global Education · analytics.seedglobaleducation.com