Sign in to Community
Sign in to view all badges
We have a client where we need to deploy Target across their Angular UI-router SPA.
We’re struggling on setting this up on our sandbox to test the deployment, we’ve added a demo Angular site https://yamahaclub.com/angular-test/ to set Target up on before we start the client work.
The Adobe documentation isn’t consistent, one says you need a manual mbox one doesn’t.
One of the guidelines say to use at.js without the auto-created mbox but doesn’t say why, can we not use the auto mbox at all?
If the site has a static component and an SPA, do we need to change the tool instance to use a manually configured mbox?
Do we need to manually create a DTM rule with the ‘adobe.target.ext.angular.initStates’ for every app and module in the SPA we want to test or are we able to somehow have a global one?
Also will this work for SPAs where the URL doesn’t change or have fragments.
I know this post is a little old, but have you looked at at,js 2.0 recently. The 2.x versions were built specifically for handling SPA's
How at.js works overview