Why did my DiscoLike lead count change for the same search?

The DiscoLike help pages give 4 common reasons. The first to rule out: If an employee range or revenue range filter is written in a form DiscoLike cannot read, the search can run without that filter, as its docs explain, so the count can jump.

What causes it?

  1. If an employee range or revenue range filter is written in a form DiscoLike cannot read, the search can run without that filter, as its docs explain, so the count can jump.

    In the DiscoLike help: employee_range and revenue_range are the exception: a value that does not parse is silently dropped and the query runs without the filter. Discover API | DiscoLike API, read 2026-11-12.

  2. Searches carry a minimum footprint score unless you change it, so companies with a very small online footprint can be left out.

    In the DiscoLike help: Minimum digital footprint score (0-800, default: 25). Discover API | DiscoLike API, read 2026-11-12.

  3. Domains that redirect elsewhere are not included by default, so a company known by a redirecting domain can be missing.

    In the DiscoLike help: Include domains that redirect to another domain (default: false) Discover API | DiscoLike API, read 2026-11-12.

  4. A search that stops on its own can come back empty on a later page, which DiscoLike describes as reaching the edge of the market rather than an error.

    In the DiscoLike help: A stopped list can return an empty later page, which means the market edge was reached Discover API | DiscoLike API, read 2026-11-12.

How do I check it myself?

  1. Preview how many companies a search will return before running it, and compare that with the count you got last time.

    In the DiscoLike help: Use Count to preview result volume before running a full query Discover API | DiscoLike API, read 2026-11-12.

  2. Compare the filters DiscoLike reports it used with the ones you meant to set, since a dropped filter shows up there.

    In the DiscoLike help: JSON object containing the filters actually used for the search. Discover API | DiscoLike API, read 2026-11-12.

How does DiscoLike work with Feder?

  • Connect DiscoLike to Feder and it joins your Interest apps.
  • When you connect DiscoLike, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.

Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.

See whether you can trust the numbers in DiscoLike, one of your Interest apps. Feder only reads. It never changes anything in DiscoLike.

Where do these answers come from?

Every cause and check on this page comes from the DiscoLike help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.

Know the day a number breaks, not the month after.