TLDR;
If you have release a service with last week release branch there is a chance that you will need to hotfix it by cherrypicking commit b0b8a4e31ca68161432fdd65ed0109eb556527fdThis commit fix missing tracking data that caused by wrong config. As long as it's not hotfixed some tracking parameter will lost.
Summary
We are losing tracking data from old tracking that still based on json, this issue only impacted for services that released by last week release branch (release/2018-10-09). The event that impacted are:
booking.insurance.failed
booking.price.down
booking.price.up
booking.transfer.failed
booking.va.agree
booking.virtualaccount.failed
dateflow
flight.homepage.button
flight.reschedule.button
reschedule.button
search
sort
survey.closed
survey.displayed
survey.link.dismissed
survey.opened
survey.submitted
swipe
trip.select
visit
visit.flight
visit.hotel
We do apologise for this inconvenience. The commit b0b8a4e31ca68161432fdd65ed0109eb556527fd also happen to become this week release branch to ensure this issue won't impact this week release.
Postmortem : 2018-10-15 Wrong trackingdata format on several topic
#20181015-track-config