Revenue Conduit Data Sync: HubSpot Properties
  1. Knowledge Base
  2. Revenue Conduit & HubSpot
  3. Revenue Conduit Data Sync: HubSpot Properties

HubSpot Properties: Property Groups and Properties Overview

Looking for the default fields we sync to the contact record in HubSpot? Some of these are also duplicated for the deal record, refer to the deal record sync property groups overview. This is specific to the marketing portion of HubSpot only.

Note:If the HubSpot Properties you want to use in this feature are NOT showing up in Revenue Conduit, please click the Refresh Fields button in the top right corner and wait 1-2 minutes, then refresh the page. You may need to Logout of Revenue Conduit and log back in if they still aren’t refreshing.Here’s our full article on Refreshing Fields.

RFM Fields

Account Creation Date – Type: Date Picker - The date of the account creation is stored. (Ex. The account was created on 5/12/2016.)
Average Days Between Orders – Type: Number - The average days between orders made by the customers is stored. (Ex. The average days between the orders is 2 days, so every 2 days there will be orders).
Average Order Value – Type: Number - The average order value made by the customer is stored. (Ex. Customer no.1 has an average order value of $250).
First Order Date – Type: Date Picker - The first order date of the customer is stored from the time you signed up in RC up to today. (Ex. The date 5/12/2016 where the customer made its first order).
First Order Value – Type: Number - The first order value of the customer is stored from the time you signed up in RC up to today. (Ex. The first order value of customer no.1 is $150.00).
Last Order Date – Type: Date Picker - The last order date of the customer is stored from the time you signed up in RC up to today. (Ex. The date 5/12/2016 where the customer made its last order).
Last Order Value – Type: Number - The last order value of the customer is stored from the time you signed up in RC up to today. (Ex. The last order value of customer no.1 is $150.00).
Total Number of Orders – Type: Number - The total number of orders made by the customer is stored. (Ex. Customer no.1 has 29 orders).
Total Value of Orders – Type: Number - The total value of orders made by the customer is stored. (Ex. Customer no.1 has a total of $1500.00 value of orders).

ROI Tracking Fields
Abandoned Cart Recovery Workflow Conversion – Type: Single Checkbox - Used for conversion under the Abandoned Cart Recovery Workflow.
Abandoned Cart Recovery Workflow Conversion Amount – Type: Number - The conversion amount for Abandoned Cart Recovery Workflow is stored. (Ex. Customer no.1 made a conversion worth $150.00 through the Abandoned Cart Recovery Workflow).
Abandoned Cart Recovery Workflow Conversion Date – Type: Date Picker - The conversion date for Abandoned Cart Recovery Workflow is stored. (Ex. Customer no.1 made the conversion on 5/12/2016).
Abandoned Cart Recovery Workflow Start Date – Type: Date Picker - The start date for Abandoned Cart Recovery Workflow is stored. (Ex. The Abandoned Cart Recovery Workflow for customer no.1 started on 5/12/2016).

Current ROI Campaign – Type: Dropdown - The campaigns for the Current ROI Campaign is stored. (Ex. The Current ROI Campaign for customerno.1 is 01: MQL Nurture & Conversion).
Customer Reengagement Workflow Conversion – Type: Single Checkbox - Used for conversion under the Customer Reengagement Workflow.
Customer Reengagement Workflow Conversion Amount – Type: Number - The conversion amount for Customer Reengagement Workflow is stored. (Ex. Customer no.1 made a conversion worth $150.00 through the Customer Reengagement Workflow).
Customer Reengagement Workflow Conversion Date – Type: Date Picker - The conversion date for Customer Reengagement Workflow is stored. (Ex. Customer no.1 made the conversion on 5/12/2016).
Customer Reengagement Workflow Start Date – Type: Date Picker - The start date for Customer Reengagement Workflow is stored. (Ex. The Customer Reengagement Workflow for customer no.1 started on 5/12/2016).

