|
System
Initialization
This section addresses integration of transaction-management capabilities
to regular web site pages. All shopping cart pages automatically manage
transaction states.
Integration is provided through a set of include files. The files included
contain the various data definitions, functions and libraries. They
perform complex work yet can be easily and transparently implemented.
Pre-Requisites:
This document assumes that the ezStore123 software has been installed
and can communicate with the database server.
Installation and connection issues are normally handled by the VAR
since ezStore123 is marketed as a managed service.
Initialization:
In order to initialize referrer capabilities (click-through), coupon
referral capabilities and/or to manage transaction state when users return
to the main page after completing a sale, the files listed below must be
included in the web site's default page or any page used as an entry point
to the web site.
<!-- #include virtual="/ezStore123/_sysdefs.asp" -->
<!-- #include virtual="/ezStore123/_library.asp" -->
<!-- #include virtual="/ezStore123/_ezs123Init.asp" -->
The main page or entry point page including
the start-up libraries must be processed by IIS as an ASP file or the
initialization will have no effect.
This does not mean the main page or entry point page must have a .ASP
extension. It is possible to configure IIS to process other file types
(such as .HTM or .HTML) Please refer to IIS documentation on how to
process other file types.
Not including the start-up libraries or absence of IIS configuration to
process other file types will not generate errors or disable the shopping cart.
However, customers may encounter adverse effects (such as losing the
cart's content) if they exit the shopping cart pages before completing
their purchase. This limitation does not apply to ezStore123 listings or to
the product detail pages automatically generated by ezStore123.
Leveraging ezStore123 advanced referral capabilities:
Using 'domain by-pass referrals', you can track how the various pages
of your web site refer visitors to shopping cart pages by specifying a
TXREFID
parameter to any hyperlink to a product or listing page.
How-To:
Goal: we want to know how often customers go to shopping cart
pages from a specific page on the web site. In this example, the page will
be called MYPAGE.HTM.
- Create a referrer (referrer code: MYPAGE) using the Admin Center.
- Set up every link pointing to a shopping cart page or listing in
MYPAGE.HTM to specify the referring code. Example:
<a href=/ezstore123/DTCatalogList.asp?TXREFID=MYPAGE>Product
Catalog</a>
The system will automatically track all referrals to the catalog listing
from MYPAGE. Since there are no limits on the number of referrers that can
be created, your referral tracking strategy can be much more sophisticated than
what is shown in this example.
This referring mechanism also applies to any hyperlink referral to any
page on your web site from e-mails, other sites or other documents
supporting hyperlinks. See help topic about Referrers
for a complete discussion of this subject.
Coupon referral using TXREFID
is available in the same fashion. You could provide a
special coupon for visitors clicking from a specific page either on your
own web site or any other referring web site. Both coupon and referrer
features may be used simultaneously if needed. Example:
<a href=/ezstore123/DTCatalogList.asp?TXCOUPONID=MYCOUPON&TXREFID=MYPAGE>Product
Catalog</a>
|
|