How to Use BiddingStack Change Logs to Monitor Ad Configurations
BiddingStack automatically records every update to your ad configuration. Change logs help teams track modifications, verify settings, and troubleshoot issues efficiently.
Understanding Change Logs
Each change log entry contains:
-
Version number: Shows when the update occurred.
-
Account and site identifiers: Indicates which account and site the change applies to.
-
Domain: The affected domain.
-
Specific changes: Records all modifications made to the configuration. This shows exactly what was added, removed, or modified in the system.
Reading Change Log Diffs
BiddingStack displays updates in a diff-style format. Lines starting with "-" indicate removed content, while lines starting with "+" indicate newly added content. For example:
- "version": "2025120601"
+ "version": "2025120801"
This shows the old version was replaced with a new one.
Using Change Logs Effectively
Change logs allow you to track updates between versions and verify that targeting rules, placements, bidder settings, and other changes are applied correctly. By maintaining consistent versioning and reviewing logs regularly before deployment, you can ensure the configuration is accurate, prevent misconfigurations, and keep a reliable record of all changes aligned with your ad strategy.
BiddingStack's change log feature provides a clear record of all configuration changes, making it easier to manage updates and maintain operational consistency.