Epom WL DSP 6.8: A Menu of Refinements and Upgrades

A new update in only a month?! Yes, dear reader, Epom is cooking.

And while the oven is hot, we are ready to deliver the most delicious features. It’s not just the appetizers and desserts we have on the table today but long-awaited main courses from our Michelin-approved chefs as well.

Get your handkerchiefs and forks ready; this is gonna be one hell of a feast!

Azure Blob Storage

Let’s start with the canape.

You can now create one more storage to work with bidstream data, and this is none other than Microsoft’s Azure Blob Storage. Yes, we’ve heard you, and we’ve added Azure.

For those unaware, the flow with Azure Blob is the same as Google and Amazon. Right now, there are two ways to create storage:

1. Connection String
2. SAS Token + Endpoint

Fear not; we know that not everyone knows how to use Azure Blob. For detailed descriptions on how to create an account, which permissions to give, how to work with containers and how to set the whole thing up, we’ve made an easy-to-use documentation.

Feature Switcher for Retargeting

Are you tired of a Retargeting-Ready label on your SSP Endpoint? The point of adding it was to automatically mark the endpoints with valid traffic, but some of you didn’t quite like it.

It’s okay, though, our feelings aren’t hurt at all. That’s why we’ve added the FeatureSwitcher to disable the Retargeting-Ready label and the functionality associated with it.

If RETARGETING_READY is Off, the 'Retargeting-ready' is not displayed:

1. On SSP Endpoints → Labels Manager page.
2. On SSP Endpoints page in the Labels column.
3. In the Labels drop-down on the SSP Endpoints page.
4. On the Campaign → Targeting Options → Traffic Source page.

Analytics: Sort Data Improvement

It’s time to make the Analytics tab a bit more usable and friendly. We had this one in our minds for a long time, and we’re finally ready to present sorting by data groups.

The best part is that sorting by any other column counts paging.

There’s not much to talk about in this one, but trust us, you’ll feel its usefulness a lot the next time you go into Analytics.

Bidding Rules: Reworked

Now for the main course – we’ve made a significant upgrade to the bidding rules.

Two new operations are available:

• x multiply
• / divide

Two old operations are reworked:

• +% increase by %
• -% decrease by %

If the Modifier list is empty, the following value is default for the Modifier list:

• + add = ‘0’
• - subtract = ‘0’
• x multiply = ‘1’
• / divide = ‘1’
• +% increase by % = ‘1’
• -% decrease by % = ‘1’

The sweetest part is that we’ve finally brought order to how these operations work.

You see, in the previous versions, Multiply and Divide operations migrated to increase by % and decrease by % accordingly. This is because they were doing similar things, but on the UI, they were signed as if they were multiplying or dividing. Now, it’s all finally sorted out.

And to sweeten this up, we’ve added a Feature Switcher for Bidding rules execution.

Traffic Funnel Upgrade

Bidding rules weren’t the only thing that needed some love and care. So we’ve upgraded Epom WL DSP in three aspects. They are mostly technical but will significantly improve how you use our platform.

Tech Errors Reworked

Firstly, No matter how frustrating, technical errors are a part of every SaaS. They get even more annoying when you, as a user, don’t understand what the hell happened. We decided to sort things up a bit.

From now on, technical errors will be split into three categories:

• Out of context: When the context has no info on how to sort this bid. For example, the user has insufficient funds or the creative is not approved for bidding. It is visible whenever triggered and allocated to a separate UI section.
• Invalid request: When the request has no device, no ID or doesn’t suit OpenRTB. It is visible all the time whenever triggered and visually displayed in the tech error section.
• Technical issue: Multiple complex examples like server timeouts. This one appears only when it is higher than 20% of traffic and hides when it is less than 20%.

New Request Metrics

If you are a tech-savvy user who likes dwelling on how things work from the inside, we have a pleasant surprise for you. Namely, we’ve added new request metrics to optimize the bidding process:

• requestImpressions - the sum of the number of impressions from all requests. If you have 1 imps in your requests, then this is essentially the number of requests, if you have 3 imps each, then this is the requests * 3.

• bidOpportunities - how many creatives were found for each imp. If you have 2 creatives in the context, and 2 imps, then this thing will essentially give 2 creatives for each imp, that is, there will be +4 bidOpportunities for each such request.

• bidsPercent - bids/bidsPercent x 100.

  If you have a TECHNICAL_ISSUE, then requestImpressions is added according to the number of imps.

  If you have INVALID_REQUEST, then we could not parse the request, requestImpressions is added by 1

