At Pinkk, we believe in transparency. This page explains how our platform measures, calculates, and presents analytics data. We're honest about what we can and cannot verify, and we want you to understand the methods and limitations behind the numbers you see.

Our goal is to provide useful insights while being clear about the probabilistic nature of web analytics and the technical constraints we work within.

System-Verified Reports

What this means and what it doesn't

When you see a report marked as "system-verified," it means the data is generated automatically from our tracking systems and cannot be edited or altered by creators or users.

What System-Verified Means

• Data is pulled directly from our database
• Reports are generated automatically by our system
• No manual editing or manipulation is possible
• Timestamps and metrics are tamper-proof

What It Does NOT Mean

• It does NOT verify that all traffic is from real humans
• It does NOT guarantee traffic quality or authenticity
• It does NOT prevent bots or fraudulent clicks from being recorded
• It only verifies that the report itself hasn't been tampered with

Think of it like a sealed envelope: we verify the envelope hasn't been opened, but we can't verify the authenticity of what's inside without additional analysis.

Traffic Quality & Human-Likely Traffic

Probabilistic estimates, not guarantees

When we show percentages like "85% human-likely traffic," these are confidence-based estimates, not absolute certainties. We analyze multiple signals to make educated guesses about traffic authenticity.

Signals We Analyze

Behavioral Signals

• Mouse movement patterns
• Scroll behavior
• Time on page
• Click patterns
• Session duration

Technical Signals

• User agent analysis
• Browser fingerprinting
• IP reputation checks
• Request timing patterns
• JavaScript execution

Important Limitations

• Not 100% accurate: Bot detection is heuristic-based and constantly evolving
• False positives/negatives: Some bots may appear human, some humans may be flagged
• Sophisticated bots: Advanced bots can mimic human behavior patterns
• Privacy tools: VPNs, privacy browsers, and ad blockers can affect detection

We continuously improve our detection algorithms, but no system is perfect. Treat these percentages as useful indicators, not absolute truth.

Revenue Estimators

Benchmarks and estimates, not guarantees

Revenue estimates shown in Pinkk are benchmarks based on industry averages and platform data. They are NOT guarantees of actual earnings and should be used for planning purposes only.

How We Calculate Estimates

• Platform averages: Aggregated data from similar creators and niches
• Traffic quality: Adjusted based on human-likely traffic percentage
• Geographic data: CPM rates vary significantly by country/region
• Engagement metrics: Click-through rates, time on page, bounce rates
• Historical trends: Seasonal variations and market conditions

Factors That Affect Actual Revenue

• Ad blocker usage
• Advertiser demand
• Content category
• Audience demographics

• Seasonal fluctuations
• Market competition
• Ad placement quality
• User engagement levels

Not a Guarantee

Revenue estimates are projections based on historical data and averages. Your actual earnings may be significantly higher or lower depending on numerous factors beyond our control. Do not make financial decisions based solely on these estimates.

Email Tracking Limitations

Privacy settings and technical constraints

Email open and click tracking is subject to significant technical limitations due to privacy features in modern email clients and user settings.

Why Email Tracking Is Imperfect

• Image blocking: Many email clients block tracking pixels by default
• Privacy protection: Apple Mail Privacy Protection pre-loads images, making opens unreliable
• Link scanning: Security tools may click links before users see them
• Preview panes: Some clients trigger "opens" without user interaction
• Plain text emails: Cannot track opens in text-only email clients

What This Means for Your Data

• Opens may be over-reported: Automated systems can trigger false opens
• Opens may be under-reported: Privacy features prevent tracking real opens
• Click tracking is more reliable: But still subject to security scanning
• Trends matter more than absolutes: Use data to compare campaigns, not measure exact engagement

We respect user privacy and comply with email tracking regulations. Our tracking methods are industry-standard, but they're inherently limited by design.

How We Collect Data

Transparent tracking methods

Understanding how we collect data helps you interpret the analytics we provide.

Server-Side Tracking

When someone clicks your Pinkk link, our servers log the request before redirecting.

• Most reliable method - works even with JavaScript disabled
• Captures: IP address, user agent, referrer, timestamp
• Cannot be blocked by ad blockers or privacy tools

Client-Side Tracking (JavaScript)

For enhanced analytics, we use JavaScript to track additional interactions.

• Captures: scroll depth, time on page, mouse movement, device details
• Can be blocked by privacy tools or disabled JavaScript
• Provides richer behavioral data for quality analysis

Cookie-Based Session Tracking

We use cookies to identify returning visitors and track sessions.

• Helps distinguish unique visitors from total clicks
• Subject to cookie consent laws and browser restrictions
• Users can delete cookies or block them entirely

Our Commitment to Transparency

What you can expect from Pinkk

We Will Always

Be honest about data limitations
Clearly label estimates vs. verified data
Explain our methodologies openly
Improve our algorithms continuously
Respect user privacy and comply with regulations

We Will Never

Claim 100% accuracy on probabilistic data
Guarantee revenue or traffic quality
Hide limitations or technical constraints
Inflate numbers to make data look better
Misrepresent what "verified" means

Bottom line: We provide the best analytics we can with current technology, but we're honest about the inherent limitations of web tracking and bot detection. Use our data as a useful tool for insights and trends, not as absolute truth. If you have questions about how specific metrics are calculated, contact our support team.

Frequently Asked Questions

Can I trust the numbers I see in my dashboard?

Yes, but with context. The raw click counts and timestamps are accurate records of requests to our servers. Quality metrics (like human-likely percentages) and revenue estimates are probabilistic and should be used as indicators, not guarantees.

Why do my numbers differ from other analytics platforms?

Different platforms use different tracking methods, bot detection algorithms, and counting methodologies. Server-side tracking (like Pinkk) typically shows higher numbers than client-side tracking (like Google Analytics) because we capture requests that JavaScript-based tools miss.

How accurate is your bot detection?

Our bot detection is continuously improving but not perfect. We use multiple signals and heuristics to estimate traffic quality. Sophisticated bots can evade detection, and legitimate users with privacy tools may be incorrectly flagged. Treat percentages as confidence levels, not certainties.

Do you sell or share my analytics data?

No. Your individual analytics data is private and never sold to third parties. We may use aggregated, anonymized data to improve our platform and calculate industry benchmarks, but your specific traffic data remains confidential.

How Pinkk Measures Data