It gives almost no information :(

Jun 6, 2016 at 6:44 PM
These three hashtag with

ObjetivoDebate26J : around 20.000 t'ws

PartidoDeVuelta : around 50.000 tw's

L6Nfamiliaiglesias : around 50.000 tw's

With NodeXL Pro:

ObjetivoDebate26J : around 2 pages. 250 tw's :(

PartidoDeVuelta : around 6 pages 850 tw's :(

L6Nfamiliaiglesias : around 4 pages 360 tw's :(

I have the pro version. What's the problem?

Best regards,
Jun 6, 2016 at 7:28 PM

Thanks for the interest in NodeXL!

TAGS and NodeXL use the same API calls so the results should be similar.

You may want to import the TAGS data into NodeXL if TAGS is collecting more data.


Twitter's public free API has many limits. Data is available only for 7-8 days. Queries cannot return more than 18,000 tweets.

The follower network is further restricted: the rate at which queries about who follows who can be asked is low.

The follower list is limited to the most recent 2,000 users.

NodeXL Pro does not enable the collection of data beyond these limits.

Twitter imposes many rate limits via its data API. NodeXL Basic and Pro are both effected by these limits.

That said, NodeXL can process data from commercial data providers (like Crimson Hexagon or Radian6). While these are expensive options, they may be the only way to get historical data from Twitter.

Please see:


Within the past 7 or 8 day time frame, you may be able to get a little bit more data from the public Twitter API by using the SINCE: and UNTIL: operators - example:

QUERYTERM since:2016-01-21 until:2016-01-27

Since: and Until: operators scope the time frame of the query.

Twitter controls its API and throttles it based on unknowable parameters. We notice that the more the volume of tweets == less tweets delivered.

One alternative is to do day long slices and append them in order to maximize the data available from Twitter.

You may also be interested in this: which enables NodeXL to connect to the "STREAM" API from Twitter (which sometimes delivers larger volumes of data).


Marked as answer by MarcSmith on 7/5/2016 at 7:06 PM