Hello, We are looking at implementing the customer attributes feature. I have reviewed the documentation both in the Target section as well as the "Experience Cloud Interface Component" docs. I understand you upload customer IDs and associated attributes to the platform and that you must send this ID to the platform on the page level after the user logs in. However, based on Adobe's docs (primarily https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/working-with-custo...

Hello,We have a a simple configured in Launch. The "trigger" event is merely Core -> Click with a simple CSS selector. There is no condition and the the "Action" portion is custom JS that fires a target mbox. However, we are having issues with this rule firing consistently. It appears to be a timing issue. When the rule fails to fire, I notice a Warning being logged to the console: "Loading failed for the with source “https://assets.adobedtm.com/xxxx/xxxx-source.min.js”. This message does not appear when the Action fires correctly (with the "firing correctly" being verified using the Adobe debugger extension.) If I manually navigate to the script that the browser warns had failed to load, it loads just fine and I can confirm that it is the custom code I wrote for the "Action" in Launch. Additionally, the source (in Firefox's Dev Tools console) of the aforementioned warning is the initial/source page (the one with the link containing the rule trigger) not the destination page. However, the Warning itself is logged while on the destination page, not the source. I am wondering if this is a common/known issues with Launch and how we might resolve. I realize there is an option to delay navigation in the "Click" event within Launch, but this is something we would like to avoid. Any tips are much appreciated.