Tracking ID container cross talk leakage
A client is receiving random transactions in their Conversions/ecommerce/tranactions area from hostnames that they are not filtering on.
Their tag is set up for transactions - History Change - trigger on hostname contains. They have 14 different hostnames (triggers) to match on their one tag. The data they receive seems to be over a week old, sometimes, as well.
We have triple checked to ensure their 'hostname contain' strings are all unique to their account.
We are puzzled how Tracking IDs could have cross talk leakage.
Has anyone had similar behavior before? or does anyone have any insight into what could be going on?