Skip to main content

Torai V3 Is Now Available

· 4 min read
Torai Support
Torai Operations Team

What is Torai V3?

Torai V3 automates the collection of engagement data on X.

Engagement screen

Engagement data collected automatically by Torai

Torai's analytics support has two main components. Most of the cost comes from retrieving users who engaged with your posts. Post analytics alone are relatively inexpensive, but retrieving information about the users who liked a post increases the cost in proportion to the number of user records returned.

Data collected

FeatureData collected
Post analyticsYour post text, posting date and time, impressions, engagement count, likes, replies, reposts, quotes, bookmarks, profile clicks, and URL clicks
Engaged-user retrievalNames and usernames of users who liked a post, users who mentioned or replied to you, and the related post
CRM and response inboxStage, tags, notes, and response status for retrieved users

With the current live-data implementation, Torai primarily saves likes and replies as engagement records. Quotes, reposts, and follows are not currently included in automatic collection.

Private metrics such as impressions and clicks are displayed only when they are available through the X API.

Tracking period and limits

You can configure the following collection settings:

  • Tracking period: 1, 7, 14, or 30 days
  • Posts per account: 1–100
  • Engaged users per post: 1–100
  • Standard settings: 7 days, 10 posts, and 25 engaged users
  • Collection frequency: Once per day
  • Additional collection when you select Refresh now

A 30-day tracking period does not mean that Torai retrieves every post without a limit each day.

For example, with a setting of 30 days and 10 posts, Torai retrieves up to the 10 most recent posts published within the last 30 days. Even if you publish 50 posts per day, Torai will not retrieve 1,500 posts on day 30.

Storage limits are as follows:

  • Engaged-user records: Up to 2,000
  • Post-analytics records: Up to 2,000
  • Daily snapshots: Up to 20,000, covering approximately 32 days
  • Records returned to the browser: Up to 1,000

Daily post trends are recorded from the day you enable post analytics. Torai does not retroactively reconstruct trends for the previous seven days.

Estimated costs shown in Torai

Torai currently uses the following unit prices for estimates:

  • Your own posts and mentions: $0.001 per record
  • User information: $0.01 per record

These estimates are based on X's official pay-per-use pricing. However, the credit usage and charges shown in the X Developer Console are authoritative. X generally reduces duplicate charges when the same resource is retrieved more than once on the same UTC day. As a result, Torai's estimate may be higher than the actual charge. See the official X API pricing.

The following examples assume one account, one collection per day, and 30 days of use.

UsagePer day30 days
Post analytics only, 10 postsApprox. $0.02Approx. $0.60
10 posts, averaging 5 engaged users per postApprox. $0.52Approx. $15.60
10 posts, up to 25 engaged users per postUp to approx. $2.52Up to approx. $75.60
Above, plus 10 replies and 10 replying usersUp to approx. $2.63Up to approx. $78.90

For multiple accounts, costs generally increase in proportion to the number of accounts. For example, using post analytics only for three accounts produces a Torai estimate of approximately $1.80 per month.

Actual costs may be lower than the table when the maximum number of posts or engaged users does not exist, or when X applies same-day deduplication. Failed requests are generally not counted as usage. See X API usage and billing.

Costs not included in the estimate

The Estimated cost this month figure includes only the data-retrieval costs generated by X Marketing. It does not include:

  • Costs associated with automatic posting to X
  • Gemini costs for AI-generated reply suggestions or text generation
  • The Torai subscription fee
  • Google Apps Script or Google Drive usage
  • Other X API features

We recommend starting with the following conservative settings:

  • Post analytics: ON
  • Engaged-user retrieval: OFF
  • Tracking period: 7 days
  • Number of posts: 10
  • Monthly limit: $5–$10

Enable engaged-user retrieval only when you need to identify the people who reacted to your posts, and begin with a low engaged-user limit. Retrieving user information for people who liked your posts accounts for most of the cost.

Torai's monthly limit is an estimated threshold used to stop retrieval. It is not a strict billing cap enforced by X. To reliably prevent unexpected costs, also configure a spending limit in the X Developer Console.