Impor­tant Note: This issue only affects peo­ple using the Face­book fea­ture known as the Face­book Social Plu­g­ins. The issue is not caused by Omni­ture or Adobe code it is an inher­ent issue caused by the design of the Face­book Social Plu­g­ins.  These are not Omni­ture or Adobe plu­g­ins, so if you are not using these Face­book tools then you do not need to worry.

If your com­pany is using Face­book social plug-ins you might have issues with your ana­lyt­ics data.  Depend­ing on the plug-in, if you don’t take action to fix the issue then you will start to receive an arti­fi­cial infla­tion of face­book refer­ring traf­fic and an increase in pageviews.

Issue:

Some face­book social plug-ins redi­rect when a user inter­acts with the plug-in.  The redi­rect goes to face­book and quickly lands the user back onto your site.  The redi­rect does not pass the refer­rer through so your traf­fic sources report will show that the visit orig­i­nated from face­book and over­write the cor­rect cam­paign or traf­fic source that brought the user to your site.  So your traf­fic sources report­ing will be significantly erroneous.

Plug-ins that may be affected:

  • Activ­ity Feed
  • Rec­om­men­da­tions
  • Like But­ton

Fix:

We have a VISTA solu­tion that will fix the issue for you.  If you are not famil­iar with VISTA solu­tions then all you need to know is the Adobe Engi­neer­ing Ser­vices team will do all the work for you.  You do not need to change any imple­men­ta­tion on your side.  We also have a JavaScript plug-in that will solve the prob­lem as well.

How to get the VISTA solution:

You can go to the Adobe Engi­neer­ing Ser­vices Solu­tion Por­tal and request more infor­ma­tion.  Once you do that we will get the request and respond back to you with the next steps within a few days.  You can also con­tact your Account Man­ager or any one of your con­tacts at Adobe and they should be able to point you in the right direction.

Other posts you might be inter­ested in:

As always, post your com­ments or e-mail me at pearcea (at) adobe​.com.  It is your com­ments and e-mails that keep me post­ing and give me ideas for future posts.

4 comments
Andy
Andy

Keith MacD: In your reply you stated: "There are a few ways to handle this collision, but you could also handle it on the base page by just appending our code to the Facebook onclick function after that function’s call." Could you shed some light on the few ways to handle this situation? Also, could you explain how to append your code the Facebook onclick funtion call?

Keith MacD
Keith MacD

We stumbled across this same problem trying to track FB share button clicks. onClick Custom Link tracking wasn't working out of the box so ClientCare provided JS code to fix the problem: "What is happening here is that your Facebook JS call is hijacking the onclick event and replacing the link's onclick with your own onclick function, which essentially overwrites the Omniture onclick code and causes it to never execute. There are a few ways to handle this collision, but you could also handle it on the base page by just appending our code to the Facebook onclick function after that function's call." This seemed to fix the basic link-tracking problem, but failed as soon as we tried to pass an s.prop in the same call. Still waiting to hear back from ClientCare with a solution to the prop problem.