Total basket price inconsistent with basket_value parameters

Problem and Background

In a conversion pixel, the basket field contains detailed conversion parameters for each product that is purchased. It has a “basket_value” field which contains the total price of the checkout basket. Conversion Basket Page View pixel requires each item in the “basket” parameter to be listed with its price and quantity. The price should be the price of a single unit, but in some instances, it is inserted as price*quantity into the price field instead, which is incorrect. This check tries to catch that case.
For example, if a shopper buys 2 of an item that is priced at $10 each:
Correct:
Price: $10
Quantity: 2
Incorrect:
Price: $20
Quantity: 2

📘

Note

There is a separate parameter for the Conversion Basket Page View pixel called “basket_value”. This is the total price of the checkout basket, that is, the sum of all price*quantity for each item after any tax, shipping, discounts, etc.

This check works as follows:

1. For a given day, it looks for PIDs that have had purchases of quantity=1 and also of quantity>1.
2. Then it takes the [price / quantity] for quantity = 1, 2, … whatever quantity values are present.
3. If the price value is correct, the [price / quantity] is expected to change at different quantities.
4. If the [price / quantity] value is the same for different quantities, it is flagged as an error.
5. The final percentage reported in the metric is
   {# of cases where for a given PID [price/quantity] is the same for different quantities} / {# of cases where a PID is purchased at different quantities}

Debugging Steps

Request Bloomreach Support to provide the list of conversions where the [price / quantity] value is the same for different quantities.

Common Causes

This issue usually occurs when the Price field is set as Price*Quantity instead of just Price on your end.

Solution

Check the issue using the debugging steps and fix the pixel implementation.

👍

Did this article help you?

Please provide your feedback. We would like to know if our help center is effective in solving your queries. You can also leave comments and suggestions on how we can make our help articles better. You can also suggest topics you’d like us to cover.