Skip to main content
Solved

Bug with displaying of deprecated parameters (?)

  • April 3, 2023
  • 1 reply
  • 273 views

Hello, everybody!

I ran into a problem. Earlier I created the "Payment" event with properties "is_discount", "price", "quantity". Mobile apps started sending this event.

After a while, I asked my developers not to send the "quantity" property anymore, since it was no longer necessary. But now this property is always displayed in the received event with a value of 1, although mobile applications do not send it (we checked the traffic).

Tell me, please, what could be the reason for this behavior?

Best answer by Saish Redkar

Hi @e.gerasimov 

In Amplitude, event data once ingested is immutable. So you will always see the quantity property and value on all your Payment events which were ingested before you made the change.

To confirm that you are no longer getting this property, you can create an event seg chart on Payment event grouped by quantity and you should see none values for this from the date you made the change.

You can further hide the quantity property from the charts using Data interface so that it no longer appears in your chart dropdowns.

Let me know if I have interpreted your use case correctly. Hope this helps.

View original
Did this topic help you find an answer to your question?

1 reply

Saish Redkar
Expert
Forum|alt.badge.img+10
  • Expert
  • 1377 replies
  • Answer
  • April 3, 2023

Hi @e.gerasimov 

In Amplitude, event data once ingested is immutable. So you will always see the quantity property and value on all your Payment events which were ingested before you made the change.

To confirm that you are no longer getting this property, you can create an event seg chart on Payment event grouped by quantity and you should see none values for this from the date you made the change.

You can further hide the quantity property from the charts using Data interface so that it no longer appears in your chart dropdowns.

Let me know if I have interpreted your use case correctly. Hope this helps.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings