Analytics Devices

With the Analytics device, you can gather information on your island to evaluate player behavior, such as the number of times gameplay elements are interacted with and various events are triggered on your island. By registering events in the Analytics device, you generate event data that can be processed and gathered in the Creator Portal, then retrieved based on the Island Code.

The Analytics device is designed to work with other devices by registering when player behavior triggers other devices such as stepping on a trigger, entering a volume, eliminating an enemy, or pressing a button. Although players will be unaware of the devices you place on your island or what they trigger, player behavior causes an interaction with the Analytics devices and any device attached to it during gameplay.

Data is recorded daily, and can be viewed in the Creator Portal.

The Analytics device takes up very little memory. The first device you place uses 39 memory, and each placed after that uses 9 memory.

The amount of times a device can be placed on an island is completely separate from how much memory the device uses. The Analytics device can be placed 100 times on an island.

If you edit your island, you will not need to re-deploy any devices that have already been placed unless the edit included removing them.

For a list of the Analytics device best practices, see the Analytics Device Dashboard document.

To find the Analytics device, go to the Creative Content browser and select the Devices category. From there, you can search or browse for the device. For more information on finding devices see Finding and Placing Devices.

When using the Analytics device, it is best to rename the Analytics device and all the associated devices tied to a specific Analytics device when editing device options in Create mode. Choose names that relate to each device’s purpose, so it’s easier to remember what each one does.

For repeat events such as player checkpoints, copy and paste the necessary devices, then rename each Event Name in the copied Analytics devices so the different events will gather analytics and generate data in the Creator Portal under the names you chose.

Device Options

This device has some basic functionality, like auto saving, and gathering analytical data on events connected to the device.

Default values are bold. Values that trigger contextual filtering are italic.

You can configure this device with the following options.

Direct Event Binding

Following are the direct event binding options for this device.

Functions

A function listens for an event on a device then performs an action.

1. For any function, click the option, then Select Device to access and select from the Device dropdown menu.

2. Once you've selected a device, click Select Event to bind the device to an event that will trigger the function for the device.

3. If more than one device or event triggers a function, press the Add button to add a line and repeat these steps.

Events

Direct event binding uses events as transmitters. An event tells another device to perform a function.

This device has no events.

Analyzing Gameplay

The following are suggested ways to use the Analytics device in popular game types.

Deathrun Example

To capture data on the number of levels completed in a deathrun, set the Analytics device to listen for player behavior that activates the Player Checkpoint device.

Configure the user options for the Player Checkpoint device on your island, then add Mutator Zones to all the level entrances.

Next, add the Analytics devices to receive information when the checkpoints are activated and to submit the checkpoint data when players enter the Mutator Zone on the next level.

DIRECT EVENT BINDING

Name the events clearly so you know what the device is monitoring, and number the events according to the number of levels in your deathrun. Notice in the example below that the name of the event is tied to the placement of the first checkpoint.

You can place up to 100 Analytics devices on an island at once.

Prop Hunt Example

Use the Analytics devices to determine whether hunters in a prop hunt game are evenly matched to the hidden players. Set up the necessary devices for the prop hunt gameplay. In this instance you’ll use two Analytics devices to track the number of players in the game versus the number eliminations.

Set one Analytics device to track the number of players that join a game, then set another Analytics device to track the number of eliminations in a game.

Direct Event Binding

Capture the Flag Example

Determine the number of times a flag is captured by monitoring how many times the flag is taken to the capture area. Once you’ve set the flag and capture areas, add an analytics device for each team. Set each device to monitor the capture event for one of the teams.

Direct Event Binding

Analyzing Events Using Verse

Ensure the devices you intend to monitor with the Analytics device have a Player Agent function. Without a player-led action, the Analytics device will not record any data. Use the Verse API to search for Player Agent functions on the device.

Set up the basic options for the devices to ensure they behave the way you want them to.

Create a Verse script following the directions in Create Your Own Verse Device.

Using Analytics in Verse

You can use the code below to control an Analytics device in Verse. This code shows how to use events and functions in the Analytics device API. Modify it to fit the needs of your experience.

using { /Fortnite.com/Devices }
using { /Verse.org/Simulation }
using { /UnrealEngine.com/Temporary/Diagnostics }


# A Verse-authored creative device that can be placed in a level
analytics_device_verse_example := class(creative_device):


    # Reference to the Analytics device in the level.
    # In the Details panel for this Verse device,
    # set this property to your Analytics device.
    @editable
    MyAnalyticsDevice:analytics_device = analytics_device{}


    # Reference to the Damage Volume device in the level.
    # In the Details panel for this Verse device,
    # set this property to your Damage Volume device.
    @editable
    DamageVolume:damage_volume_device = damage_volume_device{}


    # Runs when the device is started in a running game
    OnBegin<override>()<suspends>:void=
        # Example for subscribing to an event on the Creative device.
        # Signaled when an agent enters the damage volume.
        DamageVolume.AgentEntersEvent.Subscribe(OnAgentEntered)


    # This function runs when an agent enters the damage volume because it's an event handler for the Damage Volume device's AgentEntersEvent.
    OnAgentEntered(Agent:agent):void=
        # Submits an event for `Agent` to generate analytics.
        MyAnalyticsDevice.Submit(Agent)
Copy full snippet

using { /Fortnite.com/Devices } using { /Verse.org/Simulation } using { /UnrealEngine.com/Temporary/Diagnostics } # A Verse-authored creative device that can be placed in a level analytics_device_verse_example := class(creative_device): # Reference to the Analytics device in the level. # In the Details panel for this Verse device, # set this property to your Analytics device. @editable MyAnalyticsDevice:analytics_device = analytics_device{} # Reference to the Damage Volume device in the level. # In the Details panel for this Verse device, # set this property to your Damage Volume device. @editable DamageVolume:damage_volume_device = damage_volume_device{} # Runs when the device is started in a running game OnBegin<override>()<suspends>:void= # Example for subscribing to an event on the Creative device. # Signaled when an agent enters the damage volume. DamageVolume.AgentEntersEvent.Subscribe(OnAgentEntered) # This function runs when an agent enters the damage volume because it's an event handler for the Damage Volume device's AgentEntersEvent. OnAgentEntered(Agent:agent):void= # Submits an event for `Agent` to generate analytics. MyAnalyticsDevice.Submit(Agent)

To use this code in your UEFN experience, follow these steps.

1. Drag an Analytics device onto your island.

2. Create a new Verse device named analytics_device_verse_example. See Create Your Own Device Using Verse for steps.

3. In Visual Studio Code, open analytics_device_verse_example.verse and paste the code above.

4. Compile your code and drag your Verse-authored device onto your island. See Adding Your Verse Device to Your Level for steps.

5. Add a reference for the Analytics device on your island to your Verse device. See Adding a Verse Reference to a Creative Device in Your Level for steps.

6. Save your project and click Launch Session to playtest.

Analytics Device Verse API

See the [analytics_device](https://dev.epicgames.com/documentation/en-us/uefn/verse-api/fortnitedotcom/devices/analytics_device) API Reference for more information on using the Analytics device in Verse.