feat: SDKE-482 support custom product attributes

[jaissica12]

Instructions

1. PR target branch should be against development
2. PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
3. PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary

Add Product Attribute Mapping for Facebook Purchase Events
- Implement buildProductContents() to create nested contents array for Purchase events
- Add productAttributeMapping setting for configurable field mapping
- Map TransactionId to order_id parameter
- Support mapping both product fields and custom attributes
- Add test coverage for the changes

• 

productAttributeMapping: {
                          'Name': 'test_name',               // product.Name → test_name
                          'Brand': 'test_brand',             // product.Brand → test_brand
                          'Price': 'test_price',             // product.Price → test_price
                          'category': 'test_category'        // product.Attributes.category → test_category
                 }

Testing Plan

• Was this tested locally? If not, explain why.
• {explain how this has been tested, and what, if any, additional testing should be done}

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

• Closes https://rokt.atlassian.net/browse/SDKE-482

[rmi22186]

Can you add tests?

[rmi22186]

It looks like this is prioritizing the value of the attribute at the Product level vs the Product.Attributes level. I don't think this matters because it is likely that if a customer puts a product.attribute that is the same as the Product level attribute, that the value would be the same.

Just to call out though - for the customer who requested this, the launchpad/chats say that they want to pass in the following:
product_type: product.custom_attributes.category

This is interesting, because category is actually one of our product level keys as well (see docs here). However, when you call mParticle.eCommerce.createProduct(), what is returned is a product with a Titlecase key, ie:

var product1 = mParticle.eCommerce.createProduct(
    'Double Room - Econ Rate',  // Name
    'econ-1',                   // SKU
    100.00,                     // Price
    4,                          // Quantity
    'variant',                  // Variant
    'room',                     // Category
    'lodge-o-rama',             // Brand
    'banner',                   // Position
    null,                       // Coupon code
    customProductAttributes     // The custom attributes defined in a separate variable above
);

makes:

So if the customer puts category, since it's lowercase it will overlook Product.Category and then look at product.Attributes.category.

But I wouldn't expect it to be a different value at the end of the day. This comment is more digging in deeper as an FYI

[jaissica12]

Thanks for the detailed explanation!
Our implementation prioritizes standard product fields over custom attributes in the mapping logic. The case-sensitive key matching naturally separates these two namespaces, allowing customers to map both without conflicts. I've added test coverage for both Product.Category and Product.Attributes.category to validate this behavior and ensure both mapping types work correctly.

// Check product field first
if (product.hasOwnProperty(sourceField)) {
    value = product[sourceField];
}
// Then check custom attributes
else if (product.Attributes && product.Attributes[sourceField]) {
    value = product.Attributes[sourceField];
}

[rmi22186]

Added all my comments. Please review and lmk if you have any questions

[rmi22186]

I would use a real copied and pasted setting, like from https://jssdk-origin-qa1.qa.corp.mparticle.com/js/v2/9e77ff19b9fa2b4fa33fa0ef322addf4/config

"productAttributeMapping": "[{"jsmap":"3373707","map":"Name","maptype":"ProductAttributeSelector.Name","value":"test_name"},{"jsmap":"93997959","map":"Brand","maptype":"ProductAttributeSelector.Name","value":"test_brand"},{"jsmap":"3322014","map":"list","maptype":"ProductAttributeSelector.Name","value":"test_list"}]"

[rmi22186]

You can change the map and value in there, but at least this way you have the structure of a rela string that is returned.

[jaissica12]

I agree, and this helped with debugging as well! Updated the tests to use real settings.

[rmi22186]

one minor comment

[rmi22186]

@jaissica12 - LGTM. Only thing is please change the title from feat: [SDKE-482] support custom product attributes to feat: SDKE-482 support custom product attributes to match how we do core SDK (although we've been inconsistent there)