Sending Events

This section shows you how to send the JOIN Stories events to specific data platforms. You can use the following function of JOINStoriesListenerDelegate to redirect the JOIN Stories events to your data platform :

import JOINStoriesSDK

class YourViewController: UIViewController {

   override func viewDidLoad() {
        super.viewDidLoad()
        JOINStoriesListener.setDelegate(delegate: self)
   }
}

extension YourViewController: JOINStoriesListenerDelegate {
    func joinStoriesAnalyticsCallback(event: JOINTrackingEvent, payload: [String: Any?]) {}
}

import JOINStoriesSDK

struct YourView : View {
    
   @StateObject var viewModel = YourViewModel()
    
    var body: some View {
        Text("Hello, world!")
    }
}

class YourViewModel: ObservableObject {
    init() {
        JOINStoriesListener.setDelegate(delegate: self)
    }
}

extension YourViewModel: JOINStoriesListenerDelegate {
    func joinStoriesAnalyticsCallback(event: JOINTrackingEvent, payload: [String: Any?]) {}
}

Tracking user ID

In stories analytics, you can track user activity by adding a user ID. You can use the setTrackingUserId() method to enter the user's ID, or set it to empty if the user does not accept consent.

import JOINStoriesSDK

class YourViewController: UIViewController {

   override func viewDidLoad() {
        super.viewDidLoad()
     		JOINStories.setTrackingUserId("<custom_user_id>") // if you wish to use your personnalize ID
				//or 
				JOINStories.setTrackingUserId("") // if user does not accept consent
   }
}

Analytics Events

During its life on a mobile, a widget can trigger various analytics events. There are events related to the widget itself and events related to the stories inside of it. They track how the users interact with the widget and its content.

Analytics v2

A new Analytics stack has been implemented. Old events have been renamed, with more properties. New events have been added. They are split by categories. Each category has its own properties.

Category : Story

Category : Interaction

Category : Widget

Properties

All events have at least the common properties. Each category has its own properties.

Common properties

Story properties

Interaction properties

Widget properties

🚧

Analytics sender

When integrating, you need to be aware of the widget's lifecycle, as the widget may send events several times during use if it is destroyed and recreated, in the case of a dynamic list.

Migration from V1 to V2 events

If you are using event analysis from a callback, you can perform a simple migration of events from version V1 to version V2 using the following table :

JOIN Stories Events (Deprecated)

In order to get notification about JOIN Stories events, you should override the following functions in JOINStoriesListenerDelegate. The events are separated between trigger events (onTriggerAnalyticsCallback called) and player events (onPlayerAnalyticsCallback called).

Trigger Events

onTriggerAnalyticsCallback returns the following payload for each event:

public struct TriggerAnalyticsModel {
    public var eventOwner: String? // owner of the story (equal teamId)
    public var cpWidgetAlias: String // Alias of the trigger
    public var cpWidgetVersion: String // Version of the SDK
    public var date: Int64 // Current UNIX Timestamp in ms
    public var eventCategory: String = "widget"
    public var eventType: TriggerAnalyticsEventType // The event type
    public var eventTypeName: String // The event type name
    public var storyClicked: String // The story id - only for click events
}

Stories Fetched Event

Each time the trigger fetch the list of stories from the API, a Stories fetched event is sent:

event: .storiesFetched

Trigger Mounted Event

Each time the trigger is instantiated, a Trigger Mounted event is sent:

event: .widgetMounted

Trigger Visibility 50% Event

After instantiation, the first time the trigger is visible at least on 50% of its height, a Trigger Visible 50% event is sent:

event: .componentVisible50

Trigger Visibility 75% Event

After instantiation, the first time the trigger is visible at least on 75% of its height, a Trigger Visible 75% event is sent:

event: .componentVisible75

First Click on Trigger Event

After instantiation, the first time the trigger is clicked to open the player, a First Click on Trigger event is sent:

event: .firstClickOnWidget

It also contains the following value: storyClicked: STORY_ID

Additional Click on Trigger

Each time the trigger is clicked after the first click (see previous event), an Additional Click on Trigger event is sent:

event: .additionalClickOnWidget

It also contains the following value: storyClicked: STORY_ID

Player Events

onPlayerAnalyticsCallback returning the following payload for each event:

public struct PlayerAnalyticsModel {
    public var storyPageCount: Int // Number of chapter of the story
    public var eventOwner: String? // owner of the story (equal teamId)
    public var storyId: String? // ID of the story
    public var date: Int64 // Current UNIX Timestamp in ms
    public var eventCategory: String = "story",
    public var cpIndex: Int? // Index of the current chapter: from 0 to N
    public var cpTitle: String? // Title of the story
    public var eventType: PlayerAnalyticsEventType // The event type
    public var eventTypeName: String // The event type name
}

Chapter View Event

Each time a chapter (equivalent to story page) starts playing, a Chapter View event is sent:

event: .storyPageVisible

Last Chapter View Event

Each time the last chapter (last story page) starts playing, a Last Chapter View event is sent:

event: .storyLastPageVisible

Click Call To Action Event

Each time the user clicks on a CTA, a Click Call To Action event is sent:

event: .storyClickOnCallToAction

The parameter ctaUrl is set on this event only.