How to Count Unique Instagram Commenters Without Calling Them Followers

1. Define what your participation count covers

Write the question before you collect data. For example: “How many known accounts appear in the top-level comments we observed on these selected posts?” A top-level comment is a comment directly under a post, rather than a reply to another comment.

Keep the following details with your tables:

The observation period and comment date range serve different purposes. A comment can have an earlier publication date than the date you collected it. Keep both dates when available.

For a combined count, count an account once across all selected posts. Do not add the separate post counts and call that the number of unique accounts. The same account can comment on more than one post.

A public question asks how to find users who commented on a specific post. That supports starting with a known post and its comment authors. It does not support claims about the whole audience or demand for this method. Public question, retrieved August 11, 2026; one question record.

2. Choose a source and make a small checked collection

Use manual records if they answer the question with enough detail. Save the post address and the source evidence for each comment. If you cannot establish a stable author ID, leave that identity unresolved. A visible username alone is not a substitute for the required ID.

If you use an existing account-owner export, check its scope and fields first. Keep owner-only records separate from public comment records. A public comment does not establish a purchase. A purchase record would need its own source and a checked link to the account before it could support a buyer claim.

For a larger public comment collection, the documented fit is the Instagram Comments Scraper. An Actor is a hosted data collection program. This Actor documents collection of public top-level Instagram comments without login or cookies. You still build and check the account count yourself.

The following input is the supplied small configuration. Replace the sample address with the intended public post or Reel address before use.

{"collectAllAvailable":false,"commentSortMode":"default","maxCommentsPerPost":10,"postUrls":["https://www.instagram.com/reel/DZu6dkVyImf/"]}

The settings mean:

1. `postUrls` holds the public posts or Reels to check.
2. `maxCommentsPerPost` limits saved unique top-level comments to ten per post in this input.
3. `commentSortMode` keeps the default comment order.
4. `collectAllAvailable` remains `false`, so the limit stays in use.

The input shape was checked against the supplied public schema, which defines the accepted fields and values. No collection was run for this guide. The documented build is 0.1.21, checked on October 25, 2026. Public build and field definitions, checked October 25, 2026; documentation only.

The Actor also documents optional `commentsFrom` and `commentsUntil` fields. They filter comment publication dates, including the stated start and end dates. They are absent from the supplied input. If you add them, record their values with your results.

The order options `newest` and `oldest` sort the collected sample by date. Do not treat a sorted sample as proof that every comment was collected. Removing the limit also does not prove complete coverage. Collection can still end when the public feed ends, time runs out, or the source fails.

A public Export Instagram Comments to CSV Task, checked October 25, 2026; page presence only is available. A Task is a saved input preset. Its saved settings were not checked through an authenticated account, and it was not run for this guide. Check its input before use. CSV means comma-separated values, a file format for table data.

3. Save source fields before calculating counts

Keep the original export unchanged. Build your working tables from a copy so that each result can be checked against its source.

Save these documented fields:

Store IDs as text so your table software does not round them or change their form. The author field is `ownerId`. Use that exact field name when matching source rows.

The documented times use UTC, or Coordinated Universal Time. Keep the original times. If you display local times, label the time zone and retain the source value.

A missing value is not zero. In the documented output, `null` means unavailable. For example, `likesCount` of `0` means a known count of zero. A `null` value means that the count is unavailable. Likewise, `ownerVerified` of `false` is a known false value; `null` is unknown.

A `repliesCount` value is a count, not the text or author records of those replies. Do not add it to your collected comment rows or use it to calculate more authors. The current contract does not export follower or liker lists. Output definitions and collection scope, checked October 25, 2026; no runtime result.

4. Build the comment table before the account table

First create a table with one row per distinct `commentId`. “Distinct” means that each different ID appears once.

Follow these steps:

1. Group repeated rows with the same `commentId`.
2. Retain one comment record for the count.
3. Keep links to all source rows where you observed that comment.
4. Preserve collection times in a separate collection log if you made several checks.
5. Keep different comment IDs as different comments, even when their text matches.

Two comments from the same account remain two comments. Removing repeated sightings of one comment is a different operation from counting an author once.

Check conflicting source rows before you accept the table. If one comment ID has different author IDs in different records, retain the source evidence and mark the author link unresolved until checked. Do not choose an ID just to make the count complete.

If a working record lacks a usable comment ID, keep it outside the confirmed unique-comment total until you can check it. Identical text does not prove that two records describe the same comment.

Next create an account table with one row per known `ownerId`. Link each account to the comment IDs that support it. Use these locally created table columns:

These are analysis columns you create. They are not an extra Actor output.

Keep missing author IDs out of this known-account table. Do not place all missing IDs into one shared “unknown account.” That would invent an identity link. Keep the affected comments in a separate unresolved table instead.

5. Count accounts and unknown-author comments separately

Calculate three main values from the checked comment table:

1. Unique comments: the number of distinct known `commentId` values.
2. Known author accounts: the number of distinct known `ownerId` values linked to those comments.
3. Unknown-author comments: the number of unique comments whose author identity remains missing or unresolved.

Keep the units in your report. Comments, accounts, and people are different units.

An unknown-author comment might belong to an account already in your table. It might belong to a different account. Several unknown-author comments might also share one author. Therefore, do not add one account for every missing author ID.

Use “accounts” rather than “people.” One person may operate several accounts, and the supplied source does not resolve who operates each account. A comment also does not prove follower membership, a purchase, or a relationship between accounts.

6. Check the arithmetic with an original fictional example

Original fiction: all IDs and counts in this example are invented. The table illustrates the method. It is not an Actor result. The six rows below have six different comment IDs.

The known-account table is:

The unknown-author table contains:

The arithmetic is:

• Known-author comments: 2 comments + 1 comment + 2 comments = 5 comments.
• All unique comments: 5 known-author comments + 1 unknown-author comment = 6 comments.
• Known distinct authors: account A + account B + account C = 3 accounts.
• Unknown-author comments: 1 comment.

The report should say: “The observed records contain six unique top-level comments in total: five from three known author accounts and one with unknown author identity.”

Do not report exactly four accounts. C4 could belong to A, B, C, or another account. Do not report six people, three followers, or any confirmed customers.

C2 and C6 remain in the comment count. They do not add new known accounts. C4 remains unresolved; it is not deleted and is not assigned to a guessed author.

7. Add public profile context only when needed

A comment participation count does not require a full profile review. Add profile checks only when the research question needs current public account context.

Check only known public profile addresses that you have verified. Save the check date and keep the profile table separate from the comment and account tables. Do not turn an uncertain username into a confirmed account match.

A later profile check describes what was available at that later time. It does not establish follower membership, buyer status, or a relationship between two accounts. It also does not change an unknown author into a known one without a checked identity link.

If you later need to clean repeated profile records, use the separate Instagram profile identity guide. That is a later profile-record task. Keep the comment participation count based on its own source IDs.

If the next task is to review contest entries, use the Instagram giveaway entry guide. This participation count does not decide eligibility. An observed commenter account is not automatically an accepted contest entry.

8. Check the tables and state collection limits

Accept the result only after these checks pass:

1. Every counted comment links to a source row and selected post.
2. Every counted account links to at least one comment with a known author ID.
3. Repeated sightings of one comment do not increase the unique-comment count.
4. Several comments from one author do not increase the known-account count.
5. Missing author IDs remain unresolved.
6. The known-author and unknown-author comment counts add to the unique-comment total.
7. The report states the selected posts, collection times, comment scope, and limits.

When a check fails, preserve the affected records and state the reason. Use this decision table:

A collection below its limit still does not prove complete coverage. Report what you observed. Avoid “all commenters” unless separate evidence supports that claim.

For repeated collections, retain a collection log and match comment IDs across exports. The documented input has no since-last-run or new-comment-only switch. Do not assume that running it again returns only new records. Input scope, checked October 25, 2026; documented settings only.

Your report should give the comment count, known-account count, unknown-author comment count, post coverage, and collection limits together. State that replies, followers, likers, and private customer records are outside this public top-level-comment analysis.