Generic Proxy Setup

This guide covers the core concepts for setting up a AddonPulse proxy with any reverse proxy or server framework. If your specific framework has a dedicated guide, we recommend following that instead for optimized instructions.

Prerequisites

Before setting up the proxy, ensure you have:

A domain or subdomain where you'll serve the proxied scripts (e.g., yourdomain.com or analytics.yourdomain.com)
SSL/TLS certificate for HTTPS (required for modern browsers)
Server or platform with reverse proxy capabilities
Your AddonPulse instance URL https://app.addonpulse.com
Your AddonPulse site ID (found in your AddonPulse dashboard)

Understanding the Endpoints

AddonPulse uses several endpoints for tracking. You can choose between a minimal setup or full proxy:

Required endpoints for basic tracking:

Endpoint	Method	Purpose	Cache
`/api/script.js`	GET	Main tracking script	1 hour
`/api/track`	POST	Event tracking endpoint	No cache

This minimal setup enables basic pageview and event tracking but won't support some advanced features.

All endpoints for complete functionality:

Endpoint	Method	Purpose	Cache
`/api/script.js`	GET	Main tracking script (minified)	1 hour
`/api/track`	POST	Event tracking endpoint	No cache
`/api/identify`	POST	User identification endpoint	No cache
`/api/site/tracking-config/:siteId`	GET	Site configuration	5 minutes

Implementation Steps

Configure Your Proxy Rules

Set up your reverse proxy to forward requests from your chosen path (e.g., /analytics/*) to the AddonPulse server.

Generic proxy configuration pattern:

Your domain path          →  AddonPulse backend
-----------------            ---------------
/analytics/script.js      →  https://app.addonpulse.com/api/script.js
/analytics/track          →  https://app.addonpulse.com/api/track
... and so on

Key requirements:

Preserve the HTTP method (GET or POST)
Forward necessary headers (User-Agent, X-Forwarded-For, Referer)
Maintain request/response body for POST requests
Set appropriate Content-Type headers

Configure Caching (Optional but Recommended)

Implement caching to reduce load on AddonPulse servers and improve performance:

Recommended cache durations:

Scripts (.js files): 1 hour (3600 seconds)
- These change infrequently but may be updated for bug fixes
Site configuration (/api/site/tracking-config/*): 5 minutes (300 seconds)
- Updated when you change settings in the dashboard
Tracking endpoints (POST requests): Never cache
- Each request contains unique event data

Example cache headers to set:

Cache-Control: public, max-age=3600  # For scripts
Cache-Control: public, max-age=300   # For config
Cache-Control: no-store              # For tracking POSTs

Update Your Tracking Script

Change your script tag to load from your proxied domain instead of directly from AddonPulse:

Before (direct loading):

<script src="https://app.addonpulse.com/api/script.js" async data-site-id="YOUR_SITE_ID"></script>

After (proxied):

<script src="https://yourdomain.com/analytics/script.js" async data-site-id="YOUR_SITE_ID"></script>

How Auto-Discovery Works: The AddonPulse script automatically extracts the analytics host from its own src attribute by splitting on /script.js. This means when it loads from https://yourdomain.com/analytics/script.js, it automatically sends all tracking data to https://yourdomain.com/analytics/* endpoints.

Verify the Setup

Test your proxy configuration to ensure everything works correctly:

Open your website in a browser with Developer Tools open
Go to the Network tab and filter by "script" or your proxy path
Verify the script loads:
- You should see a request to yourdomain.com/analytics/script.js
- Status should be 200 OK
- Content-Type should be application/javascript
Verify tracking works:
- Navigate to another page or trigger an event
- You should see POST requests to yourdomain.com/analytics/track
- Check the response is successful (200 OK)
Check your AddonPulse dashboard:
- Wait 1-2 minutes for data to process
- Verify your session appears in real-time dashboard

Configure Security Headers (Optional)

Add security headers to protect your proxy:

Recommended headers:

X-Content-Type-Options: nosniff
X-Frame-Options: DENY
Referrer-Policy: strict-origin-when-cross-origin

CORS headers (should be preserved from AddonPulse):

Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, OPTIONS
Access-Control-Allow-Headers: Content-Type

Request Header Forwarding

For accurate tracking, ensure these headers are forwarded to the AddonPulse backend:

Header	Purpose	Required
`User-Agent`	Device and browser detection	Yes
`X-Forwarded-For` or `X-Real-IP`	IP address for geolocation	Yes
`Referer`	Referrer tracking	Recommended
`Accept-Language`	Language detection	Optional

IP Forwarding: AddonPulse uses IP addresses for geolocation (country/city) and creating anonymous user identifiers (hashed IP + User Agent). If you don't forward the X-Forwarded-For or X-Real-IP header, all traffic will appear to come from your proxy server's IP.

Bandwidth Considerations

Proxying adds bandwidth usage to your infrastructure. Here's what to expect:

Typical bandwidth per session:

Initial script load: ~18 KB (one-time per session)
Pageview tracking: ~0.5-2 KB per pageview
Custom events: ~0.5-3 KB per event

Estimated monthly bandwidth for a site with 100,000 monthly sessions:

~5-10 GB/month

Most modern hosting plans can handle this easily, but verify your bandwidth limits if you have high traffic.

Performance Optimization

Use a CDN

If your server has CDN capabilities (like Cloudflare, Fastly, or AWS CloudFront), configure it to cache the static scripts:

Cache scripts at edge locations worldwide
Reduce latency for global users
Offload bandwidth from your origin server

Enable Compression

Ensure your proxy enables gzip or brotli compression:

Content-Encoding: gzip

This can reduce script size by 60-70%, improving load times and reducing bandwidth.

Connection Reuse

Configure your proxy to maintain persistent connections to AddonPulse's backend to reduce latency on repeated requests.

Common Proxy Patterns

Use a dedicated subdomain for analytics:

https://analytics.yourdomain.com/script.js  →  https://app.addonpulse.com/api/script.js
https://analytics.yourdomain.com/track      →  https://app.addonpulse.com/api/track

Pros:

Clean separation of concerns
Easy to manage SSL certificate
Can use separate CDN configuration

Cons:

Additional DNS lookup (minor performance impact)
Need to manage subdomain DNS

Use a path on your main domain:

https://yourdomain.com/analytics/script.js  →  https://app.addonpulse.com/api/script.js
https://yourdomain.com/analytics/track      →  https://app.addonpulse.com/api/track

Pros:

No additional DNS lookup
Single SSL certificate
Truly first-party from browser perspective

Cons:

Must ensure proxy path doesn't conflict with your app routes

Security Considerations

Rate Limiting

Consider adding rate limiting to prevent abuse:

Limit POST requests to tracking endpoints (e.g., 100 requests per minute per IP)
Whitelist your AddonPulse backend IP if possible
Monitor for unusual traffic patterns

Request Size Limits

Set appropriate request body size limits:

/api/track, /api/identify: 1 MB max

HTTPS Only

Always serve your proxy over HTTPS:

Modern browsers require HTTPS for many features
Protects user data in transit
Required for accurate tracking in secure contexts

Troubleshooting

If something isn't working, check:

Script loads but no events tracked: Verify all tracking endpoints (/api/track, etc.) are proxied
CORS errors: Ensure CORS headers are preserved from AddonPulse backend
404 errors: Check that URL paths exactly match expected format
Incorrect geolocation: Verify X-Forwarded-For header is forwarded

For more detailed troubleshooting, see our troubleshooting guide.

Next Steps

Now that you understand the generic concepts, choose your specific framework or platform for detailed implementation instructions:

On this page