Error Ignoring multiple install campaigns using GoogleAnalytics - android

I was testing Google Play campaign attribution for my app when I saw the following error log :
06-19 14:17:55.416 14424-14466/com.myapp.android E/GAv4﹕ Ignoring multiple install campaigns. original, new: utm_source=testSource, utm_source=testSource2
testSource and testSource2 are utm_source's I generate using the following test broadcasting method :
adb shell am broadcast -a com.android.vending.INSTALL_REFERRER -n com.myapp.android/com.google.android.gms.analytics.CampaignTrackingReceiver --es "referrer" "utm_source=testSource&utm_medium=testMedium&utm_term=testTerm&utm_content=testContent&utm_campaign=testCampaign"
I see hits for only testSource on the GoogleAnalytics website.
Can anyone explain what does the error mean ?
Why does testSource2 does not show on the GoogleAnalytics website having come from a different source ?

The error occurs since Google Play Services broadcast it for only once when the app is downloaded.
The docs say:
When your app is downloaded from Google Play Store, the Play Store app broadcasts an INTENT_REFERRER to your app during installation. This intent contains the value of the referrer parameter of the link used to reach your app's Google Play Store page, if one was present.
I was testing it for another source on the same installed apk.
To test for a new source:
1) Uninstall the apk
2) Broadcast again.
You'll definitely see the hits for your new source on Google Analytics website after some time.

Related

App Action Works on App Actions Test Tool But not On Google Assistant

I have cloned the project from https://github.com/actions-on-google/appactions-common-biis-kotlin. I made the package name of this project the same as my draft project in Play Console which has a temporary app name 'com.acesoft.actions (unreviewed)'. I can trigger the app actions with App Action Test Tool (AATT). If I set the Invocation Name to "test app" with AATT, it would work on my physical test device if I say "Open active tasks in test app". However, Google Assistant would not open the app when I say "Open active tasks in todo". Todo is the display name for the app. According to the documentation, the default invocation name is the display name of the app. The command "Open active tasks in todo" would result in a search in the web. What did I do wrong? How do I invoke the app actions without AATT?
I have also tried typing the following in Google Assistant:
"open active tasks in todo"
"open active tasks in actions" ("actions" is the last part of the temporary name)
All these commands would result in web searches instead of opening the app!
Can anyone help?
If your app is not published on the Play store, it definitely will not work. Google Assistant only formally recognizes apps that have been uploaded and have passed review. It works in the test tool because that tool establishes a temporary "preview" of how things will work if it were fully published.
Still, in some cases, Google Assistant is unable to match the name of the app as spoken to the name of the app as installed on the device. This situation is not possible to resolve on your own. What you will need to do is contact Google Assistant support and explain what you are trying to do. They might be able to make a change manually to the backend to enable this.
You can see someone else having a similar problem in this public bug. However, please do not file a new bug, and do not fill out the form unless your app is uploaded to Play. If your app is uploaded to Play, follow the instructions given in the last comment on that issue:
If your app is shipping on the Play store, then you can get support for this using this support form - you should choose "App Actions review" for now, and point out that you would like a manual mapping for your app. Don't worry about the actions console project ID - that is for another project.
For me it was enough to put my app into "internal testing" in the Play Console and then install the app on device through the test link that is provided by the Play Console. I could use Google Assistant and use the app name for invocation.

How to test if the google search app indexing is working or not?

I have verified the domain name on search console and I have added intent filters in my app. I can open the app using the adb command
adb shell am start -a android.intent.action.VIEW -d "http://www.mywebsite.com/path" com.my.package.debug
and it is opening the proper screen. My doubt is that how does google search will map the URLs? Also, as of now, I can't see the links being redirected to my app on Google search. Is it because the app is not updated on the play store?

Get referrer details after installing app from Play store

I am using Branch for deferred deep linking and I am trying to find all referral data after installing app from play store. I have added Google Analytics Campaign Parameters to Google Play URL as recommended. like.
https://play.google.com/store/apps/details?id=&referrer=utm_source%3Dgoogle%26utm_medium%3Demail%26utm_term%3D3208%26utm_content%3D47321%26utm_campaign%3D64856
but I am getting referral details for "utm_source : google-play" and for "utm_medium : organic" which is not correct.
I have also try to get referral data by broadcasting referral details from android studio's terminal like.
adb shell
am broadcast -a com.android.vending.INSTALL_REFERRER -n / --es "referrer" "utm_source=google&utm_medium=linkedin&utm_term=3208&utm_content=37413&utm_campaign=invite"
and it works well.
So plz help me out.
Alex from Branch.io here:
Branch doesn't overwrite the INSTALL_REFERRER, so these incorrect utm_source and utm_medium values are not coming from our system. Sometimes the INSTALL_REFERRER is delayed — is it possible you might have been testing multiple links with different values set in rapid succession?
Side note: Branch does also use the INSTALL_REFERRER for other purposes, so you may want to review our docs on how to use it for both Branch and your own needs.
More generally though, Branch makes the INSTALL_REFERRER obsolete. The point of the INSTALL_REFERRER was to allow you to pass values through the install process, and storing UTM parameters there is a hack to give you some basic visibility into your acquisition channels. Branch allows you to do both of these things with far more power and precision, so you really shouldn't need to be using the INSTALL_REFERRER for this at all. Check out the Branch docs pages for storing link data and setting up the Google Analytics integration for more details.

Android - How do I get referrer information on app reopen?

I have ads for my application but some users who click the ads already have my app installed.
If I visit the store after my app is already installed and click "open", the app's code is unable to read the referrer information and instead I see this message in the logcat:
12-15 18:27:27.334 32092-32092/? D/Finsky﹕ [1] 1.run: Dropped referrer for com.xxx.test because already-installed
Is there any way to read the referrer information when the app is re-openend from the store and not on first run?
The way to get referrer information for ads that link to your app if it's already installed is to use deep universal links instead. Such links do not directly go to Play Store, but rather point to your server (e.g. https://www.nimo.com) which can redirect to Play Store. The trick is that your app will declare a handler for https://www.nimo.com and treat such links (with referral) locally.
A related question has been answered here.
Some commercial solutions provide this redirection service to you, e.g. Adjust.

apk installed via adb is not visible in "my apps" section of google play store

I've a similar problem than this one (though this is not a duplicate as my question is a bit different) :
Is it possible to install an application via adb but still get Google Market updates?
Here is a list of steps that led to my problem :
I've pulled an apk (previously installed through google play store) from my phone with adb pull for backup purpose.
I uninstalled it.
A new version of this app appears on the market.
I then choose to re-install my apk that I've previously saved (at step 1) through adb
The problem is the following : it is not visible in the "my apps" section of the play store. Why ?
I've already checked, the package names are the same.
If I choose to search for this app on the google play store, it shows that it is already installed and that I can update (I indeed, can update and everything goes fine).
I've tried with different apps, they ALL have the same behaviour.
I've tried different method of installation (adb install -r, adb shell pm install [which is, among other things, basically what adb install does])
I've already tried to clear data / stop the play store app
I've already tried to restart my phone
My question is simple : why this is happening ?
I do not think this is poosible in any way, because in "my apps" do only appera apps you have downloaded from gplay. So in their database you have downloaded the app, if you called "Download" via the app or the Webpage of GPlay. If you open the GPlay app and search for the "installed" app it can be started, because the GPlay app checks internaly weather the app is reachable via the intent (e.g. Intent("com.rivio.angrybirdpro"). So you can open it directly but it is not listed in "my apps"
If you install apps from the amazon market they do not appear in gplay's "my apps" either.
Hope this is what you were asking for.

Categories

Resources