Submit a request
Sign in

Adzerk Release Notes

For most recent release notes, please visit our new portal here.

 

December 19, 2016

Updates

  • This past week we've been working primarily on end-of-year maintenance items.  Consider it an internal "Spring Cleaning" but a couple of months early.  
  • We've also been working on an Adzerk header bidding solution.  It's still under wraps, but it's close.  If you're interested in beta testing it, please contact support@adzerk.com .
  • Lastly, we're working on a massive documentation update that will go live soon!  Stay tuned!

 

December 12, 2016

Improvements

  • Ruby Gem Reporting API Updated: If using our Ruby gem to access the Adzerk API, it was possible to access a deprecated reporting endpoint without realizing it.  The old endpoint was introducing errors and occasional instability to our management APIs.  We changed the old endpoint to simply return the equivalent of an "I'm deprecated so don't use me" error, and we've updated our Ruby gem to never use that endpoint.  We recommend updating the gem in your own applications.

Bug Fixes

  • Missing Event Data in Data Shipping: Some folks were missing their custom event data in the daily data shipping logs.  Clicks and impressions were coming through for everyone, but the custom events (including conversions) were missing for some accounts.  
  • Scheduled Reporting Page Broken: A UI release we shipped last week broke the scheduled reporting page for a short time.  We noticed it right away, however, and made to sure to fix it lickety-split!

 

December 5, 2016

Improvements

  • Reporting Performance Improvements: We added an optimization that only brings in certain data internally when it's absolutely necessary for a report.  This causes many reports, especially those in forecasting, to execute much faster.
  • Click Bucketing Optional In Scheduled Reports: By popular request by our scheduled report beta testers, you can now turn off the click bucketing columns when scheduling a report to send to your advertiser customers.  If you're interested in beta testing our new scheduled report feature that enables emailing outside of your organization, please email support@adzerk.com .
  • Improved Internal UI/API Logging: We built additional debugging tools to help us get deeper context on error messages coming from the UI & API.  

Bug Fixes

  • Broken Ad Previews: An SSL certificate for the UI expired, causing ad previews to fail.  We quickly noticed and replaced the certificate.

On the Tech Blog!

We're back in the tech blogging mood, and Dave Yarwood recently posted a tech blog post: Bringing Back Bookmarklets with Clojure and Boot

 

November 28, 2016

Improvements

  • Reporting Performance Improvements: We tweaked our data ingestion services to make them a lot faster.  We had seen a few slowdowns recently in importing reporting data.  These tweaks should prevent that error case in the future and improve ingestion in general.

Bug Fixes

  • Scheduled Reporting on New Accounts: The default maximum count for scheduled reports for new accounts got a little confused.  Instead of defaulting to 100 like it was supposed to, it was defaulting to zero.  Fixed!
  • (BETA) Targeting Optimization Online: Our beta targeting optimization service was having some production issues and was offline for a time.  It is now back online and functioning properly.

 

November 21, 2016

Improvements

  • Default UI URLs Changed: Previously, both the adzerk.net and adzerk.com URLs would work for each accounts' subdomain.  For example, let's say your account's subdomain was larry, then both larry.adzerk.com and larry.adzerk.net would work to get to the Adzerk UI.  For many reasons, chief among them security, we've been consolidating only to adzerk.com for UI access. This last change makes all default URLs use adzerk.com.  If you have an old adzerk.net bookmark, please update it.
  • Robustness Improvements: We've reorganized how we internally deploy and scale our ad balancer services.
  • Security Improvements: Please note we don't publicly discuss security details, but you can rest assured we are continuously improving our defenses against would-be attackers. 

Bug Fixes

  • Email When Report Is Ready: Before running a long report in the UI, you have the option to say "email me when it's done".  However, in many cases these emails were failing to send.  This has been addressed, and you can now rely on getting an email when the report is complete.
  • Authentication Issues Around Creatives: Some customers reported getting error messages and having difficulty creating creatives in the API & UI due to an internal user authentication issue.  Fixed!
  • Reports Sorting Incorrectly: In some cases reports were sorting randomly.  For most reports, rows should sort by the highest number of impressions to the lowest, and when you group by day, week, or month it should sort them chronologically.  The correct sorting behavior has been restored!
  • Unescaped Commas When Exporting Media Plans: When exporting Media Plans to a CSV, some fields were not being escaped properly.  If they contained commas, this would mess up the columns of the CSV, making it think it had more columns than usual.
  • (BETA): Revenue Numbers Missing in Scheduled Report: Beta testers of our enhanced scheduled reporting feature quickly found this one.  The UI setting to include revenue numbers in a scheduled report was not being honored.
  • (BETA): Dates Off-By-One in Scheduled Reports: Another quick discovery by our beta testers, when creating a scheduled report the CSV would include the right dates, but would look like it was adding a day beyond what the report was supposed to show.
  • (BETA) UI 2.0 Campaign List Too Wide: Some people were seeing the campaigns list be too wide for their screens.  It was not word-wrapping properly in the "served / total" column.

November 14, 2016

Improvements

  • Improved Reliability in Custom Targeting Validation: We greatly improved the reliability and scalability of our custom targeting language validation service.  Some folks were occasionally seeing "invalid Zerkel" error messages via the management API when their Zerkel expression was indeed valid.
  • Security Improvements: Please note we don't publicly discuss security details, but you can rest assured we are continuously improving our defenses against would-be attackers.
  • Additional Reporting Logging: We've added more internal logging to our reporting systems to help debug potential future issues.  We are constantly monitoring our report services, but if you ever experience issues please note the report ID and alert support@adzerk.com .  

Bug Fixes

  • Unable to Add Creatives to an Unsaved Flight: For a short time, some folks could not add a creative to a flight that hadn't been saved yet.  We detected & fixed this issue quickly, but unfortunately it did negatively impact a few accounts.
  • VAST Tag Failures: Our beta VAST feature was having issues uploading VAST tags (video creatives) for some beta testers.
  • Forecasts with Metro Codes: Forecasts with metro codes were failing for some folks.
  • Sorting Media Plan Line Items: When exporting a media plan to a CSV, the line items were often randomly sorted.  Now they properly sort by the sort order field.
  • Long Flight Names in UI 2.0: Flights with long names were failing to save in UI 2.0.  Now it correctly shows an error message.  Flight names must be less than 100 characters.
  • Scheduled Report Emails & White-labeled UI: Some Adzerk accounts use a white-labeled domain name for their UI 1.0.  In this case, the scheduled report emails were using an incorrect domain name in report links.
  • Zone API Docs: We added a clearer example of how to update an existing Zone via the management API.  The earlier example was more about deleting a Zone, and it caused some confusion.

 

November 7, 2016

Improvements

  • Email Scheduled Reports Outside of your Organization: (BETA) New in beta, you can now email scheduled report CSV links automatically to any email address, even your advertisers!  If you're interested in beta testing this with us, please email support@adzerk.com .
  • Improved iOS Device Targeting: Previously, our device targeting system could be confused by devices running iOS 9.1 or higher.
  • Robustness Improvements: Scheduled Reporting: Our scheduled reporting system got a tune-up, oil change, and a tire rotation last week.  (Not really, but it did get some improved robustness improvements!)
  • Security Improvements: Please note we don't publicly discuss security details, but you can rest assured we are continuously improving our defenses against would-be attackers.

Bug Fixes

  • Exporting Reports to CSV: Some folks were seeing failures when attempting to use the "Export to Excel" CSV download feature on the reporting page.
  • Added Criteria to Reporting v2.0 API Responses: On our beta Reporting 2.0 API (which is still undergoing lots of changes), we added back the request criteria values that had gone missing.
  • Added Metro Names to Reporting v2.0 API Responses: Similar to the above, we've added Metro Names to the Reporting 2.0 API response.
  • Scheduled Reporting Metro Code & Name CSV Format: In CSV files generated by our new beta Scheduled Report emails, the metro code and metro name field was sometimes coming back mangled.
  • Remove Extra Search Field from UI 2.0: We have filter and search fields on the left-hand sidebar for most pages in UI 2.0.  We also had an earlier version of the search field in the header that was no longer necessary, so it has been removed.

 

