Notification

Urchin WebAnalytics Software is discontinued and is no longer supported. All Urchin documentation applies only to the Urchin product as it was at the time of discontinuation, and does not apply to any Google Analytics products or services.

Urchin 6.6, 6.601, and 6.602 Changelist

Urchin 6.6, 6.601, and 6.602 Changelist

Features Added

Here is a brief summary of the major features introduced in the Urchin 6.6, Urchin 6.601 and Urchin 6.602 releases.

  • Deep integration with Google AdWords

    • Budget Alerts: This feature warns you if the campaign budget for an AdWords campaign needs to be adjusted. It automatically becomes visible in the reporting interface if any of the CPC sources (associated with the profile being viewed) has a budget alert in the AdWords system.

    • Keyword Generation Tool: This tool allows you to generate related keywords and to see their performance information. It also allows you to add newly generated keywords and delete existing keywords from AdWords campaigns.

    • Direct links to AdWords: This feature allows you to navigate directly from Urchin to the appropriate screen in your AdWords account.

    • Urchin Tag Manager: This feature inserts a dynamic keyword insertion tag {keyword} in ad destination URLs. This feature simplifies the URL tagging experience and allows you to seamlessly import AdWords cost data into Urchin.

    • AdWords Optimizer: This tool allows you to optimize your campaign directly in AdWords.

  • Advertiser view and section

    • Advertiser dashboard template (view) and Advertisement Optimization section: These search marketing/advertiser-oriented enhancements provide new ways to view data in a paid-advertising-centric manner and to support the above mentioned AdWords-related features.

  • New reports

    • "Time On Site" report: This report can be found under Content Optimization -> Content Performance -> Engagement Metrics.

    • "Performance Comparison" report: This report allows you to compare Campaign, Keyword and Content performance across sources/mediums (e.g. Google|CPC vs Yahoo|organic). Located in Advertisement Optimization -> Marketing Campaign Results.

    • "CPC Structure": This group of reports can be found under Advertisement Optimization
      • Campaign View displays paid UTM campaign information (Google and Yahoo campaigns supported).
      • Keywords View displays paid keywords information.

  • Data API

    • Data Export API: This major new feature allows you to retrieve Urchin reporting data via SOAP 1.x and REST protocols.

  • External Authentication (LDAP)

    • In addition to Urchin-specific authentication (now called "Native"), Urchin 6.6 supports external authentication that can be configured on per-user basis.
    • External authentication modules: Support for LDAP and MSAD is provided with Urchin 6.6, while custom modules can be integrated by modifying the configuration files.
    • SSL/TLS support: These protocols are now supported as well.

  • New Urchin "Home" Page

    • Urchin "Home" (aka, the Roll-up Report) has been modified to provide metrics for all the profiles that are visible to the logged-in user. User can choose between 3 views: Basic, Business and Admin.
    • Profile metrics are provided for a day (yesterday) and the most recent week, month and year.

  • Automated CPC Data Import from Yahoo! Search Marketing (YSM)

    • In addition to Google AdWords, Urchin now allows you to import CPC data from Yahoo! Search Marketing.

  • One-Click Installer

    • All Urchin installers, except FreeBSD 6, now include Postgresql database server that can be installed during the installation process. This eliminates the requirement of a database server needing to be installed and configured prior to Urchin installation. The user may still use existing database servers by disabling this option during installation. NOTE: You may experience issues on Linux Kernel 2.4, for details see Known Issues document.

  • GeoDB Optimized load

    • Now you can choose between full and lightweight version of GeoDB to minimize memory consumption during log processing. The lightweight GeoDB only provides metro information up to the country-level.

  • Updated Zip\UnZip utility

    • Updated Zip utility allows you to work with data archives > 2 Gb.

  • Sorting in Marketing Summary Dashboard

    • On the Marketing Summary report, you can sort sources, keywords and campaigns by metrics & their deviations.

  • Miscellaneous

    • Process Control: Urchin 6.6 now allows you to kill jobs gracefully (that is, without corrupting the database), which is useful when a log-processing job becomes "stuck" for some reason.

    • User access to AdWords Tools: A new "Access to CPC Sources" setting has been introduced on a per-user basis. By default, only Super Admin has AdWords tools enabled. For all other users, this access must be explicitly granted via this new setting.

    • Bing.com: Support for the Microsoft's new bing.com search engine has been added.
    • Profile filters: These filters are now applied to CPC sources.
    • Profiles tab: A new tab called "Profiles" has been added in Log Source Management to link the log source to the multiple profiles.
    • Remote log file downloading: A configurable parameter for remote log download timeout has been added in urchin.conf file.

