I'd be very careful of hiding the fields and inserting "dummy values" because if these fields are mandatory, it's likely because the business relies on them for processing, reporting, compliance, or personalization. Dummy values could have the unintended consequence of corrupting the dataset, making...

This would be problematic. While Adobe Target could be used to hide or remove said form fields using CSS or JS, if the form is configured to require those fields on the backend, simply hiding them on the front end wouldn't allow submission unless there's additional intervention to bypass validation....

@rudraWiley perhaps I misunderstood your goal, I took it as that's what you wanted to happen (i.e. disable Target) in a given browser session.

Using the browser inspector, try blocking the delivery or interact call by selecting "Block request URL"

@rudraWiley may I ask what setting do you have your QA URLs on for "Show default content for all other activities?"

Would you mind sharing what the root cause and resolution was for you in this scenario?

@alexbishop is there documentation for the sync loading that I could point my dev/IT teams to look at? This issue is plaguing so many things and we need to resolve it.

@JeffinSa did you ever resolve this, and if so, what did you do?

@drburnsTarget27 can you please share example code for such a profile script?