9 {{ upvoteCount | shortNum }}
9 {{ upvoteCount | shortNum }}

Prosper202 and PeerFly Campaign Woes

by thedudeness
7 replies
Hi guys,

I've set up a 7search campaign with prosper202 on my own domain for tracking, but I'm having some problems. I followed LukePeerFly's tutorial to the letter and got it to work, except for when someone clicks on the link!


The problem I am having is when passing variables back from prosper202 to peerfly. It seems the s3 field (subid 3) is spitting out a value that PeerFly does not like, which is weird because I am following the tutorials and using ###RID$### as my s3 id. I get an 403 error every time I click the link if it has that variable, and when I remove it the link works just fine. Here is an example of the web address I get when I recieve the 403 error :

http://trkur.com/trk?o=____&p=____&s...#&s3=Z:5004743

Anyone have any idea what I am doing wrong? I've searched for awhile and haven't found any answers, so I am just leaving the ###RID### variable out for now until I can fix it. Thanks!
#7search #campaign #prosper202 #woes
  • Profile picture of the author ChrisBa
    What is the Z:5004743?
    Can you avoid the :?
    Signature
    {{ DiscussionBoard.errors[8160161].message }}
    • Profile picture of the author thedudeness
      Originally Posted by ChrisBa View Post

      What is the Z:5004743?
      Can you avoid the :?
      Hi ChrisBa,

      The Z:5004743 is what prosper202 passes to the PeerFly tracker URL. I think either 7Search creates that variable or prosper202 takes the Referrer ID from 7Search and changes it before it passes it to PeerFly.
      {{ DiscussionBoard.errors[8160189].message }}
      • Profile picture of the author LukePeerFly
        Originally Posted by thedudeness View Post

        Hi ChrisBa,

        The Z:5004743 is what prosper202 passes to the PeerFly tracker URL. I think either 7Search creates that variable or prosper202 takes the Referrer ID from 7Search and changes it before it passes it to PeerFly.
        A security measure we took has caused some of the special characters in SubIDs to cause the error you're seeing. We're working to get these issues fixed and will have it done very soon.

        That being said, if you simply pass [[subid]] into your first SubID (s1) of your PeerFly link and ignore [[c1]] and [[c2]] you can still view those variables on Prosper202 (the whole point of Prosper202)
        Signature

        ^ My Blog

        Are you an affiliate that runs PPV advertising? You need my PPV target scraper!
        Have a Facebook Page? FPTraffic, manages over 1,000,000,000 (BILLION) Likes! Check it out :)
        {{ DiscussionBoard.errors[8172566].message }}
        • Profile picture of the author gazelle7
          Originally Posted by LukePeerFly View Post

          A security measure we took has caused some of the special characters in SubIDs to cause the error you're seeing. We're working to get these issues fixed and will have it done very soon.

          That being said, if you simply pass [[subid]] into your first SubID (s1) of your PeerFly link and ignore [[c1]] and [[c2]] you can still view those variables on Prosper202 (the whole point of Prosper202)
          Luke are you still having the problem with the special characters?
          {{ DiscussionBoard.errors[8390158].message }}
          • Profile picture of the author LukePeerFly
            Originally Posted by gazelle7 View Post

            Luke are you still having the problem with the special characters?
            We've turned off some of the restrictions. For example, : should work fine now.
            Signature

            ^ My Blog

            Are you an affiliate that runs PPV advertising? You need my PPV target scraper!
            Have a Facebook Page? FPTraffic, manages over 1,000,000,000 (BILLION) Likes! Check it out :)
            {{ DiscussionBoard.errors[8392397].message }}
            • Profile picture of the author gazelle7
              For whatever reason my link is still getting a 403 error. If I remove the subid variables my link works fine. It has to be a problem with the variables. I'm using {creativeid:},{age:},{state:}. Any thoughts?
              {{ DiscussionBoard.errors[8392958].message }}
              • Profile picture of the author gazelle7
                It is working now. I find it odd that it wouldn't work yesterday but today it is working. Thanks for the response.
                {{ DiscussionBoard.errors[8392997].message }}

Trending Topics