Overview
We've heard from many developers and clients that app measurement QA can be painful, so we built Bloodhound to aide in your mobile analytics and mobile optimization initiatives. This tool is free to any team using the SDK if it helps your QA processes and is supported on a best effort basis. For specific questions or support, please post your question in the Forum link in the top right of Developer Connections.
The Bloodhound app measurement QA tool displays and parses real-time hit data on app measurement implementations, ensuring proper implementation for app developers and marketing team. The hit details, hit counter, and evar/prop output features streamline the app tracking QA process. The tool can be used for apps in the development cycle or to validate live apps in the app store.
The tool focuses on mobile app measurement for iOS, Android, and Windows 8, Windows Phone 8, and OS X SDK's, but has use-cases for other platforms and even desktop or mobile web.
You can find the Bloodhound documentation here.
Please reply to this thread to let me know any questions/feedback you have about Bloodhound and check back for future updates.
Note: This is not The QA Tool does not support https:// (SSL) tracking. You must disable SSL in the AppMeasurement library when testing using the QA Tool.
To learn more about how Adobe mobile analytics and optimization solutions provide comprehensive measurement of your mobile channel, deep analysis of mobile content across mobile devices, and powerful optimization tools to deliver targeted content to your mobile audience, click here.
#mobilemadesimple
Last update on November 23, 2013 (current Mac version = 2.1.0 and current Win version = 2.1.0)
The long awaited Mac version 2.0 is now available with the following updates. The Windows version with the new capability will be coming soon.
Version 2.0:
* Updated UI and added dark and light theme
* Added ability to save hits for testing
* Added test hits against saved tests
* Added the ability to view code that would generate the hit being viewed
* Added the ability to test variables based on NSRegularExpressions
* Fixed bugs in table rendering
* Fixed potential crash in context data if key started with c
Enjoy!!
It is good that Adobe created this application but it still falls short.
Many devices we are deploying Omniture onto - don't support a proxy - Samsung and LG CE TV's come to mind.
The application needs a mode to be able to listen for conversations originating from an IP address like Wireshark or similar tool but without the complication.
Secondly, the off-the shelf Adobe variables don't provide much.
For IP based emerging platforms many of the details we need simply are not offered by Adobe - and shouldn't be....however better support for context(custom) eVar's and events needs to be considered.
My recommendation is the support for custom eVar templates. Where a tester can create a MASK or set of acceptable MASKS for each context eVar. Whilst the actual value still needs to be checked for correctness checking evars and events seens against a template allows formatting and correct evars per event type issues to be idenitifed quickly and would remove the majority of leg work we find ourselves in at the moment.
We have currently deployed Omniture to the following
iPod Touch
iPhone
IPad
Andriod Phone
Andriod Tablet
Samsung CETV
LG CETV
XBOX
Playstation 4
PC Application - Not Browser
Mac Application - Not Browser
and presently are deploying others.
This is a very important tool for us ....we are very interested to see if this will allow our company to avoid having to write our own bespoke tools...time will see.
Matthew,
Thanks for the great feedback on Bloodhound. Testing templates based off of a certain key/value pair is a great idea and certainly something we will look into in future versions. Our goal is definitely for you to not have to create your own custom tool for testing, so any and all feedback you can give to enhance Bloodhound is great to have.
In reference to the comment "For IP based emerging platforms many of the details we need simply are not offered by Adobe - and shouldn't be....however better support for context(custom) eVar's and events needs to be considered.", could you elaborate a bit? Is this specifically referring to testing, or are there other areas we could provide better support?
Thank you,
Hunter (Adobe Mobile Engineer)
Hi Steve,
Thank you very much for your response. I think, I found the root cause for the issue that I am facing. My Device Carrier is AT&T. It seems Windows version of BloodHound tool is not showing the hits if "&" is part of carrier name where as MAC version is working fine.
If I attach the file with sample url to this comment, its not showing up, hence posting without the attachment.
Can you please let me know if I am missing anything here. FYI, I am using v3.0.1 Omniture SDK.
Regards,
Dhana Prakash M
dhanaprakashm - posted the 2.1 versions that have the fix for this issue.
Also, I recommend you updating to the latest 3.x version of the SDK, even if you can't upgrade to the 4.x right now, because we fixed a lot of reported issues since 3.0.1 came out over a year ago.
Roger
Posted version 2.1 with the following updates to both OS X and Windows versions:
Enjoy!
Thank you very much Roger. Now I am able to see the hits from AT&T Device at Windows Version of BloodHound tool as well.
Appreciate the very quick turn around on this.
Hello,
I need to use bloodhound to check omniture calls on Android phone & tablets, wondering how it should be configured? I tried this on iOS device it worked perfect but no idea how to use it on Android phone and Tablet.
Majidm,
On most Android devices you should be able to proxy your device to Bloodhound just as you did with iOS. Navigation to the proxy settings is different per device but it should be in the wifi configuration within network settings. Typically hidden behind an "Advanced Options" flag.
Thanks for your response. I did the Modify Network | advanced options | Manual then had my mac machine proxy hostname(IP) then proxy port but had no luck. Most android phones don't support auto proxy so I could not track any user action.
Thanks, Majid