Expand my Community achievements bar.

Webinar: Adobe Customer Journey Analytics Product Innovations: A Quarterly Overview. Come learn for the Adobe Analytics Product team who will be covering AJO reporting, Graph-based Stitching, guided analysis for CJA, and more!

Adobe Analytics Image request is not trigerring with Adobe Plugin

Avatar

Community Advisor
Hi Team,



We use  below piece of code for plugins in two different launch property.

We have also used "Common Analytics Plugins" extension also to initialize all the plugins.


In one launch property the Analytics call is trigerring and in another launch property Analytics image is not trigerring.
As soon as we remove the plugin code from extension, the image request starts firing.

Can someone please advise if there is any such known issue with the plugins and website behaviour.







#########################################

/************************** CONFIG SECTION **************************/
/* You may add or alter any code config here. */
s.cookieDomainPeriods="2";
if (document.domain.match(/\./)!=null) s.cookieDomainPeriods=document.domain.split('.').length-1;
s.linkInternalFilters=document.domain;
//Need to be reviewed with new websites using configurations
s.linkLeaveQueryString=false;
s.linkTrackVars="None";
s.linkTrackEvents="None";
s.server=document.domain;
s.version+=".4";

/* Plugins Section */
s.usePlugins=true;
s.execDoPlugins=0;
function s_doPlugins(s) {
s.execDoPlugins++;
_satellite.logger.log("============ s_doPlugins("+s.execDoPlugins+") ====================");
    /* Server Variable for every Call */
    s.linkTrackVars += ",server";
    s.server = document.domain;
    s.eVar4=s.getPreviousValue(s.pageName,'gpv_pn','');
s.prop4="D=v4";
/* Visitor Status */
s.eVar21=s.getNewRepeat(365);
s.prop21="D=v21";
/* Visit Number*/
s.eVar23=s.getVisitNum(365);
s.prop23="D=v23";
    /* Time Parting */
var timeVar=s.getTimeParting('Etc/GMT-2');
timeVar=timeVar.split('|');
today=timeVar[0]+'|'+timeVar[1]+'|'+timeVar[2];
s.eVar24=today +"|"+timeVar[2]+"|"+timeVar[3]+"|"+timeVar[4]+"|"+((timeVar[4].match(/^s.*/i)!=null)?"Weekend":"Weekday");
s.prop24="D=v24";
s.prop52=timeVar[3];
}
s.doPlugins = s_doPlugins;

/* ============= DO NOT ALTER ANYTHING BELOW THIS LINE ! ========== */
/* Adobe Consulting Plugin: getTimeParting v6.3 (Customised) (No Prerequisites Needed) */
/* The below code is customised to include to return value similar to getTimeParting plugin version 3.4*/
s.getTimeParting = function getTimeParting(t){var c=t;if("-v"===t)return{plugin:"getTimeParting",version:"6.3 (Customised)"};a:{if("undefined"!==typeof window.s_c_il){var a=0;for(var b;a<window.s_c_il.length;a++)if(b=window.s_c_il[a],b._c&&"s_c"===b._c){a=b;break a}}a=void 0}"undefined"!==typeof a&&(a.contextData.getTimeParting="6.3");c=document.documentMode?void 0:c||"Etc/GMT";a=(new Date).toLocaleDateString("en-US",{timeZone:c,second: "numeric",minute:"numeric",hour:"numeric",weekday:"long",day:"2-digit",year:"numeric",month:"2-digit"});a=/([a-zA-Z]+).*?([0-9]+).*?([0-9]+).*?([0-9]+)(.*?)([0-9])(.*)/.exec(a);return a[2]+"|"+a[3]+"|"+a[4]+"|"+a[6]+a[7]+"|"+a[1]};

####################################
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

9 Replies

Avatar

Community Advisor

No immediate issues come to mind.


The fact you use same plugin on 2 different launch properties then makes me think this is just a configuration problem.

So I would start compare the 2 launch properties, see if any evars, events or dependencies this plugin looks for are missing in the one not working.

Also check are the 2 properties similar in terms of both web based or are you trying to do a web based property and a native app one?

Avatar

Community Advisor

Hi @Pablo_Childe Thank you for your reply. We tested by removing all eVars /props/events from the Analytics rule to rule out any dependency but that didnt help us also.

Avatar

Community Advisor

Have you tried enabling Debugging mode?

 

// In Browser Console
// Turn Debugging on
_satellite.setDebug(true);

// Turn Debugging off
_satellite.setDebug(false);

 

Also, are you getting any JS errors?

 

If this plugin isn't set up just right, it could be causing a critical JS error that prevents tracking from proceeding.

Avatar

Community Advisor

Hi @Jennifer_Dungan  Thank you for your reply.
yeah we did debugging In and could not see related console errors.

Avatar

Community Advisor

Hey @ambikaTewari_ATCI 

 

Are the cookie domain periods the same for both the domains assuming two properties are for two domains?

 

That can also sometimes cause issues with plugin installations.

 

Cheers,

Abhinav

 

 

Avatar

Community Advisor

Would you be willing to share the links to the working and non-working sites (even if done via private messaging) so that we can look at the issue in action?

Avatar

Level 1

Hello @ambikaTewari_ATCI ,

 

Can you try-> 'try'-'catch' block inside s_doPlugins(s) function and check if there is any execution error while executing any plugins inside s_doPlugins function?

For ex,

function s_doPlugins(s) {
try{
s.execDoPlugins++;
_satellite.logger.log("============ s_doPlugins("+s.execDoPlugins+") ====================");
    /* Server Variable for every Call */
    s.linkTrackVars += ",server";
    s.server = document.domain;
    s.eVar4=s.getPreviousValue(s.pageName,'gpv_pn','');
s.prop4="D=v4";
/* Visitor Status */
s.eVar21=s.getNewRepeat(365);
s.prop21="D=v21";
/* Visit Number*/
s.eVar23=s.getVisitNum(365);
s.prop23="D=v23";
    /* Time Parting */
var timeVar=s.getTimeParting('Etc/GMT-2');
timeVar=timeVar.split('|');
today=timeVar[0]+'|'+timeVar[1]+'|'+timeVar[2];
s.eVar24=today +"|"+timeVar[2]+"|"+timeVar[3]+"|"+timeVar[4]+"|"+((timeVar[4].match(/^s.*/i)!=null)?"Weekend":"Weekday");
s.prop24="D=v24";
s.prop52=timeVar[3];
}
catch(err){
  console.log("----------Analytics Error----------");
  console.log(err);
}
}

 

 
 

Avatar

Community Advisor

Hi @everyone Thank you for your inputs. we debugged it and found that there is a variable which is present in plugin which was conflicting with the varaible of HTML.

It is resolved now.

 

Thank you all.