Read Google Maps reviews as a corpus tied to the place that received them. Keep rating, text, author details, date fields, place identity, and source links together.
1
Users / 30d
28
Runs / 30d
—
Rating
Updated 1 Oct 2026
Apify builder
@reapx
Leaderboard position
out of 6,984
New Actors / 30d
#5628
Total Actors
#76
Active users / 30d
#298
Total users
#706
Runs / 30d
#484
Total runs
#221
Portfolio stats
New Actors / 30d
0
Total Actors
196
Active users / 30d
231
+31 since first snapshot
Total users
458
Runs / 30d
6K
+2.6K since first snapshot
Total runs
409.7K
Portfolio history
Daily publishing
0
Each bar represents one UTC day.
No new public Actors were detected during this 30-day window.
Actor portfolio
196 matching of 196 Actors · page 4 of 9
Read Google Maps reviews as a corpus tied to the place that received them. Keep rating, text, author details, date fields, place identity, and source links together.
1
Users / 30d
28
Runs / 30d
—
Rating
Compare app listings and publisher details from Google Play. Start with Google Play app URLs; each returned app keeps offers iap price range, app identifiers, titles, developer email, and developer address.
1
Users / 30d
29
Runs / 30d
Compare Google Play apps, publishers, and listing details. Start with Google Play URLs; each returned record keeps titles, rating value, rating count, prices, and app identifiers.
1
Users / 30d
28
Runs / 30d
Read Google Play reviews as a source-linked corpus. Start with Google Play review or listing URLs; each returned review keeps review identifiers, user names, text, publication dates, and replied at.
1
Users / 30d
28
Runs / 30d
Compare Google products, offers, and identifiers. Start with Google product URLs; each returned product keeps product identifiers, titles, prices, price value, and list price.
1
Users / 30d
28
Runs / 30d
Compare returned Google Search prices. Start with Google Search product or listing URLs; each returned price record keeps prices, price value, list price, list price value, and titles.
1
Users / 30d
27
Runs / 30d
Build a working file of Indeed roles and hiring signals. Start with Indeed URLs; each returned record keeps titles, authors, companies, other jobs at company, and company logo.
1
Users / 30d
28
Runs / 30d
Study Instagram ads across brands and campaigns. Start with Instagram ad URLs; each returned ad keeps advertiser, ad body text, titles, ad ID, and text.
1
Users / 30d
27
Runs / 30d
Keep Instagram accounts and published activity in one structured export. Review profiles, posts, captions, dates, and engagement in the same dataset.
1
Users / 30d
31
Runs / 30d
Collect Instagram media records with source details. Start with Instagram media file URLs; each returned media file keeps titles, authors, handles, descriptions, and publication dates.
1
Users / 30d
28
Runs / 30d
Map Instagram audiences for account research. Start with Instagram follower URLs; each returned follower keeps followers, names, handles, source handles, and user identifiers.
1
Users / 30d
28
Runs / 30d
Collect short-form video records from Instagram. Start with Instagram short-video URLs; each returned short video keeps titles, authors, handles, descriptions, and publication dates.
1
Users / 30d
29
Runs / 30d
Collect Instagram videos and their publishing signals. Start with Instagram video URLs; each returned video keeps titles, authors, video URL, publication dates, and view counts.
1
Users / 30d
29
Runs / 30d
Collect LinkedIn account records for company research. Start with LinkedIn account URLs; each returned account keeps titles, authors, companies, date, and descriptions.
1
Users / 30d
29
Runs / 30d
Study LinkedIn ads across brands and campaigns. Start with LinkedIn ad URLs; each returned ad keeps headlines, advertiser, ad identifiers, advertiser names, and advertiser bio.
1
Users / 30d
28
Runs / 30d
Keep LinkedIn job records with titles, companies, locations, descriptions, and source links. Start with LinkedIn URLs; each returned record keeps titles, authors, companies, date, and descriptions.
1
Users / 30d
28
Runs / 30d
Compare places and business listings from Maps. Start with Maps place URLs; each returned place keeps names, titles, place identifiers, addresses, and phone numbers.
1
Users / 30d
28
Runs / 30d
Read Maps reviews as a source-linked corpus. Start with Maps review or listing URLs; each returned review keeps review identifiers, ratings, text, author names, and relative date.
1
Users / 30d
28
Runs / 30d
Keep Mobile.de search results in rows you can compare. Start with Mobile.de searches or result URLs; each returned search result keeps titles, price amount, currencies, first registration, and fuel type.
1
Users / 30d
52
Runs / 30d
Read Naver reviews as a source-linked corpus. Start with Naver review or listing URLs; each returned review keeps visitor review count, total review count, review identifiers, review text, and visitor review score.
1
Users / 30d
28
Runs / 30d
Compare Pinterest profiles. Start with Pinterest profile URLs; each returned profile keeps handles, names, is private profile, instagram username, and audience size.
1
Users / 30d
28
Runs / 30d
Keep Pinterest search results in rows you can compare. Start with Pinterest searches or result URLs; each returned search result keeps titles, repin count, descriptions, position, and identifiers.
1
Users / 30d
29
Runs / 30d
Keep Quora questions and answers in a source-linked reading file. Preserve answer text, author context, dates, engagement signals, question identity, and source URL together.
1
Users / 30d
27
Runs / 30d
Keep Reddit communities, posts, and visible discussion records in one export. Preserve titles, authors, dates, scores, comment volume, community, and source links.
1
Users / 30d
28
Runs / 30d
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating