At a Glance: This article helps you understand the Logs section in the Partner Dashboard, where you can view raw data for clicks, impressions, installs, events, and postbacks.
Overview
The Logs section in the Partner Dashboard provides partners with detailed, real-time records of user activity and campaign tracking. Each log type—click, impression, install, event, and postback—comes with built-in reporting options and filters, allowing you to validate traffic, debug issues, and keep campaign performance transparent.
Types of Logs Available
1. Click Logs
Click logs capture every user click on your campaign’s ad placements. These logs are critical for validating the number of clicks received and troubleshooting attribution mismatches.
Reporting Options
Partner Click ID: Identifier passed by the partner network for easier reconciliation.
Click IP: The IP address from which the click originated.
GEO: Geographic location based on the user’s IP.
Operating System: The user’s device operating system at the time of the click.
User Agent: An HTTP header providing detailed information about the device, browser, and OS used during the click. This helps detect bots, understand user environments, and ensure proper rendering.
Cost: The monetary cost incurred per click.
Param 1 & Param 2: Custom parameters for capturing campaign-specific data.
Created: Timestamp capturing when the click was logged.
Filters Available
You can filter click logs by Agency, Geo and Click ID to narrow the dataset for deeper traffic analysis.
2. Impression Logs
Impression logs provide visibility into every recorded ad impression before a user clicks. These are essential for understanding ad delivery and measuring CTR (click-through rate).
Reporting Options:
ID: Unique identifier for each impression.
Param 1 & Param 2: Custom tracking fields used to capture extra campaign-specific details.
Impression IP: The IP address of the user who received the ad.
GEO: Geographic location based on IP.
Created: Timestamp noting when the impression was recorded.
Operating System: Details of the OS on the user’s device.
User Agent: Captures device, browser, and OS details — helpful for verifying if impressions were served to real users or bots.
Cost: Cost incurred per impression.
Filters Available:
Filters include Agency, Geo and Impression ID, helping you locate specific impressions related to certain partners or campaigns.
3. Install Logs
Install logs track every install attributed to your campaigns. They are the most commonly used dataset for validating conversion delivery and measuring partner performance.
Reporting Options:
IP: The IP address recorded at the time of installation.
Campaign ID: Unique ID of the campaign leading to the install.
GEO: Geographical location of the user at install time.
Install Time: Timestamp indicating when the install was completed.
Cost: Monetary value of the install, used for billing or ROI calculations.
Campaign: Name or ID of the campaign that drove the install.
Filters Available:
Available filters include Agency, Geo, Install ID, GAID (Google Advertising ID) and Click ID to analyze install patterns.
4. Event Logs
Event logs record in-app activities triggered by users after install, such as signups, purchases, or level completions. They are crucial for partners to understand post-install engagement quality.
Reporting Options:
ID: Unique event log identifier.
Event: Name of the in-app event (e.g., signup, purchase).
Event ID: Identifier for the specific event.
Event Time: The exact timestamp when the event occurred.
Ad / Ad Set / Site ID: Details about the ad campaign components for granular attribution.
Created: Log generation time for the event.
Filters Available:
Use New User Data and AND condition toggles alongside filters like Agency, Geo, Event Name, In-App Event Log ID, Install ID, Click ID, and SDK Types to refine event data.
5. Postback Logs
Postback logs display every server-to-server postback sent from Apptrove to your system. These logs help partners verify that all conversions and events have been successfully delivered.
Reporting Options:
Postback ID: Unique identifier for the postback.
Type: Classifies the postback as an Install or Event.
Event/Install Log ID: Links the postback to the original event or install that triggered it.
URL: The destination URL where the postback was sent.
Date: Timestamp when the postback was fired.
Response Status Code: HTTP response code (e.g., 200 OK) indicating successful delivery or failure.
Event: The specific event that led to the postback.
Filters Available:
Filters include Postback Log ID, Type, and Install/Event Log ID for precise retrieval and troubleshooting.
Broaden your knowledge:
We are delighted to have assembled a world-class team of experienced professionals who are ready to take care of your queries and answer any questions you may have.
Feel free to reach out to us at any time by emailing us at support@apptrove.com or by using the in-platform chat feature. We'd love to hear from you!