Bug Fixes

Here is a brief summary of the major bug fixes introduced in the Urchin 6.6, Urchin 6.601 and Urchin 6.602 releases.

  • Administration

    • In Urchin 6.5 and prior versions, profile-related folders were not renamed when a profile was renamed on the admin interface. This has been fixed.

  • Log Processing

    • In certain cases, Urchin encountered a segmentation fault while processing ELF2 logs. This resulted in incomplete log processing job and inconsistent reporting data. This has been fixed.
    • Incorrect treatment of the profile's local-time configuration during log processing was resulting in the reporting data being shifted by hours in the months. This was happening for the months when day light saving starts or ends for the selected profile's timezone. This has been fixed.

    • A problem with processing multiple UNC log sources has been fixed. For remaining issues with UNC log sources and best practices, refer to on-line Help Article:

                       Working with UNC log sources

  • SSL Support

    • A problem with connecting to Urchin via https on Windows 2003 has been fixed.

  • Special characters in CPC source passwords

    • Certain special characters were not allowed in CPC source passwords. This has been fixed and the characters !@#$%^~`&* _+»<>{}[]()№?-=:;\|/,. are now allowed.

  • Licensing

    • Regular license re-set and reactivation were required after upgrade to 6.600 on Linux and FreeBSD. This has been fixed in Urchin 6.601 and reactivation is no longer required.
    • Prior to Urchin 6.602, upgrading while using a demo license could result in login/licensing issues. This issue has been fixed. NOTE: Upgrading an instance of Urchin that is using a Demo license does not extend the demo period.
    • For a regular license, the maximum number of log sources has been increased from 1000 to 3000. This change requires generation of a new license key from the urchin licensing server. 'New' installations of urchin (regardless of urchin version) will automatically get this changes. Existing installations or upgrades will require manual execution of ugetlicense utility by the urchin administrators.

  • Migration

    • The reporting data migration utility (convert-u5data) has been significantly improved and performance further optimized. In most of the cases, now it will take much less time to import 'large' reporting data.
    • In certain cases, when migration of the reporting databases from Urchin 5 to Urchin 6 crashed or was interrupted, subsequent attempts to resume importing failed with the warning message: "WARNING: (8010-577-1192) Database file is the wrong size - run sanitizer". This issue has been fixed.
    • During u5 to u6 reporting data migration, some data was not properly imported into urchin 6. This has been fixed.

  • Miscellaneous

    • The Urchin Embedded Help and various online Urchin Help Center articles have been updated.

Important Usage Notes

  • MySQL

    • Urchin 6.6xx does not support MySQL 4.x.x. Your existing MySQL instance must be upgraded to MySQL 5.03+ in order for Urchin 6.6 to function properly.

  • FreeBSD 5.x

    • FreeBSD 5.x platform has been deprecated.

  • Client-side Cookies

    • To facilitate enhanced interaction in the reporting interface, Urchin 6.6 uses client-side cookies. Proper viewing of reports requires that client-side cookies be enabled in the client browser.

  • Restricted usage under 'Demo' License

    • Urchin 6.6 introduces certain demo license restrictions. Profiles and log sources are limited to 5 each. There is no limit on filters, cpc sources, users, accounts or groups.

  • Upgrade

    • Urchin 6.6 introduces a new report section and views. After upgrading from earlier versions, these reports and views may not show any data. We recommend reprocessing existing profiles to populate the new reports.
 
true
Search
Clear search
Close search
Main menu
1773969530570209511
true
Search Help Center
true
true
true
false
false