Connect X / Twitter Public Data to Power BI

Create an X developer application with access to the required endpoints and connect Catchr using its Bearer Token and monitored usernames. In Catchr’s Power BI query builder, select a small sample of recent posts and public counters and preview a short extraction. Import the generated URL through Get data > Web in Power BI Desktop. Check the returned rows before building measures, keeping post IDs, extraction coverage and observation time clear in the model.

You can request supported public account and post data where your X API access allows it. This does not grant access to protected posts, private messages, or account-owner analytics. Availability also depends on the endpoint access and limits attached to your developer application. Test the target usernames and required fields before building a competitor dashboard, rather than assuming everything visible in the X interface is available through the connection.

The catalog includes post likes, reposts, replies, quotes, bookmarks, and impressions where returned, plus profile follower, following, listed, and post counts. Post dimensions include ID, text, language, author, and creation date. A field in the catalog may be unavailable for a particular post or access level. The source does not expose private URL-click or profile-click analytics, advertising spend, or conversion reporting.

The date range selects posts by creation time. The public counters are the values returned for those posts when retrieved, not a dated log of each like, reply, or repost. A report of posts published last month can therefore change as those posts accumulate engagement. Label charts by the publication period and avoid describing their totals as interactions that happened exclusively within those dates.

Catchr uses the user-post timeline endpoint, which X documents as covering up to the 3,200 most recent posts. Your application's access and usage limits can further affect the results. Older dates do not turn this endpoint into a full archive, especially for accounts that publish frequently. Check the oldest post returned and the actual post count before making long-term comparisons, and retain dated exports when you need a reporting history.

Follower count is a current profile snapshot, so historical growth requires saved snapshots rather than a different dashboard date filter. For post comparisons, define the actions included in your engagement calculation and show the sample size. A follower-based rate uses the current account size; it is not a unique-reach rate. If you use impressions as a denominator, check availability and keep missing values distinct from zero.

Yes. Add the separate X Ads source for advertising metrics and keep the two datasets clearly labeled. Public post totals should not automatically be treated as organic-only delivery or added to paid metrics, because promoted activity may overlap with public counters. Match posts by stable IDs where applicable and compare dates and measurement definitions before building a combined performance report.