Standard v/s custom fields for tracking product information

[Harveer_SinghGi1]

Hi Team,

What could be the pros and cons if we tracked the product information in custom XDM fields instead of standard XDM fields for all commerce events. So instead of using this,

{
  "productListItems": [
    {
      "SKU": "12345",
      "name": "dummy product",
      "priceTotal": 123.45,
      "quantity": 1
    }
  ]
}

what if we used this,

{
  "_tenatID": {
    "product": [
      {
        "SKU": "12345",
        "name": "dummy product",
        "priceTotal": 123.45,
        "quantity": 1
      }
    ]
  }
}

What kind benefits we can get and what will be the drawbacks and limitations?

[bjoern__koth · Accepted solution]

Hi @Harveer_SinghGi1 

in general, using the standard fields makes sure that connected systems can for instance apply automatic mappings, since they know where to look to find product information.

If possible, I would stick with those, especially if you are using multiple Adobe products. Else, the overhead to "make things work" the way you want to can increase.

[Rite18]

@Harveer_SinghGi1  agree with @bjoern__koth it is more of a mapping effort along with governance/label/ AI model which would be more handy if you use standard fields 

[Harveer_SinghGi1]

Thanks for the response @bjoern__koth and @Rite18 . Is there a way of knowing what all standard fields are utilized in which connected services to estimate the affect of dropping them in implementation? Do we have some repository which list down which of standard fields are available in which all connected services and if these are required or optional fields in there?

[Rite18]

@Harveer_SinghGi1, I am not aware of any repo or documentation. The idea behind standard fields is to standardize common use cases for quick and seamless implementation with the Adobe Ecosystem for better performance. However, you can use your fields—maybe you can think of buying a car with a predefined config if it does not fit your needs and customize it.