Advanced task settings unlock the full power of our tracking service, allowing you to handle complex scenarios like JavaScript-heavy sites, authentication requirements, custom headers, and sophisticated bot detection systems. This comprehensive guide covers all advanced configuration options to maximize your tracking success rate.
🚀 Advanced Settings Power
Master these settings to track any website successfully - from simple static pages to complex JavaScript applications with anti-bot protection, authentication, and dynamic content loading.
Render Levels: Choosing the Right Engine
Render level determines how your target website is processed and affects both accuracy and token costs:
No Rendering (HTTP Only)
- Cost: Lowest token usage (base cost only)
- Speed: Fastest processing time
- Use Case: Static content, APIs, simple HTML pages
- Limitations: No JavaScript execution, no dynamic content
- Best For: RSS feeds, price APIs, server-side rendered content
Server Rendering
- Cost: Moderate token usage (+8 tokens)
- Speed: Medium processing time
- Use Case: Sites with minimal JavaScript requirements
- Features: Basic JavaScript execution, simple DOM manipulation
- Best For: WordPress sites, basic e-commerce platforms
Advanced Browser Rendering
- Cost: Highest token usage (+15 tokens)
- Speed: Slower processing (full browser simulation)
- Use Case: Complex JavaScript applications, SPAs, React/Vue apps
- Features: Full browser environment, advanced JavaScript support
- Best For: Modern web apps, AJAX-loaded content, complex interactions
💡 Render Level Selection Guide
- Start with "No Rendering" and upgrade only if content is missing
- Use "Server Rendering" for sites that load content via simple JavaScript
- Choose "Advanced Browser Rendering" for single-page applications and complex sites
- Monitor task success rates to validate your choice
Custom Request Methods
Control how HTTP requests are made to your target websites:
GET Requests (Default)
- Use Case: Standard web page retrieval
- Browser Compatibility: Works with all render levels
- Caching: Can be cached by servers and CDNs
- Best For: Public pages, product listings, news content
POST Requests
- Use Case: Form submissions, API endpoints
- Limitations: Not compatible with browser rendering
- Body Support: Can include request body data
- Best For: Search results, form-based content, API monitoring
Other Methods (PUT, DELETE, PATCH)
- Use Case: API endpoint monitoring
- Requirements: HTTP-only mode (no browser rendering)
- Authentication: Often require custom headers
- Best For: RESTful API monitoring, webhook testing
⚠️ Method Compatibility Rules
- Browser rendering only supports GET methods - other methods automatically switch to HTTP mode
- Request body data is ignored when using browser rendering
- POST/PUT/PATCH methods are ideal for API endpoint monitoring
- Authentication headers work with any request method
Custom Headers Configuration
Add custom HTTP headers to authenticate, customize requests, or bypass restrictions:
Authentication Headers
Authorization: Bearer your-jwt-token-here
API-Key: your-api-key-here
X-API-Token: custom-token-format
User-Agent Customization
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
User-Agent: YourBot/1.0 ([email protected])
User-Agent: Mobile Browser Simulation String
Content Type and Accept Headers
Accept: application/json, text/plain, */*
Content-Type: application/json
Accept-Language: en-US,en;q=0.9
Accept-Encoding: gzip, deflate, br
Anti-Bot Bypass Headers
X-Forwarded-For: 203.0.113.1
X-Real-IP: 203.0.113.1
Referer: https://google.com/
Cache-Control: no-cache
Request Body Configuration
Send data in the request body for POST, PUT, and PATCH requests:
JSON Data
{
"query": "search term",
"filters": {
"category": "electronics",
"price_max": 500
},
"page": 1
}
Form Data
username=testuser&password=testpass&action=login
search_term=laptop&category=computers&sort=price_asc
XML Data
<?xml version="1.0" encoding="UTF-8"?>
<request>
<action>search</action>
<query>product name</query>
</request>
Cookie Management
Manage session cookies for authentication and state persistence:
Session Cookies
session_id=abc123def456; Path=/; HttpOnly
auth_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9; Secure
user_pref=theme=dark&lang=en; Max-Age=86400
Authentication Cookies
login_cookie=user123:hashedpassword
remember_me=1; Expires=Wed, 21 Jan 2026 07:28:00 GMT
csrf_token=random-csrf-token-here
Cookie Format Guidelines
- Format: name=value; name2=value2
- Attributes: Path, Domain, Expires, Max-Age, Secure, HttpOnly
- Security: Never include sensitive data in cookies
- Testing: Copy from browser developer tools for accuracy
Browser Device Emulation
Simulate different devices and browsers when using advanced rendering:
Device Types
- Desktop: Standard computer browser (default)
- Mobile: Smartphone browser with touch support
- Tablet: Tablet browser with medium screen size
Custom Viewport Settings
Desktop
- Width: 1920px
- Height: 1080px
- Use Case: Full desktop experience
Mobile
- Width: 375px
- Height: 667px
- Use Case: Mobile-first sites
Tablet
- Width: 768px
- Height: 1024px
- Use Case: Tablet-optimized layouts
Session Context and State Management
Advanced rendering supports session context for maintaining state across requests:
Session Context Benefits
- State Persistence: Maintain login sessions and user state
- Shopping Carts: Track cart contents across page loads
- User Preferences: Remember settings and customizations
- Multi-step Processes: Handle forms and wizards
Session Management
- Automatic Creation: Sessions created automatically when enabled
- Session Lifetime: Sessions persist for the duration of tracking
- Cookie Sharing: Cookies shared between related requests
- Storage Isolation: Each task has its own session context
🔒 Security Considerations
- Never include real passwords or sensitive data in task settings
- Use test accounts or API keys specifically created for monitoring
- Rotate authentication tokens regularly
- Monitor for unauthorized access in your application logs
Advanced Configuration Examples
E-commerce Price Monitoring
Scenario: Track prices on a JavaScript-heavy shopping site
- Render Level: Advanced Browser Rendering
- Request Method: GET
- Headers: User-Agent: Shopper Bot; Accept-Language: en-US
- Device Type: Desktop
- Session Context: Enabled
API Endpoint Monitoring
Scenario: Monitor REST API for data changes
- Render Level: No Rendering
- Request Method: GET
- Headers: Authorization: Bearer token123; Accept: application/json
- Request Body: (none for GET)
Form Submission Monitoring
Scenario: Monitor search results or form responses
- Render Level: No Rendering
- Request Method: POST
- Headers: Content-Type: application/x-www-form-urlencoded
- Request Body: search=query&category=all&sort=date
Mobile-First Site Tracking
Scenario: Track mobile-specific content or layouts
- Render Level: Advanced Browser Rendering
- Request Method: GET
- Device Type: Mobile
- Viewport: 375x667
- Headers: User-Agent: Mobile Browser String
Troubleshooting Configuration Issues
Content Not Loading
- Upgrade Render Level: Switch from HTTP to Server Rendering or Advanced Browser Rendering
- Check JavaScript Dependencies: Some content requires full browser environment
- Verify Selectors: Ensure CSS selectors target the correct elements
- Wait Times: Increase wait time for slow-loading content
Authentication Failures
- Token Expiration: Check if API tokens have expired
- Header Format: Verify authentication headers are correctly formatted
- Cookie Issues: Ensure session cookies are valid and current
- Permission Scope: Confirm API tokens have necessary permissions
High Token Consumption
- Render Level: Use the minimum level required for your content
- Frequency Optimization: Adjust check frequency based on content change patterns
- Selector Efficiency: Use precise selectors to reduce processing time
- Conditional Screenshots: Only take screenshots when necessary
🎯 Configuration Testing Strategy
- Start with minimal settings and add complexity as needed
- Test configurations thoroughly before enabling high-frequency monitoring
- Monitor task success rates and adjust settings accordingly
- Document successful configurations for similar websites
- Use the "Test Task" feature to validate settings before saving
Performance Optimization
Efficient Configuration
- Minimal Headers: Only include necessary custom headers
- Appropriate Render Level: Don't over-engineer simple use cases
- Selective Screenshots: Enable only when visual confirmation is needed
- Optimal Frequency: Balance timeliness with resource usage
Resource Management
- Token Budgeting: Plan token usage across all your tasks
- Priority Tasks: Use advanced settings for your most important tracking
- Batch Testing: Test multiple configurations efficiently
- Usage Monitoring: Track performance metrics and success rates
Mastering advanced task settings enables you to track virtually any website or API endpoint successfully. The key is understanding when and how to apply these powerful features while optimizing for both accuracy and efficiency.
Create Advanced Tracking Tasks
Apply these advanced configuration techniques to handle complex tracking scenarios with authentication, custom headers, and sophisticated content loading.
Configure Advanced Tasks