- This topic is empty.
-
Posts
-
The link should track just fine. It should not matter if it is urlencoded or not. Both urls mean exactly the same thing.
If they don’t track properly, then the aff program just needs a simple piece of code on their end to fix it.
I doubt that anything nefarious is happening here. Just a simple mistake, if anything, that should be corrected immediately.
Quote:If they don’t track properly, then the aff program just needs a simple piece of code on their end to fix it.Not very encouraging if you lost 500 players in a mega promo to dud url’s eh?
I also wonder if the account numbers shouldn’t be partly xxx out for privacy reasons, if one was mine you would be in deep shit.
I DON”T think I saw it mentioned in this post but newbie affs should be aware to use 3rd party click tracking scripts for simple comparison to aff program stats. Reduces the screwability margin to close to zero.
If I didn’t cross reference this info with a good friend of mine I wouldn’t be 100% sure. But when I saw the url it told me unix and I realized it was a bit hackerish. There is good asc and bad this one is a bad. The URL is a very old protocal using pipes and double underscores I ask for what purpose? Can this possible be a mistake? maybe.
No disrespect intended Kwblue an encoded url such as this does matter both urls are very different. The one for Jackpotcity is alarming.
I say again NOT a browser related issue. This will be all I have to say on the matter.
Thanks Deaning you know this stuff!
greek39
Hi Deaning,
well the aff code is mine and the rest is a tester I use (upon checking, I see I did make a mistake in letting them be seen when I posted Trish’s reply, other than that: I dont’ think there were any account #s shown), but that’s not a likely problem anyway.
He’s worked with me before and gets money from me to play so I doubt he’ll be too upset.
that said: as long as the passwords aren’t posted is there really a security issue? If you think there is: I’ll ask him not to use those accounts.
I guess I”ll go ahead and delete them anyway. thanks for the heads up. my mistake.
______________________
Here is what someone has told me about all this who is much smarter than myself.
When I trace the http stream through the linking code with the pipe’s I get this (you can just skip the technobabble if you want, I’ve summed it up near the bottom:
http://www.jackpotcity.com/rfb_sa94__s||aff27237__b=sa94–04:06:11– http://www.jackpotcity.com/rfb_sa94__s
=> `rfb_sa94__s’
Resolving http://www.jackpotcity.com… 66.212.235.213
Connecting to http://www.jackpotcity.com[66.212.235.213]:80… connected.
HTTP request sent, awaiting response…
1 HTTP/1.1 302 Object moved
2 Connection: keep-alive
3 Date: Thu, 11 Jan 2007 04:14:01 GMT
4 Server: Microsoft-IIS/6.0
5 X-Powered-By: ASP.NET
6 Location: http://www.jackpotcity.com/index.asp?trd=1&s
7 Content-Length: 169
8 Content-Type: text/html
9 Set-Cookie: ASPSESSIONIDCQSSRADQ=GNBLJBDCKDIENPEBGIBGEBOI; path=/
10 Cache-control: private
Location: http://www.jackpotcity.com/index.asp?trd=1&s [following]
–04:06:16– http://www.jackpotcity.com/index.asp?trd=1&s
=> `index.asp?trd=1&s’
Connecting to http://www.jackpotcity.com[66.212.235.213]:80… connected.
HTTP request sent, awaiting response…
1 HTTP/1.1 302 Object moved
2 Connection: keep-alive
3 Date: Thu, 11 Jan 2007 04:14:02 GMT
4 Server: Microsoft-IIS/6.0
5 X-Powered-By: ASP.NET
6 Location: http://www.jackpotcity.com/index.asp?VT=285532211&trd=1&s
7 Content-Length: 186
8 Content-Type: text/html
9 Set-Cookie: CV=cv=us&vt=285532211&State=moskva&cont=ru&start=2007%2F01%2F11+06%3A14%3A02+AM; path=/
10 Set-Cookie: FVT=2007%2F01%2F11+06%3A14%3A02+AM; expires=Sat, 07-Jan-2017 22:00:00 GMT; path=/
********** 11 Set-Cookie: LSS=JPCTYPEINTRAFFIC; expires=Sat, 07-Jan-2017 22:00:00 GMT; path=/
12 Set-Cookie: FCVR=1071999795; expires=Sat, 07-Jan-2017 22:00:00 GMT; path=/
13 Cache-control: private
Location: http://www.jackpotcity.com/index.asp?VT=285532211&trd=1&s [following]
–04:06:16– http://www.jackpotcity.com/index.asp?VT=285532211&trd=1&s
=> `index.asp?VT=285532211&trd=1&s’
Connecting to http://www.jackpotcity.com[66.212.235.213]:80… connected.
HTTP request sent, awaiting response…
1 HTTP/1.1 200 OK
2 Connection: keep-alive
3 Date: Thu, 11 Jan 2007 04:14:02 GMT
4 Server: Microsoft-IIS/6.0
5 X-Powered-By: ASP.NET
6 Content-Length: 20469
7 Content-Type: text/html
8 Cache-control: privateI know that might not mean much to you, but bare with me… I’ll explain.
Now, here’s the http stream for this linking code:
http://www.jackpotcity.com/index.asp?s=aff27237–04:59:08– http://www.jackpotcity.com/index.asp?s=aff27237
=> `index.asp?s=aff27237′
Resolving http://www.jackpotcity.com… 66.212.235.213
Connecting to http://www.jackpotcity.com[66.212.235.213]:80… connected.
HTTP request sent, awaiting response…
1 HTTP/1.1 302 Object moved
2 Connection: keep-alive
3 Date: Thu, 11 Jan 2007 05:06:54 GMT
4 Server: Microsoft-IIS/6.0
5 X-Powered-By: ASP.NET
6 Location: http://www.jackpotcity.com/index.asp?VT=285532758&s=aff27237
7 Content-Length: 185
8 Content-Type: text/html
9 Set-Cookie: CV=cv=us&vt=285532758&State=moskva&cont=ru&start=2007%2F01%2F11+07%3A06%3A54+AM; path=/
10 Set-Cookie: FVT=2007%2F01%2F11+07%3A06%3A54+AM; expires=Sat, 07-Jan-2017 22:00:00 GMT; path=/
********** 11 Set-Cookie: LSS=aff27237; expires=Sat, 07-Jan-2017 22:00:00 GMT; path=/
12 Set-Cookie: FCVR=1072009553; expires=Sat, 07-Jan-2017 22:00:00 GMT; path=/
13 Set-Cookie: ASPSESSIONIDQATRRABS=IIAPOPCCOFGPEADCKJLFEDKP; path=/
14 Cache-control: private
Location: http://www.jackpotcity.com/index.asp?VT=285532758&s=aff27237 [following]
–04:59:09– http://www.jackpotcity.com/index.asp?VT=285532758&s=aff27237
=> `index.asp?VT=285532758&s=aff27237′
Connecting to http://www.jackpotcity.com[66.212.235.213]:80… connected.
HTTP request sent, awaiting response…
1 HTTP/1.1 200 OK
2 Connection: keep-alive
3 Date: Thu, 11 Jan 2007 05:06:55 GMT
4 Server: Microsoft-IIS/6.0
5 X-Powered-By: ASP.NET
6 Content-Length: 21352
7 Content-Type: text/html
8 Cache-control: privateOk, now look for the two lines that I’ve prefixed with: **********
I’ve copy and pasted it here for easy reference:http://www.jackpotcity.com/rfb_sa94__s||aff27237__b=sa94
11 Set-Cookie: LSS=JPCTYPEINTRAFFIC; expires=Sat, 07-Jan-2017 22:00:00 GMT; path=/http://www.jackpotcity.com/index.asp?s=aff27237
11 Set-Cookie: LSS=aff27237; expires=Sat, 07-Jan-2017 22:00:00 GMT; path=/I’m sure you can see the first one seems to have tagged your referral as ‘TYPE IN TRAFFIC’…
and the second one has tagged the referral to: aff27237So, that would be pretty concerning to me as I can’t find any place in the http stream for the pipe linking code that associates the referral to your affiliate account.
… on the issue of url encoding and invalid characters. As Ted said, it really should be fine. You can use any character in a URL as long as it can be URL Encoded. The whole point of url encoding something is so that there will NOT be a mistake. If a ‘funny’ character is NOT url encoded that’s typically when the side effects and other mishaps occur. I guess the point I’m trying to make is that I don’t think the tracking is failing only because they’ve used pipe’s in the linking code. If they have an inexperienced programmer building the tracking, then it would be possible that they don’t know how to handle the url encoded parameters, but that would be an extremely rookie mistake… so not sure why the issue.
So what’s it all mean??? … my two cents is that the first linking code with the pipe does look like the tracking is failing. I just don’t think it’s because of the pipe… but rather bad programming.
Hi bb1webs
Your answer to the || (Pipe) issue in our URLs:
%7c is the HEX value of a PIPE. “|”
%40 for instance is the HEX value of the @ sign.In order for data to keep it’s value as it moves across the internet it converts the PIPE into %7c so that all platforms (per se) understand that they are now dealing with a PIPE and therefore not get confused.
To conclude:
A PIPE and %7c are exactly the same thing. No tracking is affected AT ALL as there is nothing wrong with the URL.
For instance and for example:
Type | into Google. Look at the URL string in the Address bar. It now ends with your %7c.
The previous post explains the tracking very well. The comments I would like to make is the affiliate tracking overrides all references to LSS=JPCTYPEINTRAFFIC in our back end. In other words we get both strings and the affiliate tracking overrides TYPEINTRAFFIC.
Getting to the question about the players and who they belong to, can you please send me the account numbers to give you more detail.
Thanks
WayneQuote:I’m sure you can see the first one seems to have tagged your referral as ‘TYPE IN TRAFFIC’…
and the second one has tagged the referral to: aff27237So, that would be pretty concerning to me as I can’t find any place in the http stream for the pipe linking code that associates the referral to your affiliate account.
… on the issue of url encoding and invalid characters. As Ted said, it really should be fine. You can use any character in a URL as long as it can be URL Encoded. The whole point of url encoding something is so that there will NOT be a mistake. If a ‘funny’ character is NOT url encoded that’s typically when the side effects and other mishaps occur. I guess the point I’m trying to make is that I don’t think the tracking is failing only because they’ve used pipe’s in the linking code. If they have an inexperienced programmer building the tracking, then it would be possible that they don’t know how to handle the url encoded parameters, but that would be an extremely rookie mistake… so not sure why the issue.
So what’s it all mean??? … my two cents is that the first linking code with the pipe does look like the tracking is failing. I just don’t think it’s because of the pipe… but rather bad programming.
I bet you a gazillion bucks that TYPE IN TRAFFIC goes right to the whores door and the pimp don’t get a cent!
OK, bit of a joke there, we are not whores and pimps, but there is a lot of change happening on the backend of programs with the rapid advance of technology..how many “You should change your links” emails have you had lately?
How many of you change your links and DON’T CHECK THEM OUT?
Aha, yep I was caught in the same boat, it’ll be cool, just swap and forget. So far I have had to have dialogue with nearly every entitiy after trying simple tracking issues.
Just FYI, Ignore at your peril.
Wayne –
There is simply NO excuse for using the double pipe in a URL. You can provide accurate tracking without pipes. Why in the world, then, do your programmers have to do silly stuff like this? Just what does the double pipe mean to your programmers?
There has to be a limit to this silly nonsense. Wanna use an ampersand? Fine. Wanna use an equals sign? Fine. Question mark? OK. Pound (number) symbol? Only when absolutely necessary.
ANYTHING other than those four characters plus alphanumeric characters, slashes, and a colon are not necessary at all for any reason as far as the Web is concerned.
Wayne wrote:Hi bb1websYour answer to the || (Pipe) issue in our URLs:
%7c is the HEX value of a PIPE. “|”
%40 for instance is the HEX value of the @ sign.In order for data to keep it’s value as it moves across the internet it converts the PIPE into %7c so that all platforms (per se) understand that they are now dealing with a PIPE and therefore not get confused.
To conclude:
A PIPE and %7c are exactly the same thing. No tracking is affected AT ALL as there is nothing wrong with the URL.
For instance and for example:
Type | into Google. Look at the URL string in the Address bar. It now ends with your %7c.
The previous post explains the tracking very well. The comments I would like to make is the affiliate tracking overrides all references to LSS=JPCTYPEINTRAFFIC in our back end. In other words we get both strings and the affiliate tracking overrides TYPEINTRAFFIC.
Getting to the question about the players and who they belong to, can you please send me the account numbers to give you more detail.
Thanks
WayneYou are 100% correct spearmaster. I would add also, double pipes cause data loss as the packets travel. Simply TCP failure of information. If I had any doubt I would say so.
greek39
deaning wrote:I DON”T think I saw it mentioned in this post but newbie affs should be aware to use 3rd party click tracking scripts for simple comparison to aff program stats. Reduces the screwability margin to close to zero.How do these work? Can you suggest a product? Thanks.
greek39 wrote:You are 100% correct spearmaster. I would add also, double pipes cause data loss as the packets travel. Simply TCP failure of information. If I had any doubt I would say so.greek39
Greek, I’m sure you mean well, but a very high percentage of the stuff you say these days is complete and utter nonsense. I hope noone is taking you seriously.
BlackjackInfo wrote:Greek, I’m sure you mean well, but a very high percentage of the stuff you say these days is complete and utter nonsense. I hope noone is taking you seriously.Nonsense? perhaps from your perspective. I have been accused of this before from only webmasters. I can assure you if we met one on one you would think different. What would you have me do write 10 pages explaining exactly how things work.
Perhaps I will just uncloak myself and run around naked. Maybe I should spew out so much information others can use it in undisireable ways. Why is it non-sense? can you provide a better explanation? I tend to say what only needs to be said. I have no desire in explaining all the technicle aspects of things. Maybe I should find out more by doing a silly google search for it.
I can give you a link to voice your concerns. After all I only get this sort of feedback from webmasters. Come into my world and after you leave then call what I say is “nonsense”.
Maybe CAP would be better off if you are saying my posts “nonsense”. Would this make you happy?
I won’t be back until you explain to me everything there is to know about packet delivery. Just google it seeing this would be your likely source. Should take roughly 15 pages and about six months to complete.
Good day
greek39:baaa:
Greek,
I have no idea whether your posts are nonsense or not (knowing you – I suspect that they’re not nonsense) but certainly they are full of gobbledegook – that is to say jargon that is only familiar to a specialised few.
If you want to make a statement – then please take the time to phrase it in term that “webmasters” will understand – a good communicator can move between different interest groups. After all this is a webmaster board.
It really should only take a couple of paragraphs to explain why || causes “data loss” … as it is a specific example.
—-
I was personally VERY surprised to read that “double pipes” or “||” causes data loss as the packets travel …
As I would have expected the message data to be well protected inside the data packets and cannot understand how any “application” data or any combination of characters can possibly interfere with the transport layer is a serious communication protocol …
:lookarounMind you – I’m an old school computer engineer – and dealt with serious networks with secure layers and encryption – and have never done any reading on the structure or idiosyncracies of the internet.
:tongue:TheGooner wrote:As I would have expected the message data to be well protected inside the data packets and cannot understand how any “application” data or any combination of characters can possibly interfere with the transport layer is a serious communication protocol …It is, and Ken is correct – Greek’s statements have little basis in reality.
Rest assured, a pipe character is just a regular old set of 8 bits, and it’ll be delivered just as reliably as any other set of 8 bits, whether you send ’em in pairs or solo. |||||||||||||| wheeee!!! Did they all get there?
BlackjackInfo wrote:Rest assured, a pipe character is just a regular old set of 8 bits, and it’ll be delivered just as reliably as any other set of 8 bits, whether you send ’em in pairs or solo. |||||||||||||| wheeee!!! Did they all get there?
OK .. that actually made me laugh out loud …
:tongue:I’m such a computer nerd sometimes …
:hattip:
