Okay. So, I had to run a lot of experiments and try out different things to solve this issue.

After trying all the things that I have described in the question, I finally found a way to address this problem.

The main cause of this problem was that I was using a google analytics account set to track an App, to capture the data from an app that was built with meteor js (which basically utilizes cordova).

Using meteor means that my app's screens are actually web pages rendered as a mobile app. It seems like meteor uses URLs to navigate through these screens.

On the other hand, google analytics looks at (and captures) the screen name of an app's page, when an event is triggered from that page. In native apps this screen name will be something similar to "About us", "Contact Us", "Home", etc.

Now since a meteor app is not the same, the screen name returned by meteor is actually the URL of the page that has triggered the event.

This does not have anything to do with the http calls (Whether or not they are GET or POST), because it is the local URL used by meteor for navigating that is being passed down to google analytics and not any http calls.

Solutions

1.

If I had the google analytics account set as a web page tracker, I could have access to "Exclude URL Query Parameters" field and I could potentially exclude username and password as was suggested by @Mike and @PhilipPryde in the comments. However, I needed to use google analytics set as an app tracker. So, this did not work for me.

Failed

2.

I did put a filter on the whole view in the google analytics and searched for meteor.local/.* and replaced that with hiddenURL. The filters on

• Host Name
• Page Title
• Referral
• Request URI

did not work.

But when I put the same filter on

• Screen Label

field, it worked.

However, this only looked at the screen names returned by screen view hits and not the event. Thus, this did not actually solve my issue either.

Failed

Finally, I had to do this:

There is a method call on GA instance that lets you set different options up. I ended up using this:

ga('set', 'screenName', 'hiddenURL');

This changed the screen name to "hiddenURL". So, I used this before every event and it worked for me. My code for sending events to google analytics looked like this:

ga('set', 'screenName', 'hiddenURL');
ga('send', 'event', 'button', 'click', eventName);

PS:

This changes the screen name that was showing up in real-time reports of google analytics to "hiddenURL", whenever someone triggered an event. But, it changes back to a screen name as soon as they go to another page. So, it would not also mess with any of your screen view data either, since it is not being captured as a screen view.

Of course that is because, I pass the screen name to my GA instance every time I send a screen view. So it looks like this:

sendScreenViewToGA = function (screenName) {
    ga('send', 'screenview', {
        'appName': 'Something',
        'screenName': screenName,
        'appVersion': x.x
    });
}

If I had used the screen name, that is being set on the environment tight now, I would have ended up with all my screen names in analytics set to "hiddenURL".

I really hope this post will help others with same issues and save them some time.

Google analytics auth tokens do not last forever. The have to be renewed. If what you have there is a refresh token, they don't expire unless the user that granted permission revokes access.

The best way to go is with a service account as @Petr is suggested.

There are a few more steps to creating the service account and generating the .p12 file you will need. You can follow the directions for setting up a service account here: Connecting to Google Analytics API in a Rails app

Google's code examples seem to be lacking in the c# arena but I did find this post: How do I use a Service Account to Access the Google Analytics API V3 with .NET C#?