{
    "filterEnabled": true,
    "bids": 10112,
    "bidsPercent": 87.75,
    "bidOpportunities": 10112,
    "requestImpressions": 11523,
    "messagesAmount": {
        "INVALID_REQUEST": 5,
        "OUT_OF_CONTEXT_REASON": 10497,
        "TECHNICAL_ISSUE": 1406
},

Download Data Lists

Segments, IFA, and user IDs data can now be exported into a zipped file. Cool? Cool.

What’s not so cool is that right now, you have to do it “manually,” sending requests through Postman. It’s not that hard, but don’t worry, proper UI is coming in 6.9.

CampaignService Refactoring

Remember how we implemented shared user access? Apparently, you do, and even liked the feature so much that Epom WL DSP started having trouble with the amount of users tweaking the new options.

We couldn’t just leave it like that. In 6.8, we’ve implemented a bunch of improvements to make everything connected to user sharing faster, easier, and more efficient.

The list of supported operations now consists of CRUD, find(query), count(query).

As for the query, it is now far wider and more flexible, and includes:

• accountIds
• campaignStatuses
• campaignApprovalStatuses
• targeting search
• updatedFrom/updatedTo
• creativeIds
• creativeApprovalStatuses
• creativeMediaTypes
• nameRegex
• flightDateFrom
• flightDateTo
• sortBy (define specific fields which will be supported)
• limit/offset

Bidding Rules: Improve #2

Do you think we’re finished with the bidding rules? Nah, we still have little surprises.

For instance, a Button link in the select component is added to have the ability to create a new modifier list when creating a new rule.

How does it work? Upon creating a new bidding rule, you don’t need to go into Bid Modifiers to actually change it. Just complete the necessary fields on the Bidding Rules tab and choose a modifier from the list, or create a new modifier right here.

Slack Notifications Integration

“It would be cool if Slack actually sent me useful stuff.” We thought so, too.

Alert when an Account Reaches Its Daily Limit

From now on, a notification to Slack can be sent once a day when you reach the daily spending limit.

A quick reminder: in User Settings/[user_name] there is a field called “advert daily limit.” The default value for the ‘Advert Daily Limit’ is $1000, but naturally you can change it.

The Slack notification message looks something like this:

The account {{first name}} {{last name}} (link to his profile) has reached its daily spending limit of {{configured limit value}} and will be suspended from bidding for the remainder of the day. Consider increasing the spending limit to resume bidding.

Notification for Manual Campaign Deactivation

As a bonus, we’ve also added a notification for a manual campaign deactivation.

The message is displayed when any user deactivates the campaign (pauses an active campaign or archives an active campaign - in general, any case when the campaign stops bidding after user actions).

User Permission for “Stores”

A small but handy upgrade – new permission for Stores was added.

Go to User Settings/User Permissions/Advertiser/Campaign/Targeting Options, and you’ll see a Store option for Google Play and App Store. This might come in handy if you’re an ad network that wants to have full control over your advertisers.

Export CSV Option

You can now export data from the planning page into a CSV file. Group it by dimensions and filters, choose a date, and have a full-on report that you can share at your corporate meeting without the need to have the Epom WL DSP opened.

Video Creative Fixes

A pleasant surprise for our ExoClick users is here.

ExoClick is an ad network that connects advertisers and publishers, allowing them to run ads using various formats, including video ads via RTB. It’s one of the largest networks on the market today, so when something goes wrong with ExoClick it affects many users.

In this case, ExoClick video requests did not include video player sizes in their request format. This led to the following problem:

• The Epom WL DSP only allows bidding if video sizes are present.
• Since ExoClick does not send sizes, bidding fails.
• The system enforces Video Orientation targeting, and this setting cannot be disabled.

That’s why we’ve come up with a solution:

• Added permission VIDEO_ORIENTATION_REQUIRED
• Added field to creative requiresOrientation - true\false (By default true)

Video Support for Native Ads

7 words to make any person’s heart melt: You can upload videos as native ads.

Don’t thank us; we’re glad to do our job.

Redesign

Now for a dessert, the redesigns! If you’ve read this far, you’re probably tired already, so let’s make it quick:

• Campaigns Targeting (language, proxy type)

• Campaigns Targeting (filters, store categories)

• Campaigns Targeting (ISP, device type)

• Campaigns targeting (categories)

• SSP Endpoint (Test Endpoint)

• Analytics

Traffic source on a separate tab

• Campaigns Attribution links and tracking pixels

Wrapping Up

Epom WL DSP 6.8 isn’t just another update — it’s a full-course meal for our users. From long-awaited bidding rule overhauls and Azure Blob support to slick UI tweaks and deeper analytics, this release delivers both flavor and functionality.

Whether you're fine-tuning campaigns, debugging tech errors, or just downloading your data with efficiency — 6.8 brings a number of upgrades that will make your day brighter and user experience smoother.

It's not a reinvention — it's a refinement. A tastier, smarter and more intuitive upgrade, almost like adding the right spices to an already delicious dish.