PariPulse Partner Tracking & Reporting: How It Works in 2026

TL;DR: how PariPulse tracking works

Every PariPulse affiliate link encodes site, ad and tag identifiers (e.g. tag=d_<site_id>m_<ad_id>c_). Sub_id parameters (sub1, sub2, sub3...) let you segment by campaign, creative or geo. Server-to-server (S2S) postback URLs fire on registration, FTD and deposits, feeding events into your tracker. Reporting is real-time in the paripulsepartners.com dashboard with breakdowns by sub_id, geo and campaign.

Anatomy of a PariPulse tracking link

A live affiliate link looks like:

https://refpa00186.com/L?tag=d_<site>_<ad>m_<ad>c_&site=<site>&ad=<ad>&r=<landing>

Where:

• tag is your unique attribution token (PariPulse uses this for postback)
• site is the website identifier for your affiliate account (e.g. 5583325)
• ad is the campaign or creative identifier (e.g. 64497)
• r is the landing-page suffix (e.g. sign-up, promotions/first-deposit)

You can append sub1, sub2 etc. as query parameters: &sub1=summer_promo&sub2=tier1_geo. These flow back to the dashboard and let you segment performance.

Setting up S2S postback

In the affiliate dashboard, the Postback section lets you paste your tracker's postback URL with macros. PariPulse fires the URL when each event occurs:

• Registration — user creates a PariPulse account
• FTD (first-time deposit) — user funds their account for the first time
• Deposit — every subsequent deposit (some programs report only FTD; PariPulse's exact set depends on your tier)

Example postback URL for Voluum:

https://yourtracker.voluum.com/postback?cid={click_id}&payout={payout}&txid={tx_id}

PariPulse replaces the {...} placeholders with the actual event data. Test with a single click before launching at volume — most tracking issues are misconfigured macros.

Sub_id segmentation in practice

Sub_ids are how you'll know which campaigns make money. A simple convention:

• sub1 = traffic source (e.g. seo, fb_ads, telegram)
• sub2 = campaign / creative ID (e.g. cricket_blog_v3, aviator_lander_a)
• sub3 = geo segment (e.g. IN_north, TR_istanbul)

The dashboard's filter lets you group revenue by any sub_id combination. After 30 days you'll see which combinations have the best deposit ratio and adjust spend accordingly.

Tracker integrations: Voluum, Binom, RedTrack

PariPulse Partners supports all major iGaming trackers via standard postback macros. Common integrations:

• Voluum — full S2S support; configure as a 'manual postback' source
• Binom — same; use the offer-level postback URL
• RedTrack — supported; use the offer-level postback URL
• AdsBridge, FunnelFlux, Bemob — supported via custom postback configuration

If you use a custom or in-house tracker, the standard {sub_id}, {click_id}, {payout}, {currency}, {geo}, {event_type} macros are available.

Attribution model: last-click within cookie window

PariPulse uses last-click attribution. The most recent affiliate click that landed before registration and FTD wins the credit. The exact cookie window length isn't published; the affpaying.com listing notes 'Cookie Length: Unknown' — meaning it's set per partner contract rather than universally. Long-tail content sites should ask their account manager for the configured window so you can plan your funnels accordingly.

Common tracking issues

Three issues account for most lost attribution:

1. In-app browsers stripping referrers — Instagram, Telegram and Facebook mobile browsers sometimes strip the tag parameter. Workaround: use a redirect link on your own domain that 302-redirects to the PariPulse URL.
2. Cookie-blocking on iOS Safari — ITP (Intelligent Tracking Prevention) shortens cookie lifetime aggressively. Postback-based attribution helps but isn't perfect.
3. Wrong sub_id encoding — special characters in sub_id values can break attribution. Stick to alphanumeric + underscore.