February bug fixes

  • Sorting was broken for a handful of different columns in Site Auditor following the addition of Site Auditor Studio. That's been fixed so that all columns can be sorted.
  • Research Central wasn't allowing users to add competitors for comparison in the Compare section. That has been resolved.
  • We use a chat program called Drift to give trial accounts a little extra help. If a user upgraded with an unread message, Raven would permanently blink "(1) New Message" in the browser title. We removed Drift for all non-trial users.
  • In some cases, Chrome users were seeing JavaScript errors that prevented the tool from loading. We've fixed this issue, which stemmed from our navigation change, for all supported browsers.
  • An update to our billing platform briefly knocked out access to the platform. This was fixed within a few hours of their deployment. We hope that this is the first and last time that a change in the billing platform causes an outage, but we've also implemented a workaround to more quickly resolve this on our end.

Introducing Site Auditor Studio

For the past two years, Raven has maintained two products: the Raven Tools marketing platform and Site Auditor, a standalone version of the website analysis tool on our platform. Beginning today, we're unifying those tools under one roof with Site Auditor Studio.

Site Auditor Studio gives Raven users two big benefits:

  • Manage your audits by marking individual issues as fixed. You can use Site Auditor Studio as a punch list, solving problems in the report as you fix them. It also helps you do away with non-issues, like 400 Forbidden external links or redirects.
  • Grant your clients access to their Site Audits without setting them up as dedicated users. If you have a client that wants to dive deep into their website errors, you can share a link to the audit. They'll be able to see the issues, but won't be able to make changes.

To access Site Auditor Studio, click the Visit Site Auditor Studio button while viewing Site Auditor.

Site Auditor Studio is currently available for all new trial users. We'll be rolling out access to the new tool to current Raven customers in the near future.

Research Central now uses IBM Watson

With the impending deprecation of the Alchemy API on March 7th, we've upgraded the Semantic section in Research Central's domain analysis to use IBM's Watson Natural Language Understanding API.

Now, the Semantic section in Research Central will pull keywords from a researched domain through Watson's semantic analysis. These keywords are mashed up against the type and relevancy data from Open Calais, giving you a general idea of prominent keywords and ideas for Schema improvements.

Additionally, we fixed some minor issues with displaying data from Calais and cleaned up some old, unused code to make this tool speedier. Updating to the IBM Watson API also enables opportunities for further innovations in this tool (and elsewhere in Raven) going forward.

January bug fixes

  • Subusers were unable to access the platform briefly due to a navigation change.
  • The CSV Import widget subtitle in WYSIWYG Reports wasn't editable. You can now set the subtitle to something other than "Table."
  • Read-only users without access to tools in a particular tool group were still seeing the overall group name. These will now be hidden from these users.
  • When reporting on Google Analytics data, graphs set with Advanced Segments and then re-edited would result in an error. The issue was that the graph metrics were being reset to the default Advanced Segment upon edit, creating a conflict. That won't happen going forward.
  • Facebook Ads was missing from Role Manager. This can be found under the Social section, rather than the PPC section.
  • The comparison graphing on Bing Ads reporting was busted due to an API change. This has been restored to normal.
  • Due to a quirk in the newest version of Bing Ads, whenever we requested data that was a null in WYSIWYG Reports, we'd show an error in the widget instead of a zero. We've fixed our logic for these requests to resolve that error message.
  • If you compared Google Analytics data against a zero, we'd show that change over time as 0%. Google shows it as 100% which, while not technically, mathematically right, makes a little more sense than what we were showing. We switched over to their standard for this.
  • We were miscounting automatically shortened URLs in Twitter posts: we said they were 22 characters, but they're actually 23. In some cases, this would cause Tweets to fail, but this (and the increase to 280 characters) resolves that.
  • No, your eyes do not deceive you: we made the navigation menu on the left side of Raven a little skinnier, so that we can fit more content in the main part of the tool.

Research Central split into Domain and Keyword tools

When Research Central launched in 2013, we collapsed two tools into a single interface to make researching a one-stop shop. But, what we found was that our customers didn't always realize that there were two halves to research central: Domains and Keywords.

We've rectified that today by splitting this tool in half. Now, you can research domains from the Domain tool and research keywords from the Keyword tool. Looking for your saved shortcuts? Those are available from the Saved Shortcuts link.

In addition to splitting the tool, we've also renamed the AdWords section to Search Volume. It's still the same AdWords keyword data that you've always had, but with a name that better describes the tool's data.

