Hi team,
We have implemented custom tracking for the www.netapp.com top navigation. When we click on the top navigation the custom call is being aborted. Can you please let me know the reason?
1, Go to http://www.netapp.com/us
2. click on netapp.com/support/community links on the top
3. you can see the custom tracking is aborted
4. I can see this only when i test the tracking in firebug
5.It shows fine in Omnibug.
Can you please let me know what is the issue?
Regards,
Vidya
Solved! Go to Solution.
Views
Replies
Total Likes
Hi Vidya,
Occasionally, a packet monitor will report the call aborted, but the s.tl call actually went through very quickly. So quickly, the monitor reported it as aborted. There is more information here: https://marketing.adobe.com/resources/help/en_US/sc/implement/debugger_ns_binding.html You can test this with a standalone such as Charles Proxy. A list of packet analyzers is available here: https://marketing.adobe.com/resources/help/en_US/sc/implement/packet_monitor.html.
Best,
Tacia
Views
Replies
Total Likes
HI Vidya,
We tested it from our end and the custom tracking is working fine in both Adobe Debugger and Omnibug . Please refer the snapshot for more details. However when we checked in HTTP FOX debugger the request was aborted. We foresee it only as a debugger issue. Can you please confirm whether the data is being captured in Report suite or not.
Thanks & Regards
Parit Mittal
Views
Replies
Total Likes
Hi Vidya,
Occasionally, a packet monitor will report the call aborted, but the s.tl call actually went through very quickly. So quickly, the monitor reported it as aborted. There is more information here: https://marketing.adobe.com/resources/help/en_US/sc/implement/debugger_ns_binding.html You can test this with a standalone such as Charles Proxy. A list of packet analyzers is available here: https://marketing.adobe.com/resources/help/en_US/sc/implement/packet_monitor.html.
Best,
Tacia
Views
Replies
Total Likes
Views
Likes
Replies