ASP Example

Step 1. Open the result page source code and populate variables

Let's assume you offer your visitors a computer monitor "LG" worth $999.99. When a visitor clicks the 'order now' link, some ASP page is called, e.g. "thank_you.asp". This page contains the server-side script that handles the transaction and displays a thank-you message.

Here's a sample code which your "thank_you.asp" might contain:

Here's a sample code which your "thank_you.asp" might contain:

Let's make ASP store the name and the content group of the page displayed. This is how the visit to this page will be later seen in the HitLens reports.

Now let's make ASP store the transaction details. By "transaction" we mean any act that can be accomplished by your site visitors and requires a dynamic processing: an order, a subscription, a download or a sign-up all are transactions.

Your processing system probably assigns a certain number to each order / transaction. You can pass this number to the HitLens script. Each transaction ID must be unique. For instance, you may use the Auto number / Auto increment field value supported by most databases. In other words, it's a unique order number generated by your shopping cart software or database. If not applicable, you may put 0 (zero).

Note that this code is just a sample and in real life you might use completely different ways and sources of this number.

Now we capture the order details into ASP variables. HitLens is able to track 4 parameters for each order: product name, category, quantity and order amount. If a certain parameter is not applicable or unavailable, replace it with a hyphen or simply leave it blank, e.g. order_category = ""

In the variable 'quantity' you can pass numeric values as well as strings:

Let's organize the order details into one single variable, separated by commas.

Note: if your page serves several orders, you may pass them all in one variable, separating different orders with a semicolon:

Do not change the order of parameters. The amount may not exceed one billion (the max amount is 999999999.99) and should not be delimited by commas (only dots). Do not pass currency signs ($, €) in the amount parameter.

So now the ASP variable order_details contains the following string:

"LG Monitor, TFT Monitors, 1, 999.99"

That's all we needed to do on the server side for tracking. Here's the complete code:

Step 2. Insert the tracking code

The ASP script from the previous step is executed on the server when your visitor initiates an action on your site. The hosting server then sends the result to the visitor. If you want to implement HitLens tracking, you also need to make the server send the tracking code to the visitor. This code will be executed in his / her browser and report the visit details to the Seo Software's Database.

For correct reporting, this tracking script must be populated with our variables we have just created, before being sent to the visitor.

So we paste the HitLens tracking script into our ASP page after the ASP code itself, however, we use several fragments of ASP code in the HitLens tracking script in order to pass the information collected to the variables of the HitLens script.

After the closing marker of the ASP code "%>" goes the beginning of the tracking code:

Then, we pass the site ID and page ID (pc) to the script. The site ID can be found in Project Manager opposite to the given website and under the HitLens column, for example, 123456.

The pc variable should be 0 (zero), if you use specialized tracking instead of standard wizard-driven setup (as is the case for us).

The PAGENAME variable stores the user-friendly name under which this page will appear in the HitLens reports. Earlier we initialized the ASP variable pagename with the value "LG monitor thank-you-page". Now we make ASP pass this value to HitLens:

As a result, after the ASP page is executed, the visitor's browser receives the following:

Now HitLens knows that the visitor has opened the page "LG monitor thank-you-page" and will report it to the Datacenter.

The same happens to the content group. Earlier we have assigned the value "TFT Monitors" to the variable contentgroup. Now we pass it to the HitLens script.

The variable "TRANSACTION" stores the type of the transaction: it may be sales, trials, subscriptions, downloads, or anything you choose:

In our case it will be "Orders", because earlier we assigned this value to transaction.

The same happens to transaction ID and order:

As you remember, the variable "order_details" lets HitLens know the order details:

After that, you may safely insert the ending of the HitLens tracking code:

So here's the entire sample tracking script:

Comments (0)

Subscribe to this comment's feed

Name

Email

Website

Title

Comment

Write the displayed characters

Add Comment