Epom DSP 6.7: Smarter, Faster, and Packed with Upgrades

Straight to the business: Epom WL DSP 6.7 is out now. It’s packed with new features, refinements, and game-changing updates designed to make managing your campaigns, payments, and analytics smoother than ever before.

From the redesigned payment configurations that put you in control of location-based options to the introduction of Deep Storage, which gives you more flexibility with your event data — this release is all about making your life easier. Need more? Epom WL DSP 6.7 brings enhancements like invalid bid request visibility and revolutionary retargeting segment management. Sounds good, right? Well, it gets better. Let’s dive into the details of these updates and see how they will supercharge your ad campaigns.

Payment Configuration: A Fresh Look at Location-Based Options

Gone are the days of the "Euro Eligible" toggle. If you were using version 6.6, you probably remember how you could just flick that switch to automatically apply a Euro-based payment method to anyone in the Eurozone. Easy, right? But in version 6.7, we've taken a more refined approach. The Euro Eligible toggle is now history, and a much more powerful Political and Economic Units filter stands in its place. Yes, it sounds more serious, but it's also more versatile.

Here's the cool part: this filter gives you control over which payment configurations are available to users based on where they're located. It's still in the Filters block under Payment Configuration, so you won't have to go on a wild goose chase to find it.

For now, the European Union is the only available unit in the dropdown menu, but don't worry. The system's built to grow, so expect more units to be added. Oh, and you can choose to include or exclude certain political and economic zones depending on your needs. However, if a user doesn't have a country set in their profile, their payment configuration will default to Wire Transfer instead of PayPal or Stripe.

And guess what else? We've now introduced the ability to clone payment configurations. That's right, you can easily copy a configuration, and while the cloned one will be turned off by default, you won't have to start from scratch every time. Now, that's a time-saver.

New Transaction Type: “Other” – The Mystery Option

Hold up. There's something new in the payment world of Epom WL DSP 6.7, and it's called "Other." This one's for those times when you manually create a transaction (not through the usual transaction page), and none of the existing payment types quite fit. We're talking about PayPal, credit cards, and wire transfers — you know, the usual suspects. But with this update, we've added Other to the list.

This new option gives you the freedom to categorize those oddball transactions that don't fall under any of the standard types. Advertisers won't get a peek at the transaction description. Only Root, Super-Admin, and Admin users will have access to this precious info. You know, for security reasons.

Creative Bundle Support in Bid Response: A Little More Control

Remember the ability to assign an app bundle at the creative level? That feature made its debut in a previous version, but 6.7 takes it to the next level. Now, if an app bundle is set at the campaign level, the corresponding field at the creative level will be disabled. And here’s the fun part — an informational icon will appear to let you know that the bundle can’t be changed at the creative level because it’s already defined at the campaign level.

“But what if I really need to change the bundle at the creative level?” you ask. No worries! Just head back to the campaign level, remove the bundle, and then you can make your adjustments at the creative level. That’s the beauty of the flexibility now built into this feature.

Oh, and in case you missed it, the icon will appear after you enter the app bundle, confirming the bundle’s status. If the icon doesn’t show up for some reason, it might be because the app you’re working with isn’t yet in the database. But don’t fret, it’ll likely be added soon.

Invalid Bid Requests: They Won’t Get Lost Anymore

So, you've had an invalid bid request before, right? The kind you had to chase down from the DevOps team just to see the body of the request? Good news! Now, in Epom WL DSP 6.7, you don't have to bother DevOps anymore to get your hands on that info. A tab called "Invalid Bid Request" has been added to the Digest section of the SSP Endpoint page.

This is a game-changer for troubleshooting. Now, all invalid bid requests will be readily visible, just like the valid ones. The logic stays the same, so you'll see the most recent invalid requests just like you'd expect to see the latest valid ones.

The bid request body will be displayed in the same way it appears in the "Bid" section, giving you the full picture for analysis. Increased visibility? Check. Easier access? Double-check. Now, you can troubleshoot and resolve issues faster.

Region and Subdivision Macros: A Better Way to Export

But wait, there's more. We've made a few enhancements to the Region and Subdivision Macros. Starting with version 6.7, you'll notice two new dimensions appearing in the parquet files and the filters when creating bidstream events.

• Region will show the region code in line with ISO-3166-2 standards. So you'll get the exact region code you're working with.
• Region_name, on the other hand, will display the region's name, giving you the easy-to-read info you need for accurate analysis.

This update will make your reporting and filtering more precise and improve your ability to track and analyze performance across different regions and subdivisions.

Retargeting Segments: Upload CSV Files Directly into the System

Retargeting just got a lot more streamlined. With version 6.7, you can now upload and remove segments directly from the segments page by simply uploading a CSV file. The logic is the same for those familiar with uploading user ID lists or IFA files. You can now upload a CSV file in one of two formats:

• Single-column CSV: Contains only hashes.
• Two-column CSV: Contains user_agent and IP pairs.

Now, let’s talk about hashing magic. Why hashes? Simple: security and efficiency. A hash is a unique, fixed-length string generated from the user-agent and IP address using a cryptographic function like SHA-256. This ensures that sensitive data is kept safe and search queries are more efficient.

For example, if you’ve got a User-Agent like:
Mozilla/5.0 (Windows NT 10.0; Win64; x64)
and an IP address like:
192.168.1.1
You might get a hash like this:
3e7a4d9b5c1f9f7f8e9b8d6c7a2e3f4d5b6c1a9e8d7b5f6c4e3a1d2c9b8a7e6f

What happens after the upload? A new button has been added to the segment page, allowing you to directly upload the CSV segments to your list. You’ll see the number of uploaded segments displayed in the Items column, making it easy to track your retargeting progress.

Analytics Lookup Service: Now With More Data Clarity

Moving on to another major improvement in Epom DSP WL 6.7 — the Analytics Lookup Service. In the previous version, users ran into an issue where analytics sometimes returned a blank dimension — specifically, the dimension that contained the lookup. This happened because, aside from campaigns or creatives, the system would store the IDs associated with them. So, when a campaign was deleted, the related data was still available for querying. While that worked, there was a catch — sometimes, the lookup would return an empty field.

But that’s all changed in version 6.7. Now, instead of returning empty fields, the lookup service will return IDs for the campaigns or creatives, making it crystal clear which campaign or creative the data belongs to. So, even if a campaign is deleted, you can still trace back the data with its ID. No more wondering what happened to those data points.

Deep Storage: The Backbone of Event Data

Let's face it — storing massive amounts of event data in high-performance databases like Aerospike can get expensive. But what if we could keep the data and only move it to a more cost-effective storage solution when it's no longer frequently accessed? Enter Deep Storage.

In Epom WL DSP 6.7, we've added a microservice that stores Click, Impression, and Win events in Deep Storage, saving valuable resources while still allowing us to track actions and clicks over time. Here's the clever bit: these events are stored in parquet files that are space-efficient and fast to process. So, when an action arrives — even if it's days later — and the data in Aerospike has already expired, we'll still be able to track it thanks to the Deep Storage.

By default, this feature, called Deep Storage Export, will be enabled, and parquet files will be stored for 7 days (configurable). After 7 days, the files are deleted to keep things tidy, but you can extend the storage period if needed.

The best part? Parquet files are generated every 2 hours, ensuring that your event data is captured in near real-time, even in the busiest environments. If an Aerospike query fails, we've got you covered by exporting Action and Click events from deep storage. That's flexibility in action.

Druid Segment Folding: Extended Analytics for the Long Term

We’re all about helping you analyze your data over longer periods. But to do that, we had to rethink how we store and process your data. That’s where Druid Segment Folding comes in.

In Epom WL DSP 6.7, we’re rolling out a new approach for reindexing data, which enables us to provide analytics not just for a few days but for up to a year. No more being limited by short windows — now, you can analyze data across a full year. Of course, handling that much data requires some adjustments to make sure we don’t overload our systems.

We’ve introduced 3 phases of reindexing to ensure your storage is optimized without sacrificing the integrity of your analytics. Here’s how it works:

• Phase 1 (Default): Reindexes data for the past 7 days.
• Phase 2 (Folding: 11-90 days): For data in this period, we simplify certain dimensions like imp_placement_size, device_vendor, and publisher_site_id. These dimensions are folded to save storage, but you still get essential data for analysis.
• Phase 3 (Folding: 91-365 days): For the long haul (up to a year), we further reduce the granularity by folding dimensions like site_domain, app_bundle, and app_name.

Why fold data? By reducing the granularity of certain dimensions, we maintain storage efficiency without losing the insights you need for year-long analysis. Now, you can easily track trends over the course of a year, even if you don’t need all the details down to the hour.

Visualize Druid Analytics Data Availability

In the past, the date-time picker on the analytics pages would let you select any date range, regardless of whether data was available for those dates. But in WL DSP 6.7, we’ve made a smart change. Only dates with available statistics will be active. If there’s no data available for a specific date, it will appear inactive, meaning you’ll only select periods where data is present.

This updated feature applies to the following pages:

• General Analytics
• Admin Analytics
• Media Planning

Now, navigating through time periods has become more intuitive. You can quickly spot where your data is available and avoid selecting empty periods.

Swagger Docs Integrated with README: Simplifying Developer Experience

Developers, this one’s for you. We’ve made it easier to interact with the API. Previously, reading through the Swagger docs might have felt like an isolated experience. Now, we’ve integrated Swagger/OpenAPI directly with README to offer an all-in-one, user-friendly guide.

The README provides a detailed yet concise overview of how to use the API, including:

• API overview: What the API does and its core functionality.
• How to use it: Instructions on making requests, detailing endpoints, parameters, and expected responses.
• Authentication: Guidelines on how to authenticate or authorize API calls (whether it’s through an API key or tokens).
• Examples: Practical request and response examples to help you get started quickly.

Swagger allows us to generate the API documentation, making it interactive automatically. Developers can test out API endpoints directly from the documentation without leaving the page. This smooth integration helps users easily understand the API’s capabilities and how to work with it in a matter of clicks.

Redesign: Improved Tabs for a Seamless Experience

Epom WL DSP 6.7 also brings redesigns for several tabs, enhancing the user interface and providing more streamlined features for various tasks:

• Retargeting – new design for managing IFA and User IDs, making it easier to organize and track your retargeting segments.
• Moderation – a revamped moderation page with better controls and a clearer layout.
• Campaign edits – more intuitive targeting options when editing campaigns — giving you full control over audience targeting.
• Analytics in campaigns – the ability to add analytics directly to campaigns for better tracking and optimization.
• Billing page – a refreshed billing interface to make payment tracking and management smoother.
• SSP endpoints – improved user experience for managing SSP endpoints, enabling more efficient management of your integrations.

Wrapping Up

Epom DSP 6.7 has its perfect blend of flexibility, efficiency, and user-centric design to reshape how you manage your digital advertising efforts. Whether you're optimizing payment configurations, troubleshooting invalid bid requests, or gaining deeper insights into your retargeting segments, this version has you covered.

You'll have the power to track your data smarter, manage your campaigns more intuitively, and make decisions faster. It's not about offering you just a new feature here and there — Epom DSP 6.7 is about transforming how you work. Enjoy!