playMaker

Author Topic: Unity Analytics: some official pack or else?  (Read 408 times)

Broken Stylus

  • Beta Group
  • Hero Member
  • *
  • Posts: 648
    • View Profile
Unity Analytics: some official pack or else?
« on: November 04, 2020, 12:28:47 PM »
I see six actions on the ecosystem (listed under Unity 5) that have been written at least three years ago, or four; and a package called Play Maker Analytics Remote Settings (Unity 2017).
Remote Settings requires a lot of work and preparation ahead so as to make the game dynamic enough that you can fine tune it from the dashboard without having to rebuild the game and go through the same process of verification.
https://docs.unity3d.com/Manual/UnityAnalyticsRemoteSettings.html
So this is a nice extension of the purpose of Analytics. But first things first, data must be collected.

Has anyone tried those six custom actions and are they still going to work with Playmaker 1.9.x and the latest versions of Unity LTS?

Are there plans for some official pack of actions, even if it means merely checking on the current actions, dusting them a bit if necessary and officially declaring them a PM pack?

djaydino

  • Administrator
  • Hero Member
  • *****
  • Posts: 6021
    • View Profile
    • jinxtergames
Re: Unity Analytics: some official pack or else?
« Reply #1 on: November 06, 2020, 05:51:56 AM »
Hi.
As long Unity did not make major changes on it they could be fine.

Best is to make a test project to try.

actions like get/set velocity are like 10years old but still work perfectly :)

Broken Stylus

  • Beta Group
  • Hero Member
  • *
  • Posts: 648
    • View Profile
Re: Unity Analytics: some official pack or else?
« Reply #2 on: November 07, 2020, 04:14:36 AM »
OK, we'll see how this plugs into the Unity dashboard. Thus far the needs limit themselves to sending specific events to have a better view of what goes on in app.

Broken Stylus

  • Beta Group
  • Hero Member
  • *
  • Posts: 648
    • View Profile
Re: Unity Analytics: some official pack or else?
« Reply #3 on: April 26, 2021, 06:21:07 AM »
Necro time!

If someone wants to use "official" events, one would preferably use the Analytics Event Tracker component.(1) It comes with a full array of events and associated parameters that Unity collects.

If you expand the Rules region of the component, create a rule and drop a FSM component into the first field, Target, then press on the button to the right of it, by default titled "No Field", it will throw a lengthy error.
This was a quick test to see how by default both Playmaker and this Unity tool communicate. The issue is present too when trying to forward data into parameters associated to any native event sent to the Dashboard.

So is there any way for Playmaker to talk to this component, like through some kind of proxy? The official component wants to interface with delegates.

(1) This is obtained after installing Analytics Library from the Package Manager. It contains the standard events so don't install the other package known as Analytics Standard Events otherwise it will create conflicts. Also, Validator has been removed from the Services / Analytics tab since Jan 16th 2021.

Broken Stylus

  • Beta Group
  • Hero Member
  • *
  • Posts: 648
    • View Profile
Re: Unity Analytics: some official pack or else?
« Reply #4 on: April 29, 2021, 06:11:29 AM »
Integers, floats and strings are the types of data that can be sent.
I tried bools, they sort of appear in the Dashboard but come with a strange symbol and that's wholly unreadable. Therefore, anything that is not an integer, a float or a string should be converted to one of these forms beforehand.

Actions should be updated to reflect this:
 
  • 1. A warning about necessary conversions into proper data types.
     
  • 2. An error check block code at the end of the script to see if the user is using the accepted data types.

« Last Edit: April 29, 2021, 06:17:06 AM by Broken Stylus »

Broken Stylus

  • Beta Group
  • Hero Member
  • *
  • Posts: 648
    • View Profile
Re: Unity Analytics: some official pack or else?
« Reply #5 on: April 29, 2021, 06:18:04 AM »
It's also possible that one error will generate some extra false-positive errors about other FSMs using improper types used for data packets.
For example, I tried to send a Game Object reference as a piece of data, it made Unity spit out several more errors for other FSMs which I knew were actually sending perfectly valid data (string values). For a fact, once the cause of the real error was corrected, the other FSMs logically stopped causing me further trouble.