Your data element needs to be called from somewhere, such as a rule or extension, in order to output the message. This is why you don't see anything automatically when you load a page even though there is nothing syntactically wrong with your code. As this guide explains, a data element's value will attempt to be reset any time it is called: https://jimalytics.com/tag-management/adobe-launch-data-elements-guide/ Also, If you must to log messages to the console, it is recommended to always use th...

Alandy_Iceboats​ Multiple libraries can exist in Dev status but they cannot share the same embed codes, so in this case you'd need to create a new environment. You can do this by going to the Environments tab and selecting "Add Environment".The new environment will have its own unique embed code, allowing you to test only your newest changes and keep them separate from the rejected library. It sounds like your team's workflow would not permit merging your newest changes into the rejected library...

I think you may be looking for Adobe Experience Platform Mobile SDKsThis page of the documentation contains a helpful breakdown of Launch data elements and rules in the context of a mobile property. Rules Engine - Adobe Experience Platform Mobile SDKs I hope this is helpful!

Typically, when I see an error like this, it is an indication that the function has been inadvertently overwritten by something that is not a function. Below is an example of this. ==========================================Beyond this, the code that you shared has issues. It is recursing and installing multiple click listeners on your button. You end up getting a new event listener installed every 3.5 seconds. That means that if you sat on the page for 36 seconds, and then clicked the button, tr...