How can we help?

NinjaCat 3.4 - November 20, 2018



  • We’re adding 5 new integrations! We now integrate with Waze, Monday (Depulse), WorthAuto, Thinknear, and Sizmek.

  • For detailed information on these integrations, click here.

What's New

Budgets (Beta)

  • We’re excited to release all-new Budgets in beta. Track and filter your spend across all Data Sources (with spend) on a single screen. We’ve also structured Budgets so you can configure a Budget once, and share it amongst as many Accounts as you want. Contact your CSM for more information and to join the beta.


Use All Mappings selector for the Template Editor

  • If you have multiple connections to the same Data Source in an Account (say, three Google Analytics accounts) gone are the days of adding each of those Data Sources individually in the Template Editor.

  • Now, we’ve added a “Use all mappings” option on the drop-down in the Mapping field for Data Sources. Add the Data Source once, select the “Use all mappings” option, and we’ll show you the data for all Data Sources of that type. This won’t be available for Data Sources that have custom mappings (Zapier, SQL, Google Sheets, etc.) because the Metrics and Dimensions differ from mapping to mapping.

Dashboards for All

  • Dashboards V2 is now out of beta and that means everyone will have access to it. V2 dashboards are 100% customizable and use the same Shinobi template builder that drives Shinobi reports so the learning curve is minimal.

  • This short NinjaCast will have you building a dashboard in no time: 'Falling in Love with Your New Dashboard'. If you’re using Dashboards V1 or Legacy Dashboards, don’t worry, we haven’t taken those away!

And Much More!

  • We’ve updated the infrastructure that we use to generate PDF and PowerPoint reports and we should see significant improvements to the formatting of reports.

  • We've improved the way we handle reports in Email Error state. The Email Error state indicates that something might be wrong with the SMTP credentials, but not the report itself. Therefore, we don’t need to re-generate the report once the Email Error is resolved, and now we won’t. We’ll just send it immediately.

  • You now have the ability to group your calls by duration, rounded to the minute. You can find it under the “Call Duration (Minutes)” dimension in Call Tracking.


  • For email integration, we’re now able to get the data from a link within the body of the email, as long as it links to a, .ZIP, .CSV or .TXT.

  • AdWords’ Ad Customer Feed Item Report has been added.

  • A new metric called “Content Impression Share (Unique)” has been added to AdWords.

  • Amazon Ads Campaign Type and Day View options have been added to give you more control over how you present that data. You should now be able to get your Report to match Amazon Ads’ data.

  • You’re now able to add the {REPORT_DATE_RANGE}, {REPORT_DATE_RANGE_START}, {REPORT_DATE_RANGE_END} clips to the Subject and Body of emails in the reports configuration. Previously, you were able to use these clips in the File name and we’ve extended this ability to the email itself.

  • We’ve added a new font called Sansita.

Bug Fixes

  • “Re-run Failed Reports” should now attempt to run any reports in Email, Data or Critical Error state. In addition, we’ll notify you with how many of your reports ran successfully, were sent via email, or failed again.

  • We’ve added a number of notifications in the bottom right-hand corner.
    • First, we’ll tell you how many reports we’re attempting to run.
    • If Email errors are resolved, after re-running failed reports, a notification will confirm how many email errors were resolved and sent.

    • Finally, after re-running failed reports, if the error still exists, you will be notified of remaining issues

  • The ‘Clear’ button in the Dashboard date picker wasn’t working correctly, so for the time being, we’ve removed it. Expect to see it back soon.

  • When used in a Custom Dimension, “Audience Type” will no longer cause an error when calling the API.

  • We’re able to support carriage returns on CSV a little bit better.  Some formats were was causing us to mistake a carriage return for the next row of data. We’ve fixed this now.
  • With Google Analytics, we were triggering some quota errors and so we tweaked some levers in the background to avoid these errors in the future.
  • We previously didn’t have a way to delete unneeded BigQuery mappings. To cut down on the clutter, you can now delete BigQuery mappings.

  • We weren’t able to pull more than 400 days worth of data from Centro. We figured out the issue and you should now be able to pull as many days as you want.

  • When setting up a Zapier mapping, Metric or Dimension headers were sometimes not showing the most up to date options. We’ve fixed this and you should now always see the most up to date Metrics and Dimensions headers.

  • When a Zapier connection had no data, we weren’t allowing you to map the Metrics and Dimensions until it did. We will now allow you to map to a Zapier connection that only has null data, if you choose. In addition, we’ll record that null data, just in case that’s what you were expecting.

  • An issue with Google Analytics Keywords was discovered where, in some cases, a results’ data was split into two lines due to slight variations in text formatting. We’ve scrubbed away these differences so that all the data appears on a single, correct search term.

  • “Calls” metrics from AdWords were using an incorrect Time Zone, so calls at the beginning or end of the day (beginning or end, depending on where you were relative to UTC) were being attributed to the wrong day. We’ve fixed this so it will use the right Time Zone and calls should always fall into the right day.
  • Advice Local’s dimensions should now play nicely with the rest of our aggregate dimensions. You will now see Advice Local’s City, Country, State, and Zip under those respective Aggregate Dimensions.

  • DoubleClick for Publishers’ “Ad Server Active View Viewable Impressions Rate” metric was displaying incorrectly and will now always display correctly.

  • In the annotation editor, when Save was clicked, both Save and Send started spinning. That might have given the impression that we sent the report when we didn’t, so we fixed it and only the button that you clicked will spin.

  • The chat bubble button was sitting on top of some important settings on the right-hand side of the template editor and getting in the way. We asked it to move, so it shuffled over to the left-hand side of the interface.

  • When setting up a Google Analytics mapping, sometimes an account should not be required, and so now, it’s not mandatory.

  • In the template editor, when configuring a Data Source, if you changed the mapping selected and typed in a new name, only the mapping selected would be saved and the new Data Source name wouldn’t. We’ve fixed this.

  • In rare cases, when creating values for an Account Group, the value was appearing twice. Account Group values will now only appear once.

  • When configuring Global Filters at the Account level, it was previously possible to save a Global Filter that you hadn’t made any actual changes to. It would then appear “customized” in the interface even if it wasn’t. We’ve fixed this and now it’s not possible to save a completely unchanged Global Filter.

  • Also, we’ve increased the character limit for Global Filter values passed 256 so extra-long regex filters can be used.

  • For Legacy users only, Bing Ads no longer supports “Content” filter for “Display.” This was causing Bing data to be counted twice. We’ve fixed this so that now Bing data will not show up when filtering by “Display” content.


Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request