I'm going to take the opposite view from the others. I would propose having separate schemas (and datastreams) for your app, instead of using the same schema that is being used for the web. You said that you had customised the ExperienceEvent field group. I'm not sure to what extent you had customis...

Let's say your user, Tom, does this:   Monday: 12:00pm: Views homepage. 12:05pm: Clicks Promotion X. --> track "Promotion X" to eVar23. 12:10pm: Leaves the website. ... 4:00pm: Views homepage. 4:10pm: Clicks Promotion Y. --> track "Promotion Y" to eVar23. 4:20pm: Leaves the website.   Tuesday: 10:00...

Ok, you're not dealing with libraries in your question. In that case, no Development environments where their libraries have not been built will not have the upstream published changes. To verify this, I re-created my test property, with the same setup as before. But I also created a third Developme...

For this query: @chirag_madan wrote: Also, we are planning to use a common dev environment code for both dev and staging website as we have to reject changes everytime if we want to remove any other stakeholder changes from staging. Does it seems to be a good idea.   I personally wouldn't do this. ...

I just did a quick test to check this. I created a new Launch property with 2 Development environments: I checked that Publishing Workflow is empty.   So I created 2 libraries: Library 1 (using Dev1) and Library 2 (using Dev2). Both libraries don't have any Rules, Data Elements nor Extensions yet....

Interesting! This might be a bug in the extension that Adobe could investigate. You could open a new issue in the extension's Github page https://github.com/adobe/reactor-extension-alloy/issues, or you can raise this with Customer Care and let them bring it to Adobe Engineering's attenion.

Duplicate question: https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/transfer-ecid-from-one-property-to-another-property/m-p/694876/highlight/true#M52214

From the link that @PratheepArunRaj and I shared, follow the instructions there to pass the ECID from one website to the other website when a user clicks a link for that journey.

@germanroncelli wrote: Yes, this page kinda behaves like a portion of an SPA, so when passing the URL to an evar or prop, it takes the value of the previous page in the SPA and not the one I want. This is a known problem with SPAs. From those who use Google Tag Manager, the general consensus is to ...

Nope. @pradnya_balvir  #1 and #2 points are features that are exclusive to props.