Integration Highlights
- Real-time postback data sync
- Install and in-app event tracking
- Cost data aggregation
- Cohort and retention analysis
- Fraud detection data integration
Overview
The AppsFlyer integration enables bi-directional data flow between ClicksFlyer and AppsFlyer. You can receive attribution data from AppsFlyer postbacks and send click/impression data from ClicksFlyer campaigns for proper attribution.
Setup Instructions
Step 1: Get Your ClicksFlyer Postback URL
Log into ClicksFlyer and navigate to Settings â Integrations â AppsFlyer. Copy your unique postback URL:
Step 2: Configure AppsFlyer Partner
In AppsFlyer dashboard:
- Go to Configuration â Integrated Partners
- Search for "ClicksFlyer" or add as custom partner
- Enable "Install" postback
- Paste your ClicksFlyer postback URL
- Configure in-app event postbacks as needed
Step 3: Set Up Click Tracking
For campaigns driving traffic through ClicksFlyer, use our tracking links with AppsFlyer parameters:
Step 4: Test the Integration
Use AppsFlyer's integration testing tools to verify postbacks are being received correctly in ClicksFlyer.
Supported Data Points
Install Attribution
- Install timestamp
- Media source
- Campaign name & ID
- Ad set and ad creative
- Device type and OS
- Country and city
In-App Events
- Event name and timestamp
- Revenue value and currency
- Custom event parameters
- Session data
Advanced Features
Cost Integration
Enable cost data sync to pull spend data from AppsFlyer into ClicksFlyer for ROI calculations. This requires AppsFlyer's Cost API access.
Cohort Data
Sync cohort retention and LTV data for advanced user quality analysis across your campaigns.
Protect360 Fraud Data
If you have AppsFlyer Protect360, fraud signals can be integrated for enhanced traffic quality monitoring.
Troubleshooting
- Postbacks not received: Verify URL is correctly configured and test with AppsFlyer's testing tools
- Missing click_id: Ensure your tracking links pass the click_id parameter correctly
- Delayed data: AppsFlyer postbacks are typically real-time but can be delayed during high volume