Whatβs in it for you?
π Crystal-clear usage insights β See exactly how each app, project, or customer uses your APIπ° Bulletproof cost allocation β No more guesswork when dividing bills
π Performance monitoring β Track response times and success rates per app
π Data-driven decisions β Export detailed reports and spot trends instantly
π‘οΈ Smart spending controls β Set limits and get alerts before things get expensive
Getting Started: Two Ways to Tag Your Requests
Method 1: HTTP Headers (Recommended)
Clean, simple, and works everywhereMethod 2: Request Body Metadata
Perfect for complex attribution scenariosAttribution Fields Reference
Must-Have
app_id
β Your appβs unique identifier (this is the only required field)
Nice-to-Have (But Really Useful)
app_name
β Human-friendly app name for dashboardsapp_version
β Track performance across versionsuser_id
β See per-user usage patternssession_id
β Follow conversation threadsproject
β Organize by campaigns or initiativesenvironment
β Separate prod from staging costsregion
β Geographic usage distribution
Real-World Implementation
Single App Setup
Perfect for most developersMulti-Tenant SaaS Setup
When youβre serving multiple customersAnalytics That Actually Matter
Get Usage Insights
See where your moneyβs goingCost Allocation Reports
Perfect for finance teams and client billingSmart Usage Controls
Set Spending Limits
Sleep better knowing your costs are under controlReal-Time Usage Monitoring
Stay on top of your spendingPro Tips for Success
π― Smart App IDs
- Be descriptive: Use
customer-chat-prod
notapp1
- Stay consistent: Pick a naming pattern and stick to it
- Include environment: Separate
prod
,staging
,dev
π Meaningful Data
- Track what matters: User IDs for SaaS, session IDs for chat apps
- Version everything: Catch performance regressions early
- Add context: Project names, feature flags, A/B test groups
π° Cost Management
- Set realistic limits: Start conservative, adjust as needed
- Monitor trends: Weekly reviews prevent monthly surprises
- Use alerts wisely: 50% warning, 80% action needed, 95% panic mode
π Security First
- Hash user IDs: Protect customer privacy
- No secrets in tags: Attribution data is logged
- Follow regulations: GDPR, CCPA compliance matters
π Analytics Optimization
- Consistent naming: Same field names across all apps
- Rich metadata: More context = better insights
- Regular reviews: Monthly deep dives reveal optimization opportunities
Common Success Stories
π’ Multi-Tenant SaaSβWe use App Attribution to bill customers accurately and identify our power users. Revenue attribution increased 40%.β π Product Teams
βTracking by feature helped us kill underperforming products and double down on winners. ROI improved dramatically.β π§βπ» Development Teams
βSeparating staging from production costs was a game-changer. No more surprise bills from testing.β π Analytics Teams
βPer-user tracking revealed usage patterns we never knew existed. Our retention strategies are now data-driven.β πΌ Finance Teams
βCost allocation reports make budgeting and forecasting actually possible. CFO loves the transparency.β
Whatβs Next?
Ready to get surgical precision on your API costs? App Attribution gives you the visibility and control you need to optimize usage, allocate costs fairly, and make data-driven decisions about your AI investments. Start with a simpleapp_id
on your next request, then gradually add more attribution fields as your needs grow. Your future self (and your finance team) will thank you.
Happy tracking! π