Skip to main content

HitPath Integration

HitPath is an enterprise-grade affiliate tracking platform. This guide explains how to configure HitPath to track Pushnami conversions and fire postbacks automatically.

Overview​

With HitPath integration, you can:

  • Track all Pushnami traffic through HitPath's reporting
  • Automatically fire conversion postbacks to Pushnami
  • Leverage HitPath's advanced attribution features

Setup Guide​

Step 1: Create a Traffic Source in HitPath​

  1. In HitPath, go to Setup → Traffic Sources
  2. Click Add Traffic Source
  3. Name it "Pushnami"
  4. Configure the tracking parameters to capture Pushnami data
  5. Save the traffic source

Step 2: Configure Your Offer​

  1. Navigate to your offer settings in HitPath
  2. Note your tracking link format, typically:
https://yourtracker.hitpath.com/track?c=CAMPAIGN_ID&s=SOURCE_ID

Step 3: Build Your Pushnami URL​

Add Pushnami macros to your HitPath tracking URL:

https://yourtracker.hitpath.com/track?c=CAMPAIGN_ID&s=SOURCE_ID&aff_sub=<<conversion_id>>&aff_sub2={{=data.adsourceid}}&aff_sub3={{=data.adcampaignid}}

Parameter mapping:

  • aff_sub → Pushnami Conversion ID (required for postback)
  • aff_sub2 → Pushnami Source ID
  • aff_sub3 → Pushnami Campaign ID

Step 4: Set Up the Postback URL​

  1. In HitPath, go to your offer or campaign settings
  2. Navigate to Postback URLs or Pixel/Postback section
  3. Add a new server-to-server postback:
https://revtrc-api.pushnami.com/convert?t=[aff_sub]&v=[payout]
  1. Configure the postback to fire on successful conversions
  2. Save your settings

Parameter Reference​

HitPath TokenPushnami ParameterDescription
[aff_sub]tConversion ID for attribution
[payout]vConversion value/payout
[revenue]vAlternative revenue token
note

HitPath uses square brackets [token] for postback tokens. Verify the exact syntax in your HitPath documentation as it may vary by version.

Advanced Configuration​

Including Cost Data​

Track your Pushnami costs in HitPath for ROI analysis:

https://yourtracker.hitpath.com/track?c=CAMPAIGN_ID&aff_sub=<<conversion_id>>&cost=<<ad_cost>>

Geographic Tracking​

Pass location data for geo-based reporting:

https://yourtracker.hitpath.com/track?c=CAMPAIGN_ID&aff_sub=<<conversion_id>>&aff_sub4={{=data.dcountry}}&aff_sub5={{=data.dstate}}

Multiple Conversion Types​

Configure separate postbacks for different conversion events:

Lead conversion:

https://revtrc-api.pushnami.com/convert?t=[aff_sub]

Sale conversion (with value):

https://revtrc-api.pushnami.com/convert?t=[aff_sub]&v=[payout]

Using Custom Sub-IDs​

If aff_sub is already in use, you can use any available sub-ID field:

# Tracking URL with aff_sub4 for conversion ID
https://yourtracker.hitpath.com/track?c=CAMPAIGN_ID&aff_sub4=<<conversion_id>>

# Corresponding postback URL
https://revtrc-api.pushnami.com/convert?t=[aff_sub4]&v=[payout]

Complete Flow​

1. User clicks Pushnami notification
         ↓
2. Redirect to HitPath with aff_sub=<<conversion_id>>
         ↓
3. HitPath records click and redirects to landing page
         ↓
4. User completes conversion
         ↓
5. Conversion fires to HitPath
         ↓
6. HitPath fires postback to Pushnami with [aff_sub]
         ↓
7. Conversion tracked in both platforms

Testing Your Integration​

  1. Generate a test click - Click through your Pushnami campaign
  2. Verify in HitPath - Check the click log for aff_sub value
  3. Fire a test conversion - Complete a conversion or use HitPath's test tools
  4. Check postback logs - Verify HitPath sent the postback successfully
  5. Confirm in Pushnami - Check your campaign for the test conversion

Troubleshooting​

Conversions Not Recording in Pushnami​

  1. Check aff_sub - Verify the conversion ID is passing through in HitPath's click logs
  2. Verify postback URL - Ensure correct syntax: https://revtrc-api.pushnami.com/convert?t=[aff_sub]&v=[payout]
  3. Check postback logs - HitPath shows postback attempts and response codes
  4. Test manually - Copy a conversion ID and test the postback URL in a browser

Missing Conversion Values​

  1. Verify payout token - Ensure [payout] or [revenue] is correctly configured
  2. Check offer settings - Payout must be set in HitPath's offer configuration
  3. Token syntax - Confirm you're using the correct bracket format

Click ID Not Passing​

  1. URL structure - Ensure <<conversion_id>> is properly appended to aff_sub
  2. Encoding issues - Special characters should be URL-encoded
  3. Redirect chain - Use a redirect checker to verify parameters persist

Duplicate Conversions​

  1. Postback settings - Ensure postback fires only once per conversion
  2. Deduplication - Pushnami automatically deduplicates by conversion ID