morgant29080047

Re: Launch rule on a button firing but no data in Analytics - Adobe Analytics 09-03-2022

It is on the same domain and has AA on it.

190

Launch rule on a button firing but no data in Analytics - Adobe Analytics 09-03-2022

I have a rule set up on a button to capture some data and then send the beacon as a custom link, don't treat as page view. I do this all the time. I'm seeing the button fire in the console and in the Adobe Debugger but nothing is showing up in Analytics. I have our normal evars/props on it, as well as an event. I've also messed with the navigational timeout in the Launch rule, to no avail. I've never seen anything like this yet. It's clearly firing but not capturing. Since the button leads to an...

207

Re: Associate list var values with list prop like a multi... - Adobe Analytics 17-02-2021

@Khurshid_Alam Thanks, that's what I figured. But is there a way to not have it work that way? We only want to report the metadata associated the specific titles (so for each list var value, there'd be a corresponding value in prop3, prop4, etc).

329

Associate list var values with list prop like a multidimensional array? - Adobe Analytics 17-02-2021

We have an internal site that lets users pick several documents at a time and each of these documents have several pieces of metadata associated with it. We're using a list var for the document title and list props for the various metadata. But in Analytics, if you break down the title by one of these list props, we're seeing more values than should be there. You can see it below from the console when the Launch rule is called. Should the individual values of those props line up with the titles ...

376

Re: Some props writing out in a loop, others not. Why? - Adobe Experience Platform Data Collection 23-08-2019

I wish I could, Andrey. Sadly, it's an internal SPA.The main UI looks like this, the user selects from a list of docs via the checkbox and then clicks on the share and gets one of those actions. The UX on this is a mess, but I can't control that.So as the user checks boxes (or unchecks) I have a rule that's managing these in a dynamically created data element. When they select an action (each has its own rule) it processes them out. That's where I'm struggling. I've been thinking about trying to...

2.5K

Re: Some props writing out in a loop, others not. Why? - Adobe Experience Platform Data Collection 23-08-2019

Thanks for the help, I'm still getting only the first item in the array written into analytics. DocLength is correct, i can see the arrays in the console, the data is correct, it's just failing somewhere...

2.5K

Re: Some props writing out in a loop, others not. Why? - Adobe Experience Platform Data Collection 22-08-2019

Yep, positive on the report suite (since some of the data is writing out). I tried defining s and s.linkTrackVars outside of the loop but that actually prevented any data from writing out, which seemed odd to me.

2.5K

Re: Some props writing out in a loop, others not. Why? - Adobe Experience Platform Data Collection 22-08-2019

Hi, Just following up. I made some slight changes and now when I’m looping through this array of data to send out, the first item in the loop is writing into analytics, but the following items. So if the array has 3 items, only the first is working. I’m still seeing the other two in the debugger, but they aren’t getting written out. Any idea why? Here’s the code:for (var i = 0; i < docLength; i++) { var s=s_gi('mfs-distribution-intranets'); s.linkTrackVars='prop1,prop46,prop50'; s.prop1=articleI...

2.5K

Re: Some props writing out in a loop, others not. Why? - Adobe Experience Platform Data Collection 21-08-2019

It does - the data is in the debugger but not showing in analytics. I really don't get it. Is there anything weird about my code? Should I not be doing a clearVars() after the s.tl?

2.5K

Re: Some props writing out in a loop, others not. Why? - Adobe Experience Platform Data Collection 21-08-2019

That's a good thought but no, no processing rules.I feel like there's a lot going on in my rule here. I'm looping through this array (a dynamically created data element) and processing that in a custom block under conditions, then after that I'm setting some other props in the set variable block and then I'm calling a fire beacon to save those. I don't know, i feel like somehow all this is stepping on each other. The set variables are getting consistently written out, but the stuff in the loop I...

2.5K

Likes given to

User

Count

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe