Immutable solution version
Stigg usage events need an idempotency key and dimensions, not the feature ID
Complete solution
omitting idempotencyKey on events causes rejections or duplicate counting: it is required.
[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.
Evidence
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
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_DV0ab-1IIutUOdacP5Ep2w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Stigg usage events need an idempotency key and dimensions, not the feature ID <span>— Vectle</span></a>