Release date: 19 August 2025
Status: Live in production
Audience: All MyAdbooker users (admin/integrator notes marked as such)
TL;DR (highlights)
Insights — advanced analytics is available to all SSP users (no action needed). We can tailor dashboards for your organization on request.
Bulk player targeting via XLSX — upload Player IDs to auto-select screens in Line Items and Calculations with a clear match summary.
DSP network-level bidding — control which networks each DSP can bid on; our exchange only sends bids to DSPs that support the player’s network.
Plus targeted stability and UX fixes across campaigns, targeting, creatives, approvals, players & sites.
1) What’s new
Insights — advanced analytics (enabled for all SSP users)
What: Deeper, configurable dashboards and reports in Insights.
Availability: Already enabled for all SSP users.
Get more value: Want tailored dashboards (teams, objectives, markets)? Contact Support and we’ll set them up with you.
Bulk player targeting via XLSX
Where:
Campaigns → Line Items → Targeting
Calculations → New/Update → Targeting
What: Upload an .xlsx with Player IDs (names optional) to auto-select screens.
How it works:
Click Upload .xlsx (download the template next to the button if needed).
We validate the file and show a summary modal (matched vs. not found/not selectable).
Matched players are auto-selected in the UI.
Rules & validation:
File type must be .xlsx; errors show for other formats or missing data.
Player ID is required for a match (name is optional).
Players not part of the selected deal or outside your organization appear as unsuccessful in the summary.
Uploads are not stored; a new upload overwrites the previous selection in this session.
DSP network-level bidding
Where: DSPs page → new NETWORKS column and editor.
What: Decide, per DSP, which networks it can bid on.
See selected networks (amount) at a glance.
Quickly select/deselect networks (includes Select/Deselect all).
Our exchange sends BidRequests only to DSPs that support the player’s network.
Also: A Network Route SSP Identifier field is available for SSP→SSP routing.
2) Improvements
Scala playback stability — Ad responses for image placeholders now always include a default duration of 6 seconds, preventing playback loops and repeated ad requests on Scala-based players.
Shell Vehicle Detection — CUPRA added to the car-brand trigger list for more accurate targeting.
Need help adopting any of the above? Contact Support and we’ll walk you through it.
3) Fixes
Campaigns & Targeting
Filtering + pagination — When you filter while viewing later pages, the list auto-adjusts so matching results show immediately (no more “empty” pages).
Site/Network selectors — No duplicates; all active sites/networks appear once.
Inactive deals — Now hidden during line-item creation/editing to avoid accidental selection and to speed up setup.
Delete action visibility — The Delete button in Campaigns no longer appears on window resize; it remains hidden as intended.
Creatives & Approvals
Library ↔ playlist sync — Deleting a creative from the library (during line-item creative selection) now removes it from the playlist and preview automatically, so the line item can be saved without manual clean-up.
Creative Approval search — Search is now consistent and case-insensitive; expected creatives are returned reliably.
Approval “Sort” dropdown — The control is selection-only (four valid options). Free-text input is blocked to prevent errors/blank screens.
Players & Sites
Clear message on site deletion — If a site is still linked to players, the UI now clearly explains why it can’t be deleted.
Generic web players — Player create/update events now reliably update configurations (no more silent stale configs).
4) Reliability & performance (admin/integrator notes)
AdServer gateway — traffic protection
Per-device rate limiting on/v1/adrequestsprotects the platform from bursts originating from unregistered/invalid device IDs. Misconfigured devices that exceed limits receive HTTP 429 until corrected/registered. Normal traffic is unaffected.Faster data propagation via gRPC
AdServer and PMP now read CMDB data via gRPC for lower latency and greater reliability. You should see quicker reflection of inventory and player updates in targeting and delivery.
If you operate custom integrations or have edge-case traffic patterns, contact us for best-practice configuration.
5) Version matrix (for reference)
| Component | New version |
|---|---|
| SSP Back-End | 4.7.1 |
| SSP Front-End | 3.2.0 |
| PMP | 4.5.6 |
| AdServer | 3.4.2 |
| MadX | 3.5.3 |
| CMDB | 3.5.0 |
| IDP | 4.6.2 |
| OOP | 2.2.4 |
| RDW | 2.2.1 |
6) FAQs
Q: Do I need to do anything to get Insights?
A: No. Insights is enabled for all SSP users. If you’d like tailored dashboards and KPIs, contact Support.
Q: Where do I find the XLSX upload for player targeting?
A: In Campaigns → Line Items → Targeting and Calculations → Targeting. There’s an upload template next to the button.
Q: Why didn’t some players from my file get selected?
A: We require a Player ID for matching. Players must also belong to the selected deal and your organization. The summary modal lists any that couldn’t be selected and why.
If you have questions, run into anything unexpected, or want help tuning Insights for your needs, please contact Support — we’re happy to help.
Comments
0 comments
Please sign in to leave a comment.