Rendering form based activity with Tags Apply Propositions

First I would check the response of the pageview request, if it contains the personalization data you need (like the <div>). You could also log event.propositions to your console, to see if the data is delivered correctly. If you see that your request is working, it’s an issue with the append. Make sure the Selector is present, and check if you have the newest version of the WEB SDK extension, it was buggy in some versions for the form based personalization. You could also try it by custom code, to access and set the div:

// Retrieve propositions
alloy("sendEvent", {
  "renderDecisions": true,
  "xdm" :{
     "eventType" : "decisioning.propositionFetch"
  },
  "decisionScopes": ["your scope"],
  "data": {
    "__adobe": {
      "target": {
      }
    }
  }
}).then(function(result) {
  var retrievedPropositions = result.propositions;
  let data = result?.propositions[0]?.items[0]?.data.content;
  if(typeof data !== 'undefined')
    {
  const tempDiv = document.createElement('div');
  tempDiv.innerHTML = data.trim();

  const oldElement = document.querySelector('your selector');
  const newElement = tempDiv.firstElementChild;
if (oldElement && oldElement.parentNode && newElement) {
  oldElement.parentNode.replaceChild(newElement, oldElement);
}
    }  
});

In most cases with form-based activities, the content is returned as propositions but it won’t render automatically. When using tags or the Web SDK, you usually need to run Apply Propositions after the sendEvent call so the SDK knows where to inject the content into the DOM.

Make sure the decision scope matches the activity location and that the CSS selector exists on the page when the action runs. Adobe’s documentation explains the configuration here:

https://experienceleague.adobe.com/en/docs/experience-platform/tags/extensions/client/web-sdk/actions/apply-propositions