Login to download the latest version of Mint and your favorite Pepper, purchase additional licenses, or post in the Forum. Don't have an account? Create one!

In Partnership with Media Temple

Mint Forum

Outbound Links Not Showing Correct Data

Hi Shaun (and everyone)

As per your request.. I’ve just started a new troubleshooting thread for my problems with Outbound links.

My Outbound links do record the links clicked on but unfortunately, they seem to be quite inaccurate.

For example, the stats show that a certain link has been clicked on for over 1,000 times in a 48 hour period but the page where the link is placed hasn’t even been accessed by more than 200 visitors in the same timeframe so that’s just impossible.

Some of other link stats are similarly jumbled up.

I’m running the latest Mint and default pepper installs… no other additional peppers.

Can anyone help?

Shaun Inman
Mint/Pepper Developer
Posted on Aug 31, '07 at 05:05 pm

Thanks autorave (I deleted your other post). Which page and link seem to be exhibiting this behavior?

Shaun,

I can’t really pin down the specific page and link which is faulty because it seems to be randomized.

I can however say for sure that the first or top link for each time frame (past hour to 48 hours) seems to be the most inaccurate. For example, Mint shows me that a specific link was clicked on for 455 times in the last 24 hours (this was listed as the first/top result).

However, that’s not possible because the page has been accessed last than 10 times in the last 24 hours. The same thing goes for the other top links for each time frame.

I can’t confirm if the rest of the links are showing accurate results as well but I do know that they seem to be quite reasonable.. i.e. the number of link clicks fall within the number of times the page was viewed (according to the Pages frame in Mint).

One more problem.. after clicking around on each time frame, I’ve noticed that the top links with the most clicks change randomly. Just a minute ago it was showing LINK A and when I’ve clicked around and returned to the same timeframe.. the top link with the most click is showing LINK B instead now. The number of clicks however.. strangely remains the same.

Hopefully all this makes sense..and do let me know if you know a fix for this… thanks!

Shaun Inman
Mint/Pepper Developer
Posted on Sep 04, '07 at 09:58 am

That almost sounds like a unsigned v. signed checksum problem. Your server is 64-bit so the _checksum columns in your mint_outbound table should be UNSIGNED (they would be SIGNED on a 32-bit server). Can you check (using a tool like PhpMyAdmin) if that is correct?

(This post originally had the signs reversed. It has been updated to avoid future confusion.)

mitchoyoshitaka
Third-Party Pepper Developer
Posted on Dec 30, '07 at 07:34 am

Glad to have found this post—I’ve been seeing the same issue lately, I believe, and was wondering… the observation below clarifies the issue:

Right now: if I check the 24h timeframe, my top outbound link (let’s call it A) has 327 hits. Fine.

Now I check 48h. Another outbound link (B) is at top with 333 hits. A does not even show up in the 48h list, and the second place is a measly 20 hits.

Now I check “show all.” There’s another link at top with a presumed 401 hits (C—btw, there’s no way this link has that many hits) and the second place is 42 hits. A and B aren’t even on this list.

In conclusion: it seems like, often, (a) the first-place value is ridiculously inflated, for some reason, and/or (b) the values are just completely out of whack.

Any advice?

mitchoyoshitaka
Third-Party Pepper Developer
Posted on Dec 30, '07 at 07:38 am

Hm, I just checked: I’m on a 64 bit server, yet my _checksum col’s are unsigned. Is that the issue??

Shaun Inman
Mint/Pepper Developer
Posted on Dec 31, '07 at 10:29 am

Did you recently upgrade your server from 32-bit? Mint is smart enough to change the column depending on the server during installation but not smart enough to detect when its been moved from one architecture to another.

mitchoyoshitaka
Third-Party Pepper Developer
Posted on Jan 01, '08 at 04:08 am

No, my server’s always been 64bit. I cleared the table so we’ll see what happens.

Do you think there are other tables that I should check the settings for if the 64bit check didn’t seem to work?

mitchoyoshitaka
Third-Party Pepper Developer
Posted on Jan 01, '08 at 11:35 pm

Alright Shaun, that didn’t work:

I currently have, for example, site A with 11 hits as first place in the 8 hour view. Fine. Now in show all, site B is at first place with 17 hits. Second place is some other site (C) with 6 hits. Something is clearly wrong.

Any other things I should check out??

Shaun Inman
Mint/Pepper Developer
Posted on Jan 02, '08 at 12:25 pm

You changed the sign and then emptied the table? Or just cleared the table? Have you tried uninstalling and reinstalling the Outbound Pepper?

mitchoyoshitaka
Third-Party Pepper Developer
Posted on Jan 02, '08 at 11:47 pm

I changed the sign and emptied the table… but now I’ve emptied it, uninstalled, and reinstalled. We’ll see what happens…

mitchoyoshitaka
Third-Party Pepper Developer
Posted on Jan 02, '08 at 11:56 pm

I noticed after reinstalling that the checksums are all signed now… we’ll see if this works now…

mitchoyoshitaka
Third-Party Pepper Developer
Posted on Jan 03, '08 at 10:06 am

Nope—still not working. In the 4h view, site A has 7 hits… in the show all, the top hit is 8 hits, not site A, and second place has 1 hit…

Shaun Inman
Mint/Pepper Developer
Posted on Jan 04, '08 at 09:54 am

Which “Group by/display” setting are you using with Outbound?

mitchoyoshitaka
Third-Party Pepper Developer
Posted on Jan 05, '08 at 10:24 am

“Link text and launching page”… should I try the other setting?

JSSP
Minted
Posted on May 30, '09 at 05:19 pm

I have exactly the same issue as mitchoyoshitaka illustrated above with the following example.

“I currently have, for example, site A with 11 hits as first place in the 8 hour view. Fine. Now in show all, site B is at first place with 17 hits. Second place is some other site (C) with 6 hits. Something is clearly wrong.”

Did this ever get resolved?

My server is 32 bit and the _checksum columns are SIGNED (Attributes column in phpMyAdmin is blank, id and dt are UNSIGNED)

Shaun Inman
Mint/Pepper Developer
Posted on Jun 01, '09 at 10:45 am

Mitcho, your server is now reporting as 32bit. 32bit servers should have SIGNED _checksum columns.

JSSP, your server is 64bit (hover over the Mint version number in the footer) so _checksum columns should be UNSIGNED.

JSSP
Minted
Posted on Jun 01, '09 at 02:31 pm

Thanks for the reply Shaun. That’s strange because my hosting provider told me the mySQL server was 32 bit. Also the pepper installed itself with the _checksum columns as signed. Anyway, I’ll change the _checksum columns to unsigned and see what happens, and I’ll report back here.

Shaun Inman
Mint/Pepper Developer
Posted on Jun 02, '09 at 09:38 am

The checksum confusion is caused by the server running PHP, not the MySQL database server. Whenever I or Mint refer to the architecture of a server, we are always referring to the web server, not the database server.

You must be logged in to reply. Login above or create an account