Customer Rewards Workflow Conversion – Type: Single Checkbox - Used for conversion under the Customer Rewards Workflow.
Customer Rewards Workflow Conversion Amount – Type: Number - The conversion amount for Customer Rewards Workflow is stored. (Ex. Customer no.1 made a conversion worth $150.00 through the Customer Rewards Workflow).
Customer Rewards Workflow Conversion Date – Type: Date Picker - The conversion date for Customer Rewards Workflow is stored. (Ex. Customer no.1 made the conversion on 5/12/2016).
Customer Rewards Workflow Start Date – Type: Date Picker - The start date for Customer Rewards Workflow is stored. (Ex. The Customer Rewards Workflow for customer no.1 started on 5/12/2016).

MQL Capture, Nurture & Conversion – Type: Single Checkbox - Used for conversion under the MQL Capture, Nurture & Conversion.
MQL Capture, Nurture & Conversion Conversion Amount – Type: Number - The conversion amount for MQL Capture, Nurture & Conversion is stored. (Ex. Customer no.1 made a conversion worth $150.00 through the MQL Capture, Nurture & Conversion).
MQL Capture, Nurture & Conversion Conversion Date – Type: Date Picker - The conversion date for MQL Capture, Nurture & Conversion is stored. (Ex. Customer no.1 made the conversion on 5/12/2016).
MQL Capture, Nurture & Conversion Start Date – Type: Date Picker - The start date for MQL Capture, Nurture & Conversion is stored. (Ex. The MQL Capture, Nurture & Conversion for customer no.1 started on 5/12/2016).

New Customer Workflow Conversion – Type: Single Checkbox - Used for conversion under the New Customer Workflow.
New Customer Workflow Conversion Amount – Type: Number - The conversion amount for New Customer Workflow is stored. (Ex. Customer no.1 made a conversion worth $150.00 through the New Customer Workflow).
New Customer Workflow Conversion Date – Type: Date Picker - The conversion date for New Customer Workflow is stored. (Ex. Customer no.1 made the conversion on 5/12/2016).
New Customer Workflow Start Date – Type: Date Picker - The start date for New Customer Workflow is stored. (Ex. The New Customer Workflow for customer no.1 started on 5/12/2016).

Second Purchase Workflow Conversion – Type: Single Checkbox - Used for conversion under the Second Purchase Workflow.
Second Purchase Workflow Conversion Amount – Type: Number - The conversion amount for Second Purchase Workflow is stored. (Ex. Customer no.1 made a conversion worth $150.00 through the Second Purchase Workflow).
Second Purchase Workflow Conversion Date – Type: Date Picker - The conversion date for Second Purchase Workflow is stored. (Ex. Customer no.1 made the conversion on 5/12/2016).
Second Purchase Workflow Start Date – Type: Date Picker - The start date for Second Purchase Workflow is stored. (Ex. The Second Purchase Workflow for customer no.1 started on 5/12/2016).

Third Purchase Workflow Conversion – Type: Single Checkbox - Used for conversion under the Third Purchase Workflow.
Third Purchase Workflow Conversion Amount – Type: Number - The conversion amount for Third Purchase Workflow is stored. (Ex. Customer no.1 made a conversion worth $150.00 through the Third Purchase Workflow).
Third Purchase Workflow Conversion Date – Type: Date Picker - The conversion date for Third Purchase Workflow is stored. (Ex. Customer no.1 made the conversion on 5/12/2016).
Third Purchase Workflow Start Date – Type: Date Picker - The start date for Third Purchase Workflow is stored. (Ex. The Third Purchase Workflow for customer no.1 started on 5/12/2016).
Customer Fields
Accepts Marketing – Type: Single Checkbox - Used for newsletter. (Ex. The company sent a newsletter and customer check to accepts marketing).
Customer Group – Type: Dropdown - The customer group is stored for customers. (Ex. The customer is a retail customer group).
Shopify Customer Tags – Type: Multiple Checkbox - The tags for Shopify customer is stored.
Shopping Cart Customer ID – Type: Single Line Text - The ID for a Shopify cart is stored. (Ex. Customer no.162 is shopping in a Shopify cart and her ID is 00162).
Shopping Cart Fields

