Should viewname be a unique across whole website while implementing Adobe Target on a Single Page (SPA) using at.js 2.0?

[ajaym75199991]

We are implelenting adobe target in SPA application using method adobe.target.triggerView (viewName, options). In order to configure target call on every view that changes in SPA, we are triggering triggerView function so that respective experience will be rendered on respective view.

No the question here is, Should viewname be a unique across whole website in SPA?

For ex. 

i have 5 viewes in application, all rendered with different urls but have same root url.

https://www.testsample.com/section1/view1

https://www.testsample.com/section1/view2

https://www.testsample.com/section1/view3

https://www.testsample.com/section2/view1

https://www.testsample.com/section2/view2

Now 2 sections have similar url for 2 views view1 & view2, but contents are different and we would like to add different experiences on those views, currently we are passing only view names in adobe.target.triggerView. 

Will this work or should be need to pass unique viewnames like below

section1-view1

section1-view2

section1-view3

section2-view1

section2-view2

Thanks

 

[abu_shafi · Accepted solution]

Consider SPA view as Mobile apps screens (where you don't have any URL)
Now envision you solution "What what additional information do you need? Do you have enough data point in your in target audiences selection?"

Option 1: Use different mBox name to identify different placement and some additional data as profile parameters

Option 2: (my preferred way, other may not agree)
a. Use as few mBox name as possible
b. Supply all dataLayer relevant to that view /screen

c. Use of custom & profile parameters where possible 

In this way you can target multiple location based on different parameters
We use AEM fragments to deliver appropriate content to the platforms (JSON for app/html for web)
I don't have to think about content variation when creating campaigns