Using extracts/Redirects.aspx

TSL Ping Tree > Page Usage

Using extracts/Redirects.aspx

This article explains how to extract data for the Redirect event.  The extract file produced is in Comma Separated Value (CSV) format.  CSV is a popular text-based file format which can be imported by most spreadsheet and database software and can be opened in any editor that supports text based file formats.

TSL Ping Tree has an event driven architecture.  When a visit begins, for example, a Click event is raised and certain tracking information is captured.  When a lead is posted, a Form Submission (a.k.a. Submit) event is raised; this is where data items such as the name and email address of the lead are captured.

The Extracts menu lists all of the supported events.  Each option from that menu presents a web page for extracting data for the selected event.

Query Criteria

Select a time zone and enter a From and a To date.  The From date is inclusive while the To date is exclusive.  For example, to extract a single day's worth of data select that date for the From date and the following date for the To date.

Next enter the number of minutes that you wish to consider a redirect as valid.

As soon as you enter both a From and To date, and if you change a From or To date, the Filename field will automatically change to "Redirects_FromDate-ToDate.csv" e.g. "Redirects_20120101-20120201.csv".  You may change the Filename before clicking the Create Extract button.

Extract File Contents

Field Description
RedirectDateTime_Time_Zone The date and time that the event was raised down the the second.
Millseconds How many milliseconds the system took to process this event.
RedirectGuid A Globally Unique IDentifier (GUID) -based internal unique identifier for the event.
IpAddress The IP Address (v4) of the HTTP request that raised this event.
FormSubmissionGuid A Globally Unique IDentifier (GUID) -based internal unique identifier for the Submit event that produced the Redirect URL.
PingPostGuid A Globally Unique IDentifier (GUID) -based internal unique identifier for the PingPost event that produced the Redirect URL.  If a PingPost did not produce the URL then this field will be empty.
Url The Redirect URL.
Referrer The value of the HTTP "REFERER" (sic) header field for the HTTP request that raised this event.  Browsers and proxy servers control whether this URL is set and if so what URL is supplied.
RedirectCounts TRUE/FALSE: Did the system track a redirect for the Redirect URL within the allowed timeframe?
RedirectDateTime_Time_Zone The date/time the system first tracked a redirect for the Redirect URL, if any.
RawHttpRequestGuid A Globally Unique IDentifier (GUID) -based internal unique identifier for the HTTP request that raised this event.
ClickId An integer-based unique identifier for the associated Click.
SiteId The value of the SiteId (s) visit tracking parameter when the associated Click event was raised.
AffiliateId The value of the AffiliateId (a) visit tracking parameter when the associated Click event was raised.
PromotionId The value of the PromotionId (p) visit tracking parameter when the associated Click event was raised.
SubId1 The value of the SubId1 (s1) visit tracking parameter when the associated Click event was raised.
SubId2 The value of the SubId2 (s2) visit tracking parameter when the associated Click event was raised.
SubId3 The value of the SubId3 (s3) visit tracking parameter when the associated Click event was raised.