Mismatch in Adobe Analytics eVar Value After Production Deployment

[KumarRishii]

I am facing an issue with my Adobe Analytics implementation. Previously, the server was set to abc.com, but it has been updated to xyz.com. I have verified in the browser console that xyz.com is correctly being set in eVar1 during rule execution. However, after deploying this change to Production, the report still displays the old value (abc.com).What could be the possible reason for this mismatch?

[Vinay_Chauhan]

Hi @KumarRishii 

If the new value (xyz.com) is showing in the browser console but the reports still show the old one (abc.com), a few things can be checked -

• Make sure the eVar isn't set to persist across the visit, if it is, and the new value isn't being passed on every call, the old value might still be showing up.

• Double-check if the changes were fully published to the production environment, sometimes a rule or data element doesn't go live properly.

• There could be another rule firing after your current one that’s overwriting the value before the hit is sent.

• Also make sure clearVars() is being used between calls if you're sending multiple hits.

Try using the Experience Platform Debugger to confirm exactly what value is getting sent to Adobe on each call. That should help you trace where the mismatch is happening.

Hope that helps!

[Jennifer_Dungan]

You could also be experiencing people hitting cached pages where the data is still sending the old tracking?

How long has it been since your deployment, and what percentage of your data is showing the old value?

If you have a high number being returned, then it could be a failure of the deployment, an issue with the persistence maintaining the old value, or maybe you have an implementation on a sub-domain or some rule in your tracking which wasn't updated.

If the traffic is low, it might be a result of caching, or people triggering actions on pages that haven't been reloaded (they were on the site during the deployment), or if your Launch Data Element has been set to "Session" based, the value may not update until the user finishes their browser session...  

[gautham_madala · Accepted solution]

Its hard to determine where this could be happening. 
But its good to check the following - 

1. Confirm eVar1 = xyz.com is sent in the actual hit to Adobe Analytics (via debugger).
2. Ensure the rule setting eVar1 runs on every relevant page/event.
3. Check for other rules or custom code that may overwrite eVar1.
4. Verify the correct production library is deployed and active.
5. Consider setting the expiration of eVar1 to "Page View" to prevent carryover.
   Let me know if this works