My App is not showing up when I access the FB insights page (at: https://www.facebook.com/insights/)
However, if I click the create app link on the left it will show up.
Additionally - it shows no insights & tells me that I need to publish an action at least one to submit the Open Graph code - which has been done numerous times already.
my app id is: 199931010133472
Related
I've created a custom speech model and deployed it. When I select the endpoint I can export the logs at the bottom of the page. Logging is enabled for this endpoint and it worked until 2 weeks ago. Now, when i click the "Export log" button, the spinner appears for a second or two but it does not show the list of logs. I took a look on the HTTP answer, which contained json data, telling me that there should be a lot of logs ready for download.
So my assumption is that this might be an error of the page? I've tried it using latest Firefox and Chrome browser. Edge does not work either. Deleting cookies and cache data does not work either.
There is a bug in the current UI of Speech Studio Portal, and thanks for reporting this, we will fix in our next release, which will come in this week.
There are 2 cases in Playstore App
Normal Installation (Playstore shows OPEN Button)
Installation from Dynamic Link (Playstore shows CONTINUE Button)
Test Case:
Download app from Firebase dynamic link, After installation Playstore will show CONTINUE button:
There are 2 options from where user can open app after successful installation .
Open app by clicking on CONTINUE Button -> App will get the link, everything works as expected
Open app from LAUNCHER ICON, and not from playstore -> App will not get the dynamic link
Most of the users are not clicking the CONTINUE button as it is normal human behavior, therefore I am losing the Referrer link.
Is this the intended behavior of Firebase? How can I avoid this problem?
Related Post here
There are 5 events for Dynamic Links Analytics:
1. Click
2. Redirect
3. App Install
4. App First Open
5. App Re-Open
From the image above, you can see that the request is pass to Play Store and then it is ended over there.
Therefore, possible situations are:
Your previous app/website has done its job routing the dynamic link to the intended app or Play Store.
At this point, you can track the Clicks and Redirects.
Now, at Play Store, continuing the dynamic link flow, User install the app, You can track number of app installs. Or, user did not install the app, so it did not update the number of app installs.
After installation, if the user opens your app through the CONTINUE button, your app will received the data passed in from the Google Play Fragment (Like what you have done here via the Receive Setup). At this point, it will generate the meta data of 'App First Open'. But, if you press the home button, and open the app through your home page/shortcut/app tray, etc. , you will not get an update on it.
This is because no dynamic link meta data is pass when your user open the app other than the CONTINUE. The flow is broken, unless, the user go back to step 1 again to redirect to the app, now the app will track the data of app first open (the app is not open before) or app re-open if the user open the app before.
SUMMARY and CONCLUSION:
Why does the button is showing CONTINUE instead of OPEN is because the Google Play (Fragment) detected the user is directed from the dynamic link (some meta-data (your dynamic link details/info) is passed from the previous app/website).
The meaning of CONTINUE here is actually prompt the user whether they want to proceed to the newly installed app. If yes, Google Play will pass the meta data to your app, and you get the tracking data on App first open. Else, no analytic data will be produce other than click, redirect and app install.
Answering your question, you can only hope the user press on the CONTINUE! It is unavoidable because those app/sites are not in the same context (previous site vs Play Store vs Your App).
Definitions: (from documentation)
dynamic_link_first_open
Logged when a user opens the app for the first time via a Dynamic Link.
dynamic_link_app_open
Logged when a user re-opens the app via a Dynamic Link.
In my Azure Application Insights, I'm attempting to save a chart to the AI dashboard. When I attempt to do so, I'm getting a strange error which can be seen below:
I certainly have a dashboard but not sure if it's "writable shared"?
Unless you publish the dashboard it is private to you and hence the message. You should click on share -> publish which produces a shareable dashboard. Once this is ready, pin to dashboard icon shows list of published dashboard which we can select to pin the result
Just started using App Maker and I'm still getting the console displayed at the bottom of the window when I publish an app. How do I hide this please?
Do not mess Preview and Publish. By default your Preview Deployment always shows AM console(you always see Preview Deployment when you click Preview button). To open one of your published deployments you need to navigate to Settings -> Deployment and click correspondent deployemnt link. You can find some pics in this answer:
After publishing an app, how do you find the public URL to give to your end users?
Note: you can always show/hide console by toggling this URL parameter(in browser address bar):
?console=1
I am trying to create a Wordpress app using the official WordPress resource from the market place.
I fill out all of my settings as usual, like the website name, resource group and also, the ClearDB database I made.
Everything shows up correctly. My website name is valid, the resource group is correct etc.
But when I hit create, My app name is labelled as "not available" for about 1 second. This then goes away and the "create" button greys out, and now says validating. When this is done, I am taken to a page with an icon of a cloud with a drop of rain. Chrome then prompts me that my unsaved changes will be discarded. I click cancel and it appears again in an instant. If I click 'okay', then everything is cleared, and I ha ve to enter it all over again, only for the whole problem to occur once again.
Please Help!!!!
Thanks, Sean.