The Visitor Profile includes detailed information on site visitors that cannot be easily gathered from simple web analytic (hit reporting).

To view the Visitor Profile, click on the [STATISTICS] tab. The Visitor Profile makes it easy to answer these questions:

What website did the visitor come from?

What search did they perform to get here?

Are they responding to a PPC ad or organic search?

What actions did they perform once they got here? Browse Pages? Submit a Form? Create a Cart? Checkout? Submit an Order?



There are four main parts to each visit to the website that we can track and report to answer the 4 questions above: Referral, Action(s), Demographics, and Dollar (Value). Here is an explanation of each one:

Referral: Where did they come from?

Domain Name
What Domain Name did the visitor visit before this site? This is the Top Level Domain Name (TLD). We parse the referring URL (if not blocked by the visitor's browser). For example, “http://www.google.com/search?hl=en&q=RMICMS™+web+architects would result in "google.com".

Keyword(s)
What keywords or keyword phrases were used to find this site? We parse the referring URL (if not blocked by the visitor's browser). For example, "http://www.google.com/search?hl=en&q=RMICMS™+web+architects" results in "RMICMS™ web architects" as the keyword.

Tracking Code
If any visitors visit your site as a result of clicking a link that contains a tracking code, we will separate these click-throughs so you can distinguish them from other click-throughs. For example, if you broadcast an eMail promotion with a link to a landing page on your site "/pages/homepage?t=12345", then we will isolate this tracking codes and report the visit as resulting from the eMail promotion.
PPC (Pay per Click) Tracking Code
If you use a tracking code naming scheme to identify PPC click-through, we will separate these click-throughs so you can distinguish them from organic click-through. For example, if all your PPC tracking codes include the string “_kw_”, then we will isolate these tracking codes and report on them as visits resulting from a PPC click-through referrals.

Entry Page
When a visitor enters your site, the first page they view is considered their entry page or "landing page". It is important to track what they see first, coupled with their "interest" level will tell you whether the landing page is effective or not.

First Visit
Once the visitor has "landed" onto your site, we need to know if they have ever been to your site before so we can develop trends in usage of your site. We do this by setting a cookie com the visitor's computer that we can read back on subsequent visits. Cookies are a widely accepted practice, but not 100% accurate since they can be disabled and/or deleted by the visitor.Actions: What did they do when they were here?
Now that we have established where the visitor came from, and how they got to your site, we would like to know if they found you site by accident, or if they are genuinely interested in your site's content. This is the first “action” they will take – leave if they are here by mistake. We need to know this so our referral information is not skewed inadvertently.

Page Views (Shop or Leave)
We could also use this along with other stats to determine the average number of pages viewed by your customers before they take an action. We do this by setting a cookie to count the number of pages that they visit from the moment they "land" on your site.

Submit a Form
Now that we know the visitor is interested in your site and is browsing pages, the next thing we want to know is if they take any other actions on your site. Other actions include submitting contact forms, order status request forms, catalog request forms, customer service request forms, adding items to a shopping cart, retrieving a shopping cart, reordering, and submitting orders. We do this by logging the first custom form submitted during their visit at your site.

Create a Shopping Cart
Now if the visitor is interested in ordering, they will create a shopping cart by adding an item to a new cart. We want to know how many visitors took this action. We do this by logging any cart creations that occurred during their visit to your site.

Retrieve a Shopping Cart
Now if the visitor may be returning to finalize a saved cart (using a reference code), or re-ordering using their Gift List or Order History, so we want to know this. We do this by logging any cart retrievals that occurred during their visit to your site.

Check Out
Once the visitor has created or retrieved a shopping cart, they would like to know if they proceed to the checkout line. We do this by logging if the visitor clicks on the “checkout” button during their visit.

Order
If the visitor places an order (converts a cart to an order), then we would like to know this. We do this by logging if the visitor successfully completes the purchase process during their visit to your site.

Geographics: Where are they from?

If the visitor places an order, then we would like to link their actions to geographic data (which we will now have), including the Zip/Postal Code, City, State/Province, and Country. We do this by capturing the billing address for the order.

Value: How much did they spend?
If the visitor places an Order, then we would like to link their actions to a dollar value. We do this by capturing the Order Amount from the order.