Billing Address Line 1 – Type: Single Line Text - The billing address line 1 of the customer is stored.
Billing Address Line 2 – Type: Single Line Text - The billing address line 1 of the customer is stored.
Billing City – Type: Single Line Text - The city of the billing address of a customer is stored. (Ex. Customer no.1 city is Dorchester).
Billing Country – Type: Single Line Text - The country of the billing address of a customer is stored. (Ex. Customer no.1 country is United States).
Billing Postal Code – Type: Single Line Text - The postal code of the billing address of a customer is stored. (Ex. Customer no.1 postal code is 02124).
Billing State – Type: Single Line Text - The state of the billing address of a customer is stored. (Ex. Customer no.1 state is Massachusetts).

Shipping Address Line 1 – Type: Single Line Text - The shipping address line 1 of the customer is stored.
Shipping Address Line 2 – Type: Single Line Text - The shipping address line 1 of the customer is stored.
Shipping City – Type: Single Line Text - The city of the shipping address of a customer is stored. (Ex. Customer no.1 city is Dorchester).
Shipping Country – Type: Single Line Text - The country of the shipping address of a customer is stored. (Ex. Customer no.1 country is United States).
Shipping Postal Code – Type: Single Line Text - The postal code of the shipping address of a customer is stored. (Ex. Customer no.1 postal code is 02124).
Shipping State – Type: Single Line Text - The state of the shipping address of a customer is stored. (Ex. Customer no.1 state is Massachusetts).

Products & Category Fields

Categories Bought – Type: Multi Checkboxes - The categories for certain products that were bought by the customer is stored. (Ex. Customer no.1 bought product 1 under category 1).
Last Categories Bought – Type: Multi Checkboxes - The last categories for certain products that were bought by the customer is stored. (Ex. Customer no.1 bought its last product under category 1).
Last Product Bought – Type: Single Line Text - The last product bought by the customer is stored. (Ex. Customer no.1 bought its last product called product100).
Last Product Types Bought – Type: Multi Checkboxes - The type of the last product bought by the customer is stored. (Ex. Customer no.1 bought its last product and that product type is socks).
Last Products Bought – Type: Multi Checkboxes - The last products bought by the customer is stored. (Ex. Customer no.1 bought its last products called product100, produc101 and product102).
Last Products Bought HTML – Type: Multi Checkboxes - The last products was bought in HTML by the customer is stored. (Ex. Customer no.1 bought its last products in HTML called product100, produc101 and product102).
Last SKUs Bought – Type: Multi Checkboxes - The last SKU’s bought by the customer is stored. (Ex. Customer bought product101 and its SKU is 1003251).
Last Total Number of Products Bought – Type: Number - The total number of products bought by the customer is stored. (Ex. Customer no.1 last order was 5 product).
Last Vendors Bought – Type: Multi Checkboxes - The last products bought by the vendor is stored. (Ex. Vendor no.1 bought its last products called product100, produc101 and product102).
Product Types Bought – Type: Multi Checkboxes - The types of product bought by the customer is stored. (Ex. Customer no.1 bought several products with different product types like shirts, jeans and foot wear).
Products Bought – Type: Multi Checkboxes - The products bought by the customer is stored. (Ex. Customer no.1 lifetime bought all these products product1, product2 and product3).
Shopify Product Tags – Type: Multi Checkboxes - Shopify product tags are stored. (Ex. Customer no.1 bought product1 in a Shopify cart with the product tag of product_1).
SKUs Bought – Type: Multi Checkboxes - All the SKU’s bought by the customer is stored. (Ex. Customer bought product101 and its SKU is 1003251).
Vendors Bought – Type: Multi Checkboxes - All the products bought by the vendor is stored. (Ex. Vendor no.1 bought its all these products called product100, produc101 and product102).

Abandoned Cart Fields

