Clear numbers
Clicks, QR scans, and Bio Page views stay separate and use a visible date range.
Link analytics
Understand attention without slowing down the click.
See when people click or scan, which devices they use, where traffic comes from, and which campaign earns attention. Reporting runs in the background so it does not hold up the visitor.
Open analyticsUseful dimensions
Explore broad geography, device, browser, and referrer without exposing raw visitor identifiers.
Honest timing
The dashboard shows the reporting period and makes normal processing delays clear.
Every metric should keep the same meaning
A click, QR scan, and Bio Page view are different actions. Gods.ly records the link, workspace, action type, and time so dashboards and exports use consistent definitions.
Activity is recorded after the visitor is sent onward, keeping the redirect fast.
Privacy is built into reporting
Gods.ly reduces referrers to their host and avoids exposing raw visitor identifiers in customer reports. Historical data is moved into the same privacy-reduced format.
Retention rules apply to the reports people can access instead of leaving a hidden full-detail export behind.
Campaigns connect the context
Campaign and channel records group multiple routes without rewriting their destinations. Teams can compare distribution channels while keeping each public asset independently manageable.
A zero state clearly distinguishes no traffic from a temporarily unavailable report.
Common questions
What teams ask before they start.
Does analytics make redirects slower?
No. Gods.ly sends the visitor to the destination and records the event in the background.
Does the dashboard expose raw visitor IP addresses?
No. Customer reports use privacy-reduced information rather than displaying raw visitor IP addresses.
Start with a real workflow