Would love to see this feature available to use

I have just received this from Adobe Customer Care. "The best way is removing the complete record from the file altogether."

Hi there @m_nakayama , and thanks for taking the time to respond.This isn't quite what I was after, I'm not trying to stop them being targeted in our normal onsite personalisation, just on 3rd party platforms with people based destinations. I'll try and rephrase the question.I have 2 data sources. O...

Hello community.I am looking at file-based ID Sync for people-based destinations and have a question about behaviour of new files over old ones.Say I have a customer with a hashed email against their Member ID, and on a subsequent file import, this person no longer qualifies for being targeted (no l...

So seems like we've had a breakthrough.Now I'm not sure if all SF configurations are the same as ours, but what seemed to work was first targeting the DIV.ui-widget element and then the element that I needed.eg. I wanted to target a h3, so using the selector h3:eq(0) (or equivalent) in VEC didn't wo...

Hi @PratheepArunRaj,thanks for taking the time for replying. This is tricky, and unfortunately it doesn't seem as simple as implementing a triggerView(). It could also be that SFL is working with Lightning Locker (which is a Salesforce architectural layer focused on security - more in here https://r...

Hi there I was wondering if anyone else has had any issues/success with integrating Target into Salesforce Lightning(SFL)? We are trying to run some experiments/personalisation activities within SFL but are having issues with Target being able to modify elements on the page. Target scripts load succ...

I haven't seen this problem in a little while, but then again I had switched to using Firefox to debug once the Debugger was made available to Firefox, and everything seems to work fine there. But I'm not sure whether the problem has resolved in Chrome

Thanks for responding @Amelia_Waliany. Though it doesn't look like that page references anything to do with the Debugger

Hi there. I'm wondering if anyone can shed any light as to why I'm getting the following error in my browser console on the Target response (.tt.omtrdc...) payload?I've copied the QA URL from my activity, and when I paste into the browser, I can't debug the payload, because this is the only message ...