October 31, 2016

Improvements

  • Robustness Improvements: Ad Serving: We learn much from every outage, and last week's DNS issues that took down much of the Internet was no exception.  We made several important internal tweaks to better weather storms like those in the future.
  • Robustness Improvements: Scalability: We've removed dependencies on some third-party systems that might possibly cause us scalability issues in an emergency.  Uptime is always a top concern, so we're always looking for weak points in our system that might endanger it.  No mercy.
  • Robustness Improvements: Data Shipping: Data shipping got several robustness improvements this week too.  Gotta keep that data on time.
  • Security Improvements: Please note we don't publicly discuss security details, but you can rest assured we are continuously improving our defenses against would-be attackers. 

Bug Fixes

  •  Missing Click Bucketing Data: Some clicks for some customers were not handled properly by our click bucketing service starting in early October.  This resulted in a "unique clicks" count lower than expected for some accounts, although the old-school "clicks" values were still accurate.  This problem has been resolved and the click bucketing data is now correct again.
  • Server to Server Conversions Too Strict on User Agent: The server-to-server conversion tracking endpoint was using the same User Agent verification that we use for client to server impressions and conversions and was incorrectly rejecting valid server conversions in some cases.
  • Wrong Domain in Email Links: Some emails sent by Adzerk contained links with the old adzerk.net UI domain rather than the correct adzerk.com.  This was not a problem before the DNS DDoS attack last week caused us to be stricter with our domain names.  We've now corrected the emails.
  • Conversion Pixels Returned Error Code: Our conversion pixels were being a bit overzealous in some cases and returned 400 error codes unnecessarily.  This caused some especially perceptive ad viewers to see errors in their web browser's JavaScript consoles.  No real harm done, but some folks were left scratching their heads.  We've resolved this.
  • Conversion Cookies Overflowing with Keywords: Some customers with a very large number of ad request keywords and a large number of conversion tracking campaigns were seeing impression pixel errors.  The impression pixel built a set-cookie header that contained all the keywords on all conversion pixels and sneak past the four kilobyte cookie size limit.  The impression was still counted, but it caused an error response in the ad viewer's web browser console.  We've resolved this by more precisely calculating the actual size of the cookie and trimming old conversion tracking pixels from the cookie as necessary.

 

October 24, 2016

Improvements

  • Scheduled Reporting: Our scheduled report feature has left Beta testing to now be available to all customers!  
  • Robustness Improvements: Our ad servers now better handle some error conditions that could cause heavy load.
  • Security Improvements: Please note we don't publicly discuss security details, but you can rest assured we are continuously improving our defenses against would-be attackers. 

Bug Fixes

  • Truncated Keywords in Reports: Ad requests with keywords that went over the 512 character limit would sometimes cut off a keyword in the middle.  For example, if the last keyword was "durham" it might be cut to "du" in the reporting data.  Now we totally trim any keywords that push the total keyword list over the limit.  We still strongly recommend keeping your keyword total well under 512 characters, but now you can rest easy that if you do go over you won't end up with scraps of your keywords littering your reports.
  • Report Formatting: If a site report had a piece of data with no site, the reporting UI would incorrectly skip a column.  This could be pretty confusing, but now the UI properly handles this case.

 

October 17, 2016

Bug Fixes

  • UI 2.0 Not Creating Flights: For a short time this past week it was impossible to add a new flight to a campaign in our new UI 2.0.  Fixed!
  • Advertisers Could Not Download Report CSV: Advertiser users could run reports fine, but if they tried to download them as CSVs it would fail.  Fixed!
  • Report Formatting for Server Conversions: Reports that contained server conversions were having formatting issues which made the rate type and price return incorrectly as "0".
  • Report with Uppercase Keywords Failing: Filtering by uppercased keywords would cause the report to fail.  Long story short -- we now correctly treat all keywords as case-insensitive.
  • Broken Sites Menu: If you clicked on a site configuration in our UI 1.0, you could end up on a "Sites" menu that didn't have all our normal menu options.  No more!
  • Creative Previews Default to HTTPS: We're encouraging all our customers to prefer HTTPS, the secure version of the web, as much as possible.  When previewing creatives, we now default to HTTPS, but you can still fallback to using HTTP for legacy creatives.

 

October 10, 2016

Improvements

  • Improved IPv6 & IPv4 Geolocation: Our new and improved geolocation system went live last week and provides much better resolution accuracy and precise intra-country targeting for both traditional IPv4 and the rapidly growing IPv6 addresses.  
  • Keyword Response Time Improvements: We have new ad server optimizations that lower ad delivery times significantly for keyword-targeting ads.  We continue to roll this out gradually, customer by customer.
  • RTB: Pubmatic Video: (BETA) We now support programmatic RTB requests for Pubmatic video ads.  If you're interested in beta testing this feature, please contact support@adzerk.com .
  • RTB: Index Exchange Video: (BETA) Similarly, we have a beta integration with Index Exchange for video ads.  If you're interested in beta testing this feature, please contact support@adzerk.com .
  • Security Improvements in UI 2.0: Please note we don't publicly discuss security details, but you can rest assured we are continuously improving our defenses against would-be attackers. 
  • Reporting 1.0 Fully Decommissioned: It's official!  Our venerable Reporting 1.0 system was turned off this past week!  We're super excited!  Please fasten your seat-belts and return your tray tables to their upright position while we prepare to launch several new reporting extensions in the coming weeks!

Bug Fixes

  • Incorrect Advertiser Creative Links in UI 2.0: Clicking on the "Creatives" link on an advertiser page in UI 2.0 could take you to a list of creatives for the wrong advertiser!
  • Reserved Keys Documentation: Time examples on the Reserved Keys entry have been corrected to use 1-based indexing rather than 0-based indexing.

 

October 3, 2016

Improvements

  • Improved IPv6 & IPv4 Geolocation: Today we are rolling out our new and improved geolocation system.  We'll provide much better resolution accuracy, but the non-US region codes will be changing for API users.  Additionally, IPv6 addresses will now be available correctly via our data shipping feature.
  • Keyword Response Time Improvements: We have started rolling out ad server optimizations around keyword usage that should lower response times significantly for accounts with large numbers of keyword-targeting ads.  We are gradually rolling this out customer by customer over the next couple weeks.
  • Forecasting Based on Reporting 2.0: As of last week, our Sales App forecasting feature now uses Reporting 2.0 data.  This is a big milestone for us as it was the last feature using the Reporting 1.0 system!
  • Increased Unmatched Limit in Reporting: Previously, the total number of characters in unmatched keywords passed in on a single request was truncated at 256 characters.  We've doubled that to 512 characters.
  • Reporting Robustness Improvements: There were lots of improved monitoring, self-healing, and minor bug fixes for our reporting system this past week!
  • Security Improvements in UI 2.0: Please note we don't publicly discuss security details, but you can rest assured we are continously improving our defenses against would-be attackers.

Bug Fixes

  • Companion Ad Fixes: There were some edge cases wherecompanion ads might serve even though they should not.  One example was if a companion ad required a certain number of placements but an ad request had a smaller number.  In that case there was a bug were the companion ad might serve, even though it could not show all of its components.  Similarly, if a companion ad had multiple placements of the same size, it might not serve correctly.  These have been corrected.
  • Reporting API Race Condition: There was a slight chance of a race condition when checking by the reporting API if a report was complete.  In some rare cases, the API would indicate the report was complete before it truly was.

 

September 26, 2016

Improvements

  • Creative Templates in UI 2.0: (BETA) The creative templates beta feature is now supported in our UI 2.0 beta! (more details)

Bug Fixes

  • Reporting API Incorrect Datatype: Some fields in our reporting API started being returned as strings instead of integers.

