New Integrations
- LinkedIN
- NinjaCat is now fully integrated with LinkedIN!
- NinjaCat is now fully integrated with LinkedIN!
- AppNexus Integration
- As a note, at times AppNexus will refuse a request and the error message will look something like "AppNexus Error…." when your date range goes too far back. There isn't any real consistency as you at times can get data going back 1 year and sometimes it errors out past 6 months.
- WhatConvert Integration
- This is part of a CallTracking Integration
New Features
- Shinobi Template editor - Axis Hiding
- There is now the ability to remove and hide the labels on a chart's X or Y axis.
- There is now the ability to remove and hide the labels on a chart's X or Y axis.
- Changes to Report List
- We now have reports separated into 2 areas within the command center: 1) Reports (Legacy) and 2) Reports
- The report list has a few new modifications that have been made to it which is as follows:
- Account Column
- Account Name
- Report Name (Filename)
- Template Name (clickable link to the actual template)
- Union of data source icons associated to both the template and account
- Status
- Schedule - report was never run or sent
- Pending Review - Report is set to Manual delivery and has never been run nor has been sent
- Sent - Report has been sent by email
- Critical Error - Report did not generate
- Data Error - Report was generated but one of the data sources has failed or one of the widgets is not returning any data
- Frequency
- Line 1 - Shows Period set up as Daily, Weekly, or Monthly
- Line 2 - Shows Last date the report was run (uses browser's setting in configuration of MM/DD/YYYY or DD/MM/YYYY)
- Line 3 - Shows when the report is scheduled to run next
- Delivery
- Line 1 - Shows if report is set up as Manual or Automatic
- Line 2 - Shows when the report was last emailed
- Range
- Shows the Date Range that is being used in the report as the default
- Dashboard, Download
- No Changes
- Action
- The only new action that has been added is the "Send" button
- This button will only appear if a successful report has already been generated and an email exists in either the edit report page or account settings.
- The last successful report will be sent by email
- We now have reports separated into 2 areas within the command center: 1) Reports (Legacy) and 2) Reports
- Aggregate City Data across multiple data sources
- "City" is now an aggregated dimension for the following networks.
- Simplifi
- DoubleClick
- DoubleClick Bid Manager
- Google Adwords
- Gemini - currently not live in Shinobi
- Facebook Insights
- Centro
- Call Tracking
- Bing Ads
- "City" is now an aggregated dimension for the following networks.
- Added new custom calculated fields display options (TIME)
- Within custom metrics and metric mappings, the following display as options have been added: Time, Time (from ms), and Duration.
- When creating mappings for google sheets or zapier, the following display as options have been added to dimensions: As Is, Date, Date Time, Month, Month (from number), Month & Year, Year, Weekday, Phone Number, Title Case, Country (from ISO)
- If you select an aggregation for a dimension mapping, the "display as" option will be hidden
- For "Weekday" display as option, the data will be interpolated from either a date or an integer from 0-6
- The "Duration" display as option rounds
- Within custom metrics and metric mappings, the following display as options have been added: Time, Time (from ms), and Duration.
- Reports - Bulk Re-run/Send
- Reporting> Reports: There is now a button that will re-run all failed reports including those failed because of critical errors and data errors.
- This button should put all failed reports back in the scheduled status and it will be pick up by the reporting queue to run.
- This may take some time so if there are a lot of reports with errors bare in mind they will all need to queue and run.
- Reporting> Reports: There is now a button that will re-run all failed reports including those failed because of critical errors and data errors.
- Migrate Bing to V11 for Shinobi
- Add a notice that some data sources are legacy only
- At the Advertiser level the following networks now have a message in their help text when adding a network from a Command Center explaining "Please note that this data source can only be used for Legacy Integrations".
- Bing Webmaster Tools
- Google Places
- Verve (call tracking)
- At the Advertiser level the following networks now have a message in their help text when adding a network from a Command Center explaining "Please note that this data source can only be used for Legacy Integrations".
- Change Twillio to primary NT Provider
- Previously we had Bandwidth as our primary NinjaTrack Provider, but now the switch has been made to Twillio for both Toll Free and Local Numbers
- Change History Widget
- This new "Change History" widget is permission based. In order to view this widget within the command center, they must either have the "System Admin" permission or contain a Permission that has this new "Manage Change History" role .
- The change history widget showing all entries is located at the bottom of the accounts command center, below the KPI widget. The widget displays Subject, Details, Date, Created By information. And contains a delete button. Subject, Date, and Created By columns can be sorted alphabetically.
- Feature allows free-form journalling of changes and other comments.
- New entries are added by clicking the + sign, while existing entries can be modified by clicking on the appropriate row.
- There are three mandatory fields in each entry, two of which are populated by default as follows:
- Subject Line - must be completed by the user, typically used to summarize the nature of the change. 180 character maximum.
- Change Date - defaults to current date, but can be modified to any future or historical date.
- Created By - defaults to current user, but can be modified to any other user (note required access privileges above).
- A categories field was added to aid users the ability to filter through entries.
- A privacy settings toggle is available to indicate whether an entry is public (shown to all users by default), or private (not shown to all users by default). This is applicable to reports and dashboards.
- A Details text box is available for users to enter their desired information.
- Change History Reporting - users can report on historical entries, by setting up a template with any widget, and selecting Change History, as a data source.
- Only available metric is Count → a numeric measure of how many times a given entry was added to an account.
- Available dimensions are:
- Categories - displays entries from categories field
- Created By - displays selected user from entry
- Details - displays first few rows of data from field
- Private - "Yes" or "No", depending on what was selected for a given entry.
- Subject Line - displays the data that was entered in this field.
- "Show Private" toggle - once Change History is selected as a data source, a "Show Private" checkbox becomes available that allows users to enable or disable display of private entries.
- Account Group Reports - Data Source Bypass
- We now have within the global settings tab of the template editor a "Roll-up Report" toggle.
- This toggle was introduced in order for typical errors to be bypassed where the primary account does not have the data source as the other accounts in its group and post all available data coming from that account group.
- Roll-up Report Toggle NOT ENABLED expected outcomes:
- If the account that is being reported on does not have a data source nor an account group that is being reported on, than no data will render and you will see the following message within the template editor "No data was returned. The account "[Account Name]" does not have [Name of data source] setup as a data source".
- If the account that is being reported on does not have the data source but has the same account group as the one in the data source widget of the template editor, than no data will render and you will see the following message within the template editor "No data was returned. The account "[Account Name]" does not have [Name of data source] setup as a data source"
- If the account that is being reported on does have the same data source but has a different account group than the one set in the template editor, than data will render but only for that particular account
- Roll-up Report Toggle ENABLED expected outcomes
- If the account that is being reported on does not have a data source nor an account group that is being reported on, than no data will render and you will see the following message within the template editor "No data was returned The account "[Account Name]" does not have [Name of data source] setup as a data source"
- If the account that is being reported on does not have the data source but has the same account group as the one in the data source widget of the template editor, then the error message gets bypassed and you will get data back from all the other accounts that are part of that account group and have that data source.
- If the account that is being reported on does have the same data source but has a different account group than the one set in the template editor, than data will render but only for that particular account
- We now have within the global settings tab of the template editor a "Roll-up Report" toggle.
Bug Fixes
- Adwords - Campaign Group dimension with cost metric breaks
- Now if you try to create a widget with just "Campaign Group" as a dimension and "Cost" as metric, data will render as expected.
- Now if you try to create a widget with just "Campaign Group" as a dimension and "Cost" as metric, data will render as expected.
- Bing Ads - Cannot Filter by Ad Text
- dims.AdDescription, dims.TitlePart1, and dims.TitlePart2 are all now filterable with Bing Ads.
- Call Tracking - Missed Calls not being calculated correctly.
- Call tracking custom metrics were not calculating the correct values, zeros were being returned. This is now resolved.
- The 'Google AdWords -> Keyword' Dimension Significantly Differs From 'Aggregate -> Keywords'
- To avoid a user seeing the aggregate dimension "Keywords" and being confused with the network dimension "Keyword", it has been changed to "Keyword Matching Query"
- To avoid a user seeing the aggregate dimension "Keywords" and being confused with the network dimension "Keyword", it has been changed to "Keyword Matching Query"
- Zapier header mappings will now get updated based on new zaps coming in
- The entire data set for each zapier network is being captured to ensure that all header mappings appear.
- Google sheet mapping connections do not get the updated sheet name
- Now when you update an existing connection to a different spreadsheet / sheet, the sheet appropriately update to the correct sheet name.
Comments
0 comments
Please sign in to leave a comment.