Search Unity

  1. Check out the Unite LA keynote for updates on the Visual Effect Editor, the FPS Sample, ECS, Unity for Film and more! Watch it now!
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. Improved Prefab workflow (includes Nested Prefabs!), 2D isometric Tilemap and more! Get the 2018.3 Beta now.
    Dismiss Notice
  4. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice
  5. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice

Explore custom events with two parameters

Discussion in 'Unity Analytics' started by solid_, Feb 12, 2018.

  1. solid_

    solid_

    Joined:
    Jul 10, 2015
    Posts:
    5
    Hello, all.
    I want to track average turn count in each of level by using Data Explorer tab.
    For my game i create custom event:
    Analytics.CustomEvent("LevelCompleteAll", new Dictionary <string, object>
    {
    { "level", currentLevel },
    { "turn", turn}
    } );

    Also i create custom segmet to separate data of each level
    upload_2018-2-12_11-47-44.png

    But when i use this segmet i see only empty sheet.
    upload_2018-2-12_11-48-13.png

    What im doing wrong?
    Thanks
     
    Zaphod-Beeblebrox likes this.
  2. Zaphod-Beeblebrox

    Zaphod-Beeblebrox

    Joined:
    Nov 7, 2015
    Posts:
    3
    I also want to know the right way to explore custom event with more than one parameters inside.
     
    Last edited: Feb 12, 2018
  3. aresgameshk

    aresgameshk

    Joined:
    May 19, 2014
    Posts:
    21
    still no answer...
     
  4. JeffDUnity3D

    JeffDUnity3D

    Unity Technologies

    Joined:
    May 2, 2017
    Posts:
    2,610
    @aresgameshk Please describe what you are trying to do. The first post only had a single parameter, and remains to be determined if the event was received at our end. The segment may indeed be empty. Also, segments only start to populate for new events that are sent AFTER the segment is created. We don't back fill from previously sent events.