Release Notes - MAB Version 3.5.0

Release – MAB Version 3.5.0
Release date: 16 October 2025
Status: Live in production
Audience: All MyAdbooker users

TL;DR (highlights)

• Prevent adding line items to inactive campaigns — a new modal now appears when attempting to add a line item to an inactive campaign, ensuring proper campaign activation before proceeding.

• Deals API enhancement — new Publisher and BidFloorPrice fields added for richer DSP integration and reporting context.

• Campaign reporting filters fixed and improved — campaign metrics can now be filtered correctly by date, with a new 30-day range limit to ensure performance and accuracy.

1) What’s new

Prevent adding line items to inactive campaigns

Where: Campaigns → Line Items → + Add New Line Item

What changed:
When a user attempts to add a new line item to an inactive campaign, the system now blocks the action and shows a mandatory modal dialog:

“This campaign is currently inactive. Do you want to Activate it?”

• Yes → The campaign is automatically activated, allowing the user to proceed with adding the new line item.

• No → The action is cancelled; the campaign remains inactive, and no new line item can be created.

Why it matters:
This change prevents accidental configuration errors where users could previously add line items to inactive campaigns — ensuring data consistency and reflecting true campaign intent.

2) Improvements

Deals API fields expansion

Where: Deals API endpoints
Endpoints affected:

• GET /v1/deals

• GET /v1/deals/{deal-id}

New fields added:

• publisher → Returns the Organization Name where the deal was created.

• bidFloorPrice → Returns the bid floor price configured for the deal.

Why it matters:
Enables DSPs and reporting systems to access richer deal information.

 

Campaign reporting filters

Where: Campaigns → Reporting tab

What was fixed:
Previously, campaign totals (e.g., budget and impressions) did not update correctly when filters were applied — filtered results still showed totals for the full campaign duration.

Now:

• Users can filter reporting data by custom date range, and totals dynamically reflect only the selected period.

• Filtering is limited to a maximum range of 30 days, ensuring fast query execution and accurate KPI aggregation.

• If a user selects a wider range, an error message appears indicating the limit.

Why it matters:
Ensures campaign analytics reflect accurate filtered data while maintaining backend stability and query performance.

3) FAQs

Q: What happens if I try to add a line item to an inactive campaign?
A: You’ll see a modal asking if you want to activate the campaign. Selecting Yes activates it; selecting No cancels the action.

Q: Why can I only filter campaign data for 30 days?
A: The 30-day limit ensures stable performance and fast results when querying large data sets.

Q: Are existing DSP integrations affected by the Deals API update?
A: No. The new fields are additive — existing integrations remain fully compatible.

Q: Where can I view the new Deals API fields?
A: In responses from both GET /v1/deals and GET /v1/deals/{deal-id}.

If you encounter any issues or have questions about this release, please contact Support — we’re here to help.