Adobe generally frowns on having personally identifiable information (PII) data in Analytics. But yes, do consult your managers / lawyers about this, particularly with modern sensitivities around data privacy.

How is your segment defined? Can you show a screenshot of it?

Since these are Direct Calls, then that should mean that you have 4 different _satellite.track() calls in your web page(s). Is that correct? If so, you could try this: Study your Direct Call triggers to find out their firing order. I have a feeling that the Direct Call triggers are not happening at ...

The Core extension has a "Enters Viewport" event: That might work for you.

In your <iframe> HTML tag, are there any attributes besides the standard "src" one? IFRAMEs can have attributes that instruct the browser to restrict the data that can be sent between the parent frame and the IFrame, and that could cause issues like what you're observing with your cookie. One way to...

@Jennifer_Dungan is right, you don't want to use event serialization. Reference: https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/events/event-serialization.html?lang=en Instead, what you want to do is to track that final selection when the user actually makes the call...

Following from @Jennifer_Dungan 's reply, assuming that expiring by a Success Event doesn't work for you (for the reasons that she's provided), and you absolutely, positively need to ensure that your eVar expires within the same session, then you will have to resort to: Using a "Hit" expiration with...

This is correct. You DO NOT need to do any filtering if you use the Target Experiences and Target Activities dimensions. You can think of Target Experiences/Activities as visit-scoped dimensions, e.g. similar in scope to Entry Page and Exit Page.

The InDesign forum is at https://community.adobe.com/t5/indesign/ct-p/ct-indesign?page=1&sort=latest_replies&lang=all&tabid=all . Try asking there instead.

Try resetting your Debugger. In the Debugger window, click "Settings" in the left navigation, then click the "Reset all data and settings" button. The Debugger will close automatically. Re-open the Debugger and re-login, and see if Edge Logs works again. If Edge Logs still doesn't work, you may need...