Sections:
Introduction to Datasets
Using Traffic Activity Tracking Reports and Tools
Sub-Page Visitor Activity Tracking
Conversion rate report
Enhanced Advertisement tracking - SrcTag
Spider Filters
SRC URL Filters
Referrer Report
Local Product Searches
Referrer Sales Report
CTracker Order and Whois Report
Correlated Sales Report
Q Phrase Report
Click Through Reports
Page Load Report
Exact Match Sales Report
Enhanced CTracker Operation
Referral Header Information
Click-Fraud Report
Technical Details
Advanced Search Engine Optimization System
List of ISO 3166 country codes
List of ISO 639 language codes
Introduction
SendSafe can track visitors and customers to the site and then through the site - while collecting as much detail as you
need on activity.
Far more accurate reports are possible than with log analyzers or JavaScript page tagging systems, because this tracking is
tightly integrated with the e-commerce system, web, and database servers. SendSafe uses 100% server-side tracking logic for the
highest possible accuracy. Other system require JavaScript redirects or other techniques which are less reliable and can be
easily blocked.
SendSafe's Traffic Activity Tracking is included with the purchase of SendSafe.
SendSafe Sub-Page Visitor Activity Tracking is included with the purchase of SendSafe's e-storefront framework.
SendSafe also includes an advanced next generation automatic search engine optimization system (SEOS) which covers the entire site.
As customers arrive at your site, SendSafe's Traffic Activity Tracking shows the relationship between PPC advertisements and sales. SendSafe can track and report on immediate-purchases as well as delayed-returning-customer purchases and much more. This type of reporting is something you cannot get with Google or Overture(Yahoo) reports which can only accurately show immediate sales.
While customers are at your site, SendSafe Sub-Page Visitor Activity Tracking shows detailed customer activity at the sub-page level. Setting up SendSafe based visitor tracking is the advanced solution and is the most powerful and accurate method available on the market today. It is the only solution that can give you super-detailed sub-page activity tracking. For example:
Sub-Page Visitor Activity reporting tools are not included. While SendSafe does capture this very detailed data, Sub-Page Visitor Activity reporting requires site specific custom reporting tools to view the data which is captured. You can create these tools using SQL Query Analyzer OR CPrompt can design and build them for you.
SendSafe Sub-Page Visitor Activity Tracking can provide web-log-analyzer like reports such as page load counts but with much greater detail than the web-log-analyzer option. For example: with web-log-analyzers, you can get a report that shows that a particular product display page was loaded 10 times but you often cannot know which products were displayed on the page OR which customer/visitor it was that loaded that page and saw those products. i.e. with the web-log-analyzer option you can report that the product display page was loaded but you will not know what dynamic content was displayed on that page. The best analogy is television: you know the television was tuned to channel 11, but you do not know what was playing on channel 11 at that time the person looked at the screen.
There are a number of built in reporting tools in SendSafe, but much more can be added. Theses tools can be used to build consolidated marketing reports, tracking PPC click through rates, report on conversion rates, and more. It is possible with custom tracking addons to accurately track the exact sequence of events from when a customer arrives at the site, to how they browse products, enter products into the shopping cart, and then checkout.
There are a number of key items used to analyze Site Activity. Theses items are:
MIReferrer: The database column where the referrer information is stored for a customer. This information can be used for verification and measurement of PPC advertising. Note: This information does not include the SrcTag or Browser type data which is saved in the eventlog. This this extended info you will need to cross-reference to the eventlog records associated with this order.
function getReferrer(): The function which retrieve cached referrer information from cookies.
SendSafe.RefCapture.inc.asp: This is the include file which contains programming logic which captures referrer information for customer records. This file needs to be included in all NON-SENDSAFE ASP webpage (none SendSafe pages are pages which do not include basic SendSafe support functions). For core SendSafe webpages and Store.* webpages, SendSafe.RefCapture.inc.asp is included as part of SendSafe.pageinfo.inc.asp logic.
sub logSessionEvent(): The function logs all visitors to the system. One EventLog entry is made for every visit (debounced with session cookie continuity checking). Event = 10001 (ecVistorTracking). Logic is invoked when the Sub Application_SendSafe_OnStartSession event fires.
EventLog table: The Eventlog database table contains various event logs including visitor arrival and customer login/logoff. Security related events are also included in this table.
EventLogArchive table: The EventlogArchive database table is an optional table which contains archived event logs. This table should be setup for all higher traffic sites. To disable use of archive set Application("EventLogArchive") = "".
Event ecVistorTracking: The ecVistorTracking event contains the IP Address of the visitor and in the info field the first 256 characters of the referrer URL (i.e. www.yahoo.com ……). This record can be used for verification and measurement of PPC advertising and can help in cases of click fraud. The customerID is not known at this stage of a visit and therefore will always be zero. Custom reports can be created for this information. This record is also used by the SendSafe conversion rate report. Special search engine tags can be (optionally) included. If the search engine URL includes a tag then the value of that tag is saved along with referrer information. The tag is defined by Application("SActivityPPATag") = "SrcTag"
One tracking event will be added to the DB for each new visit. A visit is defined as any of the followingThese various events are filtered and reported. The absence of referrer information can be used to identify a bookmark or URL entry. The presence of referrer information can be used to identify a website link or search result. The presence of a SrcTag can be used to absolutely identity the source.
- A search engine link is clicked
- A bookmark is clicked
- A URL is typed into the browser
- A link on a webpage is clicked
Event ecVistorPageLoad or ecCustomerPageLoad: The ecVistorPageLoad or ecCustomerPageLoad events contain the IP Address of the visitor, the customerID (if a customer record) or the Session.ID (if a vistor record), and in the info field the file that was loaded:See also Sub-Page Visitor Activity Tracking.
- full file name of webpage - If the file was directly loaded
- root file name for webpage subcomponent - if CLDR/CLDRF dynamic loading is involved
- full file name of webpage plus AdCodeId - If the file load was the result of an advertisement clickcount
- If the vistor is a spider then the info field will contain the name of the spider.
Event ecVistorPBrowse or ecCustomerPBrowse: The ecVistorPBrowse or ecCustomerPBrowse events contain the IP Address of the visitor, the customerID (if a customer record) or the Session.ID (if a vistor record), and either:See also Sub-Page Visitor Activity Tracking.
- When product browsing is occurring: the DB field being queried and the value being selected (i.e. AdvSearch=red or Lev2List=Consulting)
- When a product showcase is loaded: showcase = productID.
Event ecVistorLBrowse or ecCustomerLBrowse: The ecVistorLBrowse or ecCustomerLBrowse events contain the IP Address of the visitor, the customerID (if a customer record) or the Session.ID (if a vistor record), and either:See also Sub-Page Visitor Activity Tracking.
- When listing browsing is occurring: no part of the SQL query is saved in the eventlog; the size of the complex queries is too big to be saved in an eventlog record (metrics are available from ecSQLBLoadMetric). Note: The query string is saved in the audit records with a tag of: "B1>>> Query set"
- When a showcase is loaded: showcase = indexKey for the listing.
Event ecVistorAddToCart or ecCustomerAddToCart: The ecVistorPBrowse or ecCustomerPBrowse events contain the IP Address of the visitor, the customerID (if a customer record) or the Session.ID (if a vistor record), and in the info field the ItemCodeId of the item that was added to the cart. See also Sub-Page Visitor Activity Tracking.
Event ecSQLBLoadMetric: The PRODUCT BROWSER ecSQLBLoadMetric events contain the IP Address of the visitor, the customerID (if a customer record) or the Session.ID (if a vistor record), and a count of the number of records returned for display as a result of the SQL DB Selection. This data which is used to analyze SQL DB load from the product browser search engine.
Event ecSQLLLoadMetric: The LISTING BROWSER ecSQLLLoadMetric events contain the IP Address of the visitor, the customerID (if a customer record) or the Session.ID (if a vistor record), and a count of the number of records returned for display as a result of the SQL DB Selection. This data which is used to analyze SQL DB load from the listing browser search engine.
Conversion Rate Report: This report shows what percentage of visitors bought something. It is the single most important sales efficiency measurement tool available for a website. This ratio allows you to make changes to your site and then measure the effects of those changes.
Using Traffic Activity Tracking Reports and Tools
We have several different kinds of reports that are used to review information on sales vs. advertisements.
SendSafe has these reports on-line:
With these reports we can get stats on search engine referrals and overall sales. This allows for analysis of effectiveness of advertisements.
*These reports require additional SendSafe configuration. If you want these reports added to your storefront contract your system admin or CPrompt.
CPrompt can also develop many different custom data mining report which can dig out other correlations between search engine referrals and sales. With data mining, we can draw correlations between people that bookmarked and then bought days later.
SRC URL Filters
This filter is very important. The filter operates on the entire URL including parameters.
It is used to select specific sources of traffic for analysis. Typically an SrcTag will be used
in this field to limit the report to a specific advertisement or other source of traffic.
This field accepts multiple entires delimited by commas. Each entry can have a '-' minus sign prefix which means EXCLUDE any URL which contains this phrase.
TIPS:
Spider Filters
The SPIDER dropdown on the reports page allows you to choose to include or exclude spiders from your report.
Spiders are internet-robots which visit a site and index it. Google, Yahoo, etc. all use spiders.
If you do not exclude spiders from your reports, you will see many non-human visitors since the spiders will be reported as visitors to the site.
Since spiders do not buy anything (yet), it is advisable to exclude them from all reports unless you are specifically analyzing spider
activity on the site; in which case you should include only the spiders.
Settings:
Please note that using the spider filter on reports can dramatically alter the reported results. The spider filter will not work on Exact Match Sales Reports.
CTracker Orders and Whois Report
This Traffic Activity Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
This report lists the orders and customerid (whois) for a specific Ctracker code and date range. This report is useful to find which orders occured for Ctrackers which were found in other reports such as CTracker Sales reports.
Transactions will be listed more than once if multiple Ctrackers were found with linkage to the same transaction. Multiple records for the same transaction will be grouped together. SRC URL Filter is not valid for this report.
Referrer Report
This Traffic Activity Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
The referrer and referrer grouped reports show the raw data that was captured SendSafe. This data is used for other reports. This data is captured regardless whether a visitor has cookies enabled, javascript enabled, etc. It is the single most accurate capture of site activity data. Far more accurate that WebTrends-like log analyzer reports and far more accurate that native search engine reports. This data comes from the eventlog database table.
See Referral Header Information for an understanding what the data in this report means.
Note: grouped reports will often show a different total than non-grouped reports. This difference is due to the fact grouped reports require referrer information including URL parameters. Non-grouped reports do not require this information. So items without this information can show up in the non-grouped report.
Click Through Report
This Traffic Activity Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
See the referrals to buying sites or other desired events which have occured are link those events back to the advertising source. Events are any Eventype=10001 event. These events are logged by the SendSafe.clcr.asp page or a custom page.
Use the Src URL Filter to select the traffic source sites you would like to check. Leave the DST Page filter empty or set it to a specific click-through target or event note (i.e. amazon.com or ebay.com)
This report lists click-through events which occur on your site (not an advertiser's site); for example: someone clicks on a link which loads amazon.com OR loads a PDF page for viewing. The click-through event is captured by using the SendSafe.clcr.asp redirector page (see usage below).
There are several version of this report: "Click Through Report" and "Click Through Report with Src Filer" with various reporting additions
This report uses CTracker to link multiple events together. In this case of this report, the initial referer event is linked. You can enter SRC URL filter values such as the name of the referring website i.e. "nytimes" or a SrcTag i.e. (Google. By entering this type of filter information you can answer questions like: "How many click-throughs from an advertising source resulted in a local click-through event"
The click through src report can be used to see which advertising sources resulted in visitors performing the desired click-through or event.
The Click Through Count Report can be very useful in assessing how productive a given advertisement or other traffic source is in generating click-throughs. This report when used in combination with SrcTag filters in the SRC URL field provides statistics for the SrcTaged source.
SendSafe.clcr.asp page usage:
Usage: SendSafe.clcr.asp?s=index.asp&c=cid&r=http://www.hshsg.com
c = customerId (optional)
r = redirect URL
s = source tag
Example:
<a target=_blank href="http://www.yoursite.com/SendSafe.clcr.asp?s=index.asp&r=http://www.amazon.com/books/dp/182736">Amazon.com</a>
<a target=_blank href="http://www.yoursite.com/SendSafe.clcr.asp?s=index.asp&r=http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?z=y%26EAN=1234567%26itm=1">Barnes & Noble</a>
Use the CTracker Order and Whois Report to identify specific orders and customers shown in this report.
Page Load Report
This Traffic Activity Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
Use the Pageload Count report to see if a specific traffic source is sending interested visitors. Use +/- URL filters to select the traffic source sites you would like to check. The more pages a visitor clicks on, the more interested they are in your site. Once click or two click wonders are visitors that are not interested in what they have found on your site.
Set the destination page filter to limit this report to specific pages on your site.
This report lists target page load events; for example the buying page was loaded or a special information was loaded. The page load to check for is entered into the "DST PAGE FILTER" field. This does not have to be a full page name (SQL %yourpage% wild cards are used AND therefore it is possible to include multiple similar pages).
There are two version of this report. "Click Through Report" and "Click Through Report with Src Filer"
The "page load count" version of this report is very useful in ranking and identifying which advertising sources are sending people which load more pages and are therefore generally more active visitors.
This report uses CTracker to link multiple events together. In this case of this report, the initial referer event is linked. You can enter SRC URL filter values such as the name of the referring website i.e. "nytimes" or a SrcTag i.e. (Google. By entering this type of filter information you can answer questions like: "How many click-throughs from an advertising source resulted in a specific page load"
For this report to work, Sub-Page Visitor Activity Tracking must be enabled AND Application("urlfor_BASEORDERINGPAGE") must be set correctly to the page where orders are placed.
Use the CTracker Order and Whois Report to identify specific orders and customers shown in this report.
Local Product Searches
This report lists events when customers search on your site for products on your site. Both product searches and product browsing
are included in this report i.e. ecSQLLoadMetric eventtype = 10017.
The Search term or browser drilldown category is listed along with the number of records which were returned. The Term Information is tagged with a "C" for category or an "A" for Advanced Search.
The "Local Product Search per Hour" report shows how many searches were performed per hour. This is a measure of the workload the system is functioning under.
Q Phrase and Q Phrase Grouped Report
This Traffic Activity Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
Use these reports to list what people typed into Google. This is the search phrase which brought them to your site.
This report will list search phrases and (in the grouped report) the number of times that search phrase was used. This report will only work with search engines which use the "Q=" URL search format. All other search engine results will not be included. This report will include google and some of google's affiliated networks.
See Referral Header Information for an understanding what the data in this report means.
Phrase Grouped Report
This Traffic Activity Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
This report will list search phrases and the number of times that search phrase was used. This report will list all search phrase in raw URL format including all URL parameters with the "&" delimited removed.
Note: grouped reports will often show a different total than non-grouped reports. This difference is due to the fact grouped reports require referrer information including URL parameters. Non-grouped reports do not require this information. So items without this information can show up in the non-grouped report.
Referrer Sales Report
This Traffic Activity Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
See which search terms contributed to sales.
This report lists all referrer data associated with all sales. This powerful report uses data mining and CTracker data to link customer who bought products with the search terms they typed to find the site. This report will also show which advertisements brought them.
This report is almost 100% inclusive; unlike exact match or correlated sales. This report is more complicated to interpret since it is possible that a single buyer may have been brought to the site by multiple ads, and therefore, multiple ads will be reported. It is up to the user to understand the implications of multi-sourced buyers and account for it in any statistical analysis.
This report mines data in three steps:
Use the CTracker Order and Whois Report to identify specific orders and customers shown in this report.
There are three different versions of this report:
Referrer Sales Report: Use this report to identify long term treads in customer interest in specific advertisements. This report collects into a pool all customers that completed a purchase during their entire history with the site. This report then filters to include only customers who clicked on ads during a period of twice the date range or a minimum of 10 days. The report can be further filtered by the source URL (tag) and other filters you set.
Referrer Sales Report Date limited: Use this report to gauge the effectiveness of a promotion over time. This report can be used to list only sales resulting from a click which occured around a period of time. This report collects into a pool all customers who completed a purchase during a period of twice the date range or a minimum of 10 days. The report can be further filtered by the source URL (tag) and other filters you set.
Referrer Sales Report Exact Range: Use this report to measure the immediate short-term results of a promotion. This report can be used to list only sales resulting from a click which occured during an exact date range (i.e. limited to an advertisement campaign run). This report collects into a pool all customers who completed a purchase during the exact date range entered for the report. The report can be further filtered by the source URL (tag) and other filters you set.
CTracker data capture for these reports is extended beyond the entered date range for a period of twice the date range or a minimum of 10 days.
Correlated Sales Report
This Traffic Activity Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
The purpose of this report is to show sales which can be attributed to search engines. The report shows a filtered subset of impulse and collateral buyers and the ads which brought them to the site. This report will not show you all the collateral or impulse buyers but does show you a reliable subset designed for use for statistical analysis.
This report shows the relationship between search engine clicks and delayed purchases. This report will show you that a customer clicked on PPC advertisement 2 months ago and then bought the product today returning via a bookmark.
This report performs data mining to identify relationships between search engine click-throughs and subsequent sales. This report differs from reports such as "Exact Match Sales" because this report will relate a sale to a click-through that occurred during a different (prior) visit to the site; where the visit to the site can have occurred as much as 90 days prior to the sale.
The date range of records checked for correlation will be equal to the start date of the report minus 90 days.
The IP Address included in this report is the IP Address with which the order was stamped. This IP Address is an ironclad identifier of where this order came from and can be used to correlate this order to other events.
Filters only apply to correlated sales NOT exact match which are included in this report.
This report will include all exact match orders which occurred during the timeframe. Exact match bypasses all filtering; and therefore exact match orders will be included in a report regardless any IP Address or URL filters used.
This type of data mining does not generate 100% results; sales that should be included are sometimes not picked up in the report and visa versa. Typically more sales are excluded wrongly then included wrongly. It is difficult to state a single accuracy figure for this type of data mining report. Here are a few examples:
Important Note: An automatic filter is applied for this report to accurately identify correlated sales. This filter will exclude pages loaded from bookmarks that cannot be unassociated with a search engine click-through. This filter is [ NOT LIKE '%yoursite.com%' ].
The correlates sales report uses intelligent IP data mining NOT matching. This is done to capture the sales from people who use modems or broadband with dynamic IP addresses.
Exact Match Sales Report
This Traffic Activity Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
Use this report to see your impulse buyers. This report shows only customers who can be 100% confirmed to have come to the site and bought immediately.
Important filtering note: You must not use Spider Filtering with this report. Disable spider filtering by selecting the "ignore" option from the dropdown box.
This report shows the relationship between search engine clicks and immediate purchases. This report will show you that a customer clicked on PPC advertisement and then during the same visit purchased a product.
This report identifies 100% certain relationships between a search engine click-through and an immediate sale. To be included in this report the sale must have occurred during the same visit as the search engine click-through. The vistor must have cookies enabled in their browser for this report to capture their sales information.
All sales reported in by exact Match will also be found by the data mining report correlated Sales.”
The IP Address included in this report is the IP Address with which the order was stamped. This IP Address is an ironclad identifier of where this order came from and can be used to correlate this order to other events.
Important Note: An automatic filter is applied for this report to accurately identify correlated sales. This filter will exclude pages loaded from bookmarks that cannot be unassociated with a search engine click-through. This filter is [ NOT LIKE '%yoursite.com%' ].
100% accurate relationships can only be captured when a customer comes from the search engine and then makes a purchase. If the customer bookmarks the site and then returns another day to make their purchase, a 100% accurate relationship cannot be made. So 100% accurate relationship data is valuable, but it will not include all sales attributable to a search engine. Therefore, it only provides a partial picture which must then be augmented with statistics from other SendSafe reports such as the "Correlated Sales Report."
Enhanced CTracker Operation
This Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
This report shows in great detail what a customer does and in what order they did it! This report shows the search terms used to get to the site, it shows the pages visited on the site, it shows the products purchased, and it does ALL this spanning mulitiple visits and days.
CTracker enhanced operation uses a cookie to identify and track returning visitors. Without Ctracker, correlated sales and other reports must rely on fuzzy IP address to identify a vistor. While fuzzy IP address identification works reasonably well, there are miss identifications which can occur when a proxy or NAT device is used by the vistor.
CTracker saves a GUID in the CTracker column of the event log. This Ctracker value can then be used to link otherwise disparate eventlog records together. Important notes on using Ctracker in reports:
The Sendsafe.ShoppingODBC.inc.asp file contains logic which reads the GUID CTracker value from the cookie Request.Cookies("REFINFO")("TK").
Every EventLog entry is then stamped with the GUID obtained from the cookie.
CTracker is disabled by default on older systems. For an older systems to use CTracker, a CTracker column to their DB. Once the column is found, the system will automatically enable CTracker operation (Application("SACtivityCTracker") = true).
[CTracker] char (20) NULLThe function which performs this automated on/off function is: setSACtivityCTracking().
The function logSessionEvent() in globalcode.in.asa will create a GUID Ctracker value for any visitor that does not already have a GUID.
Click-Fraud Report
This Tracking report can be found in the SendSafe Activity Report Admin web page vao.SiteActivityReport.asp
The Click-Fraud report shows which IP addresses are repeatedly accessing your site via PPC advertisements.
It is recommended that you include a SActivityPPATag in the URL FILTER fields. This will limit the report to a specific PPC source (i.e. Google or Yahoo).
This report will show when someone using the same or similar IP address is repeatedly clicking on your PPC advertisements. This system does not rely on statistics from PPC vendors or end users; and therefore cannot be tampered with. Disguising the originating IP Address of the source is impossible. The only way this report can be partially affected is if the source of the click-fraud is using a blind proxy to relay their HTTP traffic; and this effort at disguise does not prevent the clicks from being identified as fraudulent, it only hampers the ability to identify the ultimate perpetrator.
A reverse DNS lookup should be preformed on all questionable IP Addresses to identify the company or individual.
This report generates far more accurate results than WebTrends-like log analyzer reports and far more accurate than results native search engine reports. This data comes from the eventlog database table.
Referer Header Information
A key source of detailed referral information comes from data provided by each visitor's web browser.
This information is found in the "HTTP referer header" (yes, it's spelled Referer instead of Referrer). This header information is a key source of offsite
tracking data.
Every browser keeps a record of the hyperlink that was clicked on which brought the browser to its current webpage destination. The information found in the "HTTP referer header" includes both the URL of the web site where the link was located and all URL parameters. Search engines use URL parameters to perform searches and as a side-result, these URL parameters are included in the "HTTP Referer header." This means that the query which was entered by a visitor on a search engine is passed to the destination HTTP server as part of a page load request (HTTP GET). The SendSafe system will record this reliable PPA/CPM advertising information as long as the HTTP header information is intact.
Referral header information can be blocked by 3rd party security software or special anonymous ISP configurations. SendSafe can also used Enhanced Advertisement Tracking which cannot be blocked by either security software OR anonymous ISP configurations. For high accuracy PPC advertisement tracking, using Enhanced Advertisement Tracking is strongly recommend.
Referer header information is difficult for a nontechnical person to block. No current browsers block it because to do so would cripple many different kinds of security, auditing, and commence functions on a vast number of websites. Some 3rd party security programs sold to consumers have the ability to block some of this Referer information. The result is that consumers using this security software find that while invisible information is blocked, for some unknown reason some websites just don't work anymore because they needed Referer information to function.
Blocking Referer information is a misguided attempt to preserve anonymity. This information is not useful for abuse and reveals nothing secret. All it does is send a copy of the "URL which was clicked" to the same webpage which was opened by that same click. It does not contain a history of past sites. It does not reveal personal information. It is anonymous marketing data.
Interpreting Referer information in SendSafe:
SendSafe captures all the referering information avaialable at the time of first contact. SendSafe adds some additional information to each
block of captured referer header information. Each entry is flagged by SemdSafe with extra visitor information.
The first 1 character code in each entry indicates the following:
Referer information is HTML URL encoded. This means some punctuation charcaters are encoded by the referring website (google, yahoo, etc.).
Character Code
(Hex)Dollar ("$")
Ampersand ("&")
Plus ("+")
Comma (",")
Forward slash/Virgule ("/")
Colon (":")
Semi-colon (";")
Equals ("=")
Question mark ("?")
'At' symbol ("@")24
26
2B
2C
2F
3A
3B
3D
3F
40
These codes will appear in phrases and look like this: This is John %26 Mary.
Where %26 = the ampersand '&'."
Enhanced Advertisement tracking - SrcTag
Enhanced Advertisement tracking is used to differentiate between PPC clicks and non-paid-for search engine clicks.
Enhanced Advertisement tracking does not rely on Referral Header Information and therefore cannot be blocked by security programs or other filtering devices.
When using enhance tracking, all of the sales containing the “(Enhanced tracking)” source tag can be attributed to the PPC vendor with almost 100% certainty. For example, you can be very sure that sales tagged with the “(google)” tag came from google, a google affiliate, or a site which scraped google PPC search results. All of these sources are 100% attributable to google and sales which you would not have had without the google PPC listing.
Enhanced tracking tags are included in the event log by adding a special tracking tag in the URL which is used by your advertisement. The tag is defined by Application("SActivityPPATag") = "SrcTag". The search engine advertisement URL will need to include this tag as a URL parameter. For example: the following tag will result in all traffic coming from your advertisement on Google being tagged in the event log with the word "(google)" - www.yousite.com/index.asp?SrcTag=Google
Conversion Rate Report
This report can be found in the SendSafe Admin web page v2.AdminConvRate.asp
The industry average conversion rate is 0.5% to 2%. This means about 1 out of every 100 visitors buys something. This is a broad average covering all e-commerce sites that participate in marketing studies.
Conversion rates do vary broadly depending upon product line, price, target demographics, policies, and focus of advertising and pay-per-click.
These listed ranges are averages of all industries and should only be used as rough guides. What is import are any trends in conversion rate for your business. Medium term trends of a few months (up or down) should be investigated to see what has been changed. Valuable information for tuning the website and your business practices can be obtained from this report.
Industry experience has shown a range of 0.3% to 25%. The industry benchmarks on Conversion rates are:
Data from this report is set up so that you can directly cut & paste data from the web page into an Excel spread sheet. To do this ONLY mark the report data itself and no other areas of the web page, then cut & paste.
Data column descriptions:
| Month | This is the month for this line of the report |
| Day | This is the day for this line of the report |
| Year | This is the year for this line of the report |
| Orders | This is the total number of orders completed during this period |
| Sales | This is the total dollar amount of all completed sales (charges which failed to authorize are not included) |
| Sessions | This is the total number of sessions on the web site during this period. A visitor may come back more than once during a day and this will result in more than one session which will marginally inflate the true session count. |
| Uniques | This is the total number of unique visitor sources to the web site during this period. Due to technical limitations in tracking largely anonymous visitations, this count is always lower than the number of visitors unless all visitors are using static Internet routable workstation IP addresses (which is very unlikely). |
| Visitors | This is the estimated total number of visitors to the web site during this period. Due to technical limitations in tracking largely anonymous visitations, this count is an estimation. |
| Conv rate Sessions | This is the ratio of the number of unique sessions verses number of orders completed. |
| Conv rate Uniques | This is ratio of the total number of uniques verses number of orders completed. |
| Conv rate Visitors | This is a calculated visitor standard conversion ratio which is the most accurate of the three different ratios which are displayed. This ratio uses the average number of sessions, uniques, and visitor to calculate the ratio of orders placed. |
Sub-Page Visitor Activity Tracking
Capturing Sub-Page Visitor Activity Tracking data is an optional add-on in the e-store framework.
This tracking data provides superior accuracy for tracking which pages are loaded and more importantly
(for dynamic content sites) what is displayed on the content page or product browsing pages that are loaded.
The system also tracks as separate events every time an item is added to the cart.
The logic which captures this information is located in the e-store framework (incfile_loader.inc.asp:incFileLoaderWriter_ENDPAGE()).
The key browsing events are:
For Sub-Page Visitor Activity Tracking to function, Application("SACtivityPageLevDetail") = true
Sub-Page Visitor Activity reporting tools are not included. While SendSafe does capture this very detailed data, reporting requires site specific custom reporting tools to view it effectively. You can create these tools using SQL Query Analyzer OR CPrompt can design and build them for you.
The tracking data is used for two different analytical purposes: customer behavior and content popularity.
The Analysis of behavior data usually follows one the paths listed below; other paths are possible.
Popularity Ratings usually includes some of the following:
ecVisitorTracking: Visitor session is the key activity tracking for incoming visitors (both customers and non-customers). The ecVisitorTracking data including CTracker is captured in the sendsafe.globalcode.inc.asa file -> logSessionEvent() which is part of the Sub Application_SendSafe_OnStartSession event handler.
ecCustomerTracking: is unused at this time.
If you use application level redirects from one domain name to another ON THE SAME PHYSICAL SITE then you will experience multiple duplicate eventlog entries in the database table. You can eliminate these duplicate entires by using the control variable Application("SActivitySiteLimiter") to limit capturing to a specific website domain name (i.e. www.c-prompt.com).
ecCustomerPBrowse: is captured IF SACtivityPageLevDetail = true. The capture occurs inside the incfile_loader.asp module invoked by the browser.inc.asp module.
Advanced Search Engine Optimization System
All websites managed by the SendSafe e-store framework use dynamic database driven content.
This type of website works differently than static HTML.
All dynamic content sites should have dynamic / automatic SEO.
SendSafe has dynamic / automatic SEO.
The site detects a visiting search engine spider and display itself in a way that's very friendly to spiders and very ugly to people.
This means that the website looks totally different to search engines than people:
Spider visits are logged in the eventlog. The eventlog record will be ecVisitorPageLoad type with the information field set to the "HTTP_USER_AGENT" value = the name of the spider. The info field will have a prefix of: "SPDR="
CLDR/CLDRF pages can be excluded from spider SEO indexing by including a postfix of .NL. in the sub component file name.
Sample Configuration for global.inc.asa
' Spider Control
Application("SpiderDisplayOnThisPage") = "index.asp"
Application("SpiderDisplayDynamicContentRender") = "CLDR.asp?PG=
Application("SpiderProductDisplayPage") = "whatisoffered.asp"
Application("SpiderDynamicFileMatchToInclude") = "xxx.inc.htm"
Application("SpiderDisplayPageIncludeFile") = "spider.inc.htm"
Application("SpiderListOfContents") = true
Application("SpiderListOfPages") = true
Application("SpiderDynamicFileMinSizeToInclude") = 1000
ISO 3166 Country Codes
Below is a list of the international standard ISO 3166 Country Codes. You will find these codes embedded in the
URL strings which have been captured except for the USA (which often has no country code appended).
All these codes are applied by the search engine. The exact format will vary from one search engine to the next.
AFGHANISTAN AF ÅLAND ISLANDS AX ALBANIA AL ALGERIA DZ AMERICAN SAMOA AS ANDORRA AD ANGOLA AO ANGUILLA AI ANTARCTICA AQ ANTIGUA AND BARBUDA AG ARGENTINA AR ARMENIA AM ARUBA AW AUSTRALIA AU AUSTRIA AT AZERBAIJAN AZ BAHAMAS BS BAHRAIN BH BANGLADESH BD BARBADOS BB BELARUS BY BELGIUM BE BELIZE BZ BENIN BJ BERMUDA BM BHUTAN BT BOLIVIA BO BOSNIA AND HERZEGOVINA BA BOTSWANA BW BOUVET ISLAND BV BRAZIL BR BRITISH INDIAN OCEAN TERRITORY IO BRUNEI DARUSSALAM BN BULGARIA BG BURKINA FASO BF BURUNDI BI CAMBODIA KH CAMEROON CM CANADA CA CAPE VERDE CV CAYMAN ISLANDS KY CENTRAL AFRICAN REPUBLIC CF CHAD TD CHILE CL CHINA CN CHRISTMAS ISLAND CX COCOS (KEELING) ISLANDS CC COLOMBIA CO COMOROS KM CONGO CG CONGO, THE DEMOCRATIC REPUBLIC OF THE CD COOK ISLANDS CK COSTA RICA CR CÔTE D'IVOIRE CI CROATIA HR CUBA CU CYPRUS CY CZECH REPUBLIC CZ DENMARK DK DJIBOUTI DJ DOMINICA DM DOMINICAN REPUBLIC DO ECUADOR EC EGYPT EG EL SALVADOR SV EQUATORIAL GUINEA GQ ERITREA ER ESTONIA EE ETHIOPIA ET FALKLAND ISLANDS (MALVINAS) FK FAROE ISLANDS FO FIJI FJ FINLAND FI FRANCE FR FRENCH GUIANA GF FRENCH POLYNESIA PF FRENCH SOUTHERN TERRITORIES TF GABON GA GAMBIA GM GEORGIA GE GERMANY DE GHANA GH GIBRALTAR GI GREECE GR GREENLAND GL GRENADA GD GUADELOUPE GP GUAM GU GUATEMALA GT GUINEA GN GUINEA-BISSAU GW GUYANA GY HAITI HT HEARD ISLAND AND MCDONALD ISLANDS HM HOLY SEE (VATICAN CITY STATE) VA HONDURAS HN HONG KONG HK HUNGARY HU ICELAND IS INDIA IN INDONESIA ID IRAN, ISLAMIC REPUBLIC OF IR IRAQ IQ IRELAND IE ISRAEL IL ITALY IT JAMAICA JM JAPAN JP JORDAN JO KAZAKHSTAN KZ KENYA KE KIRIBATI KI KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF KP KOREA, REPUBLIC OF KR KUWAIT KW KYRGYZSTAN KG LAO PEOPLE'S DEMOCRATIC REPUBLIC LA LATVIA LV LEBANON LB LESOTHO LS LIBERIA LR LIBYAN ARAB JAMAHIRIYA LY LIECHTENSTEIN LI LITHUANIA LT LUXEMBOURG LU MACAO MO MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF MK MADAGASCAR MG MALAWI MW MALAYSIA MY MALDIVES MV MALI ML MALTA MT MARSHALL ISLANDS MH MARTINIQUE MQ MAURITANIA MR MAURITIUS MU MAYOTTE YT MEXICO MX MICRONESIA, FEDERATED STATES OF FM MOLDOVA, REPUBLIC OF MD MONACO MC MONGOLIA MN MONTSERRAT MS MOROCCO MA MOZAMBIQUE MZ MYANMAR MM NAMIBIA NA NAURU NR NEPAL NP NETHERLANDS NL NETHERLANDS ANTILLES AN NEW CALEDONIA NC NEW ZEALAND NZ NICARAGUA NI NIGER NE NIGERIA NG NIUE NU NORFOLK ISLAND NF NORTHERN MARIANA ISLANDS MP NORWAY NO OMAN OM PAKISTAN PK PALAU PW PALESTINIAN TERRITORY, OCCUPIED PS PANAMA PA PAPUA NEW GUINEA PG PARAGUAY PY PERU PE PHILIPPINES PH PITCAIRN PN POLAND PL PORTUGAL PT PUERTO RICO PR QATAR QA RÉUNION RE ROMANIA RO RUSSIAN FEDERATION RU RWANDA RW SAINT HELENA SH SAINT KITTS AND NEVIS KN SAINT LUCIA LC SAINT PIERRE AND MIQUELON PM SAINT VINCENT AND THE GRENADINES VC SAMOA WS SAN MARINO SM SAO TOME AND PRINCIPE ST SAUDI ARABIA SA SENEGAL SN SERBIA AND MONTENEGRO CS SEYCHELLES SC SIERRA LEONE SL SINGAPORE SG SLOVAKIA SK SLOVENIA SI SOLOMON ISLANDS SB SOMALIA SO SOUTH AFRICA ZA SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS GS SPAIN ES SRI LANKA LK SUDAN SD SURINAME SR SVALBARD AND JAN MAYEN SJ SWAZILAND SZ SWEDEN SE SWITZERLAND CH SYRIAN ARAB REPUBLIC SY TAIWAN, PROVINCE OF CHINA TW TAJIKISTAN TJ TANZANIA, UNITED REPUBLIC OF TZ THAILAND TH TIMOR-LESTE TL TOGO TG TOKELAU TK TONGA TO TRINIDAD AND TOBAGO TT TUNISIA TN TURKEY TR TURKMENISTAN TM TURKS AND CAICOS ISLANDS TC TUVALU TV UGANDA UG UKRAINE UA UNITED ARAB EMIRATES AE UNITED KINGDOM GB UNITED STATES US UNITED STATES MINOR OUTLYING ISLANDS UM URUGUAY UY UZBEKISTAN UZ VANUATU VU Vatican City State see HOLY SEE VENEZUELA VE VIET NAM VN VIRGIN ISLANDS, BRITISH VG VIRGIN ISLANDS, U.S. VI WALLIS AND FUTUNA WF WESTERN SAHARA EH YEMEN YE Zaire see CONGO, THE DEMOCRATIC REPUBLIC OF THE ZAMBIA ZM ZIMBABWE ZW
ISO 639 Language Codes
Below are two lists of the international standard ISO 639 Language Codes. You will sometimes find these codes embedded in the
URL strings which have been captured. Often the two letter codes are used but sometimes you will find the
three letter codes. All these codes are applied by the search engine. The exact format will vary from
one search engine to the next.
AA "Afar" AB "Abkhazian" AF "Afrikaans" AM "Amharic" AR "Arabic" AS "Assamese" AY "Aymara" AZ "Azerbaijani" BA "Bashkir" BE "Byelorussian" BG "Bulgarian" BH "Bihari" BI "Bislama" BN "Bengali" "Bangla" BO "Tibetan" BR "Breton" CA "Catalan" CO "Corsican" CS "Czech" CY "Welsh" DA "Danish" DE "German" DZ "Bhutani" EL "Greek" EN "English" "American" EO "Esperanto" ES "Spanish" ET "Estonian" EU "Basque" FA "Persian" FI "Finnish" FJ "Fiji" FO "Faeroese" FR "French" FY "Frisian" GA "Irish" GD "Gaelic" "Scots Gaelic" GL "Galician" GN "Guarani" GU "Gujarati" HA "Hausa" HI "Hindi" HR "Croatian" HU "Hungarian" HY "Armenian" IA "Interlingua" IE "Interlingue" IK "Inupiak" IN "Indonesian" IS "Icelandic" IT "Italian" IW "Hebrew" JA "Japanese" JI "Yiddish" JW "Javanese" KA "Georgian" KK "Kazakh" KL "Greenlandic" KM "Cambodian" KN "Kannada" KO "Korean" KS "Kashmiri" KU "Kurdish" KY "Kirghiz" LA "Latin" LN "Lingala" LO "Laothian" LT "Lithuanian" LV "Latvian" "Lettish" MG "Malagasy" MI "Maori" MK "Macedonian" ML "Malayalam" MN "Mongolian" MO "Moldavian" MR "Marathi" MS "Malay" MT "Maltese" MY "Burmese" NA "Nauru" NE "Nepali" NL "Dutch" NO "Norwegian" OC "Occitan" OM "Oromo" "Afan" OR "Oriya" PA "Punjabi" PL "Polish" PS "Pashto" "Pushto" PT "Portuguese" QU "Quechua" RM "Rhaeto-Romance" RN "Kirundi" RO "Romanian" RU "Russian" RW "Kinyarwanda" SA "Sanskrit" SD "Sindhi" SG "Sangro" SH "Serbo-Croatian" SI "Singhalese" SK "Slovak" SL "Slovenian" SM "Samoan" SN "Shona" SO "Somali" SQ "Albanian" SR "Serbian" SS "Siswati" ST "Sesotho" SU "Sudanese" SV "Swedish" SW "Swahili" TA "Tamil" TE "Tegulu" TG "Tajik" TH "Thai" TI "Tigrinya" TK "Turkmen" TL "Tagalog" TN "Setswana" TO "Tonga" TR "Turkish" TS "Tsonga" TT "Tatar" TW "Twi" UK "Ukrainian" UR "Urdu" UZ "Uzbek" VI "Vietnamese" VO "Volapuk" WO "Wolof" XH "Xhosa" YO "Yoruba" ZH "Chinese" ZU "Zulu"
abk ab Abkhazian
ace Achinese
ach Acoli
ada Adangme
aar aa Afar
afh Afrihili
afr af Afrikaans
afa Afro-Asiatic (Other)
aka Akan
akk Akkadian
alb/sqi sq Albanian
ale Aleut
alg Algonquian languages
tut Altaic (Other)
amh am Amharic
apa Apache languages
ara ar Arabic
arc Aramaic
arp Arapaho
arn Araucanian
arw Arawak
arm/hye hy Armenian
art Artificial (Other)
asm as Assamese
ath Athapascan languages
map Austronesian (Other)
ava Avaric
ave Avestan
awa Awadhi
aym ay Aymara
aze az Azerbaijani
nah Aztec
ban Balinese
bat Baltic (Other)
bal Baluchi
bam Bambara
bai Bamileke languages
bad Banda
bnt Bantu (Other)
bas Basa
bak ba Bashkir
baq/eus eu Basque
bej Beja
bem Bemba
ben bn Bengali
ber Berber (Other)
bho Bhojpuri
bih bh Bihari
bik Bikol
bin Bini
bis bi Bislama
bra Braj
bre be Breton
bug Buginese
bul bg Bulgarian
bua Buriat
bur/mya my Burmese
bel be Byelorussian
cad Caddo
car Carib
cat ca Catalan
cau Caucasian (Other)
ceb Cebuano
cel Celtic (Other)
cai Central American Indian (Other)
chg Chagatai
cha Chamorro
che Chechen
chr Cherokee
chy Cheyenne
chb Chibcha
chi/zho zh Chinese
chn Chinook jargon
cho Choctaw
chu Church Slavic
chv Chuvash
cop Coptic
cor Cornish
cos co Corsican
cre Cree
mus Creek
crp Creoles and Pidgins (Other)
cpe Creoles and Pidgins, English-based (Other)
cpf Creoles and Pidgins, French-based (Other)
cpp Creoles and Pidgins, Portuguese-based (Other)
cus Cushitic (Other)
hr Croatian
ces/cze cs Czech
dak Dakota
dan da Danish
del Delaware
din Dinka
div Divehi
doi Dogri
dra Dravidian (Other)
dua Duala
dut/nla nl Dutch
dum Dutch, Middle (ca. 1050-1350)
dyu Dyula
dzo dz Dzongkha
efi Efik
egy Egyptian (Ancient)
eka Ekajuk
elx Elamite
eng en English
enm English, Middle (ca. 1100-1500)
ang English, Old (ca. 450-1100)
esk Eskimo (Other)
epo eo Esperanto
est et Estonian
ewe Ewe
ewo Ewondo
fan Fang
fat Fanti
fao fo Faroese
fij fj Fijian
fin fi Finnish
fiu Finno-Ugrian (Other)
fon Fon
fra/fre fr French
frm French, Middle (ca. 1400-1600)
fro French, Old (842- ca. 1400)
fry fy Frisian
ful Fulah
gaa Ga
gae/gdh Gaelic (Scots)
glg gl Gallegan
lug Ganda
gay Gayo
gez Geez
geo/kat ka Georgian
deu/ger de German
gmh German, Middle High (ca. 1050-1500)
goh German, Old High (ca. 750-1050)
gem Germanic (Other)
gil Gilbertese
gon Gondi
got Gothic
grb Grebo
grc Greek, Ancient (to 1453)
ell/gre el Greek, Modern (1453-)
kal kl Greenlandic
grn gn Guarani
guj gu Gujarati
hai Haida
hau ha Hausa
haw Hawaiian
heb he Hebrew
her Herero
hil Hiligaynon
him Himachali
hin hi Hindi
hmo Hiri Motu
hun hu Hungarian
hup Hupa
iba Iban
ice/isl is Icelandic
ibo Igbo
ijo Ijo
ilo Iloko
inc Indic (Other)
ine Indo-European (Other)
ind id Indonesian
ina ia Interlingua (International Auxiliary language Association)
ine - Interlingue
iku iu Inuktitut
ipk ik Inupiak
ira Iranian (Other)
gai/iri ga Irish
sga Irish, Old (to 900)
mga Irish, Middle (900 - 1200)
iro Iroquoian languages
ita it Italian
jpn ja Japanese
jav/jaw jv/jw Javanese
jrb Judeo-Arabic
jpr Judeo-Persian
kab Kabyle
kac Kachin
kam Kamba
kan kn Kannada
kau Kanuri
kaa Kara-Kalpak
kar Karen
kas ks Kashmiri
kaw Kawi
kaz kk Kazakh
kha Khasi
khm km Khmer
khi Khoisan (Other)
kho Khotanese
kik Kikuyu
kin rw Kinyarwanda
kir ky Kirghiz
kom Komi
kon Kongo
kok Konkani
kor ko Korean
kpe Kpelle
kro Kru
kua Kuanyama
kum Kumyk
kur ku Kurdish
kru Kurukh
kus Kusaie
kut Kutenai
lad Ladino
lah Lahnda
lam Lamba
oci oc Langue d'Oc (post 1500)
lao lo Lao
lat la Latin
lav lv Latvian
ltz Letzeburgesch
lez Lezghian
lin ln Lingala
lit lt Lithuanian
loz Lozi
lub Luba-Katanga
lui Luiseno
lun Lunda
luo Luo (Kenya and Tanzania)
mac/mak mk Macedonian
mad Madurese
mag Magahi
mai Maithili
mak Makasar
mlg mg Malagasy
may/msa ms Malay
mal Malayalam
mlt ml Maltese
man Mandingo
mni Manipuri
mno Manobo languages
max Manx
mao/mri mi Maori
mar mr Marathi
chm Mari
mah Marshall
mwr Marwari
mas Masai
myn Mayan languages
men Mende
mic Micmac
min Minangkabau
mis Miscellaneous (Other)
moh Mohawk
mol mo Moldavian
mkh Mon-Kmer (Other)
lol Mongo
mon mn Mongolian
mos Mossi
mul Multiple languages
mun Munda languages
nau na Nauru
nav Navajo
nde Ndebele, North
nbl Ndebele, South
ndo Ndongo
nep ne Nepali
new Newari
nic Niger-Kordofanian (Other)
ssa Nilo-Saharan (Other)
niu Niuean
non Norse, Old
nai North American Indian (Other)
nor no Norwegian
nno Norwegian (Nynorsk)
nub Nubian languages
nym Nyamwezi
nya Nyanja
nyn Nyankole
nyo Nyoro
nzi Nzima
oji Ojibwa
ori or Oriya
orm om Oromo
osa Osage
oss Ossetic
oto Otomian languages
pal Pahlavi
pau Palauan
pli Pali
pam Pampanga
pag Pangasinan
pan pa Panjabi
pap Papiamento
paa Papuan-Australian (Other)
fas/per fa Persian
peo Persian, Old (ca 600 - 400 B.C.)
phn Phoenician
pol pl Polish
pon Ponape
por pt Portuguese
pra Prakrit languages
pro Provencal, Old (to 1500)
pus ps Pushto
que qu Quechua
roh rm Rhaeto-Romance
raj Rajasthani
rar Rarotongan
roa Romance (Other)
ron/rum ro Romanian
rom Romany
run rn Rundi
rus ru Russian
sal Salishan languages
sam Samaritan Aramaic
smi Sami languages
smo sm Samoan
sad Sandawe
sag sg Sango
san sa Sanskrit
srd Sardinian
sco Scots
sel Selkup
sem Semitic (Other)
sr Serbian
scr sh Serbo-Croatian
srr Serer
shn Shan
sna sn Shona
sid Sidamo
bla Siksika
snd sd Sindhi
sin si Singhalese
sit - Sino-Tibetan (Other)
sio Siouan languages
sla Slavic (Other)
ssw ss Siswant
slk/slo sk Slovak
slv sl Slovenian
sog Sogdian
som so Somali
son Songhai
wen Sorbian languages
nso Sotho, Northern
sot st Sotho, Southern
sai South American Indian (Other)
esl/spa es Spanish
suk Sukuma
sux Sumerian
sun su Sudanese
sus Susu
swa sw Swahili
ssw Swazi
sve/swe sv Swedish
syr Syriac
tgl tl Tagalog
tah Tahitian
tgk tg Tajik
tmh Tamashek
tam ta Tamil
tat tt Tatar
tel te Telugu
ter Tereno
tha th Thai
bod/tib bo Tibetan
tig Tigre
tir ti Tigrinya
tem Timne
tiv Tivi
tli Tlingit
tog to Tonga (Nyasa)
ton Tonga (Tonga Islands)
tru Truk
tsi Tsimshian
tso ts Tsonga
tsn tn Tswana
tum Tumbuka
tur tr Turkish
ota Turkish, Ottoman (1500 - 1928)
tuk tk Turkmen
tyv Tuvinian
twi tw Twi
uga Ugaritic
uig ug Uighur
ukr uk Ukrainian
umb Umbundu
und Undetermined
urd ur Urdu
uzb uz Uzbek
vai Vai
ven Venda
vie vi Vietnamese
vol vo Volapük
vot Votic
wak Wakashan languages
wal Walamo
war Waray
was Washo
cym/wel cy Welsh
wol wo Wolof
xho xh Xhosa
sah Yakut
yao Yao
yap Yap
yid yi Yiddish
yor yo Yoruba
zap Zapotec
zen Zenaga
zha za Zhuang
zul zu Zulu
zun Zuni