Myourplatform.com/maya7 on the page now
Profile views, last 30 days
11,670▲ 38%
How it works
Set up once for the whole platform
There is nothing to create for each user. Their stats start with the first visit to their page.
Add the user's ID to your page template.
The script takes the ID of the profile, store, or site on that page, such as
p_1042.We count each visit.
Page views and clicks on outbound links count for that ID within seconds. Pages without an ID count for your platform only.
Your server reads the numbers.
Ask the stats API for one ID and one period. Show the answer on your user's stats page.
What your users see
Profile views, link clicks, and where visitors come from
Each user gets visitors, page views, clicks on each link, sources, countries, and devices. Every number comes with the period before, so you can show what went up.
You build the page, so it looks like the rest of your app. Your users never see our name.
Your team gets the whole platform in the DataDad dashboard, with totals and every user ranked by visitors.
Included
What you do not have to build
A visit counter in your own database is quick to add. Unique visitors, sources, bot filtering, and fast queries on a large platform take much more work.
Unique visitors without cookies
The script sets no cookies. We tell visitors apart with an ID that changes every day.
Bots filtered out
We drop requests from known bots and crawlers before they count.
Clicks per link
We count clicks on outbound links, per link. A named link keeps its count when its address changes.
Sources, countries, and devices
We read the referrer, campaign tags, country, browser, and device of each visit. We do not store IP addresses.
Fast for small profiles
We store visits sorted by user, so a question about one small profile does not scan your whole platform.
Numbers never mix
Each request names one user, and the key stays on your server. A user's page shows only their visits.
Who it is for
Platforms where every user has a page
If your users share a link to a page you host, they will ask how many people opened it.
- Link-in-bio pages
- Website and store builders
- Portfolios and creator pages
- Marketplaces with seller pages
- Newsletter and blog platforms
- Course and event pages
FAQ
Questions about Analytics for Platforms
What is a tenant?
A tenant is one of your users' pages, such as a profile, a store, or a site. You choose its ID. DataDad counts the visits of each tenant on its own and returns them when you ask for that ID.
Do I create a project or an account for each user?
No. Your platform is one project with one script. A tenant starts with the first page view that carries its ID, so your sign-up flow does not change.
How do my users see their numbers?
Your server calls the stats API with the user's tenant ID and shows the answer on your own page, in your own design. Your users never see the DataDad name.
Can users of my platform see each other's statistics?
Not through DataDad. The API key stays on your server, and each request names one tenant. Your server checks that the signed-in user owns the page before it asks.
Which numbers does the API give for a tenant?
Visitors, page views, visits, bounce rate, visit duration, and link clicks, with the previous period. It also gives the top pages, sources, countries, devices, campaigns, and links, and points for a chart.
Do visitors need to accept cookies?
The default script sets no analytics identity cookies. Your setup and local rules determine whether consent is required. How cookieless analytics works.
Also in DataDad