Copeac + p202

[profitaddiction]

Every other network I'm with has tracked flawlessly, but I've had consistent problems with Copeac.

Does anybody else have issues with subIDs failing to appear/incorrectly appearing in Copeac? If so, do you know what caused it?

 

[BigWill]

why not just ask your AM?

But really.. you use subid1 or o

 

[profitaddiction]

I've asked my AM and he said everything is tracking fine on their end. I use other DT networks and they track 100% flawlessly.

I use subID1=

 

[JoshTodd]

Don't use subid1=, just put your subid after the o=. Then you pull up your stats by going to the stats page, then selecting "Download Optional Info". This is much more reliable than subid1=. (I used to be an AM at a DT network).

 

[profitaddiction]

Thanks Josh, I'll try that

 

[JoshTodd]

Sorry just revised it. Try putting it after o=

 

[profitaddiction]

haha I was just looking and about to post: "wtf there is no slash"

Thanks, I'll try it after the o=

 

[JoshTodd]

Some networks use the encrypted links, like affiliate.com, they use hxxp://login.tracking101.com/ez/asdlkfjasldk/SUBIDGOESHERE. Just FYI. lol.

 

[kingrock]

I'll try it p202

 

[Sohan]

Yeah, o= works. But I've heard copeac having problems with pixels firing, but nothing first hand so don't know about that.

Another option is go in for a link trust network or a hitpath one. Some of the big dogs use those platforms too.

 

[fcreature]

I used to have problems with their sub ID's too. Just stop using the links they give you, and change the o= as other people mentioned here. That fixes it up.

 

[profitaddiction]

Thanks all - Pretty frustrating and of course when I'm testing an offer, the first few leads are the ones that don't track so I sit there with a thumb up my ass.

 

[goddfadda]

An important step that I didn't see mentioned - you have to move the &o= to the END of the tracking url.

p202 just appends the sub id to the end of your tracking string, so it is imperative that you put the &o= last. It will not effect tracking, just allow the 'o' variable to be set to the sub ID value during a click.

Yet another reason why I don't like direct track.

 

[zimok]

An important step that I didn't see mentioned - you have to move the &o= to the END of the tracking url.

p202 just appends the sub id to the end of your tracking string, so it is imperative that you put the &o= last. It will not effect tracking, just allow the 'o' variable to be set to the sub ID value during a click.

Yet another reason why I don't like direct track.

I didn't know this was mandatory, just did it out of habit since I saw Wes's training videos.. nice to know, thanks

 

[megler]

An important step that I didn't see mentioned - you have to move the &o= to the END of the tracking url.

p202 just appends the sub id to the end of your tracking string, so it is imperative that you put the &o= last. It will not effect tracking, just allow the 'o' variable to be set to the sub ID value during a click.

Yet another reason why I don't like direct track.

So my link would look like:

http://www.copeaclink.com/secure.asp?e=ckkllapzxlql&d=mypubid&l=0&o=&p=0

where I just removed all of the subid=1,2,3 etc crap?

 

[redmonkey]

on DT networks, i've found optionalInfo( &o= )is the most accurate one. And it supports all kinds of DT system.

 

[profitaddiction]

So my link would look like:

http://www.copeaclink.com/secure.asp?e=ckkllapzxlql&d=mypubid&l=0&o=&p=0

where I just removed all of the subid=1,2,3 etc crap?

I think it should be like this:

http://www.copeaclink.com/secure.asp?e=ckkllapzxlql&d=mypubid&l=0&o=

That's what I've gathered at least