Tracking Visits from users who clicked on email links

[SeánKe]

Hi there, 

We have a scenario where our email system and our AA instance are wildly off. I know comparing between two platforms always leads to issues however there is no trend whatsoever between the two systems. 

We decided to run a test, an email campaign that would only be sent to select internal users, and test on a multitude of devices, browsers etc. The email would contain a number of links to products and has unique campaign info that we can use to know that it is only our data. We found that all users using desktop were tracked as expected, so no issues there. However on mobile, only 3 of the 8 tests we did reached AA. In instances where we clicked on the email link from a mobile browser, seemed to reach AA ok. However, if we clicked on the links from outlook or gmail apps, there were more issues with receiving the data in AA. 

My question is - does anyone know of any issues surrounding email app clicks and how that works with AA tracking? The link clicks have opened both in chrome and safari. This is NOT a cookie consent issue, we are always accepting cookies during our tests and we are sure of this. 

Any insight would be a massive help. 

Thanks

[bjoern__koth]

Hi @SeánKe 

Can you confirm that there are no redirects in place that could potentially cut off request params? Just a wild guess.

Outlook does such things, but then I would expect that behavior to work the same way on web and mobile.

Which params do you use?

[SeánKe]

No redirects that I can notice. The relevant query param is in the url on my phone when the page is loaded

[bjoern__koth]

Worthwhile checking your network traffic through a proxy like Charles Proxy (https://apps.apple.com/ch/app/charles-proxy/id1134218562)

Maybe this gives you an idea of aborted tracking requests that could explain what's happening.

The general mobile traffic is captured as expected?

[Jennifer_Dungan]

Hmm that is interesting... what type of device (iPhone or Android)? The WebView shouldn't have issues inherently... but maybe there is something in the way your site is rendering?

I haven't noticed this myself, but I will try to do some testing and see if I can replicate on my own site...