Summary
Analytics and public reports are related, but they are not interchangeable. In TruAgents:- Analytics is the in-product reporting surface used by authenticated users.
- Public reports are tokenized share links created from analytics data for external or broader distribution.
Who this is for
- Users reviewing campaign and communications performance
- Admins or operators sharing reporting outside the app
- Internal teammates documenting reporting behavior and access expectations
Where to find it in the app
- Analytics
- Analytics → Published Reports
- public report links under
/reports/...
The two reporting modes
In-product analytics
The authenticated analytics experience is where teams explore performance using filters, views, and internal reporting components. The current app suggests this includes:- overview metrics
- filterable date and channel analysis
- campaign and channel breakdowns
- issues-oriented reporting
- run-specific analysis
- how are campaigns performing overall?
- which channel is contributing most of the activity?
- what changed in a specific date range?
- which campaign runs need closer inspection?
Public reports
Public reports are meant for controlled external sharing. They are created from the analytics flow and then managed separately. The current app also suggests that public reports can be:- activated or deactivated
- rotated to create a new token
- deleted
- scoped or constrained by filters and reporting rules
How the share flow works
The current product model is:- choose the analytics view you want
- click Share
- create a tokenized report link from that scoped view
- manage that link later from Analytics → Published Reports
What stays locked versus what can still change
One subtle but important detail from the current implementation: public reports can preserve locked scope such as channel, campaign, or segment, while still allowing the viewer to adjust the date range.| Reporting detail | In Analytics | In Public Reports |
|---|---|---|
| Channel and campaign exploration | Freely adjustable for internal users | Can be locked when the link is created |
| Segment scope | Freely adjustable for internal users | Can be locked when the link is created |
| Date range | Adjustable | Still adjustable |
| Access model | Normal authenticated product access | Tokenized link access |
| Link lifecycle | Not applicable | Can be activated, deactivated, rotated, or deleted |
Why this distinction matters
- Internal analytics assumes authenticated product usage.
- Public reports assume link-based access.
- The security and audience model is different even when the underlying reporting data is related.
When to use which
Use Analytics when:- the viewer needs to explore, compare, and investigate
- the work is part of normal internal operations
- the audience already has product access
- the audience only needs a curated view
- you want distribution without creating normal app seats
- the link owner is willing to manage the lifecycle of that shared report
Common misunderstandings
- a public report is not the same thing as app access
- “shareable” does not mean “fully interactive like the internal analytics UI”
- if a report was created from the wrong scoped filters, the resulting link may still be technically valid but operationally misleading
Success checklist
- Teams know when to stay in Analytics versus when to create a public report.
- Shared links are treated as a controlled distribution mechanism, not as the same thing as app access.
- Teams understand that public reports can preserve locked scope while still allowing date changes.
- Owners understand that public report management is a separate operational responsibility.