How to Use Toolradar Data for a Software Category

Start with a question, not a position

A category position answers a defined question about a defined set of products. It does not establish which product is best for every buyer. Decide whether you want to inspect price, review coverage, directory visits or another available metric. Then check whether your product belongs in that category and whether the row's comparison group matches your question.

The methodology, checked on 5 November 2026, describes weekly snapshots. A position is shown only when at least eight tools in the group have data for that row. Missing data can mean that a row is not eligible to display; it is not proof that a tool has no customers, reviews or traffic. The table on a tool page identifies the group used for each displayed row.

Table: how to read the available surfaces, based on Toolradar's methodology and product screens checked 5 November 2026. Availability depends on the category, eligibility and the snapshot.

Find the right peer group

Open the product and check its category and the description under the row. Toolradar's public method says a position compares published tools in one category; where a tool belongs to several categories, the product table uses the most specific category with enough data. The dashboard can show positions in the peer groups a company's tools belong to. A category may therefore answer a different question from a broader grouping.

For example, a fictional scheduling app may belong to a broad productivity category and a narrower appointment category. If a table uses the narrower group, its position cannot be presented as a rank among all productivity software. Record the category, metric, group size and date together. Do not remove the denominator when sharing a position.

If the category itself seems wrong, use corrections with the product URL and a description supported by the vendor's official material. The company claim and product data are separate questions: the claim guide explains access, while a correction is assessed against its own evidence.

Read price and review rows carefully

Toolradar's method says price positions use prices read on the vendor's own pricing page and compare products on the same basis: currency and the thing priced, such as a team plan or a per-seat unit. The cheapest displayed entry price is not a total cost comparison. Usage, contract terms, seats and features can differ. Consult the pricing-check guide and the vendor's current source before presenting a price externally.

Review-based rows have their own eligibility threshold. A position based on ratings or review counts describes the data collected under that row's rule, not a controlled test of product quality. The methodology distinguishes Toolradar Data from the directory's separate category ranking composite. A review rating, a Data position and a buyer guide's display order answer different questions.

Ties share the best rank under the published method. When comparing snapshots, verify that the group, eligibility, unit and computation date are comparable before attributing a movement to a product change. A product can move because the available comparison group changed.

Understand what visits can and cannot show

The method defines page visits as distinct visitor sessions in Toolradar's own analytics, with bots excluded. Traffic can arrive through different sources, including sponsored slots. A directory visit is not automatically a qualified lead, a sale or an independent vote for the product. Different traffic sources and attribution windows make the measure unsuitable as a standalone return-on-investment calculation.

A growth row compares its stated windows and has its own minimum. If a row is absent, do not treat that absence as zero. A verified company can inspect available analytics in its company area; compare those definitions with the category row before combining figures. Do not include client-level or personal information when requesting a correction.

Check the minimum behind each metric

The method specifies different thresholds for different rows. A rating position uses products with at least 20 reviews behind their displayed rating. The page-visit row requires at least 50 visits in the 30-day window; the comparison-page visit row requires at least 20 such visits. A growth row requires at least 100 visits in each of the two 30-day windows. These are eligibility rules, not measures of statistical significance or commercial success.

A hypothetical product with 49 recorded page visits in the window may be absent from that visit position even if it has a complete profile. A product with 50 visits can still be affected by whether enough peers meet the same rule. Do not use these numbers as a target or infer a competitor's exact traffic merely from its presence or absence.

Before sharing a result, visit the product's listing directory, open the actual row and check whether the snapshot and source are displayed. If the wording on the live page differs from this guide, use the live definition and request clarification rather than merging incompatible figures.

Export and cite a snapshot

From an eligible category statistics page, open the CSV if one is available. Keep a copy of the calculation date, category name, metric definition and any eligibility note with your analysis. Toolradar states that category data is published under CC BY 4.0; review the linked license and give attribution when reusing it. A link to the page and method helps readers check context.

The download route can return no file when the category or its snapshot is unavailable. Try another eligible category only if it answers the same question. Substituting a larger or differently defined group solely to obtain a favorable position makes the comparison misleading.

G2's category research explanation, checked 5 November 2026, describes its own categorization process; G2's report overview, checked the same day, describes reports based on its own review and market-presence information. These are different products with different populations and methods. A Toolradar position cannot be transferred to a G2 report or treated as if the two measure the same thing.

Keep advertising separate from the data

Toolradar sells sponsored placements, described on its advertising page. Its Data methodology says advertising spend, campaigns, clicks sold to advertisers and placement fees are not inputs to the computation. However, visits from sponsored slots can be included in the visit measure because the measure counts eligible visits from all sources. These two statements describe different parts of the process: the calculation does not read ad spend, while the traffic measure reflects observed visits.

A paid guide position can affect display order without changing the Data calculation. Check the specific placement and its disclosure, and never describe a paid placement as an independently earned Data position. A badge has separate placement and verification rules, explained in the badge guide.

Frequently asked questions