Skip to content

Plans, Tokens, and Limits

Understand plans, token usage, feature access, and practical limits.

Plans control feature access, organization size, and included token allocation. Tokens are usage credits for captured searches, recurring tracker runs, and AI Visibility checks.

Lightest workflow

Direct Search builds a search URL and sends you to the search engine. It does not capture a full result page inside iSearchFrom.

Token-using work

Search Engine Proxy searches, additional proxy pages, tracker runs, ad tracker runs, AI Visibility checks, and manual campaign runs can spend tokens.

Billing cycle

Subscription tokens reset to the plan allocation on renewal. Extra top-up tokens are permanent organization tokens and do not reset at renewal.

Review usage

Use Billing to review subscription tokens remaining, extra tokens, recent usage, and next billing date.

Subscription tokens are spent before top-up tokens. If the subscription balance reaches zero, token-using work can continue only when the organization still has permanent top-up tokens.

More proxy result pages increase usage because each additional page requires more captured search work. Start with one page unless deeper coverage is required.

Plans can control access to projects, organization members, Search Engine Proxy usage, Direct Search usage, API access, AI Visibility, email digests, exports, priority support, and SSO.

SERP Position Tracker

Requires at least 1 tracked domain and 1 keyword. Supports up to 10 tracked domains and 10 keywords per campaign.

Ads Position Tracker

Requires at least 1 tracked domain and 1 keyword. Supports up to 10 tracked domains and 10 keywords per campaign.

AI Visibility

Requires at least 1 brand name, 1 prompt, 1 location, and 1 platform. Supports up to 20 brand names, 20 competitors, 50 prompts, 50 locations, and 500 checks per run.

Search Engine Proxy

Supports up to 10 result pages per search request. Load additional pages only when the first page does not answer the question.

These limits keep campaigns useful and predictable. If you need larger monitoring, split work into focused campaigns by market, product, or client.

Create one campaign with a small keyword or prompt set. Use one or two priority locations before adding every market.

Run the workflow manually or wait for the first scheduled run. Confirm country, city, language, domain, device, and platform settings before expanding.

Check whether the result answers a decision or report question. If it does, expand keywords, prompts, competitors, pages, or locations gradually.

Pause campaigns that no longer feed a decision. Remove test campaigns after setup so token usage stays easy to explain.

Schedules

Use weekly schedules before switching a new campaign to daily.

Campaign size

Avoid one oversized AI Visibility campaign when several focused campaigns are easier to understand.

Names and notes

Use project names and campaign descriptions so teammates understand why usage exists.

Open Billing in the app. Billing shows your current plan, included subscription tokens, extra top-up tokens, next billing date, and recent token usage.