I have a SPA that I am looking to run Target experiences on.
The SPA doesnt have the url update with hash segments so the URL remains the same as different content is displayed/loaded.
There are different sections to the SPA though with unique IDs setup on key components.
Target on the initial page load can change and update content with an experience running as expected but as soon as state changes things break and experience no longer loads.
Target then notes error indicating that the action could not be displayed due to a missing/invalid mbox name.
My assumption is its due to the state changing and my thinking is to see if a TriggerView on a particular ID being present will resolve the Mbox issue.
If anyone can assist on potential pointers on getting a TriggerView to fire on a ID being present. Would a simple getElementByID type call be as complicated as things are?