Contextter Keyword Docs
Open Contextter
Keyword Database

Balance and data refreshes

Organizing keywords is workflow work. Fetching fresh market data, SERP data, and tracking history can use balance. Scope paid actions deliberately before starting large batches.

Free organization work

Searching, filtering, lists, tags, presets, columns, and many review actions are about organizing existing data.

Paid data work

Fresh keyword metrics, SERP refreshes, competitor data, and recurring tracking can use balance depending on the action.

Scope before spending

Use lists, filters, selections, and counts to make paid data updates predictable.

Balance widget

The balance widget in the lower-left sidebar shows available EUR credit and monthly usage progress. Use it before starting larger enrichments, SERP refreshes, competitor updates, or recurring tracking schedules.

Balance is not a keyword metric. It is an operational control that helps admins and teams understand whether planned data work fits the available budget.

Actions that usually do not need balance

These actions organize existing data:

  • Searching keywords
  • Applying filters
  • Saving presets
  • Showing or hiding columns
  • Creating manual lists
  • Applying tags
  • Moving Kanban status
  • Opening existing keyword rows
  • Exporting data already available in the view

Actions that can use balance

These actions may fetch, refresh, or process paid data:

  • Keyword data enrichment
  • Fresh search volume or intent data
  • SERP refreshes
  • Competitor overview or deeper competitor analysis
  • Recurring rank tracking
  • Large paid data batches
  • Provider-backed data refreshes

The exact cost depends on provider routes, keyword count, selected packages, and whether cached or already-fresh data can be reused.

How to scope a paid refresh

1
Start from the smallest useful list or filtered view.
2
Check keyword count before opening the refresh or enrichment flow.
3
Use Data Health and data date to avoid refreshing rows that are already usable.
4
Confirm the selected data package or refresh type matches the decision.
5
Review the estimated cost and current balance before starting.
6
Use Activity after the run to confirm completion and investigate failures.

Data freshness decisions

Fresh data matters most when the decision is expensive, public, or time-sensitive. Refresh before high-stakes client exports, major campaign planning, competitor review, tracking setup, and paid-channel comparisons.

Fresh data matters less for early brainstorming, internal backlog cleanup, rough topic grouping, or exploratory search. In those cases, old data can be enough to decide whether deeper review is worthwhile.

Admin usage hygiene

Admins should decide who can start meaningful paid data actions and how teams should prepare batches. The best usage control is not blocking normal work; it is making expensive work deliberate.

Recommended habits:

  • Create lists before large refreshes
  • Avoid refreshing the entire workspace by default
  • Review Data Health first
  • Keep tracking lists focused
  • Confirm market and language before refresh
  • Teach teams to read existing data before buying new data