Hi there,

I'm just closing out some old threads. Thanks for the feature request.

We looked into this, and unfortunately, this is not something we're able to support. Here's why:

Our Twitter/X connector is built on the X Ads API, which X provides to advertising partners at no cost. The engagement user ID data you're looking for (the specific users who liked or retweeted a tweet) is only available through the X API v2, which is a separate, paid API. X's pricing for v2 starts at $200/month for Basic access (with very limited read capacity) and jumps to $5,000/month for Pro. Enterprise access runs $42,000+/month. Even at the Pro tier, the endpoints for fetching individual engager user IDs are heavily rate-limited to 75 requests per 15 minutes, with each response capped at 100 users.

Adopting X API v2 would introduce high ongoing costs that we'd need to pass on to all customers using the connector, which isn't practical given the narrow use case. The cost and rate limit constraints make it infeasible for us to offer reliable, production-grade syncing of per-tweet engagement user IDs.

We understand this is a blocker for your use case, and we're sorry we can't help here. If X changes their API pricing or makes these endpoints available through the Ads API in the future, we'd be happy to revisit.

Cheers,
Luke