Coming Soon

  • Improved IPv6 & IPv4 Geolocation: On Monday, October 3rd, 2016 we will be rolling out our new and improved geolocation system.  We'll provide much better resolution accuracy, but the non-US region codes will be changing for API users.
  • Keyword Response Time Improvements: We are shipping ad server optimizations around keyword usage that should lower response times significantly for accounts with large numbers of keyword ads.  We will be gradually rolling this out customer by customer over the next few weeks.

 

September 21, 2016

Improvements

  • Ad Chain Passback Improvements: We've made our passback codes a bit leaner and meaner.  They weather iframes better, handle multiple flights better, and are easier for us to upgrade in the future without you having to do anything.  Lastly, for you web developers out there, we made several changes to make our codes better "JavaScript citizens" including removing their impact on the global namespace.
  • UI 2.0: Create Advertiser When Creating Campaigns: (BETA) Now in our new UI 2.0 it's just as easy to create new advertisers when creating a new campaign as it was in the old UI.
  • Long-Running Report Failures: Some extremely large reports that were taking longer than fifteen minutes to process were being killed before they could finish due to an internal timeout.  This has been fixed and large reports are happy again.

UI 2.0 Bug Fixes

  • Sometimes you didn't really get logged out when you'd log out.  Whoops!
  • We now correctly disable the goal type dropdown when a flight is an auction priority.
  • The "Lottery with Outbid" selection algorithm is now displaying correctly on the priorities page.
  • The "Served/Total" column now shows correctly for flights within a campaign.
  • There were a couple of rare edge cases where a creative would incorrectly fail validation.

Coming Soon

  • Keyword Response Time Improvements: We are shipping ad server optimizations around keyword usage that should lower response times significantly for accounts with large numbers of keyword ads.  Keep your eye out for even faster ads!
  • Improved IPv6 & IPv4 Geolocation: IPv6 geolocation has been spotty in many parts of the world, but we are upgrading our geolocation systems to be much more accurate for both IPv6 and IPv4.  One side-effect of this change is that our intra-country region codes for countries other than the USA will be changing.  We'll give you a heads-up well before we roll this out.

 

September 12, 2016

Improvements

  • RTB: Pubmatic Display in Beta: Our real-time-bidding (RTB) Pubmatic integration for display ads is now live and in beta.  If you're interested in testing it with us, please contactsupport@adzerk.com

Bug Fixes

  • Scheduled Reports on Reporting 1.0: There were a handful of scheduled reports that were still using 1.0, but now all reports from all customers (scheduled or not) run on Reporting 2.0.

Coming Soon

  • Ad Chain Passback Improvements: We're working on several changes that will make our passback codes leaner and meaner.  They'll weather iframes better, handle multiple flights better, and be more resistant to change.  More details soon.
  • Improved IPv6 & IPv4 Geolocation: IPv6 geolocation has been spotty in many parts of the world, but we are upgrading our geolocation systems to be much more accurate for both IPv6 and IPv4.  One side-effect of this change is that our intra-country region codes for countries other than the USA will be changing.  We'll give you a heads-up well before we roll this out.

 

September 6, 2016

Improvements

  • Ados.js Event API: Adzerk ad tags use our ados.js JavaScript library which now has an open event API.  Your own JavaScript code callbacks can be triggered when an ad tag creates an impression, refreshes an ad, invokes a passback, etc.  (more details)
  • Click Bucketing Data in Unmatched Keyword Queries: Previously, if you were pulling a report that filtered or grouped by keywords but not by campaign, flight, ad, or advertiser, then you would get no click bucketing data.  We call this style of query anunmatched keyword query, because you are looking at the full set of keywords, not just those that are required for targeting.  Now when you pull these types of reports, you'll get the extra click bucketing data.
  • Performance Improvements for Reports without Geolocation Data: Reports that do not filter or group by country or metro got a big speed-boost this week!
  • UI 2.0: Added eCPM Optimization Form: (BETA) You can now configure eCPM optimization settings in UI 2.0!
  • Reporting by Publisher Account: Publisher accounts are a legacy feature supported for backwards compatibility.  For those customers already using it, you can filter and group by publisher in reporting 2.0.

Bug Fixes

  • Metrocode Macros Fixed: The location.dmaCode andlocation.metroCode macros were not expanding when used in the bodies of creatives.
  • Reports Before 2014 Were Failing: We are still in the process of importing data before January 1st, 2014 into our new Reporting 2.0 system, and reports requesting time frames before that were outright failing.  Now reports will safely return zeros for years 2011, 2012, and 2013 until we've imported that historical data.  Stay tuned!
  • UI 2.0: Site Targeting on Creative: The site selector was not autocompleting in some cases.
  • Small UI Failures on Thursday: Our UI 1.0 had some non-specific failures for a couple of hours on Thursday due to an errant code library.  We quickly identified the root cause and fixed it.

Coming Soon

  • Improved IPv6 & IPv4 Geolocation: IPv6 geolocation has been spotty in many parts of the world, but we are upgrading our geolocation systems to be much more accurate for both IPv6 and IPv4.  One side-effect of this change is that our intra-country region codes for countries other than the USA will be changing.  We'll give you a heads-up well before we roll this out.

 

August 29, 2016

Improvements

  • Creative Summary in UI 2.0: In our UI 2.0 open beta, we've added the current status, served count, and CTR for each creative on the flight page.
  • Robustness Improvements: We've been tuning, adding more monitoring, and adding more redundancy to our internal systems to make them even more reliable and scalable.
  • Security Improvements: Please note we don't publicly discuss security details, but rest assured we are continously looking at ways to improve our defenses against would-be attackers.

Bug Fixes

  • Missing Data on UI 2.0 Login: Fixed a UI 2.0 bug where sometimes when you would log in it would look like you had no campaigns, sites, or flights.  Refreshing the page would fix it, but now you don't have to!
  • Impression ID Macro: We added the decision.id macro to our documentation.  This value contains the impression ID and can be mapped to specific impression records in the Data Shipping logs.

 

August 22, 2016

Bug Fixes

  • Missing Report Header in CSV: Reporting rows without a site ID or zone ID (such as static text links) were causing the column headers to not line up when exporting the report to a CSV.
  • More Improvements to Passback Codes: Our passback codes now include multi-flight passback support as well as the improved iframe support we mentioned previously.
  • iOS SDK Forgetting User ID: Our iOS software development kit (SDK) was not properly remembering the UserDB ID returned for use in later ad requests.  Big thanks to the Adzerk open source community for the bug report and patch!  (details)
  • Blank Creatives: It was possible in some situations to make a creative that had a totally blank body as well as blank metadata and have it serve.  We've tightened the validations on the UI and API to prevent this from happening.
  • Ads with Override Percentage of 100% Not Serving: In some cases, the override percentage was not actually getting set properly for some ads with 100% override.  This caused those ads not to serve.
  • Flat Rate Flights Missing in Media Plan Summary: (BETA) In our beta media plan revenue summary feature, flat rate flights were not handled properly.

In Progress

  • Lots of folks jumped in and took our UI 2.0 Open Beta for a test drive last week!  We really appreciate it!  We continue to fix bugs and add features to our new UI.
  • We continue our work decommissioning the Reporting 1.0 system.

 

August 15, 2016

UI 2.0, Open Beta!

  • We are proud to announce that as of 9am Eastern (13:00 UTC) today we have opened the UI 2.0 beta to all Adzerk customers!
  • You can easily access the new UI by going tohttps://app.adzerk.com/ and using your normal Adzerk credentials.
  • You can use the new 2.0 beta UI alongside your normal Adzerk login.  Changing a campaign or inventory setting in one UI also affects the other.
  • The new UI is much faster, more secure, and has much easier filtering and searching.  (more details)

Improvements

  • Improved Data Shipping Documentation: Our optional data shipping feature, which allows you to receive a JSON log record in your own Amazon S3 account for each impression, click, and conversion, just got a big update to its documentation.  Now each field and its source is explained in more detail.

