Hi @DmytroPanchenk Are you using VEC or Form Composer (i.e. global mbox or regional mboxes) for these activities?My understanding of applyOffers is that it's generally used to apply instructions that were generated as part of a global mbox / VEC authored activity.In the past I've relied on triggerVi...

Hi @deecsilva - 2 things I would validate next are:1. Have you been able to get experiences returned from an mbox via alloy?2. Use the Experience Platform Debugger Extension to make sure everything is working as expected on the back end.https://experienceleague.adobe.com/en/docs/platform-learn/migra...

Hi @DmytroPanchenk Great news that your consumerId update is preserving the SDID after each getOffers() call.When the user navigates to another page/SPA route - I would expect you to be call something like the following prior to any Target/Analytics: visitor = Visitor.getInstance("{YOUR-ORG-ID}") vi...

Hi @PedroJi1 My understanding is that any profile parameters passed under the xdm schema data.__adobe.target (as you mentioned above) behave the same way as if they were sent via at.js.If the profile parameter key exists it's value will be updated to the new valueIf the profile parameter key doesn't...

Hi @DmytroPanchenk I don't think you are far off with your solution, I've run into a similar issue in the past..I believe you just need to pass the mbox name/names into the consumerId field of the getOffers() call.Then on any route change you should also reset the visitorState - this will clear the ...

Hi @Germedin1 I've experienced similar challenges in the past..Given your site is static/server rendered, is your main issue with flicker?Where you see the original page before the target offer is applied on page load? (given your async code)Also can you share some more detail on the way you are usi...

Hi @sushmajk Is your issue related to using the Target UI or querying the activities via API?My recommendation (based on past experience) would be to ensure any old activities are in either the "archived" or "ended" (if scheduled) state - this should be sufficient.The default filters within Target W...

Hi @JyotiSharmaV Sounds like you are using Target to modify the banner image and URL navigated to on-click.Few questions:In the VEC are you applying your target modifications on the Page Load or a Trigger View?When you notice that the modifications weren't applied, were they applied at first and the...

Hi @tejas18 My understanding (based on my own experiences) is that once you have built the Experience Fragment (XF) in AEM and click the "Export to Adobe Target" button - the XF will be exported to Target at that point in time.If you then make further changes to the XF in AEM, these won't be reflect...

Hi @srv_15 Are you trying to capture the Target Response Tokens from a WebSDK Target call, and then pass them back to an AEP dataset (within the XDM schema) in a second WebSDK send event on the page?