Attribution and client reporting
Every routing decision is recorded against the rule that fired. Turn that into per-destination analytics, a weekly digest, and exports your clients or stakeholders can actually read.
The Free plan needs no card.
The challenge
- Offline traffic looks like a black box
- Once a QR code or short link is printed, it's hard to say which rule, market, or variant actually produced a result.
- Client reporting is manual
- Agencies and multi-location operators end up screenshotting dashboards to build reports by hand every month.
- Anomalies go unnoticed
- A sudden drop or spike in a destination's performance can sit unexamined until someone happens to look at the dashboard.
The Sprykit solution
Per-rule attribution
Every routing decision is recorded against the exact rule that fired, so you always know why a visitor landed where they did.
- Rule-level visit logging
- Attribution tied to every conversion
- No manual tagging required
Per-destination analytics
See conversions, dwell time, and device or geo breakdowns for each destination a journey can route to.
- Conversion & dwell-time tracking
- Device and geo breakdowns per destination
- Insights and anomaly detection vs. prior period
Digest and exports
A weekly email digest with a CSV attachment keeps stakeholders informed, and full CSV/PDF exports are always one click away.
- Weekly email digest with CSV
- One-click CSV export
- One-click PDF export
What changes
Every routing decision is traceable to the rule that made it, and exportable.
- Per-rule
- Attribution on every routing decision, every time.
- CSV & PDF
- Export formats available for every journey's analytics.
- Weekly
- Digest delivered automatically with a CSV attached.
Perfect for
Agencies and multi-location brands
Prove which rule, market, or variant drove results for each location or client without manual data pulls.
Example: Export a PDF report straight from a journey's analytics view.
Weekly stakeholder updates
Keep marketing leads or franchise owners informed automatically with a scheduled digest instead of ad hoc check-ins.
Example: A Monday-morning email summarizes last week's routing performance with a CSV attached.
Performance monitoring
Catch a destination that's suddenly underperforming before it costs a full reporting cycle.
Example: An anomaly flag surfaces a conversion drop the same week it happens.
What you get
- Per-rule
- Every routing decision is attributed to the rule that fired.
- CSV & PDF
- Full journey reports, exportable for clients and stakeholders.
- Weekly
- An email digest with period-over-period deltas and a CSV attached.
- Per-destination
- Conversions and dwell time reported per destination, not just per journey.
Related use cases
Turn routing data into real reporting
Get per-rule attribution, exports, and a weekly digest built in with Sprykit Journeys.
The Free plan needs no card.