Hi @Jacob-DDdev, FYI: I just received confirmation that the Adobe engineering team has identified this as a bug and will create a fix in a future release. I don't have any information on when we can expect this to be fixed.

Recreated another issue with Customer Care: #200930-000158

Hi @Jacob-DDdev, for what's worth: the work-around I use is based on the asumption it being highly unlikely that two succeeding pixels are alike. Therefore in my callback function I keep track of the last payload (from the parameter) and compare that to the last received. If they are equal, the call...

Hi @Jacob-DDdev,for what's worth: the work-around I use is based on the asumption it being highly unlikely that two succeeding pixels are alike.Therefore in my callback function I keep track of the last payload (from the parameter) and compare that to the last received. If they are equal, the call i...

Hi @Jacob-DDdev,

Hi jkm-disco, I've seen this before too, and I came to the conclusion this occurs as soon as the data is being sent in a POST request instead of a GET request. At that point, the XHR is triggering the request for a second time.I've reported this about a year ago at Adobe (via customer care), but aft...