linkrunner-eventslisted

Instrument Linkrunner event and revenue tracking correctly - what events to send, when to send them, and how to avoid double-counted, dropped, or missing revenue. Platform-agnostic: covers the event taxonomy, ad-network ecommerce fields, capturePayment/removePayment correctness, and the server-side Capture Event / Revenue Tracking HTTP APIs. Use when asked to instrument Linkrunner events, track purchases or revenue with Linkrunner, decide what events to send, debug why revenue or events are missing or double-counted, or send events from a backend/web app that has no client SDK call for custom events.
linkrunner-labs/skills · ★ 0 · API & Backend · score 75

Install: claude install-skill linkrunner-labs/skills

# Linkrunner - Events & revenue instrumentation You are instrumenting **Linkrunner** event and revenue tracking. This skill is the platform-agnostic layer: what to send, when to send it, and how to keep revenue correct. It does **not** give you client call syntax - each platform's SDK skill (`skills/sdk/<platform>/references/events.md`) owns the exact `trackEvent` / `capturePayment` / `removePayment` snippets for that language. ## 0. Before you touch anything 1. Confirm **`signup()` has already been wired** for this app. Events and revenue are only stored and displayed for attributed users - a user must have been registered via `.signup` in an SDK before their events show up. If it isn't wired yet, stop and set that up first via the relevant `skills/sdk/<platform>/` skill. 2. Identify which SDK is installed (Flutter, React Native, Expo, iOS, Android, Capacitor, Cordova, Unity, Web) - or whether this is a backend/web flow with **no client SDK in the loop**. That decides whether you write client code or call the HTTP API. 3. Ask what's actually being tracked: generic product/behavior events, ecommerce events meant to feed Meta Catalog Sales, revenue/payments, or server-side-only tracking (cron jobs, webhooks, web backend). 4. If this is server-side work, get the **server key** (dashboard → Settings → Data APIs: https://dashboard.linkrunner.io/settings?s=data-apis). Never hardcode it - ask where the user keeps secrets. ## 1. Decide what the u