since ‎23-11-2015
‎06-10-2020
bennet_royj6135
Employee
Re: [UPCOMING WEBINAR] 8/7/19 Introduction to Single Page Apps Visual Experience Composer Webinar
Avatar

bennet_royj6135

Employee

bennet_royj6135
- Adobe Target
That is correct.State Changes that results in loading a new SPA page should call - adobe.target.triggerView("homeView") or adobe.target.triggerView("productView") etc.State Changes that results in visual updates that does not need to be considered as a new page (Ex: cart add) should call - adobe.target.triggerView("homeView", {page: false}) or adobe.target.triggerView("productView", {page: false}) etc.Yes, you need to include the relevant triggerView calls based on what is explained above on you...

Views

13.5K

Like

1

Replies

0
Re: [UPCOMING WEBINAR] 8/7/19 Introduction to Single Page Apps Visual Experience Composer Webinar
Avatar

bennet_royj6135

Employee

bennet_royj6135
- Adobe Target
Hi, AT.js 2.x can be used on both MPA's and SPA's.AT.js 2.x has advantages over AT.js 1.x. So, it is recommended to use AT.js 2.x for both your Non SPA's as well as SPA pages.AT.js 2.x and AT.js 1.x can be used on the same website, but not on the same page of the website.I apologize that the answer given during the webinar QA created some confusion. Let me state a situation where you may have AT.js 1.x and 2.x run on the same website. When you have multiple teams on your organization that handle...

Views

13.5K

Like

1

Replies

0
Re: [UPCOMING WEBINAR] 8/7/19 Introduction to Single Page Apps Visual Experience Composer Webinar
Avatar

bennet_royj6135

Employee

bennet_royj6135
- Adobe Target
Hi, You can consider Views as state changes as long as the state change results in a visual update on the page. if that is the case, Yes, you can use the existing event listeners to trigger the Views in Target.ThanksBennet

Views

13.5K

Like

1

Replies

2
Likes from