SPA & triggerView in Form-based Editor

[ChrisMezzo]

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

[nzchris · Accepted solution]

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

[ChrisMezzo]

Thanks Chris. Yes, I've got the extension but the site itself - our logged in area - is iframe busting (I think that's the right term), so only the third-party chat widget shows in the bottom right corner. I've been trying to resolve this with our dev team for a while, but no luck so far.

Good to know at least that there's not something I'm missing. This is definitely a feature I'd want to see in the future.

[waynec94256240]

We have the same issue and adding functionality to target "views" within the form composer would be hugely beneficial to a wide audience (I would think).

[UKCH]

Hi @nzchris , I have the same problem, is there an update? How can I target different views with form based experience composer? I need it for a React SPA