X (Twitter) Tweet Engagers & Audience Leads
Pricing
from $1.30 / 1,000 unique engager results
X (Twitter) Tweet Engagers & Audience Leads
Turn public X/Twitter Retweets, Quote Tweets, and replies into one deduplicated audience list. Compare repeat engagers across Tweets and export profiles, engagement evidence, follower counts, and verification—no login or API key required.
Pricing
from $1.30 / 1,000 unique engager results
Rating
0.0
(0)
Developer
Arjun AI
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Turn public Retweets, Quote Tweets, and replies into one deduplicated X/Twitter audience list. Add up to 25 public Tweet URLs or IDs, choose the engagement types you need, and export matching users with profile details and evidence of how each person engaged.
Use this Actor to identify repeat engagers, campaign advocates, relevant creators, active community members, and public accounts worth reviewing or contacting. No X login, cookies, API key, or proxy setup is required.
What this Actor does
- Collects public users who Retweeted, quoted, or replied to each input Tweet.
- Combines the same person across multiple Tweets and engagement types into one row.
- Shows the Tweet and action behind every match instead of returning an unexplained username list.
- Finds repeat engagers across several Tweets or people who used several engagement types.
- Filters saved users by follower count and X verification status.
- Optionally includes visible replies inside the wider conversation, not only direct replies.
- Exports structured results to JSON, CSV, Excel, XML, RSS, or the Apify API.
Common use cases
- Build a public lead list from people who engaged with a launch, event, or campaign.
- Find repeat supporters and high-intent community members across several Tweets.
- Compare who amplified, discussed, or replied to your content.
- Review public Quote Tweet and Reply text for audience research.
- Discover creators and verified accounts already engaging in a topic.
- Send clean engagement data to a CRM, spreadsheet, dashboard, or AI workflow.
How to use
- Add up to 25 public Tweet URLs or numeric Tweet IDs.
- Choose Retweets, Quote Tweets, Replies, or any combination.
- Set Users per engagement type, per Tweet. Use
0to follow every page currently exposed by X. - Optionally require repeat engagement, multiple action types, a minimum follower count, or a verification group.
- Click Start and open the Dataset when the run finishes.
The same Tweet entered more than once is processed once. Valid Tweets continue even when another input is invalid or unavailable.
Input reference
| Field | Purpose |
|---|---|
tweets | Up to 25 public Tweet URLs or numeric IDs. |
collectRetweets | Include public users who Retweeted each Tweet. |
collectQuoteTweets | Include Quote Tweet authors plus their public Quote text and metrics. |
collectReplies | Include public users who replied. |
includeThreadReplies | Also include visible replies to other replies. Ignored when Replies are off. |
maxUsersPerTypePerTweet | Collection limit for each selected type on each Tweet. 0 means all records currently exposed by X. |
engagerMatch | Save any engager, users with at least two action types, or users matching every selected type. |
minimumTweetsEngaged | Require activity on this many different input Tweets. |
minimumFollowers | Keep accounts with at least this many followers. 0 disables the filter. |
verification | Keep any, any verified, blue verified, official/legacy verified, or unverified accounts. |
Example input for finding repeat engagers across three Tweets:
{"tweets": ["https://x.com/thsottiaux/status/2109892247580000595","https://x.com/thsottiaux/status/2109812360596865224","https://x.com/thsottiaux/status/2109132167112782291"],"collectRetweets": true,"collectQuoteTweets": true,"collectReplies": true,"includeThreadReplies": false,"maxUsersPerTypePerTweet": 100,"engagerMatch": "any","minimumTweetsEngaged": 1,"minimumFollowers": 0,"verification": "any"}
How audience matching works
Every successful Dataset row represents one unique public X user, even when that person took several actions or engaged with several input Tweets.
- Any selected engagement — the broadest audience.
- At least 2 engagement types — people who used two or more selected action types.
- Every selected type across the input Tweets — actions may occur on different Tweets.
- Every selected type on the same Tweet — every selected action must occur on at least one common Tweet.
For example, someone who Retweeted Tweet A and replied to Tweet B matches across the input Tweets, but not on the same Tweet.
Output
The result is designed for both quick review and downstream processing:
usercontains the public profile, follower counts, verification, website, professional category, affiliation, and profile images when returned by X.engagement_summaryexplains the user's total actions, action types, and number of input Tweets engaged.engagements_by_tweetseparates the user's activity for each source Tweet.engagementscontains the individual Retweet, Quote Tweet, and Reply evidence. Quote Tweets and Replies include text, URL, time, and available metrics.
The following shortened row comes from a real public test run:
{"status": "success","user": {"user_id": "577207659","username": "Injection4Xcode","name": "Injection for Xcode","profile_url": "https://x.com/Injection4Xcode","location": "Italy (VT)","created_at": "2012-05-11T13:14:17Z","followers_count": 1991,"following_count": 209,"tweets_count": 12567,"verified": false,"blue_verified": false,"protected": false},"engagement_summary": {"selected_engagement_types": ["retweet", "quote", "reply"],"engagement_types": ["retweet"],"total_actions": 3,"retweets_by_user": 3,"quote_tweets_by_user": 0,"replies_by_user": 0,"tweets_engaged": 3,"matches_all_selected_types": false,"matches_all_selected_types_on_same_tweet": false},"source_tweet_ids": ["2109132167112782291","2109812360596865224","2109892247580000595"],"engagements": [{"type": "retweet","source_tweet_id": "2109892247580000595","source_tweet_url": "https://x.com/thsottiaux/status/2109892247580000595"}]}
Dataset views and status rows
The Overview view puts usernames, engagement types, repeat-engagement counts, followers, verification, affiliation, and profile links first. Use All fields for the complete nested record.
The Status rows view explains inputs that did not produce a normal user row:
invalid_input— unsupported Tweet URL or ID;not_found— deleted, private, unavailable, or nonexistent Tweet;no_results— no visible engagers or no users matching the filters;partial— some results were saved, but one collection stream could not finish;request_failed— the public request could not be completed.
Coverage and limits
X decides which public engagement records are visible and how far each timeline can be paginated. Therefore, 0 = all means all records currently exposed by X's public web timelines; it does not guarantee that the Dataset will equal the engagement counter displayed on the Tweet.
Deleted content, protected accounts, withheld content, and engagement that X does not expose cannot be returned. Large Tweets, nested conversations, multiple input Tweets, and 0 = all runs take longer than small capped runs.
Pricing
This Actor uses pay-per-event pricing. A small $0.00005 Actor start event is charged when a run begins. The engager-result event is charged once for each unique user successfully saved after deduplication and filtering. Status rows such as invalid_input, not_found, no_results, partial, and request_failed are not charged as results.
| Apify plan | Per unique engager | Per 1,000 unique engagers |
|---|---|---|
| Free | $0.00200 | $2.00 |
| Bronze | $0.00180 | $1.80 |
| Silver | $0.00150 | $1.50 |
| Gold | $0.00130 | $1.30 |
| Platinum | $0.00130 | $1.30 |
| Diamond | $0.00130 | $1.30 |
The Actor's live Pricing tab is authoritative if prices change. Use Maximum cost per run to set a hard spending limit.
API, schedules, and integrations
Run the Actor from the Apify Console, JavaScript client, Python client, REST API, Tasks, Schedules, Webhooks, or Apify MCP. Results can be sent to Google Sheets, Make, Zapier, Slack, a database, or your own application.
JavaScript example:
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('arjun_code/x-twitter-tweet-engagers').call({tweets: ['https://x.com/thsottiaux/status/2109892247580000595'],collectRetweets: true,collectQuoteTweets: true,collectReplies: true,maxUsersPerTypePerTweet: 100,engagerMatch: 'any'});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Example MCP request:
Run arjun_code/x-twitter-tweet-engagers for these three Tweet URLs. Include Retweets, Quote Tweets, and Replies, then return users who engaged with at least two Tweets.
FAQ
Does the Actor require my X account or API key?
No. Users do not provide an X login, cookies, API key, or proxy.
Why is the result count lower than the number shown on X?
Tweet counters are aggregate numbers. X may hide, remove, protect, rank, or stop exposing some underlying accounts and posts through public timelines.
Is one row one action or one user?
One successful row is one unique user. The nested engagement fields preserve all collected actions for that user.
Can it collect Likes?
No. This Actor focuses on publicly enumerable Retweets, Quote Tweets, and Replies.
Can I analyze Tweets from accounts I do not own?
Yes, when the Tweet and its engagement are publicly available. You are responsible for using the data lawfully.
Related Actors
- X (Twitter) Retweeters & Quote Tweets Scraper — use when you want one row per Retweeter or Quote Tweet author without cross-Tweet audience aggregation.
- X (Twitter) Replies Scraper — use for deeper Reply and conversation analysis.
- X (Twitter) Post Performance & Growth Monitor — track how a Tweet's engagement metrics change over time.
Privacy, responsible use, and support
This Actor collects public X data. Do not use it for harassment, discrimination, unlawful surveillance, spam, or decisions that violate applicable law or X's terms. Review your legal basis, minimize retained personal data, and delete exports when they are no longer needed.
For help, open an Issue on the Actor page and include the Run ID, sanitized input, expected behavior, and relevant log excerpt. Never post credentials or private data in an Issue.
This independent Actor is not affiliated with, endorsed by, or sponsored by X Corp.