npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

adb-ga-trace

v1.0.0

Published

Human readable output for Android Google Analytics debug log

Downloads

3

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

aeirolaaeirola

Keywords

Readme

adb-ga-trace

Build Status

Pretty print your Android Google Analytics debug logs.

Instead of looking at logs like this

07-14 18:23:39.468  6093  6121 D GAv4    : Hit delivery requested: ht=1500045819082, _s=7667, _v=ma8.4.87, a=756284080, adid=3018087d-3fcf-40a6-8d8c-3319f934b834, aid=com.google.android.dialer, aiid=com.android.vending, an=Phone, ate=1, av=9.0.155139499, cd=com.google.android.apps.dialer.extensions.GoogleDialtactsActivity.SpeedDialFragment, cid=c107f93a-9b02-4be3-b54a-3be9e46ed929, sr=1080x1794, t=screenview, tid=UA-53072813-1, ul=en-gb, v=1
07-14 18:23:40.186  6093  6121 D GAv4    : Hit sent to the device AnalyticsService for delivery

You could be looking at logs like this (+ colors!):

------- 2017-07-14T15:23:39.468Z -------
 Protocol Version: 1
 Tracking ID / Web Property ID: UA-53072813-1
 Client ID: c107f93a-9b02-4be3-b54a-3be9e46ed929
 Screen Resolution: 1080x1794
 User Language: en-gb
 Hit type: screenview
 Screen Name: com.google.android.apps.dialer.extensions.GoogleDialtactsActivity.SpeedDialFragment
 Application Name: Phone
 Application ID: com.google.android.dialer
 Application Version: 9.0.155139499
 Application Installer ID: com.android.vending
 Hit time: 1500045819082
 a: 756284080
 _s: 7667
 _v: ma8.4.87
 adid: 3018087d-3fcf-40a6-8d8c-3319f934b834
 ate: 1
----------------------------------------

Hit sent to the device AnalyticsService for delivery

Usage

Install with:

npm install -g adb-ga-trace

Connect your device, or fire up your simulator, and run with:

adb-ga-trace

You will need to have adb installed for the connection to work