However, I was puzzled this week when I was testing new default code for Adobe Analytics (by using Charles Proxy Tool) and nothing was sent on one of the pages. I thought the new s_code was broken or something, but luckily I got help from my boss and we noticed that the hit is actually sent but for some reason Omnibug isn’t showing it. I used Google and I found the answer from here https://github.com/simpsora/omnibug/issues/18. So the reason is that on certain pages the analytics hit/url is so long that Adobe will send the hit using http post and not get method. Let’s wait if Omnibug makes the update to include post request, but the initial comment was that it is going be difficult, but we’ll see…
Adobe did make announcment about this, but who remembers this kind of technical stuff? 😉 And here is the official comment from Adobe:
I also found nice blog post about this “issue” and how you can make a detour for this new setting: (But I would recommend to use the trick just for testing/debugging purposes)
http://www.searchdiscovery.com/blog/validating-adobe-analytics-http-posted-tags-pain-relief-formula/ I ain’t Justin, but I clap for you too Stewart, fantastic blog post about this issue!
So the result is, you can use packet analyzers to get also post request, HTTPFox and Charles Proxy Tool are my favorites. However, I’m going to continue to use Omnibug and for special cases I can use packet analyzer.
Adobe Analytics Debugger Chrome extension shows POST and GET requests!
Thanks for the tip Tomas!