Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Custom Call is being aborted in Firefox and cancelled in Chrome

vidyar30267388
Level 3
Level 3

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

1 Accepted Solution
taciac
Correct answer by
Level 9
Level 9

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

View solution in original post

2 Replies
ParitMittal
Level 10
Level 10

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

taciac
Correct answer by
Level 9
Level 9

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

View solution in original post