The first thing I would do is enable the response token for `profile.mboxtest` in the Administration tab so you can see the value in the response of the delivery calls.Also, if you want the result to be sticky you might need to surround the code with a check of whether the profile variable has alrea...
Is there any way to pass/access any dynamic variables in a VEC Custom Code script? Page params, profile attributes, etc. What about `options` that can be sent to a triggerView() call in addition to the identifier? I've never seen them used outside of the `{page: false}` example. Can I send `{page...
Is the activity Live (Activated)? If you are using the Preview URL to run it then I'm guessing no. If the activity is not activated then it doesn't matter what the Profile Script does, the activity will not run until you either activate it or use the Activity QA links (preview URL).
The server-side SDK, which is a Node library, utilizes the Target Delivery API (a REST service for interacting with Target). They are not mutually exclusive.
Correct. Also, if you want to have multiple experiences, such as `query=query1` and `query=query2` inside the same XT Activity, then you would need to use audiences since the page delivery URL is per activity.
Sounds like you might be able to utilize Data Providers for this depending on the technical details.https://experienceleague.adobe.com/docs/target-learn/tutorials/integrations/use-data-providers-to-integrate-third-party-data.htmlhttps://experienceleague.adobe.com/docs/target-learn/tutorials/integrat...
Are the AEP profile attributes available to enable in the Response Tokens?Also, for mobile you might consider using the `Adobe Journey Optimizer - Decisioning Extension` with accompanying Optimize library. The Delivery API hits Target directly whereas this goes through an Edge datastream.
If this is a SPA page then you probably want to use trigger views.https://experienceleague.adobe.com/docs/target-dev/developer/client-side/at-js-implementation/deploy-at-js/target-atjs-single-page-application.html?lang=en