October bug fixes

October was largely dominated by updates to AdWords, Bing Ads, and total overhaul of our platform's design, but we found some extra bugs to squash as well:

  • In order to avoid a service interruption, we updated our Bing Ads API from v9 to v11. This was a parity update, so no features were introduced, but it was necessary to keep Bing Ads running.
  • PDF Exports were briefly knocked offline when a JavaScript library was removed accidentally. That library was restored, which brought PDFs back online.
  • Clicking too quickly during our Onboarding step upon creating your account resulted in an error, preventing the process from moving forward.
  • There are a few Facebook Ads custom metrics that require particular data levels to display data. We've improved the logic in the Custom widget so that these metrics will be hidden unless the appropriate level is set.
  • Video data wasn't displaying in Facebook Ads. That data has been fully restored in our platform.
  • Big requests for Facebook Ads data were timing out, so we've adjusted our time out window for this data source.
  • We weren't displaying a horizontal scroll bar in the new design, which made viewing data from tools like Link Manager challenging. That scroll bar has been added back in.
  • We updated Google AdWords to the latest version. Similar to the Bing Ads update, this was for feature parity, rather than for new features and improvements.

A shiny new Raven experience

Welcome to the new Raven! We've given the whole platform a well-needed sprucing-up with our first design refresh since 2013. All of the tools you rely on for your digital marketing needs are still present but with more horizontal space, a more modern design, and even some bonus features.

Here's what's different:

  1. The left toolbar slides in and out, giving you more space to work in each tool.
  2. Tools have been slightly rearranged, with the Campaign section divided into three new sections: Analytics (containing Google Analytics, Site Performance, Competitor Manager, and Keyword Manager), Settings (containing Event Manager, Tag Manager, and Campaign Settings), and Email Metrics.
  3. Reports are now at the top of the toolbar, instead of at the bottom.
  4. All global icons — Help, CRM, Tasks, and Notifications — appear at the top-right of the top navigation.
  5. Profiles and Campaigns are both now searchable from the top-menu.

We'll be adding some more features and improvements in the weeks and months to come.

September bug fixes

While gearing up for a big change to Raven, we were able to squash a bunch of bugs across Raven in September:

  • Although we were looking for 301, 302, and 302 Redirects with Site Auditor, we were missing some of the more obscure redirects. We've broadened this out to accept and follow any 3xx redirect that our crawler hits.
  • Our connection to Emma in Email Metrics needed a little attention to get data back up and running from their API.
  • In certain Facebook Ads columns, we were sorting numbers alphabetically, rather than as integers. Sorting will work correctly for these columns in both the tool and reporting.
  • We still had a couple of references to the long-defunct tool Social Stream lurking around the connection wizard. Whoops!
  • The Domain Expiration metric in Research Central and Site Performance had gone dark due to an API issue. That's back up and running wherever that metric existed.
  • Semantic Analyzer and Neighborhoods in Research Central were both failing to return data due to the inclusion of extraneous information in our requests for data from Majestic and Moz. Those are both back in working order.
  • If you added a question mark to a tag, we were replacing that symbol with an HTML number and failing to filter properly based on that tag. The symbol will stay a symbol now.
  • Our login form wouldn't remember your credentials but now, for most browsers, the auto-remember feature has been turned on. Some browsers won't acknowledge our AJAX-based login form as something they can remember the username/password for, but most will work fine.
  • Some more cases of Google AdWords failing to show all available MCC and individual AdWords accounts cropped up, which we've further streamlined.
  • We were hitting our Google Analytics quota during heavy reporting days, so we're scaling back some of the automated retries on requests that will never return data. That'll result in fewer "Quota Error" messages in reports.

August bug fixes

Several bug fixes were launched during August:

  • Australian states have been added as an option in Payment Details.
  • Read-only users aren't allowed access to Research Central, but there were still links that would point them to the tool in Keyword Manager. We've removed the auto-research links from Keyword Manager for these users.
  • We were showing the wrong subtitle for Quality / Authority Metrics in Research Central.
  • If no comparison data existed for a Facebook Ads, the formatting on the table would get thrown out of whack. This data more properly mimics the styling seen in Google Analytics.
  • After simplifying the Search Analytics and Google Webmaster Tools website selection process, there were some instances where unverified versions of websites could prevent the full list of available Search Console properties from appearing. Now all verified Search Console properties will appear in the Settings menu.
  • If your Google Account had access to both a AdWords MCC and an individual AdWords account, we were only showing data from the MCC. You'll see all data for all configurations of AdWords accounts going forward.
  • Facebook Ads levels weren't paying attention to the date range set in your section, so menus like campaigns would only show the current list of active campaigns — even when reporting on a different period from the present.
  • When importing social media widgets in WYSIWYG Reports, we were retaining the account name, which led to users thinking that the data was bleeding between Campaigns. We've removed the subtitles where necessary.
  • There were some instances where Google Analytics reports returned a quota error instead of the data that our customers were expecting. We've resolved this in two ways. First, we've requested (and received!) a huge bump in our daily maximum for API requests. But, beyond that, we're now squelching any requests that would result in an error from Google before they get to the API.

Duplicate widgets and sections in WYSIWYG Reports

As part of our ongoing efforts to make the process for building reports in WYSIWYG Reports more efficient, we've rolled out a long requested feature that will make creating and customizing your reports ultra simple: duplication.

Raven customers can now duplicate both sections and widgets with just a single click. To duplicate an entire section, click the new duplicate button in the top-right corner of the section:

Voila! An exact copy of that section will appear at the bottom of your report. From there, you can drag the section wherever you want, by clicking the drag point at the right of the contents menu on the left of your report.

Only need to duplicate one widget? That's easy too:

The duplicate button works for every widget and section in WYSIWYG Reports. Our goal is to make reporting easy, and we're thrilled to bring these improvements (as well as the new Add Another Widget button) to all Raven customers.

Legacy Dashboard removed from Raven

Three years ago, we launched WYSIWYG Reports and an upgraded Dashboard experience based on the experience of our reporting tools. Some customers have had access to our older Dashboard tool — since retitled to "Legacy Dashboard" — but time has finally come to fully retire the tool.

Why did we remove Legacy Dashboard? A few reasons:

  • Changes to the Google Analytics broke several of the Dashboard Modules, particularly anything reporting on Avg. Time on Site (which doesn't exist as a metric on Google's end anymore).
  • A scant handful of customers still had access to the Legacy Dashboard tool, and almost none of those customers ever looked at it.

Removing old tools cleans up our code base, allows our developers to streamline methods that are complicated by old tools, and frees us to take steps forward.

For most of our customers, this will have zero impact on their experience; any account started since September 2014 didn't have access to this tool. But, for anyone who did have access to Legacy Dashboard and used it, we'd welcome your feedback on how we can improve our Dashboard tool.

Add Another Widget button added to Custom Widget creation

Our developers have been hard at work on some quality of life improvements when working with WYSIWYG Reports. The first of those improvements comes in the form of a simple button: Add Another Widget.

Clicking the Add Another Widget button will add your widget and then bring up a new editor window with the same settings as the widget you just added.

Used well, the Add Another Widget button will make your report creation much more efficient, especially when adding multiple widgets with the same settings: Advanced Segments, social media accounts, AdWords campaigns, and more.

Added 5 to Max Results setting in WYSIWYG Reports

Every looked at a table and thought that 10 results were twice as many as you really needed for reporting? You can now limit the maximum results in WYSIWYG Reports to just 5 results:

The new setting for Max Results is available for all tables in WYSIWYG Reports.

Instagram Ads data available as charts in WYSIWYG Reports

Agencies running advertisements on Instagram will be excited to learn that this data is now reportable in chart and graph form in WYSIWYG Reports. Similar to how the demographics and other break downs work, Instagram data can be reported by adding a custom widget and choosing the Custom metric.

All line graphs, bar charts, and pie charts are able to change the Break Downs setting. If you select the Publisher Platform option, Instagram data will display in the report.

July bug fixes

Our developers put a big dent in our reported bugs this month, fixing more than a dozen different issues in the platform. See anything that doesn't seem right? We're listening! Drop us a line from the Help box in the bottom-right of your Raven account.

  • In some cases, Google AdWords was displaying blank responsive ad previews instead of embedding image ads for Display Network ads. These will render correctly now.
  • If you cancel your account and attempt to log back into that account, we were showing an unhelpful error message suggesting that your password was incorrect. Now, for inactive accounts, we'll show an error message indicating that your account is inactive and suggests contacting support for help.
  • Table filters weren't applying to Facebook Ads tables, but are functional now.
  • The Social Network Sessions and Social Network Values widgets in Google Analytics reporting had metrics options that weren't in use. We removed these from custom reporting.
  • Bing Ads was failing to bring back ad previews due to an API issue. That has been corrected.
  • When importing a report in WYSIWYG Reports featuring widgets with blank subtitles, those subtitles were getting automatically filled in with a default text string. Importing these widgets will retain their empty subtitles now.
  • Facebook Ads only returned the most recent 25 active campaigns by default. They allow up to 5000, though, so we increased our data calls to that maximum.
  • If you have an MCC account in Google AdWords and that MCC has access to another MCC, we were only showing accounts related to one of the two MCC accounts. This has been corrected so that all available accounts are an option for reporting.
  • When segmenting Google AdWords data by Ad Group in WYSIWYG Reports, that Ad Group limiter wasn't kicking in properly.
  • If you accidentally uploaded a corrupted image to WYSIWYG Reports as a logo, the logo uploader would eat itself and break PDF reporting. We've made the uploader a little smarter to avoid corrupted images from making it too far.
  • SEO Metrics wasn't returning any data at all, thanks to the Avg. Time on Site metric being deprecated by Google Analytics. We removed this metric and everything came back, right as rain. (This widget may still exist in WYSIWYG Reports as a KPI. We recommend deleting the KPI from those reports.)
  • The "n/a" entries for missing search volumes in Search Analytics were a little garish. We replaced them with dashes, to make search volume numbers stand out more when they exist.
  • The Filename field in Site Auditor > Image Issues wasn't wrapping properly in reporting. That field received the same wordwrap feature as other URLs.
  • There were two "Link Clicks" metrics listed in custom reporting for Facebook Ads. One was actually "Inline Link Clicks," which we've renamed accordingly.
  • When reporting on responsive ads in Google AdWords, we weren't showing a preview of the ad in question. We've implemented a basic view of what your responsive ad might look like to a searcher.

No published changelogs yet.

Surely Raven will start publishing changelogs very soon.

Check out our other public changelogs: Buffer, Mention, Respond by Buffer, JSFiddle, Olark, Droplr, Piwik Pro, Prott, Ustream, ViralSweep, StartupThreads, Userlike, Unixstickers, Survicate, Envoy, Gmelius, CodeTree