Publisher · 4 actors

datarelay on the Apify Store

datarelay publishes 4 actors on the Apify Store, used by 4 people in the last 30 days. Oldest actor is 19d old. Prices, reliability and maintenance below come from our daily census of the public store catalog.

Claim this publisherIs this your catalogue? Claiming is free, and its full history is yours forever.
Last 7 dayson this catalogue

…and 4 more changes this week. Follow datarelay — every change by email each morning

By monthly users#2,536newof 4,659 publishers · 4 users in 30 days
By catalogue size#2,149newof 4,659 publishers · 4 actors listed
By users all time#2,908newof 4,659 publishers · 8 users since they began
Needs a build0 of 44 fresh · 0 aging · stale = no build in 180 days
Carry half the users2 of 4top 3 hold 75% · 25% on the largest

Places are over the 4,659 publishers listed today; the week’s move is measured against the 4,122 also listed on 27 Oct, so nobody falls because the store grew around them.

What they build4 actors in the catalogue
Platforms targeted
Google1
Google Maps1
Google News1

1 of 4 target no particular site

Biggest actors, monthly users
google-trends-api25%
google-maps-api25%
google-news-api25%
google-trending-now25%

share of this publisher’s 4 monthly users

3platforms targeted
4.1 a monthnew actors, last 30 days
Oct 2026first actor still listed
1dsince their newest actor

datarelay spreads 4 actors across 3 platforms, most of all Google (1). They have created 4.1 a month over the last 30 days.

How this is counted

Platforms come from our own classification of each actor’s listing, and an actor can target several — so these counts overlap and add up to more than the catalogue. Dates are the store’s own creation timestamp for each actor, which means the chart shows the actors still listed today, grouped by when they were made: a publisher who built forty last year and has since removed thirty shows ten. Shares are of this publisher’s own monthly users, from the same daily census as the table below.

Monthly userssummed across this catalogue
4↑ 2over 7 readings
Runs / daymatched per actor
40↑ 22over 6 readings
Runs / 30drolling window, summed
13↑ 11over 7 readings
Actorsin the census that day
4↑ 2over 7 readings

Runs per day is each actor's own step in its lifetime run counter, added up over the actors present on both days — an actor joining this catalogue moves the actor count, never the runs line. Last 30 days; the full history is in the app.

Build activitylast 60 days
27builds published
5/60days with a build
100%of the catalogue touched in 30 days
Last touched
today2
2–7d2

datarelay published 27 builds on 5 of the last 60 days. Busiest was 31 Oct (9).

How this is counted

A build is counted from the store's own build counter, read once a day, so a cell is an exact count and an empty cell is a day nobody shipped. Shading runs against this catalogue's busiest day, so it compares days here — not catalogues. “Touched” is broader than a build: it is the last change the store saw of any kind, on a rolling re-fetch, so it can lag a build by days. Per-actor history is in the app.

Sort
#ActorGradePrice / 1kUsers /30dSuccessRatingAgeFresh
1—EVT$1.20 /1k term12 total——19dfresh
2—EVT$1.33 /1k place12 total——6dfresh
3—EVT$1.95 /1k article12 total——1dfresh
4—EVT$0.70 /1k trend12 total——19dfresh
4 actors, sorted by monthly users · * prices normalized per 1,000 units Open in search with filters →