​

Tracking Issues

​

Understanding Tracking

​

Tracking Fundamentals

1. How Tracking Works
   • Click registration process and ClickKey generation
   • Cookie placement and storage mechanisms
   • Conversion attribution methods and timing
   • Data flow from click to commission processing
   For detailed implementation guidance, see How Attribution Works for operators or How Tracking Links Work for affiliates.
2. Tracking Components
   • Affiliate tracking links - Generated from trackers and contain ClickKeys
   • Conversion tracking pixels - Fire on purchase completion
   • JavaScript tracking codes - Handle ClickKey capture and storage
   • Server-to-server postbacks - Send transaction data to Affelios
   Understanding tracker-based link generation is crucial for troubleshooting. See How Tracking Links Work for the complete process.
3. Attribution Models
   • First-click attribution - Credit goes to the first affiliate link clicked
   • Last-click attribution - Credit goes to the most recent affiliate link
   • Custom attribution rules - Program-specific attribution logic
   For detailed attribution configuration and commission plan setup, see How Attribution Works.

​

Common Tracking Challenges

1. Technical Limitations
   • Browser privacy settings
   • Ad blocker interference
   • Cross-device tracking
   • Mobile app attribution
2. Implementation Issues
   • Incorrect code placement
   • Missing tracking parameters
   • Timing synchronization problems
   • Environment configuration errors

​

Click Tracking Issues

​

Missing Clicks

1. Link Structure Problems
   • Symptoms: No clicks registered despite traffic
   • Causes: Malformed tracking URLs, missing parameters, incorrect tracker configuration
   • Solutions: Validate link structure, verify tracker setup, create new tracker if needed
   • Prevention: Use proper tracker setup, validate before deployment
   For proper link generation and structure, see How Tracking Links Work. For ClickKey parameter implementation, see How Attribution Works.
2. JavaScript Errors
   • Symptoms: Intermittent click tracking failures
   • Causes: JavaScript conflicts, loading sequence issues
   • Solutions: Debug JavaScript console, optimize loading order
   • Prevention: Test across browsers, use asynchronous loading
3. Redirect Issues
   • Symptoms: Clicks not reaching destination
   • Causes: Redirect chain problems, caching issues
   • Solutions: Minimize redirect chains, clear cache
   • Prevention: Direct linking when possible, monitor redirect paths

​

Inaccurate Click Counts

1. Double Counting
   • Symptoms: Inflated click numbers
   • Causes: Multiple tracking implementations, refresh issues
   • Solutions: Deduplicate tracking codes, implement click validation
   • Prevention: Centralized tracking implementation, unique session handling
2. Bot Traffic
   • Symptoms: High clicks with low conversions
   • Causes: Automated bot clicking, click farms
   • Solutions: Implement bot detection, filter suspicious traffic
   • Prevention: Real-time validation, behavioral analysis
3. Cross-Domain Issues
   • Symptoms: Lost tracking across domains
   • Causes: Cookie domain restrictions, referrer policy changes
   • Solutions: Implement cross-domain tracking, use server-side solutions
   • Prevention: Unified tracking domain, proper cookie configuration

​

Conversion Tracking Issues

​

Missing Conversions

1. Pixel Implementation Problems
   • Symptoms: Conversions not recorded
   • Causes: Missing conversion pixels, incorrect placement, ClickKey not properly stored
   • Solutions: Verify pixel implementation, test firing conditions, check ClickKey storage
   • Prevention: Thorough testing, implementation validation
   For proper ClickKey storage implementation, see How Attribution Works. For testing procedures, see How Attribution Works.
2. Attribution Window Issues
   • Symptoms: Conversions attributed incorrectly or not at all
   • Causes: Expired cookies, incorrect attribution windows, ClickKey storage failures
   • Solutions: Adjust attribution settings, verify cookie duration, implement multiple storage methods
   • Prevention: Appropriate window configuration, clear communication, robust storage implementation
   The attribution flow from ClickKey capture to commission processing is detailed in How Attribution Works.
3. Cross-Device Attribution
   • Symptoms: Mobile clicks not attributed to desktop conversions
   • Causes: Cookie isolation between devices
   • Solutions: Implement user ID tracking, use deterministic matching
   • Prevention: Email-based attribution, login-based tracking

​

Duplicate Conversions

1. Multiple Firing Events
   • Symptoms: Same conversion recorded multiple times
   • Causes: Pixel firing on page refresh, multiple pixel implementations, missing transaction IDs
   • Solutions: Implement conversion deduplication, session-based tracking, use unique transaction IDs
   • Prevention: Unique conversion identifiers, proper pixel placement, transaction ID implementation
   Transaction ID Best Practice: Integrations should pass a unique transaction ID from the operator’s internal systems to ensure idempotency. This prevents duplicate conversions when the same transaction is reported multiple times due to network issues, retries, or system failures.For implementation details, see How Attribution Works.
2. Testing Environment Pollution
   • Symptoms: Test conversions in production data
   • Causes: Development testing on production systems, missing transaction ID validation
   • Solutions: Filter test transactions, separate environments, validate transaction IDs
   • Prevention: Dedicated testing environments, proper data segregation, transaction ID validation

​

Mobile Tracking Challenges

​

App-to-Web Attribution

1. Deep Link Issues
   • Symptoms: Lost attribution from app to website
   • Causes: Deep link configuration problems, app store attribution, platform privacy restrictions
   • Solutions: Proper deep link setup, universal link implementation
   • Prevention: Comprehensive testing, platform-specific optimization
   Platform Privacy Impact: Apple’s App Tracking Transparency (ATT) and Android’s Privacy Sandbox have significantly limited cross-platform tracking capabilities. Traditional web-to-app attribution methods are no longer reliable.
2. Mobile Browser Limitations
   • Symptoms: Inconsistent tracking on mobile browsers
   • Causes: Safari ITP, Chrome SameSite restrictions, iOS 14.5+ ATT framework
   • Solutions: Server-side tracking, first-party data collection
   • Prevention: Mobile-first tracking strategy, regular testing
   Current Affelios Mobile Support: Mobile tracking in Affelios is currently optimized for in-house analytics, such as monitoring customer registration patterns across different platforms, rather than full cross-platform attribution.
3. Cross-App Tracking
   • Symptoms: Attribution lost between mobile apps
   • Causes: App sandboxing, privacy restrictions, platform privacy frameworks
   • Solutions: SDK implementation, unified ID solutions (limited effectiveness)
   • Prevention: Platform-native attribution, compliance with guidelines
   Privacy Framework Impact: Both Apple’s ATT and Android’s Privacy Sandbox have created significant barriers to cross-app tracking, making traditional attribution methods unreliable for mobile-to-web conversions.Implementation Complexity: Cross-app tracking requires significant technical expertise and direct integration within each mobile application, including custom SDK development, attribution logic implementation, and compliance with platform-specific privacy requirements.

​

Privacy and Compliance Impact

​

Cookie Restrictions

1. Third-Party Cookie Blocking
   • Symptoms: Reduced tracking accuracy
   • Causes: Browser privacy updates, user privacy settings
   • Solutions: First-party cookie implementation, server-side tracking
   • Prevention: Privacy-compliant tracking methods, user consent management
2. GDPR and Privacy Laws
   • Symptoms: Tracking consent issues
   • Causes: Legal compliance requirements, user opt-outs
   • Solutions: Consent management platforms, privacy-compliant tracking
   • Prevention: Legal review, privacy-by-design implementation
3. Ad Blocker Impact
   • Symptoms: Tracking scripts blocked
   • Causes: Ad blocker software, privacy-focused browsers
   • Solutions: Server-side tracking, native integration methods
   • Prevention: Non-intrusive tracking methods, user education

​

Diagnostic Tools and Techniques

​

Browser-Based Debugging

1. Developer Console
   • Network tab analysis for tracking calls and ClickKey transmission
   • Console error identification
   • Cookie and storage inspection (check ClickKey storage)
   • JavaScript debugging tools
   For comprehensive testing procedures including ClickKey validation, see How Attribution Works.
2. Browser Extensions
   • Tracking pixel validators
   • Cookie inspection tools (verify ClickKey cookies)
   • Network request analyzers
   • Attribution testing tools
3. Testing Procedures
   • Incognito/private browsing tests
   • Cross-browser validation
   • Mobile device testing
   • Different network condition tests
   • ClickKey capture and storage validation
   For detailed tracker testing procedures, see How Tracking Links Work.

​

Server-Side Diagnostics

1. Log Analysis
   • Server log examination
   • Request pattern analysis
   • Error rate monitoring
   • Performance metrics review
2. API Testing
   • Webhook delivery verification
   • Postback URL testing
   • API response validation
   • Data synchronization checks
3. Database Queries
   • Raw data examination
   • Attribution chain verification
   • Duplicate detection queries
   • Performance impact analysis

​

Resolution Strategies

​

Quick Fixes

1. Common Solutions
   • Clear browser cache and cookies
   • Create new tracker or verify existing tracker setup
   • Update tracking code placement
   • Verify account settings
   • Check ClickKey parameter configuration
   For step-by-step tracker creation and link generation, see How Tracking Links Work.
2. Testing Protocols
   • End-to-end tracking tests
   • Cross-device verification
   • Multi-browser validation
   • Performance impact assessment
   • ClickKey capture and storage validation
   Comprehensive testing procedures are outlined in How Attribution Works and How Tracking Links Work.

​

Advanced Solutions

1. Technical Implementations
   • Server-side tracking setup
   • First-party data collection
   • Advanced attribution modeling
   • Custom tracking solutions
   • ClickKey storage optimization
   For detailed technical implementation guidance, see How Attribution Works and How Attribution Works.
2. Process Improvements
   • Automated testing implementation
   • Monitoring and alerting systems
   • Regular audit procedures
   • Documentation and training
   • Tracker performance optimization
   Learn about tracker-based optimization strategies in How Tracking Links Work.

​

Prevention and Best Practices

​

Implementation Best Practices

1. Code Standards
   • Consistent implementation patterns
   • Error handling procedures
   • Performance optimization
   • Security considerations
2. Testing Protocols
   • Pre-deployment testing
   • Continuous monitoring
   • Regular validation procedures
   • Performance benchmarking

​

Monitoring and Maintenance

1. Proactive Monitoring
   • Real-time tracking validation
   • Automated alert systems
   • Performance trend analysis
   • Issue prediction models
2. Regular Maintenance
   • Code updates and patches
   • Configuration reviews
   • Performance optimization
   • Compliance verification
   • Tracker performance audits

​

Related Documentation