Also, previously, AA data ingested into AEP Data Lake through source connector had no default retention and stayed indefinitely.Last year, 2024, Adobe introduced AA Event Expiration (TTL) to align AEP's aa data retention with adobe analytics (default 25 months).Enable TTL during for AA source connec...

Just to add to the above,to match custom pageviews PV (eventX) with default PageViews PV metric fire your custom event(pageviews) only on trackState calls(if doing via processing rules then Set eventX(pageviews) only when pagename  is set ), not on trackAction. This keeps both numbers aligned. PVs w...

Agreed with Jen I also don’t see any major changes either, But I did notice a slight difference in the numbers though very marginal. See right is with the segment :--  

hi @robinl39529461  This is correct approach. Using a hit level segment that includes only page view hits, combined with avg. Time on Site and the page dimension, gives the average time between that page view and the next page view, excluding exits. as you mentioned, adding the exits metric is also ...

mid is visible only in ECID2.png, not in ECID1.png. vidAPI looks like a custom Allstate implementation, maybe for visitor ID. But yes as long as MID is present and is the same, the ECID service is working. 

Sure, I also tested on https://www.allstate.com and https://purchase.allstate.com/ and can confirm that the ECID is set on the root domain .allstate.com, so that looks fine. But, the site https://shopandbuy.allstate.com isn’t accessible for me where you are having this issue as it redirects to https...

OK, it can be a bot, but if in your testing ECID persists across domains like in chrome, it means ECID service is working and cross-domain ID transfer is correctly done..also along with CNAME if you are using (appendvisitorIDsTo()), this approach also supports cross domain, but browsers with stricte...

IP remains same but domain changes mid flow. ECID reset indicates cross domain identity is not persisting. Pls test it and validate same ims org id, consistent launch/web sdk config, cookie domain scope (.allstate.com) and correct cross-domain ECID transfer (visitor.appendVisitorIDsTo() if using app...

Yes, that is correct.In your eg, selecting Vers. 1 (1st Dec) from History and using “Copy to Current Ruleset” will replace the entire current ruleset with the 45 rules from that snapshot/date. It does not merge or append rules.Once saved, the ruleset will exactly match the selected historical versio...

Yes, “Copy to Current Ruleset” in processing rule is safe and recommended for rollback. Note that changes only affect future data, past collected data remains unchanged and cannot be retroactively changed.Select the desired historical version in 'View History' then click the selected date 'View' for...