How Sub-ID Tracking and S2S Postbacks Prevent CPA Conversion Loss

The Hidden Cost of Lost Conversions

In the CPA ecosystem, every lost conversion is lost revenue. A user completes an offer, the advertiser confirms it, but the publisher never gets credited. This "conversion leak" is more common than most publishers realize — and it's almost always caused by broken tracking.

VeloxOffer's postback infrastructure processes over 2 million server-to-server (S2S) callbacks per day. Here's how our tracking architecture ensures zero conversion loss.

Understanding Server-to-Server (S2S) Postbacks

Unlike pixel-based tracking that relies on the user's browser loading a tracking pixel, S2S postbacks fire directly between servers. This makes them:

• Browser-independent: No ad blockers, cookie restrictions, or ITP policies can interfere.
• Reliable: Server-to-server HTTP requests have near-100% delivery rates compared to ~70-80% for client-side pixels.
• Secure: Postback URLs contain cryptographic click IDs that prevent spoofing.

Click ID Architecture

When a user clicks an offer on VeloxOffer, we generate a unique click_id that encodes:

• Publisher ID and placement ID
• Offer ID and advertiser campaign reference
• User fingerprint hash (device + IP + UA)
• Timestamp with microsecond precision
• Cryptographic signature (HMAC-SHA256)

This click ID is passed through the entire conversion funnel. When the advertiser fires their postback, they include this click ID, allowing VeloxOffer to instantly reconcile the conversion with the original click.

Sub-ID Tracking for Granular Analytics

Sub-IDs are additional tracking parameters that publishers can append to their offerwall URLs to segment traffic sources:

• sub1 — Traffic source (e.g., "homepage", "email", "push")
• sub2 — Creative variant (e.g., "banner_a", "native_card")
• sub3 — User segment (e.g., "new_users", "power_users")
• sub4 — Custom dimension (e.g., country, device type)

These sub-IDs flow through the postback chain and appear in your publisher dashboard analytics, enabling granular ROI analysis by traffic source, creative, and user cohort.

VeloxOffer's Automated Retry Queue

Network timeouts happen. Servers go down. To ensure no conversion is ever lost, VeloxOffer implements a 72-hour automated retry queue:

1. If an advertiser's postback fails to deliver, it's queued for retry.
2. Retries follow an exponential backoff schedule: 30s → 2m → 15m → 1h → 6h → 24h.
3. Each retry attempt is logged with full HTTP response details.
4. After 72 hours of failures, the postback is flagged for manual review.

Real-Time Postback Monitoring

VeloxOffer's Signal Intelligence dashboard provides real-time visibility into every postback received and sent. Publishers can inspect individual signals, verify parameter pass-through, and diagnose tracking issues instantly.

Key Takeaways

• Always use S2S postbacks instead of pixel tracking for reliable attribution
• Leverage sub-ID parameters for granular traffic source analysis
• Trust VeloxOffer's 72-hour retry queue to handle transient failures
• Monitor your postback health in the Signal Intelligence dashboard