Root question: How does the callback code know what subid to update in p202 if many networks use a different code like &subid=, &s=, &track= etc, does it just update by IP like Ok tell this campaign it just got a sale with this IP, then 202 sees the IP and says X keyword converted! is that it?

Long question:

I am trying to use p202 with this site i host that has an order form and sends the order data through to an order url all the networks sites use to send the order data to.

the person goes from ppc to the main page (which has javascript). Then they click order on the main page and im having them go through an intermediary go.php page that will call 202 to fetch the landing page which is just the order page.

I put in P202 the affiliate url as the order page url with &subid= on it, i grab the $_REQUEST['subid'] on that order page and since it has an order form on it, i just pass the subid through a hidden input tag. There is this other page the order form page posts the user's order data to that just takes all the data and sends it to the network's order system page which on their end updates my aff stats.

I got them to add the postback code on a page that Im guessing the first network page redirects to (dont know if it sends the data too.

But my question is, finally, how does this 202 PB code know what the subid is to update my p202 if it does not have access to the variable holding it directly? if i just add &subid=$subid in the data thats sent to the networks page, how does the 202 PB code know what variable holds the subid?

Mike

apparently the pb code advertiser places on confirmation page just checks users HD cookies and gets the subid for $202outbound whatever and tells 202 which campaign and which subid converted.

Well the postback url takes in the subid, networks like NEVERBLUEADS will hit the postback url and allow you to include the subid, so it works easy.

It sounds like the easiest way to do it is, will they just let you place the tracking pixel?

Hi Wes,

Yes the postback url is no problem, I was just asking how the pixel works, April says it will just look for the 202outbound php variable in the users cookie and update the campaign with the subid.

on another note, a question about google web optimizer (GWO). when i start a campaign i make some 202 text ads and get my Text links for PPC ads.

I make say two 202 landing pages to rotate in GWO, one for index.php and one for index2.php. In index.php I will send clicks to say go.php?v=1 and index2.php?v=2 the go.php uses a php switch statement and calls the 202 Get LP code for that landing page so i can see which lan page converts the best etc in 202 LP screen.

I will send all PPC clicks through say 1 text link I base off the first index.php landing page (which is just the index.php).

So i test my pages and find index2.php is the winner, so i make index2.php into index.php, make a nu variation and create two new 202 landing pages. I add the codes to my new index.php, index2.php and go.php, make the go.php?v=X right and setup GWO.

My question is, should everything track correctly doing this over and over? granted i end up with a long list of landing pages in LP screen, but I get to see page CR and CTR and know EXACTLY whats happenning (if this is working 100%), I seem to see the numbers but there are possibly a few anomalies like a lead showing up for a past landing page name, i just name them like 819index1 and 819index2 and use the same urls over and over (www.domain.com/index.php and index2.php). and I know im sending traffic through the latest LP codes...

I dont want to make new text links off the latest index.php LP code every time i want to run a test. do you see any problems with this? Any reason for possible data loss/confusion in the system?

Yeah you should be fine, ultimately your just split testing landing page using P202, and swapping them with more landing pages, however you do it thats fine, it shouldn't error. That works ok, I mean no reason it wouldn't work!

Sure about the pixel your correct, when visitor hits your page we COOKIE them, and then when the user completes an offer the pixel calls the t202 server, and sees if that users was cookied, and if so, it knows that user created a lead.

Ok Excellent Wes, but when I swap new landing pages to test new ones, I get clicks and leads showing up for them, great, but I also get leads on older landing page names I have since swapped.

This is mainly for sales, not leads, do you think its just the person with the cookie based on the old landing page coming back now and buying? (if that is not explained correctly let me know if that makes sense)

We are actually going to adjust the post-back url, to make it globally work for anything. So if u change the landing page right now it doesn't matter, as long as the post-back url is attached to the specific campaign it will still track.

The postback urls are attached to a specific campaign, not a landing page.