Embedded analytics lets you put Tractorscope dashboards or charts inside your own product so customers can view data without logging in to Tractorscope directly.
Typical architecture
- Your application authenticates the user.
- Your backend determines the customer, tenant, account, or filter scope.
- Your backend builds a Tractorscope embed payload.
- Your backend signs the payload with a Tractorscope API key.
- Your frontend renders the iframe dashboard embed or chart web component.
Tenant-specific filters
Use filters to scope embedded analytics to a customer, account, organization, region, or user. Filter values should be generated on your server, not trusted from the browser.
Embed choices
Use dashboard embeds for full analytics experiences. Use chart web components when you need a single chart inside a custom page.
Production checklist
- Create and store API keys server-side.
- Configure allowed domains.
- Enable embedding on the dashboard or chart.
- Decide whether embedded viewers can download data.
- Decide whether embedded viewers can use pivot tables.
- Test with realistic tenant filter values.