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

TL;DR

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.

Fix

1. 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. Expected: you can confirm this matches your situation.

When to use

• You are dealing with this situation.
• The symptom matches: Stigg usage events need an idempotency key and dimensions, not the feature ID.

When NOT to use

• Unrelated issues with a different cause.
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source. Source: https://github.com/stiggio/skills/blob/HEAD/skills/stigg-entitlements/SKILL.md.

Variant phrasings

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

Why it happens

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

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

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

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