Hi @DanielWo8 ,   so, yes, you can set the visitorID on the AppMeasurement extension as described here. This under the assumption that your Tealium server-side visitor ID is known and accessible through a cookie. https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/config-vars/vi...

Hi @Daniel_99  not sure I can fully follow. Can you maybe add 1-2 screenshots to visualize the issue you are encountering? Thx!

Hi @xiaoming123 , to clarify: are you setting the s.campaign attribute based on your "cid" query parameters? This must be set to send the tracking code to AAwhat exactly is the pipe doing in your cid=sg|cntest ?also bear in mind that eVars contain Unspecified when they have not been set yet or they ...

Fully agree with Jennifer on that one. eVars are non-numeric string values that live in the rows of your table. There is little dynamic about that. You could ask your developers to perform a calculation by the the time the eVar is generated and set that resulting value.   But bear in mind that this ...

Hi @Harveer_SinghGi1  I think this question would be better suited in the AEP forum since this corner here is more for tag management aspects.   https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform/bd-p/adobe-experience-platform-qanda  

Since YouTube is not your domain, and as the others have mentioned, the orgID is surely different, the ECID cannot be restored on Google side. The Demdex cookie is a third party cookie that can be leveraged across domains, but in times of cookie lifetime limitations for third party cookies, this is ...

Hi @JamesWh7  I think the Adobe Analytics forum isn't quite the right place. Maybe ask your question in the Developer forum instead

Hi @Herder  the getPreviousValue plugin returns the previous value exactly once. At the same time, the new value is persisted and from there on is returned as previous value.   The fix should be to make sure to only call this plugin once i.e., only request the data element in the page view rule and ...

alternatively, skipping the XDM schema, you could also leverage the data.__adobe.analytics object   content.__adobe = content.__adobe || { }; content.__adobe.analytics = content.__adobe.analytics || { }; let s = content.__adobe.analytics; s.events = "events2"; // no linkTrackVars or linkTrackEvents...

Hi @bj612511  Yeah that's a known bug. Since you are having a debug session open, I would look at it in the AEP Assurance where the filter seems to work as expected