A practical guide for regular Datadredge users
This guide covers the normal account workflow: creating sites, adding the tracking script, reading the dashboard, sharing a public link, and keeping your site list organized.
What this page is for
Use this as a quick reference when you are setting up a site for the first time or returning later to check metrics, edit settings, or share read-only access.
Getting started
Datadredge is centered around sites. Each site gets its own dashboard, tracking code, visitor metrics, event metrics, and optional public share link.
1. Sign in
Use your normal account and go to My Sites in the header.
2. Create a site
Add the site name and domain you want to track. You can return later and edit both.
3. Add tracking code
Copy the generated script snippet and place it on the site you want to measure.
4. Review data
Open the site dashboard to check visits, pages, events, countries, and trends.
Add your first site
Name: this is the label you will see in the site list and dropdown.
Domain: use the main site domain you expect traffic on.
Shared public URL: turn this on only if you want a read-only share link for other people.
After the site is created you can open it from My Sites, copy the tracking code, review the details page, and later edit the site settings if the domain or name changes.
Install tracking code
Open a site and use Get Tracking Code or Copy code. Datadredge provides the snippet tied to that specific site.
Add the script to the site you want to measure, usually in the shared page layout or template.
If the layout loads on every page, Datadredge can track visits consistently across the site.
Visit the tracked site yourself, then return to the dashboard and refresh after a short delay. You should start to see visits, page views, or other activity appear.
Yes. Datadredge can accept event tracking from external clients such as desktop apps, mobile apps, kiosk software,
or Unity projects. These clients do not use the website embed script. Instead, they send JSON directly to
POST /api/send.
For external apps you will usually send type = "event" with a clear event name such as
play-button-click or level-complete. The site's websiteId is still required.
{
"version": "1.0",
"payload": {
"websiteId": "YOUR-SITE-GUID",
"type": "event",
"name": "play-button-click",
"visitorId": "device-or-user-id",
"sessionId": "session-id",
"timestampUtc": "2026-03-09T18:00:00Z",
"data": {
"platform": "unity",
"screen": "main-menu"
}
}
}
For native apps, choose your own stable visitorId and session strategy. You can also send an
eventId when you want deduplication on retries.
Keep in mind that browser-specific fields like page URL, referrer, browser, and operating system are mainly intended for websites. External apps can still track custom events successfully, but some web-oriented breakdowns may be empty or less detailed.
Read the dashboard
Visitors and visits
Use these to understand how many distinct browsing sessions and repeat returns you are seeing over time.
Page views
Good for spotting which pages are getting attention and whether traffic is rising or falling.
Countries and referrers
Use these to understand where traffic is coming from and which channels or regions matter most.
Events
If your site sends events, this area helps you monitor feature usage and key actions.
Manage your sites
- Use the header dropdown to jump between sites without returning to the full site list.
- Use My Sites when you want the full table view with search, sorting, and paging.
- Edit a site if the name, domain, or sharing settings need to change.
- Open the details page when you need the tracking code again or want to confirm the configuration.
Common questions
Check that the script is installed on the live site, open the site yourself, then refresh the dashboard. Also confirm that you copied the code for the correct Datadredge site.
Yes. Each site has its own settings, tracking code, and reporting, and you can move between them from the site dropdown.