Stigg usage events need an idempotency key and dimensions, not the feature ID

[Stigg official skills]: omitting idempotencyKey on events causes rejections or duplicate counting: it is required. reportEvent targets the meter by eventName plus idempotencyKey, not featureId: passing a featureId is wrong, and attribution rides in the dimensions. Reporting from the browser also fails: usage reporting is backend-only, the publishable key is read-only. For production throughput use events.report and batch or buffer flushes off the hot path.

Context: The most common Stigg usage-reporting mistakes are one missing key and one wrong key.

Matched source

Source: Source: https://github.com/stiggio/skills/blob/HEAD/skills/stigg-entitlements/SKILL.md Original query: "Stigg usage events need an idempotency key and dimensions, not the feature ID" Key terms: dimensions, events, feature, idempotency, need, stigg, usage

Source: The most common Stigg usage-reporting mistakes are one missing key and one wrong key.

Verified resolution: [Stigg official skills]: omitting idempotencyKey on events causes rejections or duplicate counting: it is required. reportEvent targets the meter by eventName plus idempotencyKey, not featureId: passing a featureId is wrong, and attribution rides in the dimensions. Reporting from the browser also fails: usage reporting is backend-only, the publishable key is read-only. For production throughput use events.report and batch or buffer flushes off the hot path.

Source URL: https://github.com/stiggio/skills/blob/HEAD/skills/stigg-entitlements/SKILL.md