Search through more than a hundred articles on every aspect of User.com

Alina Shafikova
Written by Alina Shafikova

How to use deals as orders

Check a new possibility of tracking the orders.


Traditional order tracking in User.com mostly relies on front-end event logging, such as capturing a "purchase" event on a thank-you page. While being effective for basic needs, this method has own flaws like low level of flexibility and visibility into order lifecycle.

The "deals as orders" approach introduces a powerful alternative: tracking orders as editable deals, integrated with CRM, analytics, and marketing automation tools.

NOTE! Implementation of "deals as orders" processes require REST API usage. Please, check our API docs.

Definition

Each deal represents a customer order. It stores information about:

  • The user who placed it

  • The products included in the order

  • The value, status, and lifecycle stage

  • Any custom attributes like delivery method, payment channel, or submission date

Deals are fully editable and allow to update the attributes using the dynamic values from the snippet tags. They are an element of theCRM pipelines, which can be used for wider-approach ecommerce processes and support real-time updates throughout the order lifecycle: from submission to cancellation or return.

Main Characteristics

Connection with Products

Deal can include:

  • product_custom_ids: list of connected SKUs that can be used for deal segmentation.

  • order_products: detailed description of the order (SKU, quantity, value, currency, etc.) visualized on a deal profile, that allows to render the values in different communication channels.

Advanced Filtering

  • Snippet tags: for deals snippets filtering by "attributes" option gives a possibility to reach specific orders of the specific user with precise parameters.

  • Filtering & segmentation: possibility to create segments of deals on the basis of the order details and product characteristics.

  • Aggregators: this option allows to print the data from the deals in specific user attributes to make them visible on a User's profile. For example, the value of all orders, number of orders from a specific segment, etc.

Advanced Analytics

  • Using deals as orders allows you to use more options among the available widgets in the Dashboards section.

  • It also gives a possibility to set more precise aggregators for specific use cases.

  • Moreover you can use the CRM module for the ecommerce needs.

Connection with Events

  • You can still log purchase-related events for marketing or analytics purposes.

  • Events offer additional data points, but deals provide deeper CRM integration.

Connection with Product Events

Although many use cases no longer require product-related events, they remain useful for:

  • Personalizing communication

  • Feeding product recommendation engines

  • Enabling advanced segmentation (without aggregators)

How to Configure

You can treat a deal like an order by storing detailed information about the products involved like product ID, quantity, price, and currency. These details will remain fixed, even if the product itself gets updated later. This way, you’ll always be able to see both the original data from the moment the deal was made (like a receipt), and the most current product information.

To configure a deal as an order, you need to send a POST request to the /deals/ endpoint with a payload that includes all relevant order data. The key element is the order_products array, where you can define each product in the order by its product_custom_id, along with its value, currency, quantity, ad other parameters. This data is saved as a static snapshot. You can also include additional metadata such as order date or channel using custom fields.

Endpoints to check:

Example payload:

{
  "name": "Order #12345",
  "custom_id": "12345",
  "user_custom_id": "john-doe-01",
  "value": 249.99,
  "currency": "USD",
  "order_products": [
    {
      "product_custom_id": "SKU-001",
      "value": 99.99,
      "currency": "USD",
      "quantity": 1
    },
    {
      "product_custom_id": "SKU-002",
      "value": 150.00,
      "currency": "USD",
      "quantity": 1
    }
  ],
  "products_custom_id": ["SKU-001", "SKU-002"],
  "stage": 1,
  "status": 1,
  "order_method": "Online",
  "order_date": "2025-06-24T12:00:00Z"
}

Use Cases

RFM Segmentation for Loyalty Campaigns

As an ecommerce brand you want to launch a loyalty program targeting the most valuable customers. Using the "deals as orders" model, you can analyze past purchases using RFM segmentation. Set the aggregators to calculate the total number of deals per user, date of the last purchase and total value of all deals. These values will be stored as separate attributes on user profiles. Based on them you can create a segment with the high RFM scores and later use it in the automations to send personalized messages using various communication channels.

In this case "deals as orders" usage:

  • Increases retention by identifying and rewarding high-LTV users.

  • Drives repeat purchases with minimal manual effort.

  • Improves targeting precision of the campaigns.

Full-Circle Order Lifecycle Tracking

As a B2B retailer you need complete visibility into the customers’ buying journeys from interest to order, shipping, and returns. A deal is created as soon as a user completes checkout. Stages track progress: "Add to cart"→"Order Placed" → "Paid" → "Shipped" → "Delivered". If a product is returned, the deal can be updated. Each user action can trigger a dedicated automation flow to get the feedback, motivate user for the next purchases.

In this scenario "deals as orders" usage:

  • Enables granular segmentation.

  • Helps support team manage and track order status centrally.

  • Allows for highly contextual post-purchase communication.

Related Articles

Categories:
Tags: