Skip to main content

RedTrack Integration

RedTrack is an ad tracking and conversion attribution platform. This guide shows how to integrate RedTrack with Pushnami for automatic conversion tracking.

Overview​

Integrating RedTrack with Pushnami allows you to:

  • Centralize tracking for all your traffic sources
  • Automatically attribute conversions to Pushnami campaigns
  • Use RedTrack's optimization features with Pushnami data

Setup Guide​

Step 1: Add Pushnami as a Traffic Source​

  1. In RedTrack, go to Tools → Traffic Sources

  2. Click + New from template or create custom

  3. Configure the traffic source:

    • Name: Pushnami
    • Postback URL: Leave blank for now (we'll set this in the campaign)

  4. Add these parameters:

Parameter NameParameter TagPushnami Macro
Click ID{clickid}<<conversion_id>>
Source{source}{{=data.adsourceid}}
Campaign{campaign}{{=data.adcampaignid}}
  1. Save the traffic source

Step 2: Create a Campaign in RedTrack​

  1. Go to Campaigns → + Add new
  2. Select "Pushnami" as your traffic source
  3. Configure your offer and landing page
  4. Copy your campaign tracking URL

Use your RedTrack campaign URL with Pushnami macros:

https://yourtracker.redtrack.io/click?campaign_id=abc123&clickid=<<conversion_id>>&source={{=data.adsourceid}}&campaign={{=data.adcampaignid}}

Step 4: Set Up the Postback​

  1. In your RedTrack campaign, go to S2S Postback

  2. Click + Add postback

  3. Configure:

    • Postback URL:
    https://revtrc-api.pushnami.com/convert?t={clickid}&v={payout}
    • Method: GET
    • Fire on: All conversions (or specific types)

  4. Save the postback

Parameter Mapping​

RedTrack TokenPushnami ParameterDescription
{clickid}tOriginal Pushnami conversion ID
{payout}vConversion value
{revenue}vAlternative revenue token

Advanced Configuration​

Passing Cost Data​

Include Pushnami cost in your tracking for ROI calculations:

https://yourtracker.redtrack.io/click?campaign_id=abc123&clickid=<<conversion_id>>&cost=<<ad_cost>>

Geographic Data​

Pass location data to RedTrack for geo reporting:

https://yourtracker.redtrack.io/click?campaign_id=abc123&clickid=<<conversion_id>>&country={{=data.dcountry}}&city={{=data.dcity}}

Device Tracking​

Include device information:

https://yourtracker.redtrack.io/click?campaign_id=abc123&clickid=<<conversion_id>>&device={{=data.ddevice}}

Multiple Conversion Events​

RedTrack supports multiple conversion types. Configure separate postbacks for each:

Standard conversion:

https://revtrc-api.pushnami.com/convert?t={clickid}&v={payout}

Upsell/secondary conversion:

https://revtrc-api.pushnami.com/convert?t={clickid}&v={revenue}

Complete Flow​

1. User clicks Pushnami notification
         ↓
2. Pushnami appends <<conversion_id>> to URL
         ↓
3. RedTrack receives click with clickid parameter
         ↓
4. RedTrack redirects to landing page
         ↓
5. User completes conversion
         ↓
6. Your server/pixel notifies RedTrack
         ↓
7. RedTrack fires postback to Pushnami
         ↓
8. Conversion recorded in Pushnami dashboard

Testing Your Integration​

  1. Generate a test click - Click through your Pushnami campaign
  2. Check RedTrack click log - Verify the clickid is populated
  3. Fire a test conversion - Use RedTrack's test conversion feature
  4. Verify postback - Check RedTrack's postback log for 200 response
  5. Confirm in Pushnami - Verify the conversion appears in your campaign

Troubleshooting​

Click ID Not Passing​

  1. Check URL encoding - Ensure <<conversion_id>> is properly placed in the URL
  2. Verify parameter name - RedTrack expects clickid by default
  3. Check redirect chain - Use a redirect checker to verify parameters persist

Postback Failures​

  1. Check URL format - Ensure no extra spaces or characters
  2. Verify token syntax - Use {clickid} not {{clickid}}
  3. Test manually - Copy a clickid and test the postback URL directly

Duplicate Conversions​

  1. Check postback settings - Ensure you're not firing on multiple events
  2. Review conversion deduplication - RedTrack may fire multiple times for retries

Revenue Discrepancies​

  1. Token mismatch - Verify you're using {payout} or {revenue} correctly
  2. Currency formatting - Values should be numeric without currency symbols