- Account Status
- Active / Inactive Status
- Ad hoc Job
- Ad hoc Report
- Custom Data Set
- Data Source
- Data Source Logins
- Data Source Login Status
- Data Source Account Type
- External Data
- Group Account
- Group Account Timezone
- Historical Data
- Query Value
- Job Status
- Project Log
- Report Status
- Scheduled Job
- Scheduled Report
- Trackpal Data
- Usage Points
- User Uploaded Batch
Summary screen showing the current status of the subscription account. This includes how many data source logins, projects, scheduled jobs & reports, ad hoc jobs & reports are in the system, including quick access to seeing any items that are either currently running, or have issues that need resolving. It also includes a summary of their usage points.
Scheduled jobs and custom data sets that are automatically collected can be set to either active status (they continue to collect data), or inactive status (no new data collected but old data retained). Projects can also be set to inactive which results in all scheduled jobs and custom data sets contained with them being set inactive. This is useful to hide old projects without deleting them from the system.
A job that is run only once. This could be to download historical data, or to get data that is needed on an ad hoc basis.
A report that is run only once. This could be a benchmark report that is run once a new project is created and a benchmark set of results is obtained, as well as any historical data if available.
The data resulting from a specific scheduled occurrence of a scheduled job.
Sets of data that are defined by the user. They can contain either tables of data or single values for a particular date or date range, or one-off sets of data that aren’t collected on a scheduled basis.
Pre-defined sources that Trackpal obtains data easily from. These include Google search results, Google Analytics, Brandwatch, Facebook, Twitter etc.
For data sources that require user logins, for instance a Google Analytics account. Some of these require username/passwords to be encrypted and stored in the system, others allow authentication using technology such as OAuth. These accounts usually have multiple profiles available, so can be used across multiple Trackpal projects.
Each data source account has a status that it can currently be in:
- Waiting to validate: it’s been added and Trackpal is checking whether the authentication details are correct.
- Authenticated: Trackpal has access to the account with the current credentials. Trackpal confirms this on a daily basis and reports to the user if authentication fails.
- Authentication failed: Trackpal can not access the account using the current credentials. Any jobs dependent on using this data source account will not be able to run until the issue is resolved.
The type of account, i.e Google Analytics, Facebook, Google Search Console (GSC) etc.
Raw data that can be collected directly from data sources (i.e Google search results) straight within Excel (i.e not requiring Trackpal servers), or sent to Trackpal servers for data collection which then uses usage points.
Each Trackpal customer has a subscription that gives multiple users access to the same set of Projects. In order to have access to a different or sub set of projects, a separate subscription is required.
Each subscription has a timezone (i.e hours from GMT) that is the basis for determining when scheduled items should run.
Data that can be retrieved from the past directly out of data sources (i.e such as Google Analytics) or imported by a user from their own data.
Most basic data sources require some kind of primary query value in order to retrieve data. Examples of these include keywords for search results, usernames for Twitter or Facebook accounts, URLs or domain names etc. This is the generic name used to cover all of these.
Data that is collected from pre-defined data sources setup by Trackpal. These can either be in the form of a scheduled job, or an ad hoc job.
Each job has a status that it can currently be in:
- Created: The job is not yet transferred to the data collection engine.
- Not yet run: The job has transferred to the data collection engine, but not due to run yet.
- Due to run: The scheduled time that its next batch is due to run, but isn’t yet (can occur when there is a lot of items due to run at the same time).
- Running: The batch is currently running.
- Running (with errors): The batch is currently running, but some items failed to run (the user can then view these to see why and sort out the issues).
- Finalising: The batch has all its data collected, but is currently going through a finalisation process that includes validating the data and making the entire batch data set available to the user.
- Finished: The batch has completed and been finalised without any errors.
- Finished (with errors): The batch has completed and been finalised but some items failed to run (the user can then view these to see why and sort out the issues.)
- Last Run / Next Run: The date a scheduled job or scheduled report ran or is next due.
This includes a list of extra parameters that can be customised for a particular Trackpal subscription. There are some standard parameters, which are domain names for tracking and monitoring search ranking, brand terms, competitors etc. This allows flexibility for Trackpal to support specific customer needs.
All the data collected on a scheduled basis for a campaign (or client). Each project can have a name, a logo, one or more scheduled jobs, custom data sets (either manually entered, or automatically collected), scheduled reports, and parameters.
Each project has a log of all activity that has occurred against it. This includes when it was created, scheduled jobs run, and when changes are made to it.
The email address of people who will receive automatically emailed copies of reports.
An automatically generated Excel spreadsheet that uses a report template to determine its layout and structure, and a report macro to automatically pull in the relevant data into the template.
Each report has a status that it can currently be in:
- Not yet due: Next due date is in the future.
- Waiting on jobs: Scheduled time of its next run is due, however it is waiting on some scheduled job's data collection to be completed.
- Waiting to run: All dependent scheduled jobs have been run and finalised, and the report is now ready to run.
- Running: The report is currently being generated on the server and will soon be emailed through.
- Failed (try again): The report failed to run, however it will try again soon (this could be due to some temporary fault).
- Failed: The report failed to run several times, and any further attempts have stopped. This requires user action to make it run, or Trackpal Support to determine the cause of this.
- Run: A specific scheduled occurrence of a scheduled job.
The pre-defined schedule that a Job or Report is set up to run. For example on a daily, weekly or monthly basis. They can run at set intervals of these (i.e every 3 days). By default they run just after midnight of the subscription timezone.
A job that is run on a scheduled basis (i.e daily, weekly, monthly etc). It will continue running and collecting data on this basis until it becomes inactive.
A report that is run on a scheduled basis (i.e daily, weekly, monthly etc). It will continue running and collecting data on this basis until it is deleted.
Raw data collected by Trackpal that can be pulled into Excel for analysing.
Every item of data collected consumes a set number of usage points. Each group account has an allowance of usage points. When the allowance is exceeded, additional blocks will be billed to you. You will be informed when you are reaching their limit, or if you exceed it.
An inpidual Trackpal user account. Each group account can have multiple users.
For scheduled jobs that require historical data to be manually uploaded if it wasn’t collected via Trackpal (i.e search positions using 3rd party tools) users can manually upload data into the system.