Support
- Advanced Backup
- Client Side
- Cloud Enterprise
- ColdFusion
- Control Panel
- cPanel
- Customer Portal
- DNS Information
- Dedicated Servers
- DirectAdmin
- Domain Name
- dotDefender
- Dreamweaver
- FileCatalyst
- Front Page
- FTP
- General Information
- Hosted Exchange & SharePoint
- IIS6
- IIS7
- Juniper Netscreen Firewalls
- Linux
- List Server
- MIVA Merchant
- Addattribute
- Addcategory
- Addproduct
- Adminlockout
- Assigncategory
- Basicguide
- Batchorders
- Changeimageprod
- Createstore
- Disablecustomeraccount
- Encryptorders
- Expiredshoppingbaskets
- Exportdata
- Imagetypes
- Imerchant
- Integratedreamweaverandmiva
- Mailserver
- Movestore
- Nonsecure
- Packdatafiles
- Paymentgateways
- Processorders
- Removecreditcard
- Reorder Products
- Securestore
- Simplevalidation
- Ssl
- Testpurchase
- Toplink
- Upgradewizard
- Welcomemessage
- Miva5
- Add a Site Map in Miva 5.5
- Availability Groups in Miva 5.5
- Calculating Shipping Charges in Miva 5.5
- Creating Meta Tags with Miva 5.5
- Create Store Administration Groups in Miva 5.5
- Create the Main Store in Miva 5.5
- Set up Customer Accounts in Miva 5.5
- Delete Expired Baskets in Miva 5.5
- Existing Web Site Integration In Miva 5.5
- Export Orders to a Flat File (.dat)
- Give Customers the Best Price with Price Group Overlap Resolution in Miva 5.5
- Launchpad Configuration in Miva 5.5
- Logging Affiliate Payouts in Miva 5.5
- Logging and Statistics in Miva 5.5
- Overview of Miva Merchant 5.5 Admin Page Options
- What are "Modules" for Miva
- PayPal SDK v4.31 Changes
- Put a Search Box on Every Page in Miva 5.5
- Replace Navigation and Shopping Buttons in Miva 5.5
- Run an Affiliate Program in Miva 5.5
- Take the Store Offline in Miva 5.5
- Template Structure in Miva 5.5
- Void Specific Affiliate Earnings in Miva 5.5
- Price Groups in Miva 5.5
- Determining the Database Your Miva Store is Using on Linux
- Preventing Malicious Login Attempts to Your Miva Administrator
- MySQL
- Patching / Server Updates
- phpMyAdmin
- Plesk
- Policies and Procedures
- Premium Spam Filtering
- Programming
- Ruby on Rails
- Search Engine Submission
- SharePoint 3
- SharePoint 2010
- SiteDesigner
- SmarterMail 3
- SmarterMail 4
- SmarterMail 5
- SmarterMail 6
- SmarterMail 7
- SmarterStats
- SmarterTrack
- SQL Server
- Secure Socket Layer (SSL)
- Uploading Your Website
- Video Tutorials
- Windows Server 2003
- Windows Server 2008
- Web Design
- WordPress
- Advanced Monitoring
- MediaWiki
- Enkompass
- Microsoft Outlook 2010
- Android
- Outlook Web Access
- Critical Availability Service
- NAS Data Transfer
- Customer Portal Demos
- Joomla
- Moodle
- Cloud Dedicated
- Gallery CMS
- phpBB
- Standard Monitoring
- Righteous Restore
- NAS (Network Attached Storage)
- Networking
- SmarterMail 8
- PCI Security Scan
- LinkTiger
- Windows Cloud VPS
- Linux Cloud VPS
- Linux VPS
- Windows VPS
- Hyper V
- ENSIM
- Alert Logic
- Webmin
- e107
- Vbulletin
- VPN
- Visual Vault
- Mozilla Thunderbird
- PyroCMS
- Active Directory
- Vmware Related
- Drupal
Logging and Statistics in Miva 5.5
Miva Merchant Access Log
The Miva Merchant Access Log module logs customers' actions throughout the store, which you can view in a flat file format. With the file you can determine what browsers customers are using, what search terms they used, and their step-by-step actions (such as clicking on products, adding products to the basket, removing products from the basket, etc.) throughout the store.
This type of logging should not be confused with actual server log files, which usually provide statistics on actions throughout an entire Web site. The Miva Merchant Access Log only supplies information about the Miva Merchant store itself. However, it can be helpful in the study of what search terms customers are using, in turn giving you insight on keywords you should be including in product descriptions.
Activating the Logging
To turn on the Miva Merchant Access Log, in your Admin Menu, click the Logging Settings link, check off the Miva Merchant Access Log box, and click Update. By default, the name of the file created will be malf.log. You can change this in the Admin by clicking the Access Log link under Logging Settings, entering a new file name, and clicking Update.
How It Works
Once activated, the module will begin writing actions in the Miva Merchant store to a file named
malf.log (or other name you may have given the file). Logging will begin only when the module is activated in the store, so any prior customer actions will not be included.
Getting the Log File
To obtain the log file, you need to FTP to the server and navigate to the store's data directory. For some versions, the file may be located in a log directory.
Reading the File
The malf.log file is a delimited file that can be opened in nearly any text, spreadsheet or database program. When first viewed, it will look like a jumble of various information. Once you study it further, you will see that it shows how visitors moved about the store. Each visitor's movement is also noted by a unique Session_ID number. To analyze the log file you may need to setup special functions in a database or spreadsheet program. Some third-party developers have created tools for reading the malf.log file via a Web browser.
Resetting the Log File
The malf.log file can get quite large in file size, which may cause problems if your host limits you to the amount of drive space you can use. Since Miva Merchant will always look for the malf.log file, and will create the file if it is not present, you can back up and then remove this file from the server whenever you need to free up some space. You can always keep a backup for future reference.
Miva Merchant Statistics
You can view basic statistics on the main screen in the Admin. These statistics will tell you how many visitors have accessed the store, as well as how many orders were placed, along with best sellers. To view the statistics, in the Admin, click the Main link in the Admin Menu. Depending on store notifications and other features, you may need to scroll down the right-hand screen.
This feature provides the following information:
Hits: How many individual screens have been loaded; a single visitor can log several hits.
Visitors: The number of unique visitors to the store.
Orders: The number of orders placed.
Revenue: The total sales amount of the orders placed.
Products Sold: The total number of products sold in the orders.
Best Sellers: The top five products sold and the quantity of each.
