Sign in

Welcome to our Support Center

Get help with integration and live campaigns

Welcome to our Support Center. Get help with integration and live campaigns

Warning - Hardcoded Price

Overview

This warning message appears when you are not implementing the Criteo OneTag Price parameter dynamically. The value of the price could be hard coded on the Criteo OneTag exactly as it appears in the Integrate Platform.

Remember – the price passed on the Criteo OneTag must be unit price of the product on your site. 

The price parameter is required for the viewBasket and trackTransaction events. Find more info on events here.

 

Example

{ event: "viewBasket", item:    [{id: "A123", price: price_1, quantity: "quantity_1" }]}

Solution

Check the price dynamically implemented on the Criteo OneTag  for basket and confirmation pages and make sure the price is the unit price of the product on your site.

This is correct:
If a user is on a basket page and the price for the product displayed on that particular page is 29.95, the viewBasket event in the Criteo OneTag should look like this:

{ event: "viewBasket", item:

    [{id: "A123", price: 29.95, quantity: 1 }]

}

However, if the user selects a different product with a different price, for example, product is B456 with unit price 45.99, the viewBasket event in the Criteo OneTag should look like this:

{ event: "viewBasket", item:

    [{id: "B456", price: 45.99, quantity: 1 }]

}

 

If you implement the Criteo OneTag via Google Tag Manager, please make sure your variables are correctly defined and the Google Tag Manager dataLayer contains the information used in those variables.

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk