🐺 Tripadvisor Reviews Scraper | Pay Per Result $0.5/1K reviews
Pay $0.50 for 1,000 reviews
🐺 Tripadvisor Reviews Scraper | Pay Per Result $0.5/1K reviews
Pay $0.50 for 1,000 reviews
The Wolves proudly presents TripAdvisor Review Scraper, the perfect solution for TripAdvisor review extraction. Incredibly, it retrieves 100-200 reviews per second at an amazing cost-effective rate of $0.50 per 1000 reviews. Get any data from TripAdvisor by targeting. Cheapest!!
The WolvesActor Metrics
47 Monthly users
No reviews yet
13 bookmarks
97% runs succeeded
9.7 hours response time
Created in Apr 2024
Modified 14 hours ago
The maximum number of reviews per input does not work as expected.
This parameter is applied to all inputs collectively and seems equivalent to the one found in "Run Options > Maximum charged results". Anyway, its behavior is quite different from what is found in other Apify scrapers and does not seem matching what is stated in the instructions. Can you please clarify the semantics of this parameter? It would be nice if it worked as a limit on a single input. Thanks. Mauro
Hello,
The behavior of this parameter is the same as maximum charged results, we will fix the documentation thanks a lot for letting us know!
If you want to control per item, our suggestion is to create separate runs for each of them.
Cheers
humatics
Thanks for the quick reply. Yes, I understand it can be automated using one instance per item but for few thousands locations the GUI is appropriate if it worked as expected. I would be much happier if the GUI was fixed and not the documentation, but that's your choice.
Hello,
It is actually working as expected, the only thing is the wrong field in the documentation which we will fix as soon as possible. We always encourage people to use the actors via API. If you do this programmatically via API, I think it will be an easy job to create those runs separately.
Let me know if you have any more questions!
Best
humatics
I know, keeping documentation and software aligned is always a headache. I also understand that you don't want to change the semantics of the field to not break compatibility with existing workflows. However, you could add a new field and this could be more similar to what happens with other Apify actors (well known UI design principle of least surprise). In the end, the first "conventional" field in Apify GUI is start URL(s!) that accepts many URLs at once, I doubt you'll change it. Any user trying your actor would expect a field to limit the maximum number of reviews per URL: you can't escape this logic. The field works as expected from the developer point of view, not for an Apify user. Thanks for your concern. Mauro.
Hello,
Unfortunately our actor doesn't have this feature, it is on our roadmap but we don't have any ETA for it.
All actors have different features and different plans and we mainly focus being fast and cheap. Since there is a workaround for this (executing several runs), it is not prioritized yet. Also our actor's structure is not suitable for this right now.
I will keep you posted when we have this feature, in the meantime feel free to use other actors if they are more suitable for your needs.
Best
