AV Insights tracking without the Piano Analytics SDK. 

In server-side implementations, the support provided by the Piano Analytics SDK is not available. The SDK typically: 

• Adds contextual properties to events, including previous event name and position (e.g., av_previous_position, av_previous_event). 

• Sends heartbeat events during playback. 

• Ensures event sequencing within the same AV session. 

Without the SDK, these mechanisms must be managed manually, which can be complex. To simplify server-side tracking, Piano Analytics offers a Light version of AV Insight, specifically designed for this use case. 

What is AV Light? 

To ensure AV Insights compatibility with server-side implementations, AV Light reduces the amount of information required for tracking.

Warning : When the four properties typically added by the Piano SDK are missing, the processing system automatically reconstructs them and manages the AV session. However, these four properties must not be included in the tag; otherwise, the event will not be recognized as AV Light and will be discarded. 

The four properties managed by processing: 

• av_session_id – Unique identifier grouping events from the same playback session. 

• av_previous_event – Identifies the previous AV Insight event. 

• av_previous_position – Tracks the cursor position of the previous event. 

• av_duration – Specifies the duration of the previous event. 

Since these parameters are handled by our processing system, their management will follow the predefined logic established by Piano Analytics. 

→ To illustrate, an av_session_id is created under specific conditions during certain AV-related events, including: 

• av.play 

• av.buffer.start 

• av.buffer.heartbeat 

• av.start 

• av.rebuffer.start 

• av.rebuffer.heartbeat 

• av.heartbeat 

• av.pause 

• av.backward 

• av.forward 

• av.resume 

• av.seek.start 

The former av_session_id is terminated and a new av_session_id is generated when the previous session concludes with an av.stop event or when any of the following parameters differ from the previous AV event: 

• Date of the event 

• visitor_id 

• site_id 

• av_content_id 

If you need more details on how these parameters are processed, please contact our support center at support@piano.io. 

What is Not Supported? 

We recommend manually implementing av.heartbeat events on the server side. This ensures the continuity of an audio/video session and prevents underestimation of playback time calculations. 

Implementation Recommendations for Server-Side Environments 

✅ Optimized Tracking for Simplicity 

• Basic AV Light – Minimal implementation without handling complex properties or technical events. Suitable for short media, such as clips.  

• Advanced AV Light – Minimal implementation with av.heartbeat events triggered at each video quartile. Recommended for extended content, including broadcast, episodes or podcasts. 

🔍 Advanced Tracking with Full Client Control 

• Full AV Server-Side – A more advanced implementation where clients manage parameters autonomously, providing greater flexibility.