Hi @shaikhshoeb  In Form-based Experience Composer, Content delivered to custom scopes is not rendered automatically by the Platform Web SDK. It can be rendered using an action types in Tags (Launch).  You can modify your page load rule to add a custom decision scope. Add a scope to send event actio...

Hi @DeepakUp  If you’re seeing this error, it’s likely because your script contains characters outside the UTF-8 range.There might be possibility that in your form based campaign, the script you wrote has contain some invalid characters that cause issues when working with Target activities.   Please...

Hi @Michael_Soprano  The certification include both at.js and Web SDK concepts. While Adobe recommends Web SDK for new implementations, at.js is still widely used and appears in the exam objectives.  So ideally in actual exam you can see the questions from both the sides.    Did you check this Exam ...

Hey @JanP42  Thank you so much for coming back !!! Really appreciate!!! Glad that this is resolved now and you've a solution is in place !!!  Yes, absolutely, completely agree with your point. I’ll raise this with the AT team so they can review and update the documentation to prevent such issues in ...

Hi @emmak109  Please consider these caveats when using virtual report suites in the context of Adobe Target: You cannot send data directly from Target to a virtual report suite, only to a real report suite.You can report on A4T activities within a virtual report suite. However, the A4T data is...

Hi @PrasanthV   I did try with custom code just added document.querySelector('') with right DOM element from page and it's working for me. So when the DOM element is available then only I can see the Target is getting fired.    So may I ask why you're using setInterval method here? the element you'v...

Hi @TNxx  So what I understood from your question that, you are trying to access mbox parameters in profile script right?  But ideally custom mbox parameters must be passed in XDM data with sendEvent command to be consumable by Target. And mbox parameters cannot be passed as part of the data object....

Hi @Michael_Soprano  I believe revenue-generating location where a Target experience is suppose to delivered so I mean you already request personalization content (rendered a proposition) so like below you can report  alloy("sendEvent", { xdm: { _experience: { decisioning: { prop...

Hi @PoojaMudgal  As far as I know, in Adobe target when you clone or migrate activities from one account or environment to another, the historical performance data (reporting data)  doesn't come directly. It's always start with new data. And also there is no built in functionality which allows this ...

Hi @PrasanthV  Generally the delivery calls happening at the time of page loads. In case you want this to restrict based on DOM elements then you can create a Rule in Adobe Launch ( tag manager)  that checks for the presence of a DOM element before firing the Target delivery call.    Like in below R...