This will depend on the endpoint you are using, and the volume of interactions you are seeing.
-
statuses/sample is always just a 1% sampling of the main firehose. I assume you’re not using that one, as you’re talking about getting Tweets about a specific brand.
-
statuses/filter using e.g. the track parameter is also limited to an overall 1% volume cap. This means that if the term you are tracking is at a particularly high volume “spike” for some reasons, there’s a chance that you may miss some Tweets. However, in most cases this is not a practical limitation as the Tweet volumes on any topic do not often jump to a level where this is a problem.
If you absolutely require comprehensive coverage, then you’d want to use the commercial PowerTrack API in the future as your solution scales.
Lastly, just to point your attention to our recent announcement about the future deprecation of user and site streams. We expect the other sample / filter APIs to continue to be freely available, in a more robust form, in the future. We’ll be making more streaming data available at new commercial tiers along the road as well.
