Skip to main content

​
Contact Product Purchases

This import is meant to capture aggregated purchase history per Contact, broken down by product category and year. Required fields
  • purchased_amount - Total spend, in USD (Example: 52000, do not include any formatting such as currency symbol $, commas, etc.)
  • year - 4-digit year (Example: 2025)
  • contact_id - Unique customer contact identifier, should match customer Contact ‘contact_id’ field (e.g. ERP customer ID or number; Salesforce Account ID; etc)
One of the following: product_name - Name of product, which should match product definitions linked to Contacts (Examples: Zidua; Xitavo; 3210 Brand; Acuron; Amistar; etc.) OR product_id - Product ID, which should match product ID definitions linked to Contacts (Examples: 1234xyz; etc.) Optional fields
  • crop - Commodity code, see list of supported commodity codes in this CSV attached to this help article; used if product has variable pricing depending on the crop commodity
  • map_item_external_id - Internal unique identifier linking the purchase to an imported point or boundary feature of interest (e.g. retail or wholesale location); if provided, must map to an previously imported location (see Creating Custom Map Layers: Location Points) Example
A contact has one row per product, year, crop, and location combination.
Last modified on September 14, 2026