Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

SPA & triggerView in Form-based Editor

Avatar

Avatar
Boost 3
Level 1
ChrisMezzo
Level 1

Likes

4 likes

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile

Avatar
Boost 3
Level 1
ChrisMezzo
Level 1

Likes

4 likes

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile
ChrisMezzo
Level 1

30-06-2020

Hi all,

 

I see that for SPAs, triggerView() fires a 'delivery' network request for a 'notification', much like a metric used under adobe.target.trackEvent(), rather than 'content' as seen with adobe.target.applyOffer().

 

I understand how to configure builds against triggerView in the VEC, but we have issues with the VEC in our secure account area, in that security issues currently restrict the site being viewed through an iFrame. This makes editing very tricky.

 

My question is therefore: Is it possible to use the Form-based editor in conjunction with triggerView? In the 'Location' field, I see no option to select the 'view' key that is passed in the triggerView() call, and targeting the 'target-global-mbox' with audience refinements for page URL doesn't work either.

How does the VEC recognise these view changes if it's not with new mbox names? Can that be replicated in the form-based editor?

 

Many thanks,

Chris

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 3
nzchris
Level 3

Likes

18 likes

Total Posts

24 posts

Correct Reply

8 solutions
Top badges earned
Validate 1
Give Back
Boost 5
Boost 3
Boost 10
View profile

Avatar
Validate 1
Level 3
nzchris
Level 3

Likes

18 likes

Total Posts

24 posts

Correct Reply

8 solutions
Top badges earned
Validate 1
Give Back
Boost 5
Boost 3
Boost 10
View profile
nzchris
Level 3

13-07-2020

Hey Chris,

 

As far as I'm aware - using triggerView in the form based composer isn't available (+1 vote for this in the future). Have you tried using the Adobe Target chrome extension? It helps to remove the iframe busing headers on your browser:

https://chrome.google.com/webstore/detail/adobe-target-vec-helper/ggjpideecfnbipkacplkhhaflkdjagak

 

The only other thing around this is you could put an offer code on the target-global-mbox and utilise the success events to watch for the triggerView call to fire the code?

 

Hope that helps,

Another Chris

Answers (0)