<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ameeruddin Muhammed on Medium]]></title>
        <description><![CDATA[Stories by Ameeruddin Muhammed on Medium]]></description>
        <link>https://medium.com/@ameeruddin?source=rss-a4365ac467ee------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ERQsm5S4pbWnnPG-.</url>
            <title>Stories by Ameeruddin Muhammed on Medium</title>
            <link>https://medium.com/@ameeruddin?source=rss-a4365ac467ee------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:30:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ameeruddin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Real World Adobe Analytics to CJA Migration (What Actually Happens)]]></title>
            <link>https://medium.com/@ameeruddin/real-world-adobe-analytics-to-cja-migration-what-actually-happens-97902308aaa6?source=rss-a4365ac467ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/97902308aaa6</guid>
            <category><![CDATA[adobe-cja]]></category>
            <category><![CDATA[adobe-analytics]]></category>
            <dc:creator><![CDATA[Ameeruddin Muhammed]]></dc:creator>
            <pubDate>Fri, 23 Jan 2026 22:26:20 GMT</pubDate>
            <atom:updated>2026-01-23T22:26:20.584Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me be honest.</p><p>The first time you migrate from Adobe Analytics to CJA, it feels uncomfortable. Not because the tool is bad. But because CJA quietly exposes all the shortcuts we took for years.</p><p>Most teams ask me one question on day one:</p><blockquote><em>“How do we map props and eVars in CJA?”</em></blockquote><p>That question already tells me where the struggle will be.</p><h3>Page Views, Props, and eVars: The First Mental Shift</h3><p>In Adobe Analytics, we were trained to think like this:</p><ul><li>Page View is the hero metric</li><li>Props are short-lived</li><li>eVars are long-lived</li><li>Everything revolves around visit scope</li></ul><p>So naturally, teams try to recreate that in CJA.</p><p>It doesn’t work.</p><p>In CJA, a page view is just an event. Nothing more. There is no prop vs eVar safety net.</p><p>What finally clicks for people is this:</p><p>You don’t decide persistence at collection time anymore. You decide it <strong>when you analyze</strong>.</p><p>Once teams move page name, page URL, page type, and section into clean event-level fields, life becomes simpler. No more “which variable should this be?” debates.</p><p>That alone removes a lot of implementation anxiety.</p><h3>Marketing Channels: Where Old Habits Die Hard</h3><p>Marketing channel discussions are emotional. Everyone has opinions.</p><p>In Adobe Analytics, channel rules were sacred. Once defined, they were hard to change without chaos.</p><p>In CJA, the first thing I tell teams is:</p><blockquote><em>“Don’t solve channels yet.”</em></blockquote><p>Just collect reality.</p><p>Capture:</p><ul><li>referrer</li><li>UTMs</li><li>campaign IDs</li><li>click context</li></ul><p>That’s it.</p><p>Later, in Data Views, you can create:</p><ul><li>a marketing-friendly channel definition</li><li>a product-focused one</li><li>even an executive-friendly simplified version</li></ul><p>Same data. Different interpretations.</p><p>This is where CJA feels liberating, especially for teams that spent years fighting over “correct” attribution.</p><h3>Events: This Is Where CJA Feels Refreshing</h3><p>Adobe Analytics events were powerful, but let’s be honest, they were also cryptic.</p><p>Event 12 means Add to Cart.<br> Event 18 means Purchase.<br> If you are a individual contributor or in a team — you know the rule, document them and refer them back when in confusion.</p><p>In CJA, events finally say what they mean. Yes, you don’t have to refer anything else. They literally mean what the name reads.</p><p>Instead of encoding meaning in numbers, you just say:</p><ul><li>add_to_cart</li><li>begin_checkout</li><li>purchase</li></ul><p>And you attach context right there.</p><p>When analysts open the dataset six months later, they don’t need a Rosetta Stone to understand what’s happening. That’s a huge win that people only appreciate after living with it.</p><h3>Products and Merchandising: The Part Everyone Fears</h3><p>This is usually the moment where someone says:</p><blockquote><em>“But what about the products string?”</em></blockquote><p>Short answer: let it go. Yes, that’s true. Just “LET IT GO”</p><p>Long answer: the products string was clever for its time, but it forced too much meaning into one compressed format.</p><p>In CJA, products behave like real objects.</p><p>One product interaction equals one event with:</p><ul><li>product ID</li><li>name</li><li>category</li><li>price</li><li>quantity</li></ul><p>At first, teams worry this will explode data volume.</p><p>In practice, it simplifies analysis and unlocks things Adobe Analytics could never do cleanly, especially across devices and time.</p><h3>Visits, Sessions, and Time: The Quiet Shift</h3><p>Here’s something I’ve noticed.</p><p>Teams don’t stop using sessions immediately. They slowly stop caring about them.</p><p>CJA doesn’t remove sessions. It just stops forcing them on you.</p><p>Over time, people start asking better questions:</p><ul><li>How many people reached this point?</li><li>What did they do before converting?</li><li>What happens after they convert?</li></ul><p>Those questions don’t need visits. They need journeys.</p><p>That’s when CJA starts earning trust.</p><h3>Identity Migration: Go Slower Than You Think</h3><p>This is where I see the most damage done.</p><p>Teams rush identity stitching because it feels powerful. My advice is boring but safe:</p><ul><li>start anonymous</li><li>layer identity gradually</li><li>upgrade when you’re confident</li></ul><p>CJA works even when identity is imperfect. Adobe Analytics often didn’t.</p><p>That difference matters a lot in real implementations.</p><p>If you try to recreate Adobe Analytics exactly inside CJA, you’ll rebuild the same limitations with a new UI.</p><p>The teams that succeed are the ones that accept a short transition period and focus on long-term clarity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97902308aaa6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>