Release date: 28 January 2026
Status: Live in production
Audience: All MyAdbooker users
TL;DR (highlights)
- Deals API enhancement — new PublisherID field added to identify the organization where a deal was created
- Line Item Cost Calculator update — default Frequency (SOT) and Playouts per hour aligned with BRO market standards
- Frontend stability & performance improvements through internal platform framework upgrades
- Multiple bug fixes across reporting, deals, sites, SSP, and auction handling
- No downtime and no client action required
1) What’s New
Deals API – PublisherID
Where: Deals API
Note: Not all DSPs have subscribed to the deals API.
What changed:
- A new field, PublisherID, has been added to the Deals API responses
- PublisherID represents the Organization ID where the deal was created
Available in list of the deals or single deal lookup.
Why it matters:
- Enables DSPs to clearly identify the originating publisher organization
- Improves transparency and reliability of deal integrations
2) Improvements
Frontend Stability & Performance
What changed:
- Internal platform framework upgrades
Why it matters:
- Improves overall application stability and performance
- Aligned with latest security standards and modern web practices
Line Item Cost Calculator – Updated Defaults
Where: Line Item Cost Calculation Input
What changed:
The default (prepopulated) values have been updated to align with BRO market standards:
- Frequency (SOT): 12.5% → 16.7%
- Playouts per hour: 45 → 60
Behavior:
- Defaults apply only when creating a new Line Item Cost Calculation Input
- Values remain editable by the user
- Existing calculations, deals, and line items remain unchanged
Why it matters:
- Improves accuracy of campaign budget estimates
- Aligns buyer expectations with BRO-defined delivery baselines
- Reduces the risk of underestimated PMP budgets
3) Bug Fixes
Line Item Cost Calculator – Frequency Validation
Issue:
- Users could enter playouts per hour values that resulted in frequency exceeding 100%, which is invalid
Fix:
- Validation has been added to prevent frequency values above 100%
Reporting – Player Reporting Widget Responsiveness
Issue:
- On smaller screen sizes, some columns disappeared from the Player Reporting widget
Fix:
- The widget now adapts correctly to screen size, ensuring all columns remain accessible
Deals – Trigger Dropdown White Screen
Issue:
- A white screen appeared when typing in the “Trade name” dropdown or selecting operators (Equals, Greater than, Less than)
Fix:
- Users can now type and search within dropdowns without the application crashing
Sites – Latitude & Longitude Auto-Fill
Issue:
- Latitude and longitude fields were not automatically populated when entering an address
Fix:
- Coordinates are now automatically filled once an address is provided
SSP – Security Upgrade
Fix:
- Additional security enhancements have been deployed to improve platform safety
Floating CPM Deals – Auction Type
Issue:
- Floating CPM deals were sent with an improper OpenRTB auction type (at = 4)
Fix:
- Floating CPM deals are now correctly sent as First Price auctions (at = 1), in compliance with OpenRTB specifications
4) Impact & Risk Statement
- No downtime occurred during deployment
- No client action is required
- Existing deals, calculations, and integrations remain unaffected
5) FAQs
Q: Do I need to take any action for this release?
A: No. This release does not require any client action.
Q: Was there any downtime during deployment?
A: No. Version 4.0.0 was deployed without downtime.
Q: What is the new PublisherID field in the Deals API?
A: PublisherID represents the Organization ID where the deal was created and helps identify the originating publisher.
Q: Will the new PublisherID field affect existing Deals API integrations?
A: No. The field is additive and fully backward-compatible.
Q: Why were the default values in the Line Item Cost Calculator updated?
A: The defaults were updated to align with current BRO market standards and improve budget planning accuracy.
Q: Can I still change Frequency (SOT) and Playouts per hour manually?
A: Yes. The updated values are defaults only and remain fully editable.
Q: Do the new defaults affect existing deals or line items?
A: No. Existing calculations, deals, and line items remain unchanged.
Q: What changed for Floating CPM deals?
A: Floating CPM deals are now sent as First Price auctions (at = 1), in compliance with OpenRTB requirements.
Comments
0 comments
Please sign in to leave a comment.