This is fixed in v1.6.1, available now in the Chrome store

This is fixed in v1.6.1, available now in the Chrome store

This should be fixed now in v1.6.1. If the extension doesn't update automatically, go to Manage Extension and click the Update button.  

@akwankl , in the future you may want to look into the new Identity Linking Rules feature which just went into beta. One of the use cases it was designed for is "erroneous or bad identity values". It won't help with historical data, but could help you out in future use cases. You can read up on it h...

 I have validated and reported this issue, but I don't have any ETA. If you have the ability to open a customer care ticket, that's always a good idea.

Hi Tom,If this was implemented in June 2023, this would have been before our "guided events" approach to two call implementations come out. Can you adjust your top-of-page and bottom-of-page calls to use it? The first call needs to use the "Request personalization" option and the second call needs t...

Hi @tarun_jamana8469 ,Good question. Be sure to check the migration checkbox for Target too, so that the mbox cookie details will transition. I haven't heard of any specific issues with migrating activities with A4T. Are you going to use a two call or single call implementation of Web SDK? The A4T m...

Hi Tom,How are you implemented? Do you have a single call per page load that is used for both Target and Analytics? Or do you have two calls per page load, with one at the top used for personalization and one at the bottom for analytics?

Hi @PeggyWaiteBradley ,Hope you are well. So, you have two sendEvents on every page load? The first with "use guided events" and "request personalization" and the second with "use guided events" and "collect analytics"? With this setup the Target data needed for A4T is returned from the first call's...

Hi, I monitor it. Will try to check in more often!