we are using the Enhanced E-Commerce Extension of Google Analytics for tracking leads. So sending a form will trigger a purchase. The value of a lead is 0.00 € for us so we set the variable product_price to "0". The price is mapped over the E-Commerce Extension from Tealium.
For any reason Google Analytics will track it as "1.00" anyways. We already tried different types of data but none solved the problem. We also tried to map the price directly in the Google Analytics Tag.
Is there any way to fix this? Which data type do we have to choose to write the price into UDO?
Thanks in advance
Solved! Go to Solution.
08-04-2016 02:21 PM - edited 08-05-2016 10:31 AM
It is not clear if you wat to set the 'value' for the transaction or the 'price' for the item ?
For GUA, the 'value' for the transaction or 'Transaction Revenue' ( the 'tr' query parameter value ) is derived from "_ctotal".
If you have the ecommerce extension, look there to see that you have a sub_total variable mapped there. If you do then set '_ctotal' to '0.00' in an extension scoped to GUA with conditions set for this event. You then you will send a zero 'value' for the purchase. Alternately if you have a UDO total variable mapped to the GUA tag's 'Revenue ' then you wil set that to '0.00'instead.
To set just the 'price' to zero ( assuming that you only have the one item ) then the price or the 'pr1pr' query parameter is derived from '_cprice'. Setting that to zero is similar except product variables are expected as an array of strings. ["0.00"]
thanks for your answer.
Our intention was to set the price for one product (and with this the price for the whole order) to 0.00€.
We already set this value in the UDO which was fine in Web Companion, but Google Analytics received a price of 1.00€ instead.
I incidentially found out what was the issue. There is an "Auto Fill E-Commerce Option" in the GUA-Tag, which is populating price, quantity and name of a product, if there isn't a value set. Obviously this doesn't recognize "0.00" as a value and fills it as it is supposed to be with a standard value of "1.00".
Maybe this could be fixed in a new version of the tag?! I found it really helpful, that quantity was auto-populated with "1", because in our lead-based business every transaction is based on a quantity of "1". But in my opinion it isn't really reasonable to auto-fill price with "1.00", if there is a value of "0.00" set in UDO.
My Problem is solved for now, thanks and have a nice weekend.