Data Collection

Performance and Stability

Enabled by default. The SDK collects this data automatically. No configuration or instrumentation required.

Data collected:

• Mods download
• Mods update
• Mod install and update success and failure rates
• Mod ecosystem health including
  • Number of creators
  • Number of available mods
  • Mods creation trend

User Engagement

Disabled by default. To enable:

1. Open the CFCore plugin settings in the Unreal Editor.
2. Enable the User Engagement analytics category.
3. Instrument your game code with the SDK calls below.

important

The SDK must be fully initialized before calling any analytics functions.

Game Play Session

Call this at the end of every game session, modded or unmodded. This call is the foundation of session-level engagement data and feeds the Modded MAU calculation visible in the console.

• Blueprint: Send Game Play Session Analytic
• C++: ICFCoreAnalytics::SendGamePlaySession

Parameters (FGamePlaySessionParams):

Field	Type	Description
sessionLengthInSecs	int32	Duration of the session in seconds
sessionType	ECFCoreSessionType	Local or Server
modIds	TArray<int64>	IDs of mods active during the session
serverName	FString	Server identifier (only relevant when sessionType = Server)

Mod Browser Funnel

Two calls cover the mod browser funnel: one for impressions (a mod was shown to the player) and one for actions (the player did something). The data populates a conversion view in the console showing drop-off across the full sequence: browser open, impression, action, install. Use this to diagnose discovery friction and identify underperforming shelves or placements.

• Blueprint (impression): Send Mod Browsing Funnel Impression Analytic
• Blueprint (action): Send Mod Browsing Funnel Action Analytic
• C++ (impression): ICFCoreAnalytics::SendModBrowsingFunnelImpression
• C++ (action): ICFCoreAnalytics::SendModBrowsingFunnelAction

Both calls use FModBrowsingFunnelParams:

Field	Type	Description
pageName	FString	The UI page where the event occurred
pageComponent	FString	Sub-component within the page (e.g. a carousel or shelf)
shelfName	FString	Shelf identifier, if applicable
modId	int64	The mod involved in the event
pageId	int64	Themed page identifier, if applicable
itemPosition	int64	Position within a carousel or shelf, if applicable
actionType	FString	For action events: the action taken (e.g. install, uninstall, purchase, update)

note

Numeric fields left at their default value are ignored by the SDK and not sent.

Premium and Revenue

Collected automatically. No instrumentation required. The platform records every premium mod transaction and surfaces the data at two levels: per-mod for authors in the Premium Mods dashboard, and aggregated across the full game ecosystem for studio-side visibility.

Data collected:

• Transaction id
• CF User id
• Platform
• Console user Id (PS / Xbox / Steam / Nintendo)
• Premium mod ID
• Gross price
• Platform fees (including gateway and payment vendor fees)
• Player's country (Windows only)

Cloud Cooker Status

Collected automatically. No instrumentation required. The platform records cooking activity for every mod submission and surfaces it in the author-facing Cloud Cooker Stats dashboard.

Data collected:

• Number of cooks initiated
• Cooking success rate
• Cooker uptime
• Per cluster cooking time
• File clusters in the cooker's queue