Overview
Audit Logs (also referred to as Settings Logs) automatically record every change made to payout configurations and campaign settings within Pingtree. Each log entry captures what changed, the previous value, the new value, who made the change, and when it occurred. Navigate to a campaign’s settings and open the Audit Logs tab to review the change history for that campaign.
Access: Audit Logs require the settings_logs role permission. Users without this permission will not see this section.
What Gets Logged
Audit Logs capture changes to the following areas:| Change Type | Examples |
|---|---|
| Payout changes | Updating fixed payout amounts, switching between fixed cost and revenue share, modifying sub-source payout overrides |
| Settings changes | Adjustments to campaign-level configuration fields |
| Payout field selection | Changing the selected payout field (e.g., from sub1 to sub2) |
| Sub-source additions | Adding a new publisher ID to the sub-source payout list |
Filtering Audit Logs
The audit log view supports two filters to help you narrow down the change history:Filter by Type
Select the category of change you want to review:| Type | Description |
|---|---|
| Payout | Shows all payout-related changes (default view) |
| Settings | Shows all non-payout settings changes |
Filter by Reference ID
Scope the log to changes related to a specific source or buyer by entering their reference ID. This is useful when investigating payout discrepancies for a particular marketing partner or custom endpoint.Reading Audit Log Entries
Each audit log entry is displayed as a human-readable description of the change. The platform translates raw field names and IDs into plain language, replacing internal references with the actual entity names (e.g., a source ID is shown as the source’s company name). A typical log entry includes:| Field | Description |
|---|---|
| Timestamp | The date and time the change was made |
| User | The team member who made the change |
| Title | A short label describing the area of the change (e.g., “Source Payout Settings”) |
| Description | A human-readable summary of what changed, including old and new values |
Example Log Entries
Source "Acme Media" click payout modifiers sub1 pub123 payout structure changed from Revenue Share to Fixed CostSelected Payout Field for Acme Media updated from sub1 to sub2Source "Acme Media" form payout modifiers sub1 pub456 override amount changed from $5.00 to $7.50
Use Cases
| Scenario | How Audit Logs Help |
|---|---|
| Compliance | Demonstrate to partners or auditors that payout changes were tracked and authorized |
| Debugging payout discrepancies | Identify when a payout was changed and who changed it to explain unexpected payout amounts |
| Team accountability | See which team member made a specific configuration change and when |
| Change rollback reference | Use the old value recorded in the log to manually revert a change if needed |
| Partner dispute resolution | Show a marketing partner the exact history of their payout settings |