December bug fixes

  • YouTube video options weren't populating in WYSIWYG Reports widget options. Those have now been restored.
  • Nested items in sub-navigation menus looked a little crummy, so we made them stand out better.
  • There were a few columns missing from CSV exports in Research Central's Backlinks section.
  • When saving Twitter searches, we weren't clearing the cache so that you could see those newly saved searches. It looked like they weren't saving, but they'll update more quickly now.
  • One of the biggest headaches in Facebook reporting has been dealing with disconnected accounts. When a Facebook account has been disconnected, we'd ask you to connect a new account. But, when that new account was connected, we were still reporting on the disconnected account. That circuitous logic resulted in a ton of duplicate accounts and even more frustration for our customers. We came up with a way to make that whole process less crazy and much more manageable.
  • You can set a custom Logout URL under the Custom Domain settings, but that field was too constricted to allow any changes to it. We loosened it up significantly to allow these changes to be made.
  • After adding Cover Pages and Tables of Contents to WYSIWYG Reports, the Campaign URL identifier was overlapping tables and other elements in the report. We removed that identifier when Cover Pages are active.
  • When viewing Facebook Ads data where there is no comparison, we were showing a fairly garish "NaN" as the value. That's not in the same style as everything else in Raven, so we cleaned it up.
  • The Average Position KPI in Search Analytics had its color flipped, showing green for negative changes and red for positive. We turned the logic around to make it more intuitive.

Greater visibility and sharing for Dashboards

When the updated Dashboard launched in 2014, it was created as a tool for individuals to determine their own needs and their own Dashboards. For that reason, Dashboards were tied to individual users, rather than to Campaigns or Profiles.

While this worked for some users, we found that this decision strongly limited the tool's potential for collaboration — particularly for individuals who wanted to show their clients a Dashboard they created. With that in mind, we made a few improvements:

  • Dashboards can now be shared! Yes, at long last, your read-only users and sub-users can be granted access to view your Dashboard. When you allow access to your Dashboard, other users will be able to select your name from a dropdown menu in their accounts.
  • Want to show your Dashboard to someone who isn't a user in your account? You can now publish the Dashboard just like you would a report. Click the Publish Options button and click Publish to create an HTML version of the Dashboard. This can also be exported as a PDF, just like in WYSIWYG Reports.
  • Defaults have been moved out of the Dashboard: if you want to set a default Campaign, you can do that in Campaign Settings now.

We're thrilled to make this tool more accessible, and couldn't have done it without the valuable feedback from our customers. Is there anything that would make your life in Raven easier? Drop us a line — we'd love to hear from you.

Updates to WYSIWYG Reports templates

We've made two slight changes to the import option in WYSIWYG Reports. The button now reads Use Template (rather than Import Report) and now only reports that have been explicitly set as templates will appear in the import listing.

  • Historically, Raven has shied away from using the word "Template" to describe reports that you can import in WYSIWYG Reports, largely because of the similarly named feature in Report Wizard. We decided that the precaution was unnecessary and, now, are more accurately describing what these template settings do.
  • More significantly, prior to this change, we listed every report in your Campaign as an import option, but we found that this made it hard to find the right template to use. Now, we'll only list reports that have been explicitly set as templates.

You can set a WYSIWYG Reports as a template by editing your report, clicking the Report Settings button, and flipping the template option to "Yes."

Cover Pages and Tables of Contents in WYSIWYG Reports PDFs

Ever since Raven launched WYSIWYG Reports to replace Report Wizard, there's been one resounding request to bring greater parity between the old reports and the new: Cover Pages and Tables of Contents.

Now, in WYSIWYG Reports PDFs, Cover Pages and Tables of Contents can be optionally added to improve the professionalism of your reports. Both can be enabled by following these steps:

  1. Edit the report that you want to enable these options on.
  2. Click the Report Settings or Scheduled Report Settings button.
  3. Navigate to the PDF Options tab in your Settings window.
  4. Enable the Cover Page and/or Table of Contents options.
  5. Customize the titles, subtitles, and bylines as desired.
  6. Click Submit to save your changes.
  7. For one-time reports, click the Publish Changes button to output a new report with these options enabled.

Cover Pages will use the logo set in your report, so be sure that you're using a high-resolution image.

Facebook Ads data outage resolved

For a brief period during the day, Facebook Ads was inaccessible in the platform for both existing accounts and new connections. We found that the API version that we were using to bring in Ads data had been deprecated by Facebook and was no longer operational.

After discovering that issue, our developers worked quickly to address this in the platform to update this connector. The platform is now on v2.10, which will remain valid for at least six months. Going forward, this will be changed well in advance of deprecation deadlines.

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