Has purchased

Has Purchased returns a list of orders that meets the threshold that you define – for example, exactly 4, less than 5, more than 2, or between 2 and 10 – and occurred during your chosen date range. For example, return all customers who have purchased 3 (or more) times in the previous 2 years:

After you specify a value and date range you may apply filters to associate customers who have purchased with specific products, brands, channels, and stores. For example, return all customers who have purchased wool or cotton socks from your website.

What are purchase behaviors?

Purchase behaviors are a feature of Amperity that are built on top of standard output for transactions (orders and items). Purchase behaviors require standardized product catalog field names to be present in your standard output for transactions.

Use purchase behaviors in segments to return a list of customers, and then filter that list of customers by any combination of brand, channel, individual items in your product catalog, and store.

Purchase behaviors are available for first order, has not purchased, has purchased, most frequent order, repeat order, and total value of orders.

How has purchased works

Has Purchased returns a list of orders that meets the threshold that you define – for example, exactly 4, less than 5, more than 2, or between 2 and 10 – and occurred during your chosen date range. For example, return all customers who have purchased 3 (or more) times in the previous 2 years:

After you specify a value and date range you may apply filters to associate customers who have purchased with specific products, brands, channels, and stores. For example, return all customers who have purchased wool or cotton socks from your website.

How this attribute works

Has Purchased represents a common approach people use when they build segments: start with all orders, and then associate that list of orders to the products and brands your customers purchased.

Has Purchased is a compound attribute, which means that it’s built from a combination of attributes that already exist in your data, and then appears as a single attribute that you can choose from the Segment Editor.

With this attribute, you can focus less on SQL and more on finding answers that align to your marketing goals and strategies. Purchase behavior attributes simplify the number of steps that are required to associate a list of customers to your products, stores, channels, and brands.

Tip

For more information about how Has Purchased works, including an explanation of the SQL that runs behind the Segment Editor, review the Has Purchased topic in the Amperity A-Z reference.

Use has purchased in a segment

To find all customers who made their first order within a specified date range, start with the Has Purchased attribute located under Purchase behaviors:

After the attribute appears in your segment, set the purchase count and choose a date range:

After you specify a purchase count and date range you may apply filters to associate these customers to specific products, brands, channels, and stores.

Example: Who has purchased a watch?

The following example uses Has Purchased to return a list of customers who have purchased at least one watch within the previous two years:

Available conditions

The following table lists the conditions that are available to this attribute.

Note

Recommended conditions for this attribute are identified with “ More useful” and conditions with more limited use cases are identified with “ Less useful”.

Condition	Description
between	Returns a list of customers whose order threshold is in-between two specified values.
exactly	Returns a list of customers whose order threshold exactly matches specified value.
less than	Returns a list of customers whose order threshold is less than the specified value.
more than	Returns a list of customers whose order threshold is more than the specified value.

Filter attributes

A filter attribute is a standard column that is output by Amperity and is available from the Unified Itemized Transactions table. When a filter attribute is associated with a purchase behavior attribute, you may use them to filter the results by specific items in your product catalog, such as by brand, by channel, by store, or by specific details about the items in your product catalog, such as color, SKU, and so on. The list of filter attributes that will be available for product catalogs depends on their availability within your Unified Itemized Transactions table.