duplicate track request for the same product by the same user

[muly]

scenario:

1. user searches for google pixel and select the google pixel 7a 5g and request the track request. 2, and later same user searches for google pixel 7a 5g and select the google pixel 7a 5g and request the track request.

the url for these two instances will be different even though the product is same.

for example: https://www.amazon.in/Pixel-Sea-8GB-128GB-Storage/dp/B0CMHLNVGS/ref=sr_1_4?crid=29M7LBVDXVQCP&keywords=google+pixel+7a+5g&qid=1700846878&sprefix=google+pixel+7a+5g%2Caps%2C159&sr=8-4 https://www.amazon.in/Pixel-Sea-8GB-128GB-Storage/dp/B0CMHLNVGS/ref=sr_1_3?crid=15JYE7A72BD2R&keywords=google+pixel&qid=1700846833&sprefix=google+pixel%2Caps%2C187&sr=8-3

above two url are for the same product, but because user visited this page using different search keywords, the url formed is slightly different. because of this, when user tracks again, a different track request is created, which it should not.

one solution: strip the use to remove the extra information before storing in our database. for example only store the below as url. https://www.amazon.in/Pixel-Sea-8GB-128GB-Storage/dp/B0CMHLNVGS/

[muly]

do we still have this error? can you please test and close this defect, with notes, if the error is no longer there.