--- title: "Historical Transactions/Purchases Parameters" slug: "historical-transactionspurchases-parameters" updated: 2020-04-16T20:58:53Z published: 2020-04-16T20:58:53Z canonical: "onpremises.webtrends.help/historical-transactionspurchases-parameters" --- > ## Documentation Index > Fetch the complete documentation index at: https://onpremises.webtrends.help/llms.txt > Use this file to discover all available pages before exploring further. # Historical Transactions/Purchases Parameters Webtrends generates and maintains these parameters using the Webtrends analysis process when you enable Visitor History. For more information, see “Visitor History Parameters.” The following parameters are calculated using the transaction parameters. For more information, see “Transaction Parameters.” #### WT.vr.vv `WT.vr.vv=VisitorValue` Webtrends generates this Visitor History parameter to track the visitor’s overall value, which is the value of all purchases recorded for a visitor over time. This is a floating-point value containing the amount of money spent by this visitor back to and including the visitor’s first visit. When using this as a measure for dimensions other than Visitor, you usually configure the average value. The sum of this measure has no meaning. #### WT.vr.ltb `WT.vr.ltb=High/Moderate/Some/Low descriptor` Webtrends generates this Visitor History parameter to classify the `WT.vr.vv` parameter value in one of four categories. The value is non-numeric and is used as a custom report dimension. You can change the number of categories by editing the `vrbucket.ini` file. By default, the file is configured as follows: `[LTBValues]` `High = 750` `Moderate = 500` `Some = 250` The following table shows the meaning of the default values: | [LTBValues] | Meaning | | --- | --- | | High=750 | x >750 | | Moderate=500 | 500 > x <750 | | Some=5 | 250> x <500 | By default, the minimum value for `Some` is 250. Any visitor whose value is less than 250 is assigned to the Low category. Example 1: Adjust all of the ranges in `vrbucket.ini` to: `[LTBValues]` `High = 1500` `Moderate = 1000` `Some = 500` Example 2: To create two buckets (for example, *`High/Low`*), change `vrbucket.ini` to: `[LTBValues]` `High = 750` `Moderate = 750` `Some = 750` The result of example 2 is: `High` is >750 `Low` is >0 <750 #### WT.vr.ppv `WT.vr.ppv=PreviousPurchaseValue` Webtrends generates this Visitor History parameter to track the visitor’s previous purchase amount. This is a floating-point value containing the amount spent on the most recent purchase. This parameter is not generated until a visitor makes the first purchase. When using this parameter as a custom report measure for the Visitor dimension, use the maximum value. When using this parameter as a measure for dimensions other than Visitor, you usually configure the average value. The sum of this measure has no meaning. #### WT.vr.vp `WT.vr.vp=VisitorPurchases` Webtrends generates this Visitor History parameter to track the total number of purchases ever made by a visitor. The value is an integer containing the number of purchase transactions (not the total number of units purchased) back to and including the visitor’s first visit. When using this parameter as a custom report measure for the Visitor dimension, use the maximum value. When using this parameter as a measure for dimensions other than Visitor, you usually configure the average value. The sum of this measure has no meaning. #### WT.vr.fpd `WT.vr.fpd=DaysSinceFirstPurchase` Webtrends generates this Visitor History parameter to track the days since the visitor’s first purchase. The value is an integer containing the days since the visitor’s first purchase. This parameter is best used as a visit filter or as a custom report measure. This parameter is not generated until a visitor makes the first purchase. When using this parameter as a measure for the Visitor dimension, use the maximum value. When using this parameter as a measure for dimensions other than Visitor, you usually configure the average value. The sum of this measure has no meaning. #### WT.vr.bpd `WT.vr.bpd=DaysBeforeFirstPurchase` Webtrends generates this Visitor History parameter to track the days before the visitor’s first purchase. The value is an integer containing the number of days between the visitor’s first visit and the first purchase. This parameter is best used as a visit filter or as a measure. This parameter is not provided until a visitor makes the first purchase. When using this as a measure for dimensions other than Visitor, you usually configure the average value. The sum of this measure has no meaning. Webtrends generates the following set of parameters to track unique buyers and buyer’s status for daily, weekly, monthly, quarterly, yearly, and lifetime periods. #### WT.vr_brws `WT.vr_brws=Buyer/Non-Buyer` Webtrends generates this query parameter on a visitor’s first visit of the day. Its value indicates whether a visitor has purchased in the past. Buyer indicates that the visitor has purchased before. `Non-buyer` indicates that the visitor has not purchased. A visitor is considered a buyer if the `WT.tx_s` parameter is passed in the query string for the visit. A visitor is considered a non-buyer if `WT.tx_s` is not passed in the query string. In addition, Webtrends uses the following invoice parameters to evaluate whether `WT.tx_s` should be used for buyer determination: - `WT.tx_id` and `WT.tx_it` - `WT.tx_i` If both `WT.tx_id` and `WT.tx_it` parameters are passed during the visit and are properly formatted, Webtrends uses them to evaluate whether `WT.tx_s` should be used for buyer determination. If the date and time specified by these parameters is older than the time of the hit by more than the configured invoice age limit, `WT.tx_s` is not used and the visitor is considered a non-buyer. The invoice age limit is set at two days, meaning that any invoices three days or older than the first hit associated with the invoice are not used for buyer determination. If the `WT.tx_i` parameter is passed during the visit, Webtrends uses it to evaluate whether `WT.tx_s` should be used for buyer determination. Webtrends looks for the invoice number passed in for this query parameter in the visitor’s invoice history. If it has seen this invoice number before, `WT.tx_s` is not used and the visitor is considered a non-buyer. Three invoices are kept per visitor. Invoices more than two days old are purged from the visitor’s invoice history. #### WT.vr_by `WT.vr_by=New Buyer/Repeat Buyer` Webtrends generates this Visitor History parameter when a visitor makes a purchase. It indicates whether the visitor is purchasing for the first time or has purchased before. #### WT.vr.bt_d `WT.vr.bt_d=1` Webtrends generates this Visitor History parameter to identify the visitor’s first daily purchase. This parameter is generated and set to 1 for the first purchase from a visitor for a day. #### WT.vr.bt_w `WT.vr.bt_w=1` Webtrends generates this Visitor History parameter to identify the visitor’s first weekly purchase. This parameter is generated and set to 1 for the first purchase from a visitor during a week. #### WT.vr.bt_m `WT.vr.bt_m=1` Webtrends generates this Visitor History parameter to identify the visitor’s first monthly purchase. This parameter is generated and set to 1 for the first purchase from a visitor during a month. #### WT.vr.bt_q `WT.vr.bt_q=1` Webtrends generates this Visitor History parameter to identify the visitor’s first quarterly purchase. This parameter is generated and set to 1 for the first purchase from a visitor during a quarter. #### WT.vr.bt_y `WT.vr.bt_y=1` Webtrends generates this Visitor History parameter to identify the visitor’s first yearly purchase. This parameter is generated and set to 1 for the first purchase from a visitor during a year. #### WT.vr.bt_f `WT.vr.bt_f=1` Webtrends generates this Visitor History parameter to identify the visitor’s first purchase. This parameter is generated and set to 1 for the first purchase from a visitor.