Abandoned Cart Categories – Type: Multi Checkboxes - All the categories for abandoned cart is stored. (Ex. Customer no.1 has its product under category1 category2 and category3 for its abandoned cart).
Abandoned Cart Counter – Type: Number - The counter for abandoned cart is stored.
Abandoned Cart Date – Type: Date Picker - The abandoned card date is stored. (Ex. Customer no.1 had its abandoned cart last 5/12/2016).
Abandoned Cart Products – Type: Multi Checkboxes - All the products for abandoned cart is stored. (Ex. Customer no.1 had product1, product2 and product3 for its abandoned cart).
Abandoned Cart Products HTML – Type: Multi Checkboxes - The products in HTML for abandoned cart is stored. (Ex. Customer no.1 had its abandoned cart products in HTML called product100, produc101 and product102).
Abandoned Cart URL – Type: Single Line Text - The URL for the abandoned cart is stored. (Ex. Customer no.1 had its abandoned cart and its url is http//:abandonedcart.com/abandoned-cart).

An Overview of the 'Product 1', 'Product 2', and 'Product 3' Property Parameters for 'Abandoned' - If the customer only had one product line-item in their last Abandoned Cart, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last Abandoned Cart, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last abandoned cart, respectively.

Abandoned Product 1 Image URL – Type: Single Line Text - This field allows you to access specific data from the customer's most recent Abandoned Cart for use in your followup automation. This is the URL of the cover image file for the last product the customer abandoned. If the customer only had one product line-item in their last Abandoned Cart, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last abandoned cart, then the parameters for 'Product 1' will apply to the most expensive single product in that last cart while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last cart, respectively. The first image url of the abandon by the customer is stored in this property.(Ex. Customer has most recently abandoned a cart with 4 line items and Product X was the most expensive product in that cart at $150. Abandoned Product 1 Image URL will contain the first product image url of http://samplesite.com/productX/cover-image.jpg)

Abandoned Product 1 Name – Type: Single Line Text - The name of your first product in abandoned cart is stored. (Ex. Customer no.1 have 3 products on its abandoned cart and the first product name is Product101).
Abandoned Product 1 Price – Type: Single Line Text - The price of your first product in abandoned cart is stored. (Ex. Customer no.1 have 3 products on its abandoned cart and the price for its first product is $150.00).
Abandoned Product 1 URL – Type: Single Line Text - The URL of your first product in abandoned cart is stored. (Ex. Customer no.1 have 3 products on its abandoned cart and the URL for its first product is of http://sampleproduct.com/abandoned-cart).

Abandoned Product 2 Image URL – Type: Single Line Text - The image url of your second product in abandoned cart is stored. (Ex. Customer no.1 have 3 products on its abandoned cart and the second product has the image url of http://sampleimage.com/abandoned-cart)
Abandoned Product 2 Name – Type: Single Line Text - The name of your second product in abandoned cart is stored. (Ex. Customer no.1 have 3 products on its abandoned cart and the second product name is Product101).
Abandoned Product 2 Price – Type: Single Line Text - The price of your second product in abandoned cart is stored. (Ex. Customer no.1 have 3 products on its abandoned cart and the price for its second product is $150.00).
Abandoned Product 2 URL – Type: Single Line Text - The URL of your second product in abandoned cart is stored. (Ex. Customer no.1 have 3 products on its abandoned cart and the URL for its second product is of http://sampleproduct.com/abandoned-cart)

Abandoned Product 3 Image URL – Type: Single Line Text - The image url of your third product in abandoned cart is stored. (Ex. Customer no.1 have 4 products on its abandoned cart and the third product has the image url of http://sampleimage.com/abandoned-cart)
Abandoned Product 3 Name – Type: Single Line Text - The name of your third product in abandoned cart is stored. (Ex. Customer no.1 have 4 products on its abandoned cart and the third product name is Product101).
Abandoned Product 3 Price – Type: Single Line Text - The price of your third product in abandoned cart is stored. (Ex. Customer no.1 have 4 products on its abandoned cart and the price for its third product is $150.00).
Abandoned Product 3 URL – Type: Single Line Text - The URL of your third product in abandoned cart is stored. (Ex. Customer no.1 have 4 products on its abandoned cart and the URL for its third product is of http://sampleproduct.com/abandoned-cart).

Current Abandoned Cart – Type: Dropdown - Your current abandoned cart is stored.
Total Number of Cart Products – Type: Number - The total number of cart products is stored. (Ex. Customer no.1 have a total of 17 abandoned cart products).
Total Value of Abandoned Cart – Type: Number - The total value of your abandoned cart is stored. (Ex. Customer no.1 made a total of $1500.00 for its abandoned cart).

Order Fields

Last Order Fulfillment Status – Type: Dropdown - The fulfillment status of the customer’s last order is stored. (Ex. Customer no. 1 had it its last order fulfillment status as success).
Last Order Number – Type: Single Line Text - The number of the last order is stored. (Ex. Customer no.1 last order number is 108261).
Last Order Shipment Carrier – Type: Single Line Text - The shipment carrier of the customer’s last order is stored. (Ex. Customer no.1 made its last order with FedEx as the shipment carrier).
Last Order Shipment Date – Type:Date Picker - The shipment date of the customer’s last order is stored. (Ex. Customer no.1 made its last order and the shipment date was 5/12/2016).
Last Order Shopify Order Source – Type: Dropdown - The order source with the shopify cart of the last order is stored. (Ex. Customer no.1 made its last order through the web).
Last Order Status – Type: Dropdown - The status of the customer’s last order is stored. (Ex. Customer no.1 last order status is successful).
Last Order Tracking Number – Type: Single Line Text - The tracking number of the customer’s last order is stored. (Ex. Customer no.1 made its last order with the tracking number 1653J6E230).
Last Order Tracking URL – Type: Single Line Text - The tracking URL of the customer’s last order is stored. (Ex. Customer no.1 made its last order with the tracking URL http://tracking.com/track-lat-order).
Total Number of Current Orders – Type: Number - The total number of the current order is stored. (Ex. Customer no.1 have a total of 8 current orders).

Coupon Code Fields

Coupon Code Campaign X Expiration Date – Type: Date Picker - The expiration of the coupon code for a certain workflow. (Ex. You have a coupon code for New lead Workflow and that coupon code will expire on 5/19/2016).
Coupon Code Campaign X Offered – Type: Single Line Text - The coupon code offered by a certain workflow is stored.
Coupon Codes Used – Type: Single Line Text - The coupon codes that are used by the customers are stored. (Ex. Customer no.1 used the coupon code 20discount).
Last Coupon Code Used – Type: Single Line Text - The last coupon codes that was used by the customers is stored. (Ex. Customer no.1 last used this coupon code 10EasterSunday).

RFM Segmentation Fields

Monetary Rating – Type: Dropdown - where the monetary rating 5-1 for each customer is stored. (Ex. Customer no.1 has the monetary rating of 1 which means the customer have a total order value of <$100.00. Note that you will be the one to set the desired equivalent for each rating).
Order Frequency Rating – Type: Dropdown - where the frequency rating 5-1 for each customer is stored. (Ex. Customer no.1 has the frequency rating of 1 which means the customer have a total number of orders of <=1. Note that you will be the one to set the desired equivalent for each rating).
Order Recency Rating – Type: Dropdown - where the recency rating 5-1 for each customer is stored. (Ex. Customer no.1 has the recency rating of 1 which means the customer last order was 361+ days ago. Note that you will be the one to set the desired equivalent for each rating).

Multiple Store Feilds

All Stores – Type: Multi Checkboxes - All stores are stored. (Ex. Customer no.1 made its order from store1, store2 and store3).
Last Store – Type: Dropdown - The last store is stored. (Ex. Customer made its order and the last time she made an order is from store1).

Last Product Bought Fields

An Overview of the 'Product 1', 'Product 2', and 'Product 3' Property Parameters for 'Last Product Bought' - If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively.

Last Products Bought Product 1 Image URL– Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the URL of the cover image file for the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The first image url of the last products bought by the customer is stored in this property. (Ex. Customer has most recently placed an order with 4 line items and Product X was the most expensive product in that order at $150. Last Products Bought Product 1 Image URL will contain the first product image url of http://samplesite.com/productX/cover-image.jpg)

Last Products Bought Product 1 Name – Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the Name of the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The first product name of the last product bought by the customer is stored in this Property. (Ex. Customer has most recently placed an order with 4 line items and Product X was the most expensive product in that order at $150. Last Products Bought Product 1 Name will contain the name value of "Product X")

Last Products Bought Product 1 Price – Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the Price of the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The first product price of the last product bought by the customer is stored in this property. (Ex. Customer has most recently placed an order with 4 line items and Product X was the most expensive product in that order at $150. Last Products Bought Product 1 Price will contain the value of $150.00)

Last Products Bought Product 1 URL – Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the URL of the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The first product url of the last product bought by the customer is stored in this Property. (Ex. Customer has most recently placed an order with 4 line items and Product X was the most expensive product in that order at $150. Last Products Bought Product 1 URL will contain the value of http://samplesite.com/productX).

Last Products Bought Product 2 Image URL– Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the URL of the cover image file for the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The 2nd image url of the last products bought by the customer is stored in this property. (Ex. Customer has most recently placed an order with 4 line items and Product Y was the 2nd most expensive product in that order at $100. Last Products Bought Product 2 Image URL will contain the first product image url of http://samplesite.com/productY/cover-image.jpg)

Last Products Bought Product 2 Name – Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the Name of the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The 2nd product name of the last product bought by the customer is stored in this Property. (Ex.Customer has most recently placed an order with 4 line items and Product Y was the 2nd most expensive product in that order at $100. Last Products Bought Product 2 Name will contain the name value of "Product Y")

Last Products Bought Product 2 Price – Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the Price of the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The first product price of the last product bought by the customer is stored in this property. (Ex.Customer has most recently placed an order with 4 line items and Product Y was the 2nd most expensive product in that order at $100. Last Products Bought Product 2 Price will contain the value of $100.00)

Last Products Bought Product 2 URL – Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the URL of the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The first product url of the last product bought by the customer is stored in this Property. (Ex.Customer has most recently placed an order with 4 line items and Product Y was the 2nd most expensive product in that order at $100. Last Products Bought Product 2 URL will contain the value of http://samplesite.com/productY).

Last Products Bought Product 3 Image URL– Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the URL of the cover image file for the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The first image url of the last products bought by the customer is stored in this property. (Ex. Customer has most recently placed an order with 4 line items and Product Z was the 3rd most expensive product in that order at $40. Last Products Bought Product 3 Image URL will contain the first product image url of http://samplesite.com/productZ/cover-image.jpg)

Last Products Bought Product 3 Name – Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the Name of the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The first product name of the last product bought by the customer is stored in this Property. (Ex. Customer has most recently placed an order with 4 line items and Product Z was the 3rd most expensive product in that order at $40. Last Products Bought Product 3 Name will contain the name value of "Product Z")

Last Products Bought Product 3 Price – Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the Price of the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The first product price of the last product bought by the customer is stored in this property. (Ex.Customer has most recently placed an order with 4 line items and Product Z was the 3rd most expensive product in that order at $40. Last Products Bought Product 3 Price will contain the value of $40.00)

Last Products Bought Product 3 URL – Type: Single Line Text - This field allows you to access specific data from the customer's most recent purchase for use in your followup automation. This is the URL of the last product the customer purchased. If the customer only had one product line-item in their last order, then all product data will be stored under the 'Product 1' parameters. If there were multiple line items in their last order, then the parameters for 'Product 1' will apply to the most expensive single product in that last order while 'Product 2' and 'Product 3' parameters will apply to the 2nd and 3rd most expensive single products in that last order, respectively. The first product url of the last product bought by the customer is stored in this Property. (Ex.Customer has most recently placed an order with 4 line items and Product Z was the 3rd most expensive product in that order at $40. Last Products Bought Product 3 URL will contain the value of http://samplesite.com/productZ).