I have a requirement whereby a store owner may receive an email offer for every store they own, even though they have just one email address. To get around the duplication issue we marked both the Email Address and the StoreID as Primary Keys and the emails deploy separately and are tracked as such through the Journey.
When we query the _Click data view to pull records that clicked in the email, if a store owner who shares their email address across locations clicks for only one store, all records appear in the results.
We tried adding a dynamic Alias (the Store ID), but we are not seeing any results in the data extension.
Did some digging here, and found this: [Querying _Click data for link aliases] Querying _Click data for link aliases but no luck.