Experience changes only appearing on SPA page after refreshing the page

[clairea39507456]

I'm setting up an XT on our checkout which is built on React. My XT changes a bit of copy that appears on every page, so I'm adding additional pages to the experience. I have included to include the base URL in the page delivery for the first page in the experience. I've experimented with the first 3 pages of the journey just to see what's possible. 

The change on the 1st page renders ok, but when you click through to the 2nd page the change isn't there until I refresh my page. Same for the 3rd page. We use the VEC, and we have version 2.10.0 of the at.js. 

Help!!!!!!

[PratheepArunRaj]

Dear @clairea39507456 ,

Hope you are triggering Adobe Target Call on Page Load within Launch.

Since your page is a SPA, when you navigate to other pages, offers are not applied.

Kindly add one more condition to trigger the Adobe Target Call (Usually, on HISTORY CHANGE) so that the offers render onto the page without the need to re-load.

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

[clairea39507456]

Hi Pratheep,

Thanks for taking the time to respond. Unfortunately, we do not use Launch for our implementation (yet), it's hardcoded. Is there a way around this issue for our rather archaic implementation method?

Claire

[PratheepArunRaj]

Dear @clairea39507456 ,

On page change, trigger the ApplyOffer method.

Link: https://experienceleague.adobe.com/docs/target-dev/developer/client-side/at-js-implementation/functi...

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

[alexbishop · Accepted solution]

You should use triggerView(), as that's specifically designed for SPA implementations where at.js 2.x is being used

[PratheepArunRaj]

Sorry @clairea39507456 ,

My bad (Little old school ye). Please use triggerView(), as suggested by @alexbishop.

Thanks for the catch @alexbishop !

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics