Why item-level data matters

af_order_info is an event parameter that reports the individual items in an order, whether the order has one item or several. It replaces the older af_content and af_content_list fields with a single, more complete format for the same purpose. It supports two consistent array formats for both single-item and multi-item orders and works across five networks (Google Ads, DV360, Meta, TikTok, Snapchat, and Pinterest) rather than requiring a separate structure for each.

Sending this level of detail matters because these networks now optimize campaigns using more than just an order's total value. Meta, Google, TikTok, Snapchat, and Pinterest all support optimization algorithms that work at the product level, using details such as item ID, price, quantity, category, and brand to improve targeting and bidding. The more complete the item breakdown you send, the more these networks can use to fine-tune those campaigns.

Parameter structure

Each item in an order can be described using up to 7 fields. AppsFlyer supports two ways to structure these fields under af_order_info, described below.

It is sent as part of your event's event_value (or custom_data), and it works the same way whether the order has one item or several, so you can standardize on it rather than maintaining multiple order data formats.

The seven fields are:

AppsFlyer supports two ways to structure af_order_info, both nested under event_value:

• One field for all items (recommended): each field, such as sku, revenue, and qty, is sent once, as an array that covers every item in the order. This keeps the payload shorter.
• One object per item: each item in the order is sent as its own object, with all relevant fields nested inside it.

The following example shows the recommended format, with one field for all items:

{
  "af_order_info": {
    "sku": ["SKU-001", "SKU-002", "SKU-003"],
    "revenue": [50.00, 75.00, 25.00],
    "qty": [1, 1, 2],
    "content_name": ["Wireless Mouse", "Bluetooth Headphones", "USB-C Cable"],
    "content_type": ["product", "product", "product"],
    "content_category": ["accessories", "audio", "cables"],
    "brand": ["Logitech", "Sony", "Anker"]
  }
}

The following example shows the alternative format, with one object per item:

{
  "af_order_info": [
    {
      "sku": "SKU-001",
      "revenue": 50.00,
      "qty": 1,
      "content_name": "Wireless Mouse",
      "content_type": "product",
      "content_category": "accessories",
      "brand": "Logitech"
    },
    {
      "sku": "SKU-002",
      "revenue": 75.00,
      "qty": 1,
      "content_name": "Bluetooth Headphones",
      "content_type": "product",
      "content_category": "audio",
      "brand": "Sony"
    },
    {
      "sku": "SKU-003",
      "revenue": 25.00,
      "qty": 2,
      "content_name": "USB-C Cable",
      "content_type": "product",
      "content_category": "cables",
      "brand": "Anker"
    }
  ]
}

Per-network mapping

AppsFlyer reads the af_order_info array and automatically restructures it into the format each network's API expects. Field support varies by network, so not every field you send reaches every network. The following table shows the fields each network currently supports:

"app_event_data": {
  "items": [
    {"item_id": "SKU-001", "quantity": "1", "price": "50.0"},
    {"item_id": "SKU-002", "quantity": "1", "price": "75.0"},
    {"item_id": "SKU-003", "quantity": "2", "price": "25.0"}
  ]
}

"fb_content": [
  {"id": "SKU-001", "quantity": 1, "item_price": 50.00},
  {"id": "SKU-002", "quantity": 1, "item_price": 75.00},
  {"id": "SKU-003", "quantity": 2, "item_price": 25.00}
]

"properties": {
  "contents": [
    {
      "content_type": "product",
      "content_category": "accessories",
      "content_name": "Wireless Mouse",
      "quantity": 1,
      "brand": "Logitech",
      "content_id": "SKU-001",
      "price": 50.00
    }
  ],
  "currency": "USD",
  "value": 175.00
}

&item_ids=SKU-001,SKU-002,SKU-003&number_items=5&price=50.00,75.00,25.00&brands=Logitech,Sony,Anker&category=accessories,audio,cables

"contents": [
  {"id": "SKU-001", "item_price": "50.00", "quantity": 1},
  {"id": "SKU-002", "item_price": "75.00", "quantity": 1},
  {"id": "SKU-003", "item_price": "25.00", "quantity": 2}
]

Backward compatibility

Existing formats also continue to work, including the array-based af_content_id, af_quantity, and af_price fields, and the af_content and af_content_list fields. You do not need to migrate existing implementations. af_order_info will be available in a single, more complete format going forward. It is particularly useful if you want to pass richer item details, such as name, category, and brand, than the older formats support.

Traits and limitations