5.0.33 - RELEASE VERSION
- FEATURE: Add parent child product groups and kits capabilities to feed web service call used by our Comparison Shopping Engine Service
- FEATURE: Add average response times and page level response times to visitor log, view session and page views reports.
- FEATURE: Allow customers to choose a default payment method via their my account settings. 
- FEATURE: Allow all payment methods to be sorted including adding settings for credit cards w/o a gateway and echecks.
- FEATURE: Add default payment type selection to the admin customer edit page.
- FEATURE: Rule Based Analytics
- Offers complete power and customizable insight into how visitors and traffic is coded within AmeriCommerce.
- Create user defined rules to classify your traffic
- Instantly identify and track new web spiders, name traffic coming from certain sites, assign adcodes to specific incoming traffic, mark traffic as spiders or as suspect sessions
- See these results in most reports that already exist and using the API port this information to other systems.
- Cutting edge AJAX page renders quickly and efficiently for in place editing with no postbacks.
-
- MORE INFORMATION
- Customers can now specify how they want the source to be set, create customized spider rules,  mark sessions as suspect based on customized criteria, and log search engines that we do not already have specified.  Rules are loaded when a session starts and currently cached for 5 minutes, or until the rules are next updated via the admin console.
- An analytic rule is defined a series of conditions and actions.  The conditions can be evaluated on an ANY or ALL basis, and if the rule evaluates as successful, the actions are applied to the session.  We currently have the following conditions in place:
- Ad Code – Checks the incoming AdCode against a defined value to see if it matches.  Can be set to * to match any value.
- Affiliate Code – Checks the incoming Affiliate Code against a defined value to see if it matches.  Can be set to * to match any value.
- Blank Source – Checks to see if the source is blank.  This can be used at the end of a set of rules to set a default or undefined source.
- IP Address – Checks against the IP address on the session, adheres to wildcard matching (i.e. 192.168.*.* or 10.*.1.*, etc.)
- Pay Per Click Keywords – Checks the incoming Pay Per Click keywords for a defined value, or if set to * matches any value.  Can restrict this to be from a certain origin as well (default is Any, currently supported are Google, Yahoo, and MSN).
- Query String – Checks the query string of the request for variables such as feed=, and can match against a defined value.  * matches any value.  Includes a flag for exact match.
- Referring Domain – Checks for a defined mask against the referring domain, includes a flag for exact match. (i.e. “.google.”).
- Search Phrase – Checks the search phrase on the referrer for a defined value.  * matches any value.  The query variable that contains the search string must be specified.  Includes a flag for exact match.
- Store – Checks to see if the session belongs to a specified store (no support for microstores yet, but could be!)
- User Agent – Checks the user agent on the request for a specified value, includes a flag for exact match.
- Each rule can contain one or more of those conditions.  Depending on the conditions set, if the rule is successful, then all of the actions set on the rule will apply.  We currently have the following actions set up:
- Log Search Engine – Logs the visit as coming from a search engine, along with the engine’s name and search query.
- Mark Suspect – Marks the session as suspect.
- Set Source – Sets the source to the specified value.
- Set Source Group – Sets a new field, Source Group, to the specified value.  This is purely an extra field used for the Referrer Analysis right now that multiple sources may have in common (such as “feed” or “ppc”, the stuff that commonly appears in []).
- Set Spider – Flags the session as a spider.
- Many more condition types and actions coming soon!!
0
Please sign in to leave a comment.
Comments
0 comments