Bug Fixes

  • Date Range Missing Data: For a couple hours last week, some queries where the end date was the same day as today were missing data from the current month.  We quickly identified this bug and squashed it.
  • Ad Chain Passback Code Better Handle Unfriendly Iframes: Our new standard ad chain passback code handles more cases of unfriendly iframes. 
  • Incorrect End Time on Duplicated Campaigns: When a campaign was duplicated, the end time was being incorrectly set to 11:59pm.
  • Floor Price Resetting: When an Auction priority had second pricing enabled and then disabled, the floor price was being reset.

UI 2.0 Improvements & Bug Fixes 

  • Add geo-targeting, site/zone targeting, and keyword targeting summary on the campaign flights list.
  • Add site/zone targeting and distribution percentage summary on the flight creatives list.
  • Fixed: Creatives could not be previewed.
  • Fixed: The third party ad code tab on the sites page was missing the "Select Ad Code" button.
  • Fixed: The "active/inactive" toggle for creatives was failing in a few cases.
  • Fixed: Ad distribution override settings were not hidden when setting ad back to auto balance.
  • Fixed: Prominently list the filters when navigating away and back to a filtered campaign or flight view.

Coming Soon

  • Improved IPv6 & IPv4 Geolocation: IPv6 geolocation has been spotty in many parts of the world, but we are upgrading our geolocation systems to be much more accurate for both IPv6 and IPv4.  This is an important change as the Internet is seeing a big rise in IPv6 addresses due to mobile phones and Internet of Things (IoT) devices.  We'll be rolling out a new geolocation system in the coming weeks.

 

August 8, 2016

