I am trying to configure adobe analytics on new site using launch .
1. Added Launch js file
2. Added datalayer
3. Configured adobe analytics extension in launch
4. Created rule to send beacon on launch
I am seeing below error . Its a third party site and has S-code already on the pages for their tracking not sure if the inline S-code is causing adobe launch not firing the adobe beacon.
Any help would be appreciated.
Yes, there was an error on page causing the issue not coming from S-Code.
This kind of error can occur from an incompatibility with prototype.js and the Analytics Extension & Deployment within Launch. If someone can chime in and say why there incompatibility exists, that'd be great - I have not been able to identify where the issue is other than the fact that some prototype.js versions cause problems on some sites. (I have not confirmed that using the latest prototype.js fixes all issues or not, so that's an open question as well)
It looks like you've got prototype.js included, so as a first step I would try to update or remove that. Using requestly, I was able to block prototype.js from loading, and your Launch implementation was able to successfully complete all actions and send the Analytics beacon.
I see that you have cookie Domain Periods and First Party Domain Periods set to "3" in the configuration of your Adobe Analytics Extension. That does not match up with this hostname. Try removing those settings.
Thank you all for response.
I tried sending variables before beacon, didn't work
I also tested giving test values to variables, didn't work.
I tried same js code on other test page and i am seeing adobe beacon firing.
Without seeing your code it's difficult to know.
But it seems you have an undefined variable to send.
Before sending the beacon you could put a console.log(yourVariable) to look if it's defined, if it's not defined, define it by the following:
let yourVariable = 'thingYouWantToSend';
Oh. I see. You ARE loading AppMeasurement 2.10.0 via Launch.
But the site loads its own (old crusty version) from http://www.cvent.com/g/scripts/prod/s_code.js
ALTHOUGH this seems like a likely suspect (and I would still pursue getting rid of the old stuff) it probably isn't the root cause.
Try adding an AA Set Variables action in the same rule (just before the send beacon action).
In the set variables action, just set any variable you like (prop99 = "foo" or something like that).
I wonder if this might make the Launch AA extension happier...
I got this far by loading the un-minified Launch embed on your site. The issue is coming from a call to a function by the name "onlyUnique" which is called when preparing s.linkTrackVars prior to sending the beacon.
I see that your AA library is really old (H.24 in fact). I'd be pretty surprised if anything other than AppMeasurement is certified for use with Launch. I would look at moving to AppMeasurment before doing anything else.
i am getting below errors when i try to hit demdex url for DFA. however when i hit the redirect url without the demdex i am able to get adobe analytics beacon.
Your help is really appreciated here as i am loosing all my paid campaign data.
Hi Sailakumari, were you able to get everything working?