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...

I'm manually setting and submitting an array of document titles in custom code in Launch when a user executes an action. However prop47 isn't getting stored in analytics but it looks like it's getting set in both the Adobe debugger and the console. The data is correct but it's not getting stored. Pr...

We have an app where a user can select documents via checkboxes and then press a btn to email a list of links. I'm basically faking an array in Launch and storing the titles and then writing them out in custom code when the user presses the button. But now there's a requirement to capture department...

The lack of a console command is a huge problem if you're having trouble with an environment loading. We're having an issue right now where the dev environment script isn't loading correctly, but the Chrome Switch extension only works if it sees Analytics, which it can't since it's not loading. So I...

This is great, thanks! Totally works. I didn't realize you could treat a data element as an array.

Yeah, the developers on this project are not very helpful in giving me anything - they aren't writing anything to the data layer so I'm trying to do this all within Launch. I haven't worked with cookies or either storage option yet, I'll have to research.

Are variables (in this case an array) created within a rule only local in scope to that time the rule fires? Is there a way to create a persistent array within Launch?I have a page with a list of documents and a checkbox next to each. A user can select what they want, then press a button at the bott...

Thank you so much! That was it and it's working now. Seriously, I appreciate the effort to help me out. Also learned that you can't use spaces in the Custom Link name field.

That's just what I'm calling the dynamic data element I created in the previous script._satellite.setVar("featuredTileNumber2",tileIndex.toString());

Thanks for the help but it's still not displaying - I'm just getting %featuredTileNumber2% writing out when the tag fires.I wonder if it's my order of events somehow? I have a custom code block (where I have this js) -> set Analytics -> Set Beacon. Here's my console output:    [Adobe Analytics] Firi...