Creem revenue attribution
Connect your Creem store to an Insights website to see confirmed purchases and revenue alongside your traffic.
Open revenue attribution
Open your verified website in TypeUI Insights, go to Settings → Revenue attribution, and choose Creem.
Create a read-only API key
In Creem, open Developers → API Keys and create a separate key for TypeUI. Enable only:
transactions:read— read purchases and refund amounts.products:read— read product names.
Leave full access (*:*), wildcard scopes, write access, and every other permission disabled. Copy the complete key beginning with creem_. Keep your checkout integration's credentials separate.
Connect and sync
Paste your key and select Connect Creem. TypeUI detects live or test mode, verifies access, encrypts the key, and starts importing your transactions.
Use Sync now to refresh purchases, Replace key after rotating the credential, or Disconnect to delete the stored key and imported Creem purchases from this website. Replacing a key starts a fresh import so different stores or environments cannot be combined accidentally.
What appears in Insights
Paid one-time purchases and subscription payments appear with their amount, currency, date, and product name when a matching product is available. Refunds reduce revenue, and fully refunded or charged-back payments have no remaining revenue. Pending, failed, and canceled payments are excluded.
Syncs revisit transactions so a refund on an older purchase is picked up. Product names come from Creem's product catalog; free-form transaction descriptions, customer names, emails, billing addresses, and card information are not stored in Insights.
Session attribution
Creem's transaction list does not expose the checkout's TypeUI session reference. This integration imports confirmed revenue and products, but does not automatically associate Creem transactions with individual visitor journeys or campaigns. Unmatched purchases still appear in your revenue dashboard.
Troubleshooting
- Check that the complete key is active and belongs to the intended Creem store. Test-mode data is separate from live payments.
- If a read request is denied, check that both
transactions:readandproducts:readare enabled. No additional permissions are needed. - If you previously connected a full-access key, create a key with only these two read permissions and use Replace key.
- A large store can exceed the per-sync processing limit. An incomplete sync is shown as an error; contact TypeUI support if it repeats.
- If a product is no longer available in the product catalog, its transaction still contributes to revenue without a product name.
See the Revenue attribution overview for dashboard sharing and currency display, or Creem's transaction API for the available payment fields.