Decisive to prosper202 link question (12)
So if I'm direct linking a campaign from decisive to my newly installed prosper202 system, what keyword do I pass {{{bidhash}}} back to prosper in?
I currently have it in &c2={{{bidhash}}}. But I think I saw a URL in the forum somewhere showing &subid={{{bidhash}}}
To my great surprise I have everything else working well, thanks in no small part to STM.
Thanks!
You can pass it under anything you like - c1, c2, c3, c4, etc., but not subid as that isn't a key that Prosper202 expects.
Prosper202 generates a subid (a numerical value) for every click and it is this value that you pass to a network, and subsequently pass back to p202 to identify a conversion.
So, you would pass bidhash to p202 using e.g. ...&c3={{{bidhash}}}
In your affiliate link you could now pass the value of c3, using [[c3]], if you want, but would normally just pass the subid number using [[subid]], as this is what you have to communicate back to p202 for a conversion.
The value of c3 now contains the corresponding bidhash that you can pass back to Decisive, to tell them about the same conversion.
Make sense?
@zeno - thanks for the reply.
The subid that prosper202 generates from a link is unique to prosper202 though, and not he same {{{Bidhash}}} that Decisive assigns.
In that case, I can just leave out {{{bidhash}}} from Decisive to prosper, since I'll give F5 the [[subid]] value that proper202 generated for the link.
Is this correct?
If so, I think I'm starting to get it.
Nope you need to pass the bidhash too ( you could pass in on c1 ) so this way you can also see conversions on decisive.
The way it will work when a conversion occurs is :
F5 fires p202 pixel -> p202 pixel fires decisive pixel.
This way you will see conversions on both decisive and the tracker all automatically.
Originally Posted by bbrock32
Hmm. OK. So I'm wrong again.
Let me break this down to small chunks and see where my error is.
1. I grabbed the campaign link from Cake at F5 and added s2=[[subid]] to the end of the URL
2. I created a campaign in Prosper202, and placed that URL in the setup area, link #3"campaigns", like so: http://f5mtrack.com/?a=XXXXXX&c=XXXXXX&s2=[[subid]]
3. Then in prosper202, setup-> #8Get Links, I selected my traffic source and direct link style campaign, and entered {{{bidhash}}} as the c1 parameter.
4. Then I clicked get link, and got a link similar to this: http://someurl.com/tracking202/redir...hp?t202id=XXX&c1={{{bidhash}}}&t202kw=
5. I took the url from step 4 above, and entered it as my campaign link at decisive
So where and how does prosper fire the c1 back to decisive? I realize it would have to be [[c1]] somewhere in prosper202.
Unless....something like this: http://win.crwd.io/convert/[[c1]] goes in the traffic source setup in PROSPER202?
Please tell me I'm not wrong this time...
Bingo.
In the traffic sources setup you can add the third-party postback.
Passing the {{{bidhash}}} regardless is important so, if stuff doesn't work as expected, you can at least manually fire conversions to Decisive. Likewise if you mess up your postback at F5 - as long as you have passed [[subid]] you can upload conversions to p202 > then see what the corresponding bidhashes (c1) are >> reconcile all points.
Whew. Thanks Zeno.
That helps a lot. I kind of see what's going on. Only more testing and driving data will clear it up further for me.
So far after two weeks in AM:
Ran 2 campaigns in 2 geos, Direct link to google play. 3224 clicks with 8 conversions and -93 ROI.
Trashed those as per instructions and have moved to another offer. Approval should come Monday. This time I have prosper and a server for a mobile lander.
Spending the day Monday working angles, then banners, then lander.
So much left to do. Can't wait to get some testing done.
Cheers!
Need some validation from the experts here:
Campaign: App install - direct link
Traffic source: Decisive
Affiliate network: Mundo
Tracker: Self hosted Prosper 202
I noticed I had something wrong yesterday when Mundo's system showed 2 conversions, but P202 and Decisive reports had 0 leads.
Today, I carefully checked all the links between decisive, P202 & Mundo. Here's what I setup for token passing after thinking about it more carefully this morning:
Tracking/postback setup
Decisive to P202 and back:
Decisive link: I'm Passing {{{bidhash}}} to P202 like this: c1={{{bidhash}}}
P202: Passing http://win.crwd.io/convert/[[c1]] back to decisive in case of a conversion.
P202 to Mundo and back
P202: Passing subid1=[[subid]] in campaign direct link back to Mundo. (Mundo stores subid's in "subid1"
Mundo: Postback URL passes token back to P202 as subid=%TRANSACTION_ID%
My question is, am I correct in assuming that there are essentially two loops working to validate conversions?
1. Decisive/P202 uses c1 back and forth where {{{bidhash}}} becomes c1, and in case of a conversion, [[c1]] fires back at Decisive.
2. P202/Mundo where [[subid]] sets "subid1" at Mundo, and in case of conversion mundo fires %TRANSACTION_ID% back at P202 as &subid=.
I don't see any other way to pass {{{bidhash}}} in c1 all the way to mundo and back, other than letting P202 handle the negotiation between systems. Here's hoping my limited mental processes are on the right track.
I'd hate to have to go back to poll dancing for living. Women are so cruel...
Cheers
I just noticed another conversion at Mundo, without the corresponding lead in P202.
In re-reading the post from Zeno, I see that 'subid' isn't a valid field BACK to P202 from Mundo.
I completely agree with you @Zeno However, the post back link I get right from P202 (new version 1.8.4) has &subid= at the end of the postback URL that it gives for tracking.
??????
If anyone is using Mundo & P202 by all means contribute. I'm thoroughly lost here.
Prosper202 expects 'subid' in the postback conversion URL.
It does not expect it in the campaign tracking links.
The two are entirely different. In fact, prosper202 generates a subid number value once someone passes through the tracking link - so it would be nonsensical for a tracking link to expect something that does not yet exist.
Anyway, I don't use Mundo but are you sure %TRANSACTION_ID% is the right token for subid1? Usually networks have subids 1-5 in the form of s1, c1, aff_sub1, subid1, etc. appended to the tracking link.
Typically, the tokens for postbacks are then something similar, e.g. #s1#, {aff_sub1}, %subid1%, etc. Transaction ID is usually something unique generated by the network/advertiser that isn't used for your tracking, but I could be wrong.
Everything else you have set up looks fine apart from that.
What you should do is look at your Mundo stats and find the numerical subids. Can you see them? Can you see that 113, 156 and 189 converted? Or are columns blank? If so, then p202's subid has not been passed to Mundo in the first place.
If they are there, be aware you can simply upload these numbers into p202 (Update tab) to manually add the conversions.
If they are there then the postback didn't work, likely due to the reasons above.
Your third-party postback to Decisive looks fine but I'll be honest - I'm not sure if the STM-modded p202 works well with these last time I checked.
Thankfully, since you have logged these bidhash values, it really is trivial to manually fire them to Decisive (and hopefully they will implement a manual bidhash uploader).
Update:
P202 does take 'subid' as a value. The issue was that %TRANSACTION_ID% was the subid when in fact the correct token is %SUBID1%.
Anyway, I scrapped P202, loaded and setup
I'll will be using
Sorry for the rants above, but I'm sure some of you have felt the same pain.
Onward...
@zeno
As I mentioned above, I disconnected P202 and built out a
Now I can forget about technical issues until data comes in and focus on campaign creatives and landers.
I also added the Mundo tokens as a comment to iAmAtilla's token guide here if anyone needs them.
Home > Questions and Answers > Tracking Questions