Using extracts/Receivables.aspx

TSL Ping Tree > Page Usage

Using extracts/Receivables.aspx

This article explains how to extract data for the Receivable event which represents the revenue side of money - what you are owed from your lead buyers.  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.

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 "Receivables_FromDate-ToDate.csv" e.g. "Receivables_20120101-20120201.csv".  You may change the Filename before clicking the Create Extract button.

You can also include the Form Fields in the extract by checking the "Include Form Fields" checkbox. If you check this, you can also select whether the form field column headers are the Field Name or the Default HTTP Parameter Name. Note that you can not have the header be the actual HTTP parameter for a specific form (if it differs from the Default HTTP Parameter Name) because this value could vary from Ping Tree to Ping Tree within one extract.

Extract File Contents

Field Description
ReceivableDateTime_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.
ReceivableGuid A Globally Unique IDentifier (GUID) -based internal unique identifier for the event.
LeadPointUid An integer-based globally unique identifier for the associated Lead Point.
LeadPointName The Lead Point name.
InterfaceUid An integer-based globally unique identifier for the associated Interface.
InterfaceName The Interface name.
LeadBuyerUid An integer-based globally unique identifier for the associated Lead Buyer.
LeadBuyerName The Lead Buyer name.
LeadBuyerId Your ID for the Lead Buyer.
PingPostGuid A Globally Unique IDentifier (GUID) -based internal unique identifier for the PingPost event that raised this Receivable event.
Amount The Receivable amount owed to you buy your Lead Buyer.
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.
ClickDateTime_Time_Zone The date/time the associated Click event was raised.
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.