fix(ms-bing-capi): item price should be number not integer

[scottlepich-lz]

Summary

The Microsoft Bing CAPI destination's items InputField defines the per-item price property with type: 'integer'. This is too strict: Microsoft's own UET Conversions API accepts decimal item prices in whole currency units.

Because of this, Segment's mapping-kit rejects perfectly valid decimal prices (e.g. 9.99) with:

400: Item Price must be an integer but it was a number

Since mapping validation fails, the entire event is dropped — not just the price field. Any storefront selling at non-round prices (which is essentially all of them) silently loses conversion events.

Evidence (Microsoft docs)

Microsoft's official UET Conversions API integration guide documents price as a decimal:

• Docs: https://learn.microsoft.com/en-us/advertising/guides/uet-conversion-api-integration
• The parameter table gives the price example value as 25.1 (a decimal).
• Every JSON sample in that guide uses decimal prices, e.g. "price": 25.1 and "price": 27.3.
• The related top-level ecommTotalValue is typed number($double).

So integer is incorrect; the correct type is number.

Fix

Change the items[].price field from type: 'integer' to type: 'number'. quantity is left as integer (correct for quantity). Nothing else is changed.

generated-types.ts is unchanged, because both integer and number map to the TypeScript type number. Codegen (generate:types) was run for the destination and produced no diff.

Testing

• Added a unit test in sendEvent/__tests__/sendEvent.test.ts proving a decimal item price (9.99) is now accepted and forwarded to the request payload without a validation error.
• Verified the new test fails against the old type: 'integer' with the exact error Item Price must be an integer but it was a number, and passes with type: 'number'.
• Ran the scoped test suite: 16 passed, 16 total (jest src/destinations/ms-bing-capi).
• Ran typecheck and eslint for the touched destination — clean.

Follow-up observation (out of scope, not changed here)

While in this file I noticed a separate latent bug: the items field's default mapping writes to key item_price, but the defined property is price. Since the field is additionalProperties: false, item_price is silently dropped, so the default mapping never sends a price at all. I've deliberately left this out of this PR to keep it focused on the type fix; flagging it as a follow-up.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Note

Copilot couldn't run its full agentic review because no GitHub Actions runner was available. Make sure your repository has a runner available to run Copilot's review, or add a copilot-setup-steps.yml file specifying one with the runs-on attribute. See the docs for more details.

Updates the Microsoft Bing CAPI destination schema to allow decimal item prices and adds a regression test to ensure decimal prices pass mapping validation and are forwarded to Bing.

Changes:

• Relaxed items[].price validation from integer to number in the action field schema.
• Added a unit test confirming a decimal item price (9.99) is accepted and appears in the outgoing request payload.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
packages/destination-actions/src/destinations/ms-bing-capi/sendEvent/fields.ts	Loosens schema validation for item price to accept decimals.
packages/destination-actions/src/destinations/ms-bing-capi/sendEvent/tests/sendEvent.test.ts	Adds regression coverage for decimal item prices being forwarded successfully.