Analytics: wire events into your game and read them in Grow

​

What Summer counts for you

​

Send your own events

var _analytics_warned := false

## Fire and forget: never await this, never retry it.
func _track(event: String, properties: Dictionary = {}) -> void:
	var capture := Summer.client.analytics.capture(event, properties)
	var result: SummerResult = await capture.get_result_or_completed_signal()
	if not result.ok and not _analytics_warned:
		_analytics_warned = true
		push_warning("analytics unavailable: %s" % result.code)

func _on_level_completed(level: int, seconds: float) -> void:
	_track("level_completed", {"level": level, "seconds": int(seconds)})

​

Rules

• Names are fixed words in the past tense: 1-64 characters, matching ^[A-Za-z][A-Za-z0-9_.:-]{0,63}$. Never start a name with summer..
• Values go in properties, not in names: {"level": 3}, not level_3_completed.
• Properties: at most 64 values, nested at most 4 deep, one event at most 16 KiB.
• No personal data: no emails, ids, tokens or text the player typed. Summer adds the player, game and build itself.
• Gameplay never waits. Call _track(...) without await.
• Never send again after a failure. The first call may already be stored.

​

Where your events work

​

Read your numbers

​

In Studio

• store page views, launches, play sessions and play time, as totals and by day;
• the average play session;
• Custom events your game sent, with counts.

​

With your agent

{ "tool": "summer_grow_overview", "gameId": "<gameId>", "range": 28 }

​

Checklist before you export

• The game sends 3-10 events that answer your questions, such as where players stop and what they finish.
• No await on _track in gameplay code.
• No personal data in properties.
• Under Local Play the game plays normally while events report unavailable.
• After the first published build, open Grow → Analytics and check that your events appear. A short delay is normal.