Improvements

  • Reporting 2.0 Migration: Over 96% of our customers are now live on Reporting 2.0!
  • Non-tracking Click Macro: Normally, all click URL macros are wrapped in an Adzerk click-tracking URL.  For those rare cases where you need to display the raw URL, however, you can now use the new rawClickUrl macros. (details

Bug Fixes

  • iOS SDK Request Bug: Our iOS software development kit (SDK) was not properly marshalling custom properties on native ad requests.  Big thanks to the Adzerk open source community for the bug report and patch!  (details)
  • Broken 'Third-Party Server' Ad Codes: Our recent ad code improvements introduced a bug when generating an ad code to be served through a third-party ad server.

UI 2.0, Private Beta

  • Added geo-targeting, site/zone targeting, and keyword targeting summaries to the flights list page.
  • Added the "overall served" summary to the campaigns list.
  • Added more internal logging and monitoring.

Coming Soon

  • UI 2.0 Open Beta: We'll open the UI 2.0 beta to everyone next Monday!  Stay tuned for more details!
  • Improved IPv6 & IPv4 Geolocation: This is requiring a bit longer than expected to performance tune.  We'll roll it out once it is fully production-ready.

 

August 1, 2016

Improvements

  • Reporting 2.0 Migration: Over 85% of our customers are now live on Reporting 2.0!  We'll be moving everyone over in phases over the next few weeks.  We will notify you via email a few days before your account is migrated.  Most customers will notice no difference other than the addition of the new click bucketing columns.
  • Performance Improvements: We've upgraded one of our most important technologies underlying our ad-serving.  This has improved our ad-serving performance and unlocked several more performance enhancements that will come soon.  Speed, speed, speed!

Bug Fixes

  • Clash of the Geo-Targeting Rules: If you excluded a region in the United States, then the UI & API would not allow you to include a region from another country.
  • Overridden Percentage Goals: Ads with overridden percentages goals were not serving for some customers.
  • ados.js Cookies for Custom UserDB Keys: When you used your own custom UserDB user key in an ados.js HTML/JS tag, the server was unnecessarily setting a cookie.
  • Campaign List Summary Ignored Flat Rate Flights: (BETA) When using the beta campaign list summary feature, the summary did not take into account the revenue from flat-rate flights.

Coming Soon: Improved IPv6 & IPv4 Geolocation

  • IPv6 geolocation has been spotty in many parts of the world, so we are upgrading our geolocation systems to be much more accurate for both IPv6 & IPv4.  
  • This is an important change as the Internet is seeing a big rise in IPv6 addresses due to mobile phones, Internet of Things (IoT) devices, and US cable companies.
  • We'll be rolling out this new geolocation system this week.  We expect it to positively affect your geo-reporting going forward!

July 25, 2016

Improvements

  • Reporting 2.0 Migration: We now have 55% of our customers live on Reporting 2.0!  We'll be moving everyone over in phases over the next few weeks.  We will notify you via email a few days before your account is migrated.  Most customers will notice no difference other than the addition of the new click bucketing columns.
  • Improved SSL Ad Codes: Now when you generate an ad code via the UI, it will use URLs that are faster and more efficient for static assets.

Bug Fixes

  • Report Failure When Filtering and Grouping By Keyword: In Reporting 2.0, when a report was both filtered by a keyword and then grouping by keywords, it would return an error. 
  • Report Failures When Using Metrocode: In Reporting 2.0, some reports either filtering or grouping by metrocode were failing for some customers.
  • Error Setting Percentage Goals via API: In the UI, you can easily set a flight's percentage goal to above 100%.  This is actually a best-practice for many use cases.  However, there was a bug in the management API that prevented creating flights with percentage goals above 100%.  
  • Zone Targeting Failure For Customers With Many Sites: Some customers, especially those with thousands of sites, could not target by zone in the UI.

UI 2.0, Private Beta

  • Large Numbers Are Easier: You can now use commas and spaces in cap and goal fields to make it easier to enter something like "1,000,000".
  • Improved SSL Ad Codes: Newly-generated ad codes now use more efficient static URLs for SSL requests, just like in UI 1.0.
  • Bugfix: Activating & deactivating creatives did not match old UI behavior
  • Bugfix: Improved validation message when attempting to use non-unique priority weight.

 

July 18, 2016

Reporting 2.0 is Rolling Out!

The big news this week is that we have officially started rolling out Reporting 2.0!  We have started migrating customers in phases, and we will notify you via email before your account is migrated.  Most customers will notice no difference other than the addition of the new click bucketing columns and faster performance when pulling reports through the UI.

Additional Reporting 2.0 Improvements

  • Keyword reporting is now fully supported by 2.0.  If you have the optional Sales App upgrade, then keyword reporting will work for you in 2.0 just like in 1.0.
  • Bugfix: Some customers were experiencing problems with queries that filtered by ad type.
  • Bugfix: Grouping by metrocode when no metrocode data was actually available caused some columns to show up on an additional row, in effect doubling the number of rows in the report. 

 

July 11, 2016

Improvements

  • Reporting 1.0 Data Ingestion Improvements: Over the past few weeks we have "stolen" technology from the Reporting 2.0 pipeline to improve our Reporting 1.0 systems.  These should prevent future reporting delays.

Bug Fixes

  • Fixed: Custom targeting would sometimes fail to validate in the UI.

Reporting 2.0, Private Beta

  • We added lots of performance improvements, and we are working on more!
  • We raised the size of the reports that can be viewed in the UI.  If a report is too large, the UI will have you download it as a CSV instead. 

 

July 5, 2016

Last week we were heads-down working on more performance and stability improvements across the board before we went into the Fourth of July weekend here in the United States.  

Reporting 2.0, Private Beta

  • Performance & Stability Enhancements
  • Also, we're close to re-enabling unmatched keyword reports for everyone.  Stay tuned!
  • More and more customers are migrating over to the Reporting 2.0 beta each week, if you're interested, please let us know!

UI 2.0, Private Beta

  • Stability Enhancements: Intermittent login failures

Improvements

  • Performance Enhancements: Additional frequency capping optimizations

Bug Fixes

  • Sales plan totals went missing for a short time.

 

June 27, 2016

UI 2.0, Private Beta

  • Delete Flights: You can now delete flights in UI 2.0!  This feature was previously only available via the API.
  • Budget Caps: The revenue caps on flights beta feature is now available in UI 2.0.
  • Bug fix: Newly-created Priorities missing from list when reordering Priorities
  • Bug fix: Improved error message when saving a Priority
  • Bug fix: Improved message when deleting Site

Reporting 2.0, Private Beta

  • Reliability & Performance Improvements

Improvements

  • Improved Performance for Heavy Frequency Cap Usage: We've improved our storage of user ad-viewing data.  This will cause ourad engines to work faster, resulting in faster response times for customers with heavy use of frequency caps.
  • Reliability & Performance Improvements

 

June 20, 2016

Reporting 2.0, Private Beta

  • Faster UI Reports: Ever kicked off a small report in the UI and have it take longer than you expected to run?  This is because UI reports often get stuck in line behind the many thousands of API reports we do each hour.  But no more!  Now UI reports using Reporting 2.0 jump straight to the front of the line!
  • Bug fix: Filtering by Advertiser: Reports filtering by advertiser were failing in some cases.
  • Bug fix: Metro Code: Reports filtering by or grouping by metro code were failing.
  • Bug fix: Missing Channel Name: Reports grouping by channel were missing the channel name.
  • Bug fix: Scheduled Report Failures: Some scheduled reports were not sending email on completion, which is almost the same as not running!
  • Bug fix: Big Reports Download: Reports that are too big to load in the UI are being properly detected again.  In those cases, you will be asked to download the report CSV.
  • Become a Beta Tester: We continue to add customers to our private reporting beta each week.  If you're interested, please emailsupport@adzerk.com!

Improvements

  • Include Pricing Data on Native Ad Response: Now if you set includePricingData to true when making a native ad request, we will add a pricing section in the API response that will return the clear price (for second-priced auctions), price and rate type, eCPM, and real revenue for the returned ad.  (more details)

Bug Fixes

  • Report Filtering by Priority: You could add a priority filter in the reporting UI, but then we were silently ignoring it.  This affected both Reporting 1.0 & 2.0.
  • Image Upload Failures: Some images would fail to upload when configuring image creatives.

June 13, 2016

Reporting 2.0, Private Beta

  • Bug Fix: Missing Events: Custom events that should have been included in some queries were not.
  • Performance Improvements: We've sped up several slow-poke queries.
  • Reliability Improvements: We continue tuning our Reporting 2.0 backend systems to make them more reliable.
  • Become a Beta Tester: We continue to add customers to our private reporting beta each week.  If you're interested, please emailsupport@adzerk.com!

UI 2.0, Private Beta

  • Our open beta will be here soon!

Improvements

  • Performance & Reliability Improvements: We added some optimizations to better handle email ad traffic. 

 

June 6, 2016

Reporting 2.0, Private Beta

  • Price & Rate Type Included: Price and rate type fields are now included in the Reporting 2.0.  Group by flight to see these fields.
  • CSV Export Format Fix: When using the "Export to Excel" feature with the Reporting 2.0 data source, it would download in a new format.  Now it downloads in the same format as the original Reporting 1.0.
  • Country Code Fix: In some cases, reports that included a country code column were failing when requested via the Reporting 1.0 UI or API and generated with the Reporting 2.0 data source.
  • Report ID in UI: Now, when you generate a report via the UI you will see a "Report ID".  Please feel free to cut & paste this ID when emailing support@adzerk.com regarding report issues.  It will greatly speed up our investigations.
  • Become a Beta Tester: We continue to add customers to our private reporting beta.  If you're interested, please emailsupport@adzerk.com!

UI 2.0, Private Beta

  • Custom fields for flights are now supported.
  • Bug fix: The campaign active/inactive toggle was not working.
    • Bug fix: You could not create multiple campaigns in a row from the advertiser page.
  • Bug fix: Nameless flights now display with a system-generated name like in UI 1.0.
  • Bug fix: Creatives would sometimes disappear from flight page when saving flight.
    • Bug fix: Ad tags would sometimes generate without a site ID.
    • Bug fix: Ad tags for creatives could sometimes generate for an incorrect site.
  • Bug fix: We've removed the unused "fill rate" checkbox on the priorities page.
  • Bug fix: The UI was sometimes remembering the wrong organization on the login page.

 

Improvements

  • Commas In Caps & Goals: Now, when specifying an impression cap or goal, you can use commas or spaces to make reading all those zeroes easier!  For example, you can now put in "10,000,000" or "10 000 000" to mean 10 million impressions.
  • Bug fix: Click Bucketing Columns & Export to Excel: When using the "Export to Excel" feature in the UI, if click bucketing was enabled for your account, then some columns would be missing headers.  
  • Bug fix: Searching Campaigns by Salesperson: When searching by salesperson on the campaign page it was leaving out disabled campaigns.
  • Reliability & Performance Improvements: Lots of improvements to our internal systems to make them more reliable and better performing.

 

 

May 31, 2016

Reporting 2.0, Private Beta

  • Full Production Load: We have performance tuned Reporting 2.0 to now handle the full 1.0 production reporting load with no problems!  This is a huge milestone towards making 2.0 the default reporting system for all customers!
  • More Performance Tuning: We're still tweaking the new query engines to best handle production traffic.  We apologize for recent slowness, but you can't make an omelette without breaking a few computers.
  • Click Bucketing Now Built-In: When using the "Reporting 2.0" data source when using the 1.0 UI or API, you now get all click bucketing columns in the results!
  • Grouping by Week:  We now support grouping by week, just like 1.0.  This is especially helpful for those end-of-month scheduled reports.
  • Rate Limiting Removed Temporarily: We have disabled our beta testing rate limiting on 2.0 for now.  We will be reinstating a more robust rate limiting soon.
  • Reliability & Robustness Improvements: We've added several improvements to both our data ingestion and our report querying systems in Reporting 2.0 that keep the systems running better, faster, and more reliably!
  • Become a Beta Tester: We continue to add customers to our private reporting beta.  If you're interested, please emailsupport@adzerk.com!

UI 2.0, Private Beta

  • Generate Ad Codes: Can now create ad codes for sites.
  • Bugfix: Creatives with metadata would not upload.
  • Bugfix: Users would often get "cannot connect to server" errors.
  • Bugfix: The "file upload" field on creatives would stick around when it was clearly no longer needed.
  • Bugfix: Using UI 2.0 would not register your IP address as a source of test clicks for click bucketing.
  • Regression Testing: We went through the entire UI 2.0 with a fine-toothed comb to identify the last few remaining bugs.
  • Open Beta Soon: We're crushing these last few bugs and will move to Open Beta in early June!  Stay tuned!

Improvements

  • Big Infrastructure Changes: We've been separating our servers into groups to improve performance and relability.  This also introduces "bulkheads" between groups of customers.  If we experience performance problems or an outage in one group, then this should only affect that group is much less likely to affect all customers.  We also made changes to how we scale servers.  They come into service much quicker, allowing us to respond to a sudden increase in impressions much faster.
  • More Click Bucketing De-Deduplicating: (BETA) If a single IP address clicks an ad more than once in a 30-day period, we only count the first as a unique click and all others as duplicates.  We had been doing this for a 24-hour period, but we've now extended that time period to 30 days.  (more details)
  • Security Improvements: SSL updates to cover recent vulnerabilities.

Bug Fixes

  • Fixed: Advertisers logged into Adzerk could not export a report to Excel.
  • Fixed: Creatives containing metadata could not be reused on another flight.
  • Fixed: Copying an RTB flight would not copy the RTB fields on the creatives.
  • Fixed: Copying a campaign would always create an active campaign, even if the original campaign was inactive.

May 23, 2016

 Improvements

  • Frequency Capping by Advertiser & Campaign: (BETA) You can now frequency cap at the advertiser and campaign level as well as the flight and ad level.  Further, you can now specify that specific campaigns, flights, or ads do not count towards their parent caps.  (more details)
  • Ad Code Overrides: UserDB Id, IP Address, and User Agent: Now you specify your own UserDB ID, IP address, or User Agent string when making display ad calls using our HTML/JavaScript ad codes.  Being able to specify these manually have long been a part of our native ads API, but now they're easy to use via ad codes too.  (more details)
  • Regular Expressions in Custom Targeting Zerkel: Now you can use full regular expression matching in our custom targeting Zerkel queries.  (more details)
  • Internal process improvements around our creative templates beta feature allows us to create these faster and easier.  If you're interested in using creative templates, please ask support@adzerk.com.
  • Several internal robustness and performance improvements.  Just keeps getting better!

Bug Fixes

  • Could Not Use Network Zones in Management API: In some cases our management API would not allow network zones when setting up site/zone targeting on flights or ads.  Now it always properly accepts them.
  • Custom Templates Would Not Save: Unless the custom template included an image variable, it would not save. Fixed!

UI 2.0, Private Beta

  • Our main focus this week and next is deep regression testing to flush out the last bit of bugs.  
  • We are looking to open this beta for all customers in June.

Reporting 2.0, Private Beta

  • Click Bucketing included in Reporting 2.0:  Our beta Click Bucketing feature is now enabled for everyone using the Reporting 2.0 API.  Click bucketing is the future, live it now!
  • Added Price & Rate Type to Reporting 2.0 Output: Our beta Reporting 2.0 API now includes the missing Price and RateTypefields.
  • Our focus on Reporting 2.0 right now is on performance testing and tuning.  We've adding several optimizations to make it scale towards our current production reporting load and beyond.  Stay tuned!

 

May 16, 2016

Improvements

  • Creative Templates: Rich Media Creatives: (BETA) To handle rich media creatives, you must write HTML, JavaScript, and/or CSS directly into the target page and not embed it within an iframe tag.  We now support that behavior in both traditional creatives and creative templates.  Note this works similar to our ZerkML tags but is implemented differently.  Please indicate this is a "rich media creative" when requesting a creative template via support.
  • Click Bucketing: Network Ad Detection: (BETA) Previously, our click bucketing feature would ask you if a creative was a network ad (being served by a third party network via a tag) for all kinds of ads.  However, now it's a lot smarter about image and RTB ads, and it only asks you if an ad is a network ad for HTML/JavaScript ads.
  • Performance Enhancements: Our UserDB cookie syncing feature is now much more efficient, lowering processing time in most cases.

Bug Fixes

  • Native Ads Missing Title: The Title field in the data section went missing for a while.  We found it.
  • RTB: Zemanta Click Tracking: (BETA) Click tracking was broken on Zemanta RTB creatives.

UI 2.0, Private Beta

  • Ad codes for creatives were using incorrect ID.
  • Adding multiple creatives was unexpectedly reusing uploaded image.
  • Flight appeared to be missing after creation.
  • Frequency capping settings were not saved when updating a flight.

Reporting 2.0, Private Beta

  • Tuning:  We continue to tune our 2.0 reporting system in preparation of full production load.
  • Big Performance Update: We rolled out a huge performance improvement last week that vastly decreased the amount of time that the majority of reports take.  

 

May 9, 2016

Improvements

  • Auction & RTB Bid Density added to Data Shipping: For our data shipping customers, you will notice two additional fields per impression: AuctionBids and RtbBids.  These values tell you how many direct-sold and RTB bids are participating in each ad selection.  (more details)

Bug Fixes

  • Truncate Whitespace on Keywords: Some customers were seeing that if whitespace were added to the end of keywords in their keyword targeting, then the flight would not serve properly.  We now correctly trim all whitespace.
  • Performance Improvements: We've been beefing up our Reporting 1.0 data pipeline internals.

UI 2.0, Private Beta

  • So Close, So Very Close: There's only a couple last items to polish off before we share this beta release with everyone!

Reporting 2.0, Private Beta

  • Performance Tuning: We're working hard tuning the new Reporting 2.0 query system.  We're load testing and tweaking queues in preparation to handle all production reports.
  • Scheduled Reporting: Duplicate Emails: The new scheduling feature for Reporting 2.0 was sending duplicate emails.  Fixed!
  • Scheduled Reporting: Broken Daily Reports: The new scheduling feature for Reporting 2.0 was breaking for single-day reports.  Fixed!

 

 

May 2, 2016

Bug Fixes

  • Default Rate Type Caused RTB Flights to Not Serve: RTB flights must be "CPM" to run properly, but the UI used to default them to "Flat Rate".  Now all RTB flights show an uneditable rate type of "CPM".

Reporting 2.0, Private Beta

  • Scheduled Reporting: Now when you choose the data source of "Reporting 2.0" and schedule a report, that report will be ran via the 2.0 backend!
  • Performance Improvements: Ad Types: Added an optimization for queries filtering or grouping by Ad Type (aka ad size).

User 2.0, Private Beta

  • Added custom fields for campaigns. (Flights coming soon!)
  • Added creative-level site targeting.
  • Added creative-level zone targeting.
  • Added creative-level start/end date override.
  • Added several reliablity improvements.

 

April 25, 2016

Improvements

  • Click Bucketing (beta): Now in beta testing, we've revamped how we count invalid clicks, tallying each into a bucket that explains why it's invalid.  Further, we've added test clicks (originating from IP addresses that have accessed the Adzerk UI, API, or from a customer-defined list) and much more aggressive duplicate click detection based on IP address. (more details)
  • Zemanta RTB Integration (beta): Also added to our beta testing program this week, Adzerk can now request native ad RTB bids from the Zemanta One platform.
  • Multiple Zones per Request: Now when you specify multiple zones in a request, if a specific zone is used in zone targeting, then that zone will register as having the impression.  You can now also specify multiple zones when using an ados.js ad code.

Bug Fixes

  • Missing Suspicious Clicks (beta): Our suspicious clicks tracking system (still in beta) was not writing suspicious clicks counts.  Now fixed!
  • API Explorer: Filtering Reports by Country Code: Our reporting endpoint in the API Explorer was not filtering by country codes.
  • Mass Edit Flights (beta) Clicking the "select all" checkbox on the campaign page to choose all flights is now a bit easier.  Previously the button was a bit picky on where you clicked it.  Now it's much more easy-going.

Reporting 2.0, Private Beta

  • We've worked out the last few data discrepancies between 1.0 and 2.0!
  • Lots of robustness improvements.

 

April 18, 2016

Improvements

  • RTB Native Format: Now it's easier to specify the output of native RTB ads by choosing either a simple "image" output or specifying a custom format using all of the normal Adzerk macros and tokens you're used to, plus a few new RTB-specific ones. [more details]

Bug Fixes

  • Bidtellect RTB ads via Native Ad API: RTB ads from our partner Bidtellect were in some cases not coming through our Native Ad API correctly.  
  • Unable to Filter Reports by Flight (BETA): Beta testers of our new searchable dropdowns found a bug where the flight dropdown on the report page remained empty after choosing a campaign.  This made it impossible to filter by flight.  

UI 2.0, Private Beta

  • Added frequency capping to the flight page.
  • Added the ability to duplicate flights.
  • Fixed a bug where some flight fields were not being saved: Cap Type, Daily Cap, Lifetime Cap, and Custom Targeting.

Reporting 2.0, Private Beta

  • Now when a report's results are too large to display in the UI, the report will instead download as a CSV file suitable for use in Excel.
  • Added support for filtering and grouping by channel ID in the 2.0 API.
  • Fixed a bug where when trying to export a 1.0 report, you got the 2.0 CSV instead.  (This only affected beta testers.)
  • Fixed a bug where requesting an in-progress report could return an error.
  • Added much more helpful error messages when trying to queue a report with invalid parameters via the 2.0 API.
  • Fixed a bug where the start and end date times would return in slightly different formats for monthly vs daily reports.  This caused some monthly reports to fail in the UI.
  • Lots of internal robustness improvements on both our reporting service and incoming data pipeline service.  "It's gettin' real, y'all!"

Coming Soon - Click Bucketing 

Although it has long been an industry standard for ad services to just mysteriously hide invalid clicks, Adzerk will buck that trend with our forthcoming "Click Bucketing" feature.  All clicks will be accounted for in different "buckets" that tell you exactly why Adzerk considered them valid or invalid.  More details soon!

 

April 11, 2016

Improvements

  • API Explorer (beta): The long-awaited, fully-interactive version of our API documentation has finally arrived!  Just plug in your API key and go!  The API Explorer will show you detailed request and responses without requiring any coding.  It's also open source so feel free to send us comments or pull requests!
  • Internal monitoring improvements: We're continuing to improve our ability to spot and respond to potential issues before they become problems!

Bug Fixes

  • Broken Ad Macros: For a short period, we broke any creative macros starting with "ad.*"  So sorry about that; all fixed now!

Reporting 2.0, Private Beta

  • We've expanded our private beta and have several customers actively testing it.
  • We've already found a couple bugs and are busy fixing them.
  • This is a big milestone step towards rolling this massive internal upgrade to all our customers!

 

April 4, 2016

Improvements

  • Faster Loading Campaign Page (Beta): We just added a huge speed improvement for loading the list of campaigns.  We're eager to get this fully beta tested so we can roll it out to everyone!
  • API: Filter Flights & Campaigns by Active/Inactive: Now in theFlight List and Flight List by Campaign management API endpoints you can specify an optional isActive parameter that will filter out active or inactive flights.  [more details]
  • Reliability Improvements: We've added several internal improvements to our reliability and self-monitoring this week.
  • Security Improvements: Please note as a rule we don't discuss security improvements details, but rest assured we are continuously looking for ways to improve our defenses against would-be attackers.

Bug Fixes

  • Flight Priority Affecting Reports: Changing a flight's channel priority could affect how it showed up in reports, if filtering or grouping by channel or priority.  This meant that running a report on different days might return different numbers, if the flights in question had moved. However, we now only use the flight's channel and priority at the time the impression or click occurred when calculating reports.

UI 2.0, Private Beta

  • Added links back to the advertiser from the campaign page.
  • Added links back to the advertiser and campaign from the flight page.
  • Can now edit channel priority sort order.
  • Flight page side-navigation is now functional.
  • Added "Custom Targeting" to flight page side-navigation.
  • Improved flight page styling.

Reporting 2.0, Private Beta

  • We continue to work diligently on our Reporting 2.0 features.  
  • We are actively expanding our private beta now, adding more customers who are eager to help us test out the brand-spanking new reporting system.  
  • If you're interested in being a private beta tester, please contactsupport@adzerk.com.

 

 

 

March 28, 2016

Improvements

  • Device Macros in Creatives: Info about the viewing device is now available for use in creatives via "device.*" macros. more details
  • Creative & Flight Names in Creatives: The human-readable names for flights and creatives are now available for use as macros in creatives.  more details
  • Advertiser Filtering on Campaigns Performance Improvements (BETA): No more long list of advertisers on the campaign list.  It's much easier to select which advertiser to filter on by name, rather than searching through a potentially huge list.  This also speeds up loading of the campaign page.
  • Adzerk Ruby Library & HTTPS: The open source Adzerk Ruby gemnow uses secure HTTPS for all communication. 
  • Security Improvements - SSL Updates: All of Adzerk's SHA1 SSL certificates have been replaced by SHA2 SSL certificates.  Enjoy the extra security!

 

March 21, 2016

 Improvements

Bug Fixes

  • Advertiser Budget Caps Defaulted to Zero (BETA): We now no longer save $0 budget caps for advertisers with no budget cap.
  • "Do Not Track" Ignored on Flight Copy (BETA): Copying a flight with "Do Not Track" settings on its creatives will now correctly also copy the "Do Not Track" creatives.

UI 2.0: Private Beta Update

  • Generate ad codes for a specific campaign, flight, or creative.
  • Removed the unused "name" field when editing/creating custom Ad Sizes.
  • Advertiser name on the campaign page is now a link to the advertiser page.
  • Enable searching for inactive campaigns.
  • Make campaign page the default page on login.
  • Show a message when trying to view a non-existent flight or campaign.

Reporting 2.0: Private Beta Update

  • Our engineers now have an internal version of the Reporting UI that can pull data from both the 1.0 and 2.0 data sources.  It's being internally tested and tweaked now!
  • This means that very soon I'll be reaching out for private beta testers who can help us test by running their reports against both the 2.0 and 1.0 data sources.  Stay tuned!

[1] Please note that custom domains are a paid add-on.  If you're interested in adding one please contact support@adzerk.com.

 

March 14, 2016

Improvements

  • API: Exclude Flights on "Get Campaign" Endpoint:  Historically, when you've requested a Campaign object via the management API you also receive all of its contained flights.  However, when you don't want all the flight data they still add latency to the request.  To get just the Campaign information, you can now pass an excludeFlights parameter.  more details
  • Custom Targeting: Bigger Zerkel: We've added performance enhancements around larger custom targeting statements in ourZerkel query language.  We still limit most custom targeting to 1KB, but for cases where you need larger queries, you can ask support@adzerk.com to enable "bigger Zerkel."
  • Reliability Improvements

UI 2.0, Private Beta

  • Support UTF8 Characters: Our UI 2.0 was not displaying some UTF8 characters correctly. (Chinese, Japanese, Korean, etc.)

 

March 7, 2016

Improvements

  • Arrays in Creative Templates (BETA): Now you can include JSON arrays in your creative templates.  The new `array` type creates a text area that treats each line as a value in your array.  Very useful for JSON creatives.

UI 2.0 Improvements & Bug Fixes

Starting this week we're sharing our UI 2.0 updates in preparation of our upcoming open beta release.  To all those folks in the private beta, we really appreciate the testing and feedback you're giving us!

  • Flight Day Parting: We've add the "Day Parting" settings section to the Flight page.
  • Flight Distribution: We've added the "Distribution" settings section to the Flight page.
  • Creatives by Advertiser: We've added the "Creatives by Advertiser" page to the Advertiser page.
  • Remember Last Organization: We now conveniently remember the last organization name you used.
  • Remember Pagination Settings: We now remember the page-size you select for each table in the UI, so for example have 100 flights, 25 campaigns, etc.  This lets you customize our many tables to best fit your specific usage pattern.
  • Start Dates Mismatch: Some folks were seeing different campaign start dates in the old UI vs UI 2.0.
  • Saving End Dates: We sometimes were not setting the end dates correctly when creating/updating flights.
  • Number Formats: Some of our numbers (including impression totals) were showing as "100.00" instead of "100".  We've removed the unnecessary decimal digits.
  • Overactive Campaign Status Bar: In some situations, the campaign status bar would jump clear off the screen!  Down boy!
  • Better Login Error Messages: Give correct error message if organization not found when attempting to log in.

 

February 29, 2016

Bug Fixes

  • Dynamic Site Selection Fallback: If you are using dynamic site selection we will fallback to a specific site if the referring domain isn't on your account. There was an issue that prevented fallback impressions from being served. more details

Coming Soon

For several long months now we've been heads-down quietly working on a couple of very, very big upgrades.  I'm mentioning them now to give you a sneak peak of what's to come in Q2 of this year when they go into full open beta.

  • Reporting 2.0: We've been rewriting our reporting infrastructure from the ground up.  We're using state of the art data warehousing technology under the hood that is drastically increasing our ability to store, process, and report on all the data you'd ever want.  Had issues with reporting in the past?  Slow?  Some filtering or grouping options you wanted just not supported?  Stay tuned.
  • UI 2.0: We've also been rewriting our UI from the ground up.  It's beautiful, but more important -- it's FAST.  Super fast... like 88 mph going back to the future fast.  Again, stay tuned!

 

February 22, 2016

Improvements

  • BETA: Improved Reporting Filter Selection: If you have lots of advertisers, campaigns, or sites, you've likely felt our old dropdown filter selection on the reporting page was pretty inconvenient.  (To put it nicely!)  Well, struggle no more!  We just released into beta a feature that makes it easy to search for advertisers, campaigns, and sites by name when creating a report.  No more huge dropdown!  If you're interested in beta-testing this feature, please email support@adzerk.com.

Bug Fixes

  • Iframe postMessage bugs: Some who were using `window.postMessage` JavaScript events to handle unfriendly iframes were experiencing a bug where our ados.js code might respond to their events.  Consider these wires uncrossed!
  • Mangled RTB Floor Prices: This is a weird one.  If you were editing an RTB creative and then hit escape rather than the "save" button, then in some cases it would append the floor price to the existing floor price.  For example, if you saw a floor price like "2.50 2.50 2.50" instead of just "2.50" then you were bit by this bug.

 

February 15, 2016

Improvements

  • API: Manage Passbacks: Now you can completely manage your passback flights via the management API!  more details

Bug Fixes

  • BETA: Same Advertiser Exclusions in Second Price Auction:Previously it could have been possible for the same advertiser to compete with themselves in a second-price auction.  Our second-price auctions now ignore all losing bids from the winning advertiser when calculating the second price. more details
  • BETA: Second Price Auction with Remainder, Single Bid: Previously, if a second-price auction had only one bid, and the remainder percentage was in play, it was possible for that single bid to serve at full price.  Now, however, if a second-price auction has only a single bid and the remainder percentage is in play, then an eligible impression from the next highest priority will serve. more details

 

February 8, 2016

Improvements

  • API: Pagination: We now have paging for all list endpoints!  List Ads for a Flight, list Flights for Campaign, list Ad Types, etc. You can request just what you need, or you can still request All The Things. Simply add an optional `pageSize` to limit what you get back. Want another page?  Also pass a `page` with your `pageSize` to get page 2, 3, etc.  more details
  • API: Exclude Ads on Get Flight endpoint: Historically, when you've requested a `Flight` object you also receive all of its contained ads. However, when you don't want all the ads they still add latency to the request. To get just the Flight information, you can now pass an `excludeAds` parameter.  more details
  • Internal robustness improvements

Bug Fixes

  • BETA: Mass Edit Flights: Our beta testers reported a bug where the campaign settings page would have no "Save" button when the Mass Edit Flights beta feature was enabled. 

  

February 1, 2016

Improvements

  • Consistent Date Format in API: In the Management API, we had several endpoints that took inconsistent date formats.  This was clumsy and cumbersome and was the result of our API growing organically over time.  No more!  

Now for every date input or output field in the management API, there is an ISO 8601 compliant date format that takes dates like `2016-02-01` for February 1st, 2016.

As an example, say we have a `StartDate` input parameter that is echoed in the output on an endpoint.  We would now accept either the old `StartDate` parameter in its old date format or a `StartDateISO` parameter that is ISO 8601-compliant.  We will prefer the ISO parameter if both are set.  

Further, in the resulting payload, we would return both a `StartDate` value in the old format and an equivalent `StartDateISO` value in the standard ISO 8601 format. 

In this way, we can easily provide backwards compatibility for our existing customer integrations while recommending the ISO-compliant versions for new code.  

  • Conversion Tracking URL via API: You can now request a conversion tracking pixel URL for an advertiser via the management API.  more details

Feature Removal

  • The Forecasting tool on the Reporting tab was superseded a year ago by the Forecasting tool in the Sales App add-on.  We have removed the old "Forecasting" tool as of today, February 1st, 2016. We encourage anyone who is actively forecasting to use the newer, more robust Sales App tool.  Please email support@adzerk.com if you're interested in adding the Sales App to your Adzerk account ($500/month).  

 

January 25, 2016

Improvements

  • Safe Harbor Certification: Adzerk has been certified as complying with the US/EU and US/Swiss Safe Harbor Privacy Principles of notice, choice, onward transfer, security, data integrity, access, and enforcement.  More details on our Ad Server privacy page.
  • Keyword Optimization API: You can now mark a Priority as being keyword-optimized via the management API.  Previously this only worked via the UI.  If you heavily rely on keywords to choose which ad to display, this can greatly improve your performance.  You can set IsKeywordOptimized when creating a priority on your channel.  More details
  • Conversion Tracking API: You can now mark a Flight as tracking conversions via the management API.  Previously this only worked via the UI.  You can set IsTrackingConversions when creating or editing a flight. More details

Feature Removal 

  • The Forecasting tool on the Reporting tab was superseded a year ago by the Forecasting tool in the Sales App add-on.  We encourage anyone who is actively forecasting to use the newer, more robust Sales App tool.  Email support@adzerk.com if you're interested in adding the Sales App to your Adzerk account ($500/month).  We will remove the old "Forecasting" tool onFebruary 1st, 2016.

January 19, 2016

Improvements

  • Creative Templates: (BETA) Do many of your ads follow a standard template, and you just want to just plug in the values each time?  Do you find yourself fiddling with repetitive JSON, XML, or HTML/JS, and you'd rather just fill out a simple form and have the computer do all the work for you?  Creative templates is your answer!  Email support@adzerk.com if you're interested in beta testing this feature.
  • Target Blocked Items: If you have used Behaviorial Targeting in the past to block users from seeing additional ads for specific advertisers, campaigns, flights, or creatives, you can now target those users via custom targeting.  You can use a Zerkel string like"$user.blockedItems.advertisers contains 12345" to target users who have blocked advertiser number #12345.  

Bug Fixes

  • If your report contains custom events, then the custom event columns used to sort randomly.  Now they always sort by the event ID keeping similar events grouped together.

Feature Removal

  • The Forecasting tool on the Reporting tab was superseded a while ago by the Forecasting tool in the Sales App.  We will be removing the old Forecasting tool on February 1st, 2016.  We encourage anyone who is actively forecasting to use the newer, more robust Sales App tool.  Feel free to hit up support@adzerk.com if you're interested in adding the Sales App to your Adzerk account.

 

December 4, 2015

 Beta Feature Improvements

  • NEW: In addition to capping your flights on impressions, clicks, or conversions, now you can also cap them on revenue!  Our "Budget Caps" feature allows you to set daily and lifetime budget limits at the flight, campaign, and advertiser levels!  [More details]
  • FIXED: Archived flights were still serving in some situations.

Improvements

  • FIXED: Some ads in an auction priority were not using their eCPM but their rate, causing the auctions to award the wrong winner.  This was rare but obviously concerning.
  • Performance improvements.

 

November 20, 2015

Improvements
  • You can now use spaces in your keywords!
  • BETA: Filtering Campaigns & Flights: You can now filter campaigns by name and flights by name, status, and delivery status!  For example, you can show only campaigns that have "test" in their name.  If you're interested in beta-testing this feature, please let us know!
  • BETA: Targeting Optimization: Added new endpoints for viewing and reseting weights by site when optimizing CTR.  If you're interested optimizing your CTR by balancing ads between sites and are willing to help us beta test this feature, please let us know!
Bug Fixes
  • Setting unknown goal types via the API was causing some ads to serve beyond their expiration date.  No longer!

 

November 11, 2015

New Stuff!
  • Placement Limit Per Advertiser  This works in tandem with our "no duplicates" feature, allowing you more flexibility.  For example, now you can configure a situation where an advertiser allows up to three of their product ads on a single page, as long as each product is unique.  You can configure one campaign per product, set each flight to "no duplicates at the campaign level" and set the advertiser placement limit to three.
  • Prevent Conflicting Targeting on Flights No longer do you need to worry about painting yourself into a corner by configuring conflicting inclusion/exclusion rules that keep the ad from serving.  Now if you accidentally set a list of targeting rules by the UI or API that conflict, you will get an error message.
Beta Feature Improvements
  • Targeting Optimization Now respects suspicious clicks when optimizing for click-through-rate (CTR).  Also, we fixed a bug where making changes via the UI could sometimes overwrite changes made through the API.  Now the UI and API play nicely together!  Animal crackers for everyone!
  • New UI In same cases the "x" / clear button would incorrectly display on non-typeahead fields. Fixed!

 

Have more questions? Submit a request

Comments

Powered by Zendesk