diff --git a/components/SelfGuidedTours.tsx b/components/SelfGuidedTours.tsx
new file mode 100644
index 0000000000..33d154a0a5
--- /dev/null
+++ b/components/SelfGuidedTours.tsx
@@ -0,0 +1,309 @@
+'use client';
+import React from 'react';
+import Image from 'next/image';
+import Script from 'next/script';
+
+/**
+ * Card data shape passed from MDX.
+ * - navatticOpen: the Navattic demo id (e.g., "cmfkxwfa5000004lc8408f5wi")
+ * - navatticTitle: optional; title for the Navattic popup chrome
+ * - img: optional; if omitted, a dark placeholder fills the media area
+ */
+type Card = {
+  badge: string;
+  title: string;
+  blurb?: string;
+  img?: string;
+  href?: string;
+  navatticOpen?: string;
+  navatticTitle?: string;
+};
+
+interface Props {
+  cards: Card[];
+}
+
+/* ---- Constants / design tokens (keep in sync with MDX usage) ---- */
+const MP_PURPLE = 'rgb(139 92 246)';
+const BORDER_RADIUS = 14;
+const CARD_W = 296;
+const CARD_H = 319;
+/** Image height is fixed for consistent badge anchoring */
+const IMAGE_H = 140;
+/** Image width is indented left and bleeds to the right edge */
+const IMAGE_W = 276;
+
+/* ---- Inline “CSS-in-TS” styles (layout is pixel-exact to your spec) ---- */
+const styles = {
+  grid: {
+    display: 'grid',
+    gap: 20,
+    gridTemplateColumns: 'repeat(auto-fit, minmax(296px, 1fr))',
+    justifyContent: 'center',
+    marginTop: 32,
+  } as React.CSSProperties,
+
+  card: {
+    position: 'relative',
+    width: CARD_W,
+    height: CARD_H,
+    borderRadius: BORDER_RADIUS,
+    overflow: 'hidden',
+    border: `2px solid ${MP_PURPLE}`,
+    boxShadow: '0 10px 30px rgba(0,0,0,.25)',
+    transition: 'transform .25s ease, box-shadow .25s ease, background .3s ease, color .3s ease',
+  } as React.CSSProperties,
+
+  dogEar: {
+    position: 'absolute',
+    right: 10,
+    top: 10,
+    width: 22,
+    height: 22,
+    background: 'var(--sgt-dogear)',
+    clipPath: 'polygon(0 0, 100% 0, 100% 100%)',
+    boxShadow: '0 0 0 2px rgba(0,0,0,.15) inset',
+    zIndex: 5,
+    pointerEvents: 'none',
+  } as React.CSSProperties,
+
+  mediaWrap: {
+    position: 'absolute',
+    top: 18,              // aligns the image to the badge’s left indent
+    height: IMAGE_H,
+    width: IMAGE_W,
+    marginLeft: 16,       // left indent (aligns with badge)
+    marginRight: -16,     // bleed to right edge (no right indent)
+    borderTopLeftRadius: 8,
+    borderBottomLeftRadius: 8,
+    overflow: 'hidden',
+    background: 'var(--sgt-media-bg)', // placeholder color behind images
+    zIndex: 1,
+  } as React.CSSProperties,
+
+  mediaImg: {
+    width: '100%',
+    height: '100%',
+    objectFit: 'cover',
+    objectPosition: 'left top',
+    display: 'block',
+  } as React.CSSProperties,
+
+  placeholder: {
+    width: '100%',
+    height: '100%',
+    background: 'var(--sgt-media-bg)',
+  } as React.CSSProperties,
+
+  /**
+   * Anchored text block:
+   * - Badge top is locked to IMAGE_H + offset so all cards align visually
+   * - Title and blurb naturally flow below the badge
+   */
+  bottom: {
+    position: 'absolute' as const,
+    top: IMAGE_H + 22,
+    left: 0,
+    right: 0,
+    bottom: 0,
+    padding: '16px 18px 22px',
+    zIndex: 3,
+  },
+
+  /* Badge = stronger weight + tighter tracking for a pill look */
+  badge: {
+    display: 'inline-block',
+    background: 'var(--sgt-badge-bg)',
+    color: 'var(--sgt-badge-fg)',
+    fontWeight: 800,
+    letterSpacing: '.04em',
+    fontSize: '11.5px',
+    lineHeight: 1,
+    borderRadius: 8,
+    padding: '8px 10px',
+    marginBottom: 10,
+  } as React.CSSProperties,
+
+  title: {
+    fontSize: 23,
+    fontWeight: 700,
+    lineHeight: 1.2,
+    margin: 0,
+    color: 'var(--sgt-title)',
+  } as React.CSSProperties,
+
+  blurb: {
+    marginTop: 8,
+    fontSize: 15,
+    color: 'var(--sgt-blurb)',
+    opacity: 0.75,
+  } as React.CSSProperties,
+
+  clickable: {
+    display: 'block',
+    width: '100%',
+    height: '100%',
+    background: 'transparent',
+    border: 0,
+    padding: 0,
+    cursor: 'pointer',
+    textAlign: 'inherit',
+  } as React.CSSProperties,
+};
+
+/* ---- One card view (supports Navattic popup or plain link) ---- */
+function CardView({ c }: { c: Card }) {
+  const inside = (
+    <>
+      <div style={styles.dogEar} aria-hidden />
+      <div style={styles.mediaWrap}>
+        {c.img ? (
+          <Image src={c.img} alt="" fill style={styles.mediaImg} priority={false} />
+        ) : (
+          <div style={styles.placeholder} />
+        )}
+      </div>
+
+      <div style={styles.bottom}>
+        <div style={styles.badge}>{c.badge}</div>
+        <h3 style={styles.title}>{c.title}</h3>
+        {c.blurb ? <div style={styles.blurb}>{c.blurb}</div> : null}
+      </div>
+    </>
+  );
+
+  // Use Navattic popup if navatticOpen is provided
+  if (c.navatticOpen) {
+      const navatticUrl = c.navatticOpen.startsWith('http')
+        ? c.navatticOpen
+        : `https://capture.navattic.com/${c.navatticOpen}`;
+
+      return (
+        <div style={styles.card} className="sgt-card">
+          <button
+            type="button"
+            style={styles.clickable}
+            className="sgt-click"
+            data-navattic-open={navatticUrl}
+            data-navattic-title={c.navatticTitle || c.title}
+          >
+            {inside}
+          </button>
+        </div>
+      );
+    }
+
+  // Fallback to href links if needed
+  if (c.href) {
+    return (
+      <div style={styles.card} className="sgt-card">
+        <a href={c.href} style={styles.clickable} className="sgt-click">
+          {inside}
+        </a>
+      </div>
+    );
+  }
+
+  // Static (non-clickable) card
+  return (
+    <div style={styles.card} className="sgt-card">
+      {inside}
+    </div>
+  );
+}
+
+/**
+ * SelfGuidedTours
+ * - Renders a responsive grid of product-tour cards
+ * - Loads Navattic's embed script once (popup mode)
+ * - Exposes a simple props API so MDX controls the content
+ */
+export default function SelfGuidedTours({ cards }: Props) {
+  return (
+    <>
+      {/* Navattic embed loader (newer API) */}
+      <Script src="https://js.navattic.com/embeds.js" strategy="afterInteractive" />
+
+      {/* Grid */}
+      <div style={styles.grid}>
+        {cards.map((c, i) => (
+          <CardView key={i} c={c} />
+        ))}
+      </div>
+
+      {/* Theme variables + interactions */}
+      <style jsx global>{`
+        /* ---- Dark defaults ---- */
+        :root {
+          --sgt-card-bg: #0a0a0b;
+          --sgt-title: #ffffff;
+          --sgt-blurb: rgba(255, 255, 255, 0.85);
+          --sgt-border: ${MP_PURPLE};
+          --sgt-media-bg: #111111;
+          --sgt-dogear: ${MP_PURPLE};
+          --sgt-badge-bg: ${MP_PURPLE};
+          --sgt-badge-fg: #ffffff;
+        }
+
+        /* ---- Prefer light scheme (also covered below by class/attr) ---- */
+        @media (prefers-color-scheme: light) {
+          :root,
+          html.light,
+          html[class*='light'],
+          [data-theme='light'] {
+            --sgt-card-bg: #ffffff;
+            --sgt-title: #111111;
+            --sgt-blurb: #333333;
+            --sgt-border: ${MP_PURPLE};
+            --sgt-media-bg: #e9e9ef;
+            --sgt-dogear: ${MP_PURPLE};
+            --sgt-badge-bg: ${MP_PURPLE};
+            --sgt-badge-fg: #ffffff;
+          }
+        }
+
+        /* ---- Explicit site light mode (Mixpanel Docs sets html.light) ---- */
+        html.light,
+        html[class*='light'],
+        [data-theme='light'] {
+          --sgt-card-bg: #ffffff;
+          --sgt-title: #111111;
+          --sgt-blurb: #333333;
+          --sgt-border: ${MP_PURPLE};
+          --sgt-media-bg: #e9e9ef;
+          --sgt-dogear: ${MP_PURPLE};
+          --sgt-badge-bg: ${MP_PURPLE};
+          --sgt-badge-fg: #ffffff;
+        }
+
+        /* ---- Card base colors ---- */
+        .sgt-card {
+          background: var(--sgt-card-bg);
+          color: var(--sgt-title);
+          border-color: var(--sgt-border);
+        }
+
+        /* ---- Micro-interactions ---- */
+        .sgt-card:hover {
+          transform: translateY(-2px);
+          box-shadow: 0 8px 24px rgba(139, 92, 246, 0.25);
+        }
+        .sgt-card:focus-within {
+          outline: 2px solid ${MP_PURPLE};
+          outline-offset: 2px;
+        }
+        .sgt-click:focus-visible {
+          outline: 2px solid ${MP_PURPLE};
+          outline-offset: 3px;
+          border-radius: 10px;
+        }
+
+        /* ---- Responsive type bump on very wide screens ---- */
+        @media (min-width: 1280px) {
+          .sgt-card h3 { font-size: 24px; }
+          .sgt-card p { font-size: 15px; }
+        }
+      `}</style>
+    </>
+  );
+}
\ No newline at end of file
diff --git a/components/svg/NavIcon.tsx b/components/svg/NavIcon.tsx
index 1f4126bf9c..86e0510cc8 100644
--- a/components/svg/NavIcon.tsx
+++ b/components/svg/NavIcon.tsx
@@ -73,6 +73,42 @@ function SupportIcon() {
     )
 }
 
+function SolutionsIcon() {
+    return (
+        <svg width="15" height="16" viewBox="0 0 15 16" fill="none" xmlns="http://www.w3.org/2000/svg">
+            <rect x="3.29968" y="14.3158" width="8.13757" height="1.68421" rx="0.842105" fill="#7856FF"/>
+            <path d="M0.0896984 13.3204C0.562919 10.7428 2.77594 9.27982 3.52632 8.8421H4.42105V14.3158H1C0.447715 14.3158 -0.0100294 13.8636 0.0896984 13.3204Z" fill="#7856FF"/>
+            <path d="M14.6471 13.3204C14.1739 10.7428 11.9609 9.27982 11.2105 8.8421H10.3158V14.3158H13.7368C14.2891 14.3158 14.7468 13.8636 14.6471 13.3204Z" fill="#7856FF"/>
+            <path d="M4.42107 14.3158L3.60288 12.4976C1.83768 8.57492 2.84346 3.95936 6.08071 1.12676C6.81799 0.481635 7.91887 0.481635 8.65616 1.12676C11.8934 3.95936 12.8992 8.57492 11.134 12.4976L10.3158 14.3158H4.42107Z" fill="#B094FF"/>
+            <circle cx="7.36836" cy="8.42106" r="2.52632" fill="#7856FF"/>
+            <path fill-rule="evenodd" clip-rule="evenodd" d="M11.2042 4.63158H3.53271C4.09604 3.3167 4.95298 2.11354 6.08073 1.12676C6.81802 0.481633 7.9189 0.481632 8.65618 1.12676C9.78393 2.11354 10.6409 3.3167 11.2042 4.63158Z" fill="#7856FF"/>
+        </svg>
+    )
+}
+
+function PlaybooksIcon() {
+    return (
+        <svg width="18" height="16" viewBox="0 0 18 16" fill="none" xmlns="http://www.w3.org/2000/svg">
+            <path d="M2 0H11.3333C12.4379 0 13.3333 0.895431 13.3333 2V14C13.3333 15.1046 12.4379 16 11.3333 16H2C0.895431 16 0 15.1046 0 14V2C0 0.895431 0.895428 0 2 0Z" fill="#B094FF"/>
+            <path d="M5.33332 12H2.66666" stroke="#7856FF" stroke-linecap="round" stroke-linejoin="round"/>
+            <path d="M5.33332 8H2.66666" stroke="#7856FF" stroke-linecap="round" stroke-linejoin="round"/>
+            <path d="M7.99999 4H2.66666" stroke="#7856FF" stroke-linecap="round" stroke-linejoin="round"/>
+            <path d="M8 7.99999V12H12L15.3333 8.66666C16.4379 7.56209 16.4379 5.77123 15.3333 4.66666C14.2288 3.56209 12.4379 3.56209 11.3333 4.66666L8 7.99999Z" fill="#B094FF" stroke="#7856FF" stroke-linejoin="round"/>
+        </svg>
+    )
+}
+
+function DiscoverIcon() {
+    return (
+        <svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg">
+            <path d="M14.2857 6.85714H13.7143C13.0831 6.85714 12.5714 7.36882 12.5714 8C12.5714 8.63118 13.0831 9.14286 13.7143 9.14286H14.2857C15.2325 9.14286 16 9.91037 16 10.8571V14C16 15.1046 15.1046 16 14 16H10.8571C9.91037 16 9.14286 15.2325 9.14286 14.2857V13.7143C9.14286 13.0831 8.63118 12.5714 8 12.5714C7.36882 12.5714 6.85714 13.0831 6.85714 13.7143V14.2857C6.85714 15.2325 6.08963 16 5.14286 16H2C0.895431 16 0 15.1046 0 14V10.8571C0 9.91037 0.767511 9.14286 1.71429 9.14286H2.28571C2.9169 9.14286 3.42857 8.63118 3.42857 8C3.42857 7.36882 2.9169 6.85714 2.28572 6.85714H1.71429C0.767512 6.85714 0 6.08963 0 5.14286V2C0 0.895431 0.89543 0 2 0H5.14286C6.08963 0 6.85714 0.767511 6.85714 1.71429V2.28571C6.85714 2.9169 7.36882 3.42857 8 3.42857C8.63118 3.42857 9.14286 2.9169 9.14286 2.28572V1.71429C9.14286 0.767512 9.91037 0 10.8571 0H14C15.1046 0 16 0.89543 16 2V5.14286C16 6.08963 15.2325 6.85714 14.2857 6.85714Z" fill="#B094FF"/>
+            <path d="M6.66669 5.33334V6.66668" stroke="#7856FF" stroke-linecap="round" stroke-linejoin="round"/>
+            <path d="M9.33331 5.33334V6.66668" stroke="#7856FF" stroke-linecap="round" stroke-linejoin="round"/>
+            <path d="M5.33331 8C5.55554 8.44444 6.39998 9.33333 7.99998 9.33333C9.59998 9.33333 10.4444 8.44444 10.6666 8" stroke="#7856FF" stroke-linecap="round"/>
+        </svg>
+    )
+}
+
 export {
     IntroIcon,
     DataInIcon,
@@ -80,4 +116,7 @@ export {
     AdminIcon,
     DataOutIcon,
     SupportIcon,
+    SolutionsIcon,
+    PlaybooksIcon,
+    DiscoverIcon
 };
diff --git a/cspell.json b/cspell.json
index 725970207c..1b2a72991b 100644
--- a/cspell.json
+++ b/cspell.json
@@ -75,6 +75,13 @@
     "cloudfunctions",
     "cloudimport",
     "clsx",
+    "cmapktdk",
+    "cmbrua",
+    "cmdrjulgv",
+    "cmead",
+    "cmer",
+    "cmfciul",
+    "cmfkxwfa",
     "cnlhbjpye",
     "Cocoapods",
     "cohorting",
@@ -128,6 +135,7 @@
     "gtag",
     "headlessui",
     "herokuapp",
+    "hgwo",
     "hideunhide",
     "Hightouch",
     "hllsketch",
@@ -149,6 +157,7 @@
     "Jayaram",
     "JDBC",
     "Jetpack",
+    "jkmbvpg",
     "Kameleoon",
     "Kapa",
     "Kapture",
@@ -157,6 +166,7 @@
     "Mailchimp",
     "Marketo",
     "Maxmind",
+    "misclick",
     "mixpanelapi",
     "Mixpanelers",
     "moengage",
@@ -173,6 +183,7 @@
     "mxpnl",
     "MYAPP",
     "mytoken",
+    "navattic",
     "nessie",
     "Next.js",
     "nextjs",
@@ -180,6 +191,7 @@
     "objc",
     "Onelogin",
     "onesignal",
+    "OADA",
     "openapi",
     "Overcomplicating",
     "pageview",
@@ -234,11 +246,13 @@
     "splitlines",
     "SPRT",
     "Stackdriver",
+    "standups",
     "stddev",
     "Steph",
     "struct",
     "sumable",
     "Sunrostern",
+    "Sunsetting",
     "superpropname",
     "superpropvalue",
     "tablename",
@@ -275,6 +289,8 @@
     "urlencode",
     "urllib",
     "urlparse",
+    "Usership",
+    "usership",
     "utag",
     "utagdb",
     "Varbyte",
@@ -302,6 +318,8 @@
     "yourfullname",
     "YOURPROJECT",
     "zzhaystackzz",
+    "zabd",
+    "zwaeqor",
     "NORTHAMERICA",
     "SOUTHAMERICA"
   ],
@@ -315,4 +333,4 @@
       "addWords": true
     }
   ]
-}
\ No newline at end of file
+}
diff --git a/middleware.ts b/middleware.ts
index 9b5df4907d..f5bd331d10 100644
--- a/middleware.ts
+++ b/middleware.ts
@@ -6,7 +6,7 @@ export function middleware() {
   // Set custom header
   response.headers.set(`X-Frame-Options`, `deny`);
   response.headers.set(`X-Content-Type-Options`, `nosniff`);
-  response.headers.set(`Content-Security-Policy`, `default-src 'self' https://*.mixpanel.com https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://ekr.zendesk.com wss://mixpanelsupport.zendesk.com https://mixpanel.com https://*.mixpanel.com; script-src 'self' 'unsafe-eval' 'unsafe-inline' https://*.kapa.ai https://*.hotjar.com https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://cdn.rollbar.com https://*.zopim.com https://assets.zendesk.com https://www.youtube.com/embed/ https://connect.facebook.net https://apis.google.com https://accounts.google.com 'unsafe-eval' https://*.6sc.co https://*.bing.com https://*.clarity.ms https://cdnjs.cloudflare.com d2wy8f7a9ursnm.cloudfront.net https://*.doubleclick.net https://*.google.com https://*.google-analytics.com https://*.googlesyndication.com https://www.googletagmanager.com https://*.gstatic.cn https://*.gstatic.com https://*.g2crowd.com https://snap.licdn.com https://*.marketo.com https://*.marketo.net https://mixpanel.com https://*.mixpanel.com https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ https://recaptcha.net https://*.recaptcha.net https://www.redditstatic.com/ads/ https://*.singular.net https://*.ads-twitter.com https://mxpnlcms.wpengine.com https://*.youtube.com https://*.zoominfo.com https://cdn.sprig.com; connect-src 'self' blob: data: https://kapa-widget-proxy-la7dkmplpq-uc.a.run.app https://*.hotjar.com wss://*.hotjar.com https://*.hotjar.io https://*.mixpanel.com https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://api.rollbar.com https://api.sprig.com https://cdn.sprig.com https://*.zdassets.com https://mixpanelsupport.zendesk.com https://*.zopim.com wss://*.zopim.com https://storage.googleapis.com https://*.facebook.com https://*.6sc.co https://*.adnxs.com https://*.bing.com https://*.bugsnag.com https://*.clarity.ms https://*.doubleclick.net https://*.google.com https://*.google-analytics.com https://*.googlesyndication.com https://*.g2crowd.com https://*.linkedin.com https://mixpanel.com https://*.mixpanel.com https://*.mktoresp.com https://cdn.linkedin.oribi.io https://*.reddit.com https://www.redditstatic.com/ads/ https://*.singular.net https://mxpnlcms.wpengine.com https://*.zoominfo.com; media-src 'self' https://user-images.githubusercontent.com; img-src 'self' blob: data: https://www.google.com https://*.gstatic.com  https://t2.gstatic.com https://github-production-user-asset-6210df.s3.amazonaws.com https://github.com https://user-images.githubusercontent.com https://avatars.githubusercontent.com/ https://*.chmln-cdn.com https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://*.zdassets.com https://*.zopim.com https://v2uploads.zopim.io https://*.facebook.com https://*.gravatar.com https://*.wp.com https://*.6sc.co https://*.adnxs.com https://*.adroll.com https://*.bidswitch.net https://*.bing.com https://cdn.bizible.com https://cdn.bizibly.com https://*.bugsnag.com https://*.casalemedia.com https://*.clarity.ms https://*.crwdcntrl.net https://*.doubleclick.net https://*.exelator.com https://*.google-analytics.com https://*.googlesyndication.com https://www.googletagmanager.com https://*.googleusercontent.com https://*.imrworldwide.com https://*.linkedin.com https://mixpanel.com https://*.mixpanel.com https://*.reddit.com https://t.co/ https://analytics.twitter.com https://*.wpengine.com https://mxpnlcms.wpengine.com https://mxpnlcms.wpenginepowered.com https://*.analytics.yahoo.com https://*.google.com https://*.google.ad https://*.google.ae https://*.google.com.af https://*.google.com.ag https://*.google.al https://*.google.am https://*.google.co.ao https://*.google.com.ar https://*.google.as https://*.google.at https://*.google.com.au https://*.google.az https://*.google.ba https://*.google.com.bd https://*.google.be https://*.google.bf https://*.google.bg https://*.google.com.bh https://*.google.bi https://*.google.bj https://*.google.com.bn https://*.google.com.bo https://*.google.com.br https://*.google.bs https://*.google.bt https://*.google.co.bw https://*.google.by https://*.google.com.bz https://*.google.ca https://*.google.cd https://*.google.cf https://*.google.cg https://*.google.ch https://*.google.ci https://*.google.co.ck https://*.google.cl https://*.google.cm https://*.google.cn https://*.google.com.co https://*.google.co.cr https://*.google.com.cu https://*.google.cv https://*.google.com.cy https://*.google.cz https://*.google.de https://*.google.dj https://*.google.dk https://*.google.dm https://*.google.com.do https://*.google.dz https://*.google.com.ec https://*.google.ee https://*.google.com.eg https://*.google.es https://*.google.com.et https://*.google.fi https://*.google.com.fj https://*.google.fm https://*.google.fr https://*.google.ga https://*.google.ge https://*.google.gg https://*.google.com.gh https://*.google.com.gi https://*.google.gl https://*.google.gm https://*.google.gr https://*.google.com.gt https://*.google.gy https://*.google.com.hk https://*.google.hn https://*.google.hr https://*.google.ht https://*.google.hu https://*.google.co.id https://*.google.ie https://*.google.co.il https://*.google.im https://*.google.co.in https://*.google.iq https://*.google.is https://*.google.it https://*.google.je https://*.google.com.jm https://*.google.jo https://*.google.co.jp https://*.google.co.ke https://*.google.com.kh https://*.google.ki https://*.google.kg https://*.google.co.kr https://*.google.com.kw https://*.google.kz https://*.google.la https://*.google.com.lb https://*.google.li https://*.google.lk https://*.google.co.ls https://*.google.lt https://*.google.lu https://*.google.lv https://*.google.com.ly https://*.google.co.ma https://*.google.md https://*.google.me https://*.google.mg https://*.google.mk https://*.google.ml https://*.google.com.mm https://*.google.mn https://*.google.com.mt https://*.google.mu https://*.google.mv https://*.google.mw https://*.google.com.mx https://*.google.com.my https://*.google.co.mz https://*.google.com.na https://*.google.com.ng https://*.google.com.ni https://*.google.ne https://*.google.nl https://*.google.no https://*.google.com.np https://*.google.nr https://*.google.nu https://*.google.co.nz https://*.google.com.om https://*.google.com.pa https://*.google.com.pe https://*.google.com.pg https://*.google.com.ph https://*.google.com.pk https://*.google.pl https://*.google.pn https://*.google.com.pr https://*.google.ps https://*.google.pt https://*.google.com.py https://*.google.com.qa https://*.google.ro https://*.google.ru https://*.google.rw https://*.google.com.sa https://*.google.com.sb https://*.google.sc https://*.google.se https://*.google.com.sg https://*.google.sh https://*.google.si https://*.google.sk https://*.google.com.sl https://*.google.sn https://*.google.so https://*.google.sm https://*.google.sr https://*.google.st https://*.google.com.sv https://*.google.td https://*.google.tg https://*.google.co.th https://*.google.com.tj https://*.google.tl https://*.google.tm https://*.google.tn https://*.google.to https://*.google.com.tr https://*.google.tt https://*.google.com.tw https://*.google.co.tz https://*.google.com.ua https://*.google.co.ug https://*.google.co.uk https://*.google.com.uy https://*.google.co.uz https://*.google.com.vc https://*.google.co.ve https://*.google.co.vi https://*.google.com.vn https://*.google.vu https://*.google.ws https://*.google.rs https://*.google.co.za https://*.google.co.zm https://*.google.co.zw https://*.google.cat; style-src 'self' 'unsafe-inline' https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://*.google.com https://*.marketo.com https://mixpanel.com https://*.mixpanel.com https://hello.myfonts.net; font-src 'self' data: https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://mixpanel.com https://*.mixpanel.com; frame-src 'self' https://www.googletagmanager.com https://js.stripe.com https://www.loom.com/embed/ https://player.vimeo.com/video/ https://www.youtube.com/embed/ https://*.facebook.com https://accounts.google.com https://static.addtoany.com https://*.bing.com https://*.doubleclick.net https://*.google.com https://*.marketo.com https://mixpanel.com https://*.mixpanel.com https://www.google.com/recaptcha/ https://recaptcha.google.com/recaptcha/ https://recaptcha.net https://*.recaptcha.net; worker-src 'self' blob:;`);
+  response.headers.set(`Content-Security-Policy`, `default-src 'self' https://*.mixpanel.com https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://ekr.zendesk.com wss://mixpanelsupport.zendesk.com https://mixpanel.com https://*.mixpanel.com; script-src 'self' 'unsafe-eval' 'unsafe-inline' https://*.kapa.ai https://*.hotjar.com https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://cdn.rollbar.com https://*.zopim.com https://assets.zendesk.com https://www.youtube.com/embed/ https://connect.facebook.net https://apis.google.com https://accounts.google.com 'unsafe-eval' https://*.6sc.co https://*.bing.com https://*.clarity.ms https://cdnjs.cloudflare.com d2wy8f7a9ursnm.cloudfront.net https://*.doubleclick.net https://*.google.com https://*.google-analytics.com https://*.googlesyndication.com https://www.googletagmanager.com https://*.gstatic.cn https://*.gstatic.com https://*.g2crowd.com https://snap.licdn.com https://*.marketo.com https://*.marketo.net https://mixpanel.com https://*.mixpanel.com https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ https://recaptcha.net https://*.recaptcha.net https://www.redditstatic.com/ads/ https://*.singular.net https://*.ads-twitter.com https://mxpnlcms.wpengine.com https://*.youtube.com https://*.zoominfo.com https://cdn.sprig.com https://js.navattic.com; connect-src 'self' blob: data: https://kapa-widget-proxy-la7dkmplpq-uc.a.run.app https://*.hotjar.com wss://*.hotjar.com https://*.hotjar.io https://*.mixpanel.com https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://api.rollbar.com https://api.sprig.com https://cdn.sprig.com https://*.zdassets.com https://mixpanelsupport.zendesk.com https://*.zopim.com wss://*.zopim.com https://storage.googleapis.com https://*.facebook.com https://*.6sc.co https://*.adnxs.com https://*.bing.com https://*.bugsnag.com https://*.clarity.ms https://*.doubleclick.net https://*.google.com https://*.google-analytics.com https://*.googlesyndication.com https://*.g2crowd.com https://*.linkedin.com https://mixpanel.com https://*.mixpanel.com https://*.mktoresp.com https://cdn.linkedin.oribi.io https://*.reddit.com https://www.redditstatic.com/ads/ https://*.singular.net https://mxpnlcms.wpengine.com https://*.zoominfo.com; media-src 'self' https://user-images.githubusercontent.com; img-src 'self' blob: data: https://www.google.com https://*.gstatic.com  https://t2.gstatic.com https://github-production-user-asset-6210df.s3.amazonaws.com https://github.com https://user-images.githubusercontent.com https://avatars.githubusercontent.com/ https://*.chmln-cdn.com https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://*.zdassets.com https://*.zopim.com https://v2uploads.zopim.io https://*.facebook.com https://*.gravatar.com https://*.wp.com https://*.6sc.co https://*.adnxs.com https://*.adroll.com https://*.bidswitch.net https://*.bing.com https://cdn.bizible.com https://cdn.bizibly.com https://*.bugsnag.com https://*.casalemedia.com https://*.clarity.ms https://*.crwdcntrl.net https://*.doubleclick.net https://*.exelator.com https://*.google-analytics.com https://*.googlesyndication.com https://www.googletagmanager.com https://*.googleusercontent.com https://*.imrworldwide.com https://*.linkedin.com https://mixpanel.com https://*.mixpanel.com https://*.reddit.com https://t.co/ https://analytics.twitter.com https://*.wpengine.com https://mxpnlcms.wpengine.com https://mxpnlcms.wpenginepowered.com https://*.analytics.yahoo.com https://*.google.com https://*.google.ad https://*.google.ae https://*.google.com.af https://*.google.com.ag https://*.google.al https://*.google.am https://*.google.co.ao https://*.google.com.ar https://*.google.as https://*.google.at https://*.google.com.au https://*.google.az https://*.google.ba https://*.google.com.bd https://*.google.be https://*.google.bf https://*.google.bg https://*.google.com.bh https://*.google.bi https://*.google.bj https://*.google.com.bn https://*.google.com.bo https://*.google.com.br https://*.google.bs https://*.google.bt https://*.google.co.bw https://*.google.by https://*.google.com.bz https://*.google.ca https://*.google.cd https://*.google.cf https://*.google.cg https://*.google.ch https://*.google.ci https://*.google.co.ck https://*.google.cl https://*.google.cm https://*.google.cn https://*.google.com.co https://*.google.co.cr https://*.google.com.cu https://*.google.cv https://*.google.com.cy https://*.google.cz https://*.google.de https://*.google.dj https://*.google.dk https://*.google.dm https://*.google.com.do https://*.google.dz https://*.google.com.ec https://*.google.ee https://*.google.com.eg https://*.google.es https://*.google.com.et https://*.google.fi https://*.google.com.fj https://*.google.fm https://*.google.fr https://*.google.ga https://*.google.ge https://*.google.gg https://*.google.com.gh https://*.google.com.gi https://*.google.gl https://*.google.gm https://*.google.gr https://*.google.com.gt https://*.google.gy https://*.google.com.hk https://*.google.hn https://*.google.hr https://*.google.ht https://*.google.hu https://*.google.co.id https://*.google.ie https://*.google.co.il https://*.google.im https://*.google.co.in https://*.google.iq https://*.google.is https://*.google.it https://*.google.je https://*.google.com.jm https://*.google.jo https://*.google.co.jp https://*.google.co.ke https://*.google.com.kh https://*.google.ki https://*.google.kg https://*.google.co.kr https://*.google.com.kw https://*.google.kz https://*.google.la https://*.google.com.lb https://*.google.li https://*.google.lk https://*.google.co.ls https://*.google.lt https://*.google.lu https://*.google.lv https://*.google.com.ly https://*.google.co.ma https://*.google.md https://*.google.me https://*.google.mg https://*.google.mk https://*.google.ml https://*.google.com.mm https://*.google.mn https://*.google.com.mt https://*.google.mu https://*.google.mv https://*.google.mw https://*.google.com.mx https://*.google.com.my https://*.google.co.mz https://*.google.com.na https://*.google.com.ng https://*.google.com.ni https://*.google.ne https://*.google.nl https://*.google.no https://*.google.com.np https://*.google.nr https://*.google.nu https://*.google.co.nz https://*.google.com.om https://*.google.com.pa https://*.google.com.pe https://*.google.com.pg https://*.google.com.ph https://*.google.com.pk https://*.google.pl https://*.google.pn https://*.google.com.pr https://*.google.ps https://*.google.pt https://*.google.com.py https://*.google.com.qa https://*.google.ro https://*.google.ru https://*.google.rw https://*.google.com.sa https://*.google.com.sb https://*.google.sc https://*.google.se https://*.google.com.sg https://*.google.sh https://*.google.si https://*.google.sk https://*.google.com.sl https://*.google.sn https://*.google.so https://*.google.sm https://*.google.sr https://*.google.st https://*.google.com.sv https://*.google.td https://*.google.tg https://*.google.co.th https://*.google.com.tj https://*.google.tl https://*.google.tm https://*.google.tn https://*.google.to https://*.google.com.tr https://*.google.tt https://*.google.com.tw https://*.google.co.tz https://*.google.com.ua https://*.google.co.ug https://*.google.co.uk https://*.google.com.uy https://*.google.co.uz https://*.google.com.vc https://*.google.co.ve https://*.google.co.vi https://*.google.com.vn https://*.google.vu https://*.google.ws https://*.google.rs https://*.google.co.za https://*.google.co.zm https://*.google.co.zw https://*.google.cat; style-src 'self' 'unsafe-inline' https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://*.google.com https://*.marketo.com https://mixpanel.com https://*.mixpanel.com https://hello.myfonts.net; font-src 'self' data: https://cdn.mxpnl.com https://cdn-dev.mxpnl.com https://mixpanel.com https://*.mixpanel.com; frame-src 'self' https://www.googletagmanager.com https://js.stripe.com https://www.loom.com/embed/ https://player.vimeo.com/video/ https://www.youtube.com/embed/ https://*.facebook.com https://accounts.google.com https://static.addtoany.com https://*.bing.com https://*.doubleclick.net https://*.google.com https://*.marketo.com https://mixpanel.com https://*.mixpanel.com https://www.google.com/recaptcha/ https://recaptcha.google.com/recaptcha/ https://recaptcha.net https://*.recaptcha.net https://capture.navattic.com; worker-src 'self' blob:;`);
   response.headers.set(`X-Permitted-Cross-Domain-Policies`, `none`);
   response.headers.set(`Referrer-Policy`, `strict-origin`);
   response.headers.set(`Permissions-Policy`, `accelerometer=(), camera=(), encrypted-media=(self "https://www.youtube.com" "https://www.loom.com"), fullscreen=(self "https://www.youtube.com" "https://www.loom.com"), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), usb=()`);
diff --git a/pages/docs/features/_meta.ts b/pages/docs/features/_meta.ts
index 733b881622..b7d943292a 100644
--- a/pages/docs/features/_meta.ts
+++ b/pages/docs/features/_meta.ts
@@ -5,9 +5,10 @@ export default {
     "chart-customization": "Chart Customization",
     "custom-buckets": "Custom Buckets",
     "custom-events": "Custom Events",
-    "computed-properties": "Computed Properties",
     "custom-properties": "Custom Properties",
+    "computed-properties": "Computed Properties",
     "mcp": "MCP Integration",
+    "revenue-analytics": "Revenue Analytics",
     "saved-metrics-and-behaviors": "Saved Metrics & Behaviors",
     "sessions": "Sessions",
     "slack-integration": "Slack Integration",
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/revenue-analytics.mdx b/pages/docs/features/revenue-analytics.mdx
similarity index 100%
rename from pages/guides/strategic-playbooks/onboarding-playbook/launch/revenue-analytics.mdx
rename to pages/docs/features/revenue-analytics.mdx
diff --git a/pages/guides/_meta.ts b/pages/guides/_meta.ts
deleted file mode 100644
index 4a816478f9..0000000000
--- a/pages/guides/_meta.ts
+++ /dev/null
@@ -1,22 +0,0 @@
-export default {
-	"discover-mixpanel": {
-		"type": "separator",
-		"title": "DISCOVER MIXPANEL"
-	},
-	"what-is-mixpanel": "What is Mixpanel?",
-	"changelog": {
-    	title: "What's New? ↗",
-    	href: "/changelogs",
-		newWindow: true
-  	},
-	"solutions-and-workflows": {
-		"type": "separator",
-		"title": "SOLUTIONS & WORKFLOWS"
-	},
-	"guides-by-use-case": "Guides by Use Case",
-	"best-practices-and-playbooks": {
-		"type": "separator",
-		"title": "BEST PRACTICES & PLAYBOOKS"
-	},
-	"strategic-playbooks": "Strategic Playbooks"
-}
diff --git a/pages/guides/_meta.tsx b/pages/guides/_meta.tsx
new file mode 100644
index 0000000000..18dcf589cb
--- /dev/null
+++ b/pages/guides/_meta.tsx
@@ -0,0 +1,42 @@
+import { SolutionsIcon,PlaybooksIcon,DiscoverIcon } from "../../components/svg/NavIcon";
+
+import style from "../docs/sidebar.module.scss";
+
+export default {
+  "discover-mixpanel": {
+    type: "separator",
+    title: (
+      <div className={style.titleContainer}>
+        <DiscoverIcon /> DISCOVER
+      </div>
+    ),
+  },
+  "mixpanel-introduction": "Mixpanel Introduction",
+  "self-guided-tours": "Self Guided Tours",
+  "changelog": {
+      title: "What's New? ↗",
+      href: "/changelogs",
+    newWindow: true
+    },
+  "solutions-and-workflows": {
+    type: "separator",
+    title: (
+      <div className={style.titleContainer}>
+        <SolutionsIcon /> WORKFLOWS
+      </div>
+    ),
+  },
+  "guides-by-use-case": "Guides by Use Case",
+  "guides-by-workflow": "Guides by Workflow",
+  "guides-by-topic": "Guides by Topic",
+  "best-practices-and-playbooks": {
+    type: "separator",
+    title: (
+      <div className={style.titleContainer}>
+        <PlaybooksIcon /> PLAYBOOKS
+      </div>
+    ),
+  },
+  "benchmarks": "Benchmarks",
+  "strategic-playbooks": "Strategic Playbooks"
+}
diff --git a/pages/guides/benchmarks.mdx b/pages/guides/benchmarks.mdx
new file mode 100644
index 0000000000..07c895bd0c
--- /dev/null
+++ b/pages/guides/benchmarks.mdx
@@ -0,0 +1,27 @@
+import { Cards } from 'nextra/components'
+
+# Benchmarks & Analytics Maturity
+Understand performance benchmarks and assess your organization’s analytics maturity. Whether you’re setting goals, comparing performance against peers, or looking for ways to advance your analytics practice, these resources will help guide your next steps.
+
+## Benchmarks
+See product performance baselines across conversion, retention, and engagement. Use these as north stars to calibrate goals and identify outliers.
+
+<Cards>
+  <Cards.Card title="Product Analytics Benchmarks" href="https://mixpanel.com/benchmarks/" target="_blank" />
+</Cards>
+
+## Benchmarks by Industry
+Drill into industry-specific norms to set context-rich targets. 
+
+<Cards>
+  <Cards.Card title="Ecommerce" href="https://mixpanel.com/m/ecommerce-benchmarks-2024/" target="_blank" />
+  <Cards.Card title="Fintech" href="https://mixpanel.com/m/benchmarks-report-2025-fintech/" target="_blank" />
+  <Cards.Card title="Media & Entertainment" href="https://mixpanel.com/m/benchmarks-report-2025-media-entertainment/" target="_blank" />
+</Cards>
+
+## Analytics Maturity
+Assess where your org sits on the analytics maturity curve and chart the next moves to unlock impact.
+
+<Cards>
+  <Cards.Card title="Analytics Maturity" href="https://mixpanel.com/content/product-analytics-strategy/get-started/" target="_blank" />
+</Cards>
\ No newline at end of file
diff --git a/pages/guides/guides-by-topic/_meta.ts b/pages/guides/guides-by-topic/_meta.ts
new file mode 100644
index 0000000000..d26e366012
--- /dev/null
+++ b/pages/guides/guides-by-topic/_meta.ts
@@ -0,0 +1,5 @@
+export default {
+    "continuous-innovation": "Continuous Innovation",
+    "features": "Features",
+    "core-reports": "Core Reports"
+}
\ No newline at end of file
diff --git a/pages/guides/guides-by-topic/continuous-innovation.mdx b/pages/guides/guides-by-topic/continuous-innovation.mdx
new file mode 100644
index 0000000000..c5d89d81f6
--- /dev/null
+++ b/pages/guides/guides-by-topic/continuous-innovation.mdx
@@ -0,0 +1,240 @@
+import { Callout, Steps } from 'nextra/components'
+
+# Mixpanel and the Continuous Innovation Loop
+The **Observe → Analyze → Decide → Act (OADA)** loop is the framework behind how great teams use Mixpanel to continuously innovate.
+
+![OADA Loop diagram](/oada-loop-detail.png)
+
+This loop represents the cycle teams follow to turn data into action by first observing what users do, then analyzing why it happens, deciding what to do next, and finally acting on those insights to drive better outcomes.
+
+Each phase represents a key moment in the product decision cycle–—and Mixpanel provides the tools to complete that loop faster with every iteration.
+
+<Callout type="info">
+**Why it matters:** Teams that move through the loop quickly learn what’s working, align faster, and deliver more impactful product improvements.
+</Callout>
+---
+
+## Why Continuous Innovation Matters
+
+Building great products isn’t just about speed—–it’s about learning continuously.
+
+Markets shift, user expectations evolve, and what worked last quarter might not work tomorrow. The teams that win are the ones that turn data into a *habit of improvement* by observing what users do, analyzing why it happens, deciding what to do next, and acting with confidence.
+
+Teams that move through the OADA loop quickly:
+- Learn what’s working and what’s not
+- Align on priorities faster
+- Deliver more impactful product improvements with each iteration
+
+<Callout type="info">
+**Pro tip**: Make closing the loop part of every sprint–—observe, analyze, decide, act.
+</Callout>
+
+Digital innovation isn’t a one-time project. It’s a continuous cycle of learning and improvement.
+
+---
+
+## How Different Industries Use the Continuous Loop
+
+Mixpanel powers the OADA loop across every industry--helping teams turn data into confident action. 
+
+Whether you’re optimizing user onboarding, increasing checkout conversions, or improving content engagement, the same continuous loop applies. 
+
+Below are examples of how teams in different industries use Mixpanel to measure, learn, and grow faster.
+
+<details>
+<summary style={{ fontSize: '1.15rem', fontWeight: 600 }}><strong>💼 SaaS: Improving Onboarding and Activation</strong></summary>
+
+<br></br>A SaaS team observes where new users drop off during onboarding, analyzes key behaviors to uncover friction points, decides which improvements will reduce time-to-value, and acts by testing guided experiences that drive activation and retention.
+
+---
+
+**Observe** <br></br>
+The team monitors early-user activity using **Session Replay**, **Heatmaps**, and **Autocapture** to see how new users interact with the onboarding flow: *Account Created → Tutorial Completed → Key Action Taken*. They set up **Alerts** to track sudden drops in completion.
+
+---
+
+**Analyze** <br></br>
+Using **Funnels**, **Flows**, and **Cohorts**, the team identifies where users are stalling and compares completion across personas. Behavioral trends show that users who skip the advanced configuration step activate faster.
+
+| Tool | Observation | Insight |
+|------|--------------|----------|
+| **Funnels & Flows** | 45% drop-off between “Account Created” and “Tutorial Completed” | Users struggle with early onboarding complexity. |
+| **Cohorts** | Different activation rates by persona | Simpler onboarding correlates with higher early success. |
+| **Session Replay** | Confusion at advanced setup screens | Users hesitate when asked to complete optional steps too soon. |
+
+---
+
+**Decide** <br></br>
+The team uses **Metric Trees** to understand which metrics--like “First Value Reached”--drive long-term retention. They decide to move optional setup later in the journey and emphasize the first “aha” moment sooner.
+
+---
+
+**Act** <br></br>
+They test this change through **Experiments**, rolling out a new guided flow to a subset of users. When the experiment shows faster activation and higher retention, they launch it to all users using **Feature Flags**.
+
+---
+
+**✨ Result:** Activation improves 15%, and new users reach value faster with fewer drop-offs.
+<br></br>
+</details>
+
+
+
+<details>
+<summary style={{ fontSize: '1.15rem', fontWeight: 600 }}><strong>🛍️ eCommerce: Increasing Checkout Conversion</strong></summary>
+
+<br></br>An eCommerce team observes shopper behavior throughout checkout, analyzes patterns to uncover mobile friction, decides which optimizations will improve conversion, and acts by testing streamlined checkout designs.
+
+---
+
+**Observe** <br></br>
+Using **Session Replay**, **Heatmaps**, and **Autocapture**, the team tracks the path from *Product Viewed → Added to Cart → Checkout Started → Purchase Completed* to see where users abandon the flow.  
+
+---
+
+**Analyze** <br></br>
+Through **Funnels**, **Cohorts**, and **Retention**, the team identifies a 40% drop-off at payment on mobile devices.  
+
+| Tool | Observation | Insight |
+|------|--------------|----------|
+| **Funnels** | 40% mobile drop-off at payment | Checkout fields are too dense for mobile screens. |
+| **Session Replay & Heatmaps** | Users zoom and misclick on payment fields | UI not optimized for mobile input. |
+
+---
+
+**Decide** <br></br>
+The team leverages **Metric Trees** to link checkout completion to revenue impact. They decide to simplify payment forms and surface the most-used payment options first.
+
+---
+
+**Act** <br></br>
+They deploy a **Feature Flag** to release the redesigned checkout to 50% of traffic and use **Experiments** to confirm conversion improvements before rolling it out universally.
+
+---
+
+**✨ Result:** Checkout completion rises 20%, and mobile shoppers complete purchases faster with fewer errors.
+<br></br>
+</details>
+
+
+
+<details>
+<summary style={{ fontSize: '1.15rem', fontWeight: 600 }}><strong>🎬 Media & Entertainment: Boosting Viewer Retention</strong></summary>
+
+<br></br>A streaming platform observes viewer engagement across content, analyzes which experiences retain audiences, decides how to personalize recommendations, and acts by iterating on what drives continued watching.
+
+---
+
+**Observe** <br></br>
+The team uses **Session Replay**, **Autocapture**, and **Alerts** to track *Episode Started → Episode Completed → Next Episode Started* events, identifying drop-offs by series and genre.
+
+---
+
+**Analyze** <br></br>
+They turn to **Retention** and **Cohorts** to learn which viewers come back.  **Funnels & Flows** show most viewers stop after Episode 2, and qualitative data confirms weak recommendations at that point.
+
+| Tool | Observation | Insight |
+|------|--------------|----------|
+| **Retention & Cohorts** | Only 30% return for Episode 3 | Low content continuity beyond early episodes. |
+| **Funnels & Flows** | Drop-off after Episode 2 | Weak recommendations between episodes. |
+
+---
+
+**Decide** <br></br>
+Using **Metric Trees**, the team connects “Episode Completion Rate” to “Viewer Retention.”  They decide to insert a personalized “Up Next” prompt and ratings flow to strengthen recommendations.
+
+---
+
+**Act** <br></br>
+They run an **Experiment** on the "Up Next" prompt. After positive results that indicate viewers who see the new recommendations have longer sessions and higher continuation rates, they expand rollout to all viewers using **Feature Flags**.
+
+
+---
+
+**✨ Result:** Viewer retention improves 25%, with stronger engagement across new series launches.
+<br></br>
+</details>
+
+
+
+<details>
+<summary style={{ fontSize: '1.15rem', fontWeight: 600 }}><strong>💰 Fintech: Increasing Feature Adoption and Retention</strong></summary>
+
+<br></br>A fintech product team observes user engagement with budgeting tools, analyzes setup friction, decides how to improve adoption, and acts by optimizing flows that drive retention.
+
+---
+
+**Observe** <br></br>
+They track customer actions with **Session Replay** and **Autocapture**, focusing on *Account Linked → Budget Created → Spending Reviewed → Budget Adjusted*. **Alerts** notify them of sudden drops in budget creation.
+
+---
+
+**Analyze** <br></br>
+Using **Funnels**, **Cohorts**, and **Retention**, they find that users linking smaller financial institutions often fail to complete setup.  
+
+| Tool | Observation | Insight |
+|------|--------------|----------|
+| **Funnels & Cohorts** | Users stop after linking a bank account | Authentication errors block progress. |
+| **Retention Reports** | Users who finish setup return 2× more often | Early success predicts long-term retention. |
+
+---
+
+**Decide** <br></br>
+The team uses **Metric Trees** to link budgeting feature adoption to retention KPIs. They decide to improve error handling and prompt users to set alerts immediately after creating a budget.
+
+---
+
+**Act** <br></br>
+They run an **Experiment** on a new “Set Alert” flow. After positive results, they expand rollout to all customers using **Feature Flags**.
+
+---
+
+**✨ Result:** Budget feature adoption increases 30%, and retention rises 15% as users set up alerts sooner.
+<br></br>
+</details>
+
+
+
+<details>
+<summary style={{ fontSize: '1.15rem', fontWeight: 600 }}><strong>🎮 Gaming: Driving Player Engagement and In-App Purchases</strong></summary>
+
+<br></br>A gaming studio observes player behavior across levels, analyzes progression data to uncover friction, decides what changes will improve engagement, and acts by launching prompts that drive completion and purchases.
+
+---
+
+**Observe** <br></br>
+The team uses **Session Replay**, **Heatmaps**, and **Autocapture** to track *Level Started → Level Completed → In-App Purchase Made*, identifying the points where players churn.
+
+---
+
+**Analyze** <br></br>
+They turn to **Funnels** and **Cohorts** on player feedback to understand why drop-offs occur.  Players who use “Power-Ups” progress faster, and replays show many ignore in-game hint icons.
+
+| Tool | Observation | Insight |
+|------|--------------|----------|
+| **Funnels & Cohorts** | High player drop-off after Level 3 | Repeated failures at one level lead to early churn. |
+| **Session Replay & Heatmaps** | Players miss hint icons | Poor visual placement of key gameplay aids. |
+
+---
+
+**Decide** <br></br>
+Using **Metric Trees**, the team links early-level completions to retention and in-app purchases. They decide to introduce Power-Up tutorials earlier to help players progress.
+
+---
+
+**Act** <br></br>
+They run an **Experiment** on a new “Use Power-Up” tutorial and measure results. When they see improved completion and monetization metrics, they expand it to all players using **Feature Flags**.
+
+---
+
+**✨ Result:** Level completion improves 35%, and in-app purchases increase 20%, driving sustained engagement.
+<br></br>
+</details>
+
+No matter your industry, the OADA loop helps you turn insights into action-—and Mixpanel gives you the tools to complete that loop faster with every iteration.
+
+---
+
+## Learn More
+
+Want to understand the strategy behind continuous innovation? Check out our blog on [How Digital Continuous Innovation Drives Sustainable Enterprise Growth](https://mixpanel.com/blog/digital-continuous-innovation/) to see how leading enterprises use the OADA framework to connect data, decisions, and action—–and build a culture of sustainable growth.
\ No newline at end of file
diff --git a/pages/guides/guides-by-topic/core-reports.mdx b/pages/guides/guides-by-topic/core-reports.mdx
new file mode 100644
index 0000000000..d950bcd8c0
--- /dev/null
+++ b/pages/guides/guides-by-topic/core-reports.mdx
@@ -0,0 +1,30 @@
+import { Cards } from 'nextra/components'
+
+# Core Reports
+
+<Cards>
+    <Cards.Card
+        title="Create Boards"
+        href="/guides/guides-by-topic/core-reports/create-boards"
+    />
+    <Cards.Card
+        title="Discover Insights"
+        href="/guides/guides-by-topic/core-reports/discover-insights"
+    />
+    <Cards.Card
+        title="Analyze Conversions"
+        href="/guides/guides-by-topic/core-reports/analyze-conversions"
+    />
+    <Cards.Card
+        title="Build User Flows"
+        href="/guides/guides-by-topic/core-reports/build-user-flows"
+    />
+    <Cards.Card
+        title="Track User Retention"
+        href="/guides/guides-by-topic/core-reports/track-user-retention"
+    />
+    <Cards.Card
+        title="Define Cohorts"
+        href="/guides/guides-by-topic/core-reports/define-cohorts"
+    />
+</Cards>
diff --git a/pages/guides/guides-by-topic/core-reports/_meta.ts b/pages/guides/guides-by-topic/core-reports/_meta.ts
new file mode 100644
index 0000000000..efaa21f53e
--- /dev/null
+++ b/pages/guides/guides-by-topic/core-reports/_meta.ts
@@ -0,0 +1,8 @@
+export default {
+	"create-boards": "Create Boards",
+	"discover-insights": "Discover Insights",
+	"analyze-conversions": "Analyze Conversions",
+	"build-user-flows": "Build User Flows",
+	"track-user-retention": "Track User Retention",
+	"define-cohorts": "Define Cohorts",
+}
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/analyze-conversions.mdx b/pages/guides/guides-by-topic/core-reports/analyze-conversions.mdx
similarity index 100%
rename from pages/guides/strategic-playbooks/onboarding-playbook/launch/analyze-conversions.mdx
rename to pages/guides/guides-by-topic/core-reports/analyze-conversions.mdx
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/build-user-flows.mdx b/pages/guides/guides-by-topic/core-reports/build-user-flows.mdx
similarity index 100%
rename from pages/guides/strategic-playbooks/onboarding-playbook/launch/build-user-flows.mdx
rename to pages/guides/guides-by-topic/core-reports/build-user-flows.mdx
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/create-boards.mdx b/pages/guides/guides-by-topic/core-reports/create-boards.mdx
similarity index 100%
rename from pages/guides/strategic-playbooks/onboarding-playbook/launch/create-boards.mdx
rename to pages/guides/guides-by-topic/core-reports/create-boards.mdx
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/define-cohorts.mdx b/pages/guides/guides-by-topic/core-reports/define-cohorts.mdx
similarity index 100%
rename from pages/guides/strategic-playbooks/onboarding-playbook/launch/define-cohorts.mdx
rename to pages/guides/guides-by-topic/core-reports/define-cohorts.mdx
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/discover-insights.mdx b/pages/guides/guides-by-topic/core-reports/discover-insights.mdx
similarity index 100%
rename from pages/guides/strategic-playbooks/onboarding-playbook/launch/discover-insights.mdx
rename to pages/guides/guides-by-topic/core-reports/discover-insights.mdx
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/track-user-retention.mdx b/pages/guides/guides-by-topic/core-reports/track-user-retention.mdx
similarity index 100%
rename from pages/guides/strategic-playbooks/onboarding-playbook/launch/track-user-retention.mdx
rename to pages/guides/guides-by-topic/core-reports/track-user-retention.mdx
diff --git a/pages/guides/guides-by-topic/features.mdx b/pages/guides/guides-by-topic/features.mdx
new file mode 100644
index 0000000000..b0174c8950
--- /dev/null
+++ b/pages/guides/guides-by-topic/features.mdx
@@ -0,0 +1,34 @@
+import { Cards } from 'nextra/components'
+
+# Features
+
+## Experiments and Feature Flags
+
+<Cards>
+    <Cards.Card
+        title="Drive Product Innovation"
+        href="/guides/guides-by-use-case/engage-your-users/drive-product-innovation"
+    />
+    <Cards.Card
+        title="Ship Features"
+        href="/guides/guides-by-use-case/engage-your-users/ship-features"
+    />
+</Cards>
+
+## Revenue Analytics
+
+<Cards>
+    <Cards.Card
+        title="Grow Revenue"
+        href="/guides/guides-by-use-case/grow-your-usership/grow-revenue"
+    />
+</Cards>
+
+## Session Replay
+
+<Cards>
+    <Cards.Card
+        title="See Replays"
+        href="/guides/guides-by-use-case/empower-your-team/see-replays"
+    />
+</Cards>
\ No newline at end of file
diff --git a/pages/guides/guides-by-use-case.mdx b/pages/guides/guides-by-use-case.mdx
new file mode 100644
index 0000000000..84a048c812
--- /dev/null
+++ b/pages/guides/guides-by-use-case.mdx
@@ -0,0 +1,34 @@
+import { Cards } from 'nextra/components'
+
+# Guides by Use Case
+
+## Engage Your Users
+
+<Cards>
+    <Cards.Card
+    title="Drive Product Innovation"
+    href="/guides/guides-by-use-case/engage-your-users/drive-product-innovation"
+    />
+    <Cards.Card
+    title="Ship Features"
+    href="/guides/guides-by-use-case/engage-your-users/ship-features"
+    />
+</Cards>
+
+## Grow Your Usership
+
+<Cards>
+    <Cards.Card
+    title="Grow Revenue"
+    href="/guides/guides-by-use-case/grow-your-usership/grow-revenue"
+    />
+</Cards>
+
+## Empower Your Team
+
+<Cards>
+    <Cards.Card
+    title="See Replays"
+    href="/guides/guides-by-use-case/empower-your-team/see-replays"
+    />
+</Cards>
diff --git a/pages/guides/guides-by-use-case/_meta.ts b/pages/guides/guides-by-use-case/_meta.ts
index 9b514422d3..3d9eb7bf69 100644
--- a/pages/guides/guides-by-use-case/_meta.ts
+++ b/pages/guides/guides-by-use-case/_meta.ts
@@ -1,5 +1,5 @@
 export default {
-    "build-a-tracking-strategy": "How to Build a Tracking Strategy",
-    "ensuring-data-quality": "Ensuring Data Quality",
-    "driving-product-innovation": "Driving Product Innovation"
+    "engage-your-users": "Engage Your Users",
+    "grow-your-usership": "Grow Your Usership",
+    "empower-your-team": "Empower Your Team",
 }
\ No newline at end of file
diff --git a/pages/guides/guides-by-use-case/empower-your-team/_meta.ts b/pages/guides/guides-by-use-case/empower-your-team/_meta.ts
new file mode 100644
index 0000000000..26ab9591b8
--- /dev/null
+++ b/pages/guides/guides-by-use-case/empower-your-team/_meta.ts
@@ -0,0 +1,3 @@
+export default {
+    "see-replays": "See Replays"
+}
\ No newline at end of file
diff --git a/pages/guides/guides-by-use-case/empower-your-team/see-replays.mdx b/pages/guides/guides-by-use-case/empower-your-team/see-replays.mdx
new file mode 100644
index 0000000000..b854e3ccba
--- /dev/null
+++ b/pages/guides/guides-by-use-case/empower-your-team/see-replays.mdx
@@ -0,0 +1,250 @@
+import { Callout, Steps } from 'nextra/components'
+
+# Turn Clicks into Clarity: Best Practices for Heatmaps & Session Replay
+
+Discover what users really experience—and turn those insights into action. This Guide shows you how to use [Heatmaps](/docs/session-replay/heatmaps) and [Session Replay](/docs/session-replay) together to quickly spot friction, understand behavior, and drive better product decisions.
+
+---
+
+## What Are Heatmaps and Session Replay?
+
+Heatmaps and Session Replay combine the “what” and the “why” of user behavior.
+
+- Heatmaps show where users click and focus attention.
+
+<br></br>
+<section id="video" aria-label="Mixpanel Heatmaps video" style={{ padding: '8px 16px 32px' }}>
+  <div
+    style={{
+      display: 'flex',
+      flexWrap: 'wrap',
+      gap: 24,
+      alignItems: 'center',
+    }}
+  >
+    {/* Left: video with a min width so it wraps when narrow */}
+    <div style={{ flex: '1 1 480px', minWidth: 320 }}>
+      <div
+        style={{
+          position: 'relative',
+          paddingBottom: '56.25%',
+          height: 0,
+          overflow: 'hidden',
+          borderRadius: '16px',
+          boxShadow: '0 4px 20px rgba(0,0,0,0.08)',
+        }}
+      >
+        <iframe
+          title="Mixpanel Heatmaps"
+          src="https://www.youtube.com/embed/af7D3exv610"
+          frameBorder="0"
+          allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
+          allowFullScreen
+          style={{ position: 'absolute', top: 0, left: 0, width: '100%', height: '100%', border: 0 }}
+        />
+      </div>
+    </div>
+
+    {/* Right: text with a flexible basis */}
+    <aside style={{ flex: '1 1 320px', minWidth: 280 }}>
+      <h2 style={{ marginTop: 0 }}>**Mixpanel Heatmaps**</h2>
+      <p>
+        In this 4-minute overview, learn how Mixpanel Heatmaps helps you visually pinpoint user friction and high engagement areas on your website, allowing you to instantly see where users are clicking and where they are getting stuck.
+      </p>
+<br></br>
+      <a href="https://youtu.be/af7D3exv610"
+         target="_blank" rel="noopener noreferrer" style={{ fontWeight: 600 }}>
+        Open in YouTube →
+      </a>
+    </aside>
+  </div>
+</section>
+
+- Session Replay shows how they move through your product in real time.
+
+<br></br>
+<section id="video" aria-label="Mixpanel Session Replay video" style={{ padding: '8px 16px 32px' }}>
+  <div
+    style={{
+      display: 'flex',
+      flexWrap: 'wrap',
+      gap: 24,
+      alignItems: 'center',
+    }}
+  >
+    {/* Left: video with a min width so it wraps when narrow */}
+    <div style={{ flex: '1 1 480px', minWidth: 320 }}>
+      <div
+        style={{
+          position: 'relative',
+          paddingBottom: '56.25%',
+          height: 0,
+          overflow: 'hidden',
+          borderRadius: '16px',
+          boxShadow: '0 4px 20px rgba(0,0,0,0.08)',
+        }}
+      >
+        <iframe
+          title="Mixpanel Session Replay"
+          src="https://www.youtube.com/embed/eig_Ta-0yZc"
+          frameBorder="0"
+          allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
+          allowFullScreen
+          style={{ position: 'absolute', top: 0, left: 0, width: '100%', height: '100%', border: 0 }}
+        />
+      </div>
+    </div>
+
+    {/* Right: text with a flexible basis */}
+    <aside style={{ flex: '1 1 320px', minWidth: 280 }}>
+      <h2 style={{ marginTop: 0 }}>**Mixpanel Session Replay**</h2>
+      <p>
+        In this 7-minute overview, discover how Mixpanel Session Replay unifies analytics and user behavior. Learn to seamlessly jump from your data to real user interactions to instantly diagnose friction and errors. The video also walks you through the incredibly easy, single-snippet implementation to accelerate your product's growth.
+      </p>
+<br></br>
+      <a href="https://youtu.be/eig_Ta-0yZc"
+         target="_blank" rel="noopener noreferrer" style={{ fontWeight: 600 }}>
+        Open in YouTube →
+      </a>
+    </aside>
+  </div>
+</section>
+
+Together, they help you understand not just *what* happened, but *why*.
+
+---
+
+## 1. Start with a Purpose
+
+Begin with a clear goal instead of watching random replays. Ask:
+
+- What behavior am I trying to understand?
+- Which conversion, drop-off, or UX flow do I want to validate?
+
+✅ **Do** define a specific question like:
+
+- “Where are users dropping off in signup?”
+- “Are people finding the new CTA?”
+- “Do mobile users engage with the feature the same way as desktop users?”
+
+❌ **Do not** assume watching any session will lead to insight. Without a clear question, you will end up chasing edge cases.
+
+👉 **Do this next:** Define what “success” looks like before opening your first replay.
+
+## 2. Use Heatmaps to Find the Pattern
+
+Heatmaps are your first stop when you want to **see interaction trends at scale.**
+
+**Steps to take:**
+
+<Steps>
+
+{<h3>Choose a meaningful page or flow, like signup, pricing, or onboarding.</h3>}
+
+{<h3>Filter by device or cohort to compare how segments behave.</h3>}
+
+{<h3>Scan for anomalies, such as ignored CTAs or clicks on non-interactive elements.</h3>}
+
+</Steps>
+
+<Callout type="info">
+    **Pro tip:** Use *Click Maps* for precision and *Traditional Heatmaps* for broader engagement patterns. Click Maps provide precise insights on dynamic pages with modals or dropdowns.
+</Callout>
+
+Learn more about [Click Maps and Traditional Heatmaps](/docs/session-replay/heatmaps#overview).
+
+---
+
+## 3. Use Session Replay to Understand the “Why”
+
+Once you have spotted a pattern, Session Replay lets you zoom in on the granular details of individual user sessions.
+
+**Steps to take:**
+
+<Steps>
+
+{<h3>Filter replays by key event or cohort.</h3>}
+
+For example, you can filter to “users who dropped after viewing pricing.”
+
+{<h3>Watch 6–8 replays.</h3>}
+
+This allows you to identify friction points and common paths your users take.
+
+{<h3>Look for behavioral feedback.</h3>}
+
+This includes excessive scrolling, hesitation, backtracking, or repeated form errors that highlights friction points.
+
+{<h3>Document your findings.</h3>}
+
+Take notes on where users struggle or deviate from expected behavior.
+
+</Steps>
+
+<Callout type="info">
+    **Pro tip:** Start from within Mixpanel reports or user profiles to stay anchored to data—not anecdotes. You can click “View Replays” directly from an Event, Funnel, or User Profile to see related sessions immediately.
+</Callout>
+
+<Callout type="warning">
+    **Pitfall:** One replay ≠ one insight. Confirm patterns across multiple sessions before drawing conclusions.
+</Callout>
+
+---
+
+## 4. Protect User Privacy and Data Integrity
+
+Session Replay gives full visibility into user behavior—but it also introduces risk if sensitive data appears on-screen.
+
+**Best practices for safe implementation:**
+
+- Use Mixpanel's privacy controls to mask or block sensitive UI screens, like checkout or profile information. 
+- Test across devices, especially for mobile SDKs and embedded web views.
+- Review your company's privacy notice and legal compliance before roll-out.
+
+Learn more about [Session Replay Privacy Controls](/docs/session-replay/session-replay-privacy-controls).
+
+---
+
+## 5. Translate Insights into Product Decisions
+
+Data becomes powerful only when shared. Once you identify friction, decide what change to make—and how you will measure its impact.
+
+**Steps to take:**
+
+<Steps>
+
+{<h3>Summarize your insight.</h3>}
+
+Turn observations into clear takeaways. For example, “Users abandon signup when validation errors are not visible.”
+
+{<h3>Share replay clips to align stakeholders on the problem.</h3>}
+
+Short, focused clips help everyone see the issue firsthand, creating a shared understanding and faster alignment on next steps.
+
+{<h3>Instrument or adjust tracking if needed.</h3>}
+
+Ensure what you are tracking capture key behaviors so you can validate results and spot new opportunities.
+
+</Steps>
+
+<Callout type="info">
+    **Pro tip:** Create a recurring “Replay Review” with PMs and designers. It builds empathy and keeps teams aligned on real user behavior.
+</Callout>
+
+**Strengthen your workflow with related features:**
+
+- [Annotations](/docs/features/annotations): Add notes to your reports to document findings and experiments.
+- [Alerts](/docs/features/alerts): Set notifications for spikes or drops in engagement or friction.
+- [Experiments](/docs/experiments): Validate your hypotheses by testing product changes and measuring lift.
+
+---
+
+## Key Takeaways
+
+- Start with a specific question or metric to guide your analysis.
+- Use Heatmaps for **patterns** and Session Replay for **context**.
+- Review **6–8** sessions per segment to find consistent trends.
+- Safeguard user privacy during implementation and QA.
+- Turn your findings into shared, actionable insights.
+
+📚 **Go deeper:** Explore the Mixpanel Docs on [Heatmaps](/docs/session-replay/heatmaps) and [Session Replay](/docs/session-replay).
diff --git a/pages/guides/guides-by-use-case/engage-your-users/_meta.ts b/pages/guides/guides-by-use-case/engage-your-users/_meta.ts
new file mode 100644
index 0000000000..f280b807ae
--- /dev/null
+++ b/pages/guides/guides-by-use-case/engage-your-users/_meta.ts
@@ -0,0 +1,4 @@
+export default {
+    "drive-product-innovation": "Drive Product Innovation",
+    "ship-features": "Ship Features"
+}
\ No newline at end of file
diff --git a/pages/guides/guides-by-use-case/driving-product-innovation.mdx b/pages/guides/guides-by-use-case/engage-your-users/drive-product-innovation.mdx
similarity index 70%
rename from pages/guides/guides-by-use-case/driving-product-innovation.mdx
rename to pages/guides/guides-by-use-case/engage-your-users/drive-product-innovation.mdx
index 559c66e527..5405d79f86 100644
--- a/pages/guides/guides-by-use-case/driving-product-innovation.mdx
+++ b/pages/guides/guides-by-use-case/engage-your-users/drive-product-innovation.mdx
@@ -1,6 +1,6 @@
 import { Callout, Steps } from 'nextra/components'
 
-# Driving Product Innovation with Mixpanel Experiments
+# Drive Product Innovation with Mixpanel Experiments
 
 Experimentation is how modern product teams make decisions with confidence. Instead of guessing, you test changes with real users, measure the impact, and move forward knowing what works. Mixpanel makes it possible to plan, run, and analyze experiments in one place.
 
@@ -16,9 +16,59 @@ Making product changes without data is risky. Experimentation helps you:
 
 Leading companies like [Step](https://mixpanel.com/customers/how-step-boosted-direct-deposits-by-14-with-mixpanels-experimentation/) use Mixpanel to build a culture of experimentation, moving quickly without losing customer trust.
 
-<Callout>
-    **Do this next**: Identify one upcoming product change you are unsure about and commit to testing it before launch.
-</Callout>
+👉 **Do this next:** Identify one upcoming product change you are unsure about and commit to testing it before launch.
+
+### See Mixpanel Experiments in Action
+
+Before you dive into best practices, take a quick look at how experimentation works inside Mixpanel.
+
+<br></br>
+<section id="video" aria-label="Mixpanel Experiments video" style={{ padding: '8px 16px 32px' }}>
+  <div
+    style={{
+      display: 'flex',
+      flexWrap: 'wrap',
+      gap: 24,
+      alignItems: 'center',
+    }}
+  >
+    {/* Left: video with a min width so it wraps when narrow */}
+    <div style={{ flex: '1 1 480px', minWidth: 320 }}>
+      <div
+        style={{
+          position: 'relative',
+          paddingBottom: '56.25%',
+          height: 0,
+          overflow: 'hidden',
+          borderRadius: '16px',
+          boxShadow: '0 4px 20px rgba(0,0,0,0.08)',
+        }}
+      >
+        <iframe
+          title="Mixpanel Experiments"
+          src="https://www.youtube.com/embed/LZfIPCXcIPE"
+          frameBorder="0"
+          allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
+          allowFullScreen
+          style={{ position: 'absolute', top: 0, left: 0, width: '100%', height: '100%', border: 0 }}
+        />
+      </div>
+    </div>
+
+    {/* Right: text with a flexible basis */}
+    <aside style={{ flex: '1 1 320px', minWidth: 280 }}>
+      <h2 style={{ marginTop: 0 }}>**Mixpanel Experiments**</h2>
+      <p>
+        In this 3-minute overview, learn how Mixpanel Experiments helps you reduce risk, learn faster, and discover surprises.
+      </p>
+<br></br>
+      <a href="https://youtu.be/LZfIPCXcIPE"
+         target="_blank" rel="noopener noreferrer" style={{ fontWeight: 600 }}>
+        Open in YouTube →
+      </a>
+    </aside>
+  </div>
+</section>
 
 ## Setting Up Experiments the Right Way
 
@@ -48,9 +98,8 @@ Do not test multiple changes at once. Focus on a single variable so you know wha
 
 Testing too many things at once makes it impossible to know which change worked.
 
-<Callout>
-**Do this next**: Draft your hypothesis and list your primary and guardrail metrics. Review with your team before launch.
-</Callout>
+👉 **Do this next:** Draft your hypothesis and list your primary and guardrail metrics. Review with your team before launch.
+
 
 ## Choosing the Right Test Model
 
@@ -97,9 +146,7 @@ If your primary metric improves and the results are significant, you can trust i
 
 Do not treat inconclusive results as failures; they provide valuable clues, even if they are not yet a win.
 
-<Callout>
-**Do this next**: Share experiment results in a [Mixpanel Board](https://mixpanel.com/blog/boards-collaborate-cards-mixpanel-feature-update/) and add notes on what the data means to provide additional context to your numbers.
-</Callout>
+👉 **Do this next:** Share experiment results in a [Mixpanel Board](https://mixpanel.com/blog/boards-collaborate-cards-mixpanel-feature-update/) and add notes on what the data means to provide additional context to your numbers.
 
 ## Acting on Experiment Insights
 
@@ -114,9 +161,7 @@ The most impactful teams do not stop at analysis; they act.
 **Pro tip**:Always explain why you made your decision, not just what you decided. This builds institutional knowledge.
 </Callout>
 
-<Callout>
-**Do this next**: Add a note in your Experiment Report explaining the reasoning behind your decision.
-</Callout>
+👉 **Do this next:** Add a note in your Experiment Report explaining the reasoning behind your decision.
 
 ## Avoid Common Pitfalls
 
@@ -129,9 +174,7 @@ Stay alert to these common mistakes:
 
 Avoid declaring a test a success at the first sign of movement; early spikes often disappear as more data arrives.
 
-<Callout>
-**Do this next**: Review your last experiment—did you hit any of these pitfalls?
-</Callout>
+👉 **Do this next:** Review your last experiment—did you hit any of these pitfalls?
 
 ## Scaling Experimentation as a Habit
 
@@ -146,9 +189,7 @@ Experimentation works best when it is part of your culture.
     **Pro tip**: Share at least one experiment outcome (good or bad) in every team meeting—it normalizes learning.
 </Callout>
 
-<Callout>
-**Do this next**: Create a recurring agenda item in your weekly standup for experiment learnings. Keep it lightweight; 2–3 minutes max.
-</Callout>
+👉 **Do this next:** Create a recurring agenda item in your weekly standup for experiment learnings. Keep it lightweight; 2–3 minutes max.
 
 ## Key Takeaways
 
@@ -159,4 +200,4 @@ To get started:
 2. **Share learnings widely.** Make results visible to other teams so everyone benefits.
 3. **Treat experimentation as a repeatable process**, not a one-off.
 
-Learn more about the [Experiments Report](/docs/reports/experiments).
\ No newline at end of file
+Learn more about the [Experiments Report](/docs/reports/experiments).
diff --git a/pages/guides/guides-by-use-case/engage-your-users/ship-features.mdx b/pages/guides/guides-by-use-case/engage-your-users/ship-features.mdx
new file mode 100644
index 0000000000..6dc9d2c33b
--- /dev/null
+++ b/pages/guides/guides-by-use-case/engage-your-users/ship-features.mdx
@@ -0,0 +1,142 @@
+import { Callout, Steps } from 'nextra/components'
+
+# How to Safely Ship New Features with Flags
+
+Feature Flags give your team the power to launch confidently, roll back instantly, and measure success in real time. Mixpanel integrates feature flagging directly into your analytics—so every rollout is both controlled and measurable.
+
+## What Are Feature Flags?
+
+Feature Flags decouple deployment (when code ships) from release (when users see it). This means engineers can deploy at any time, while product teams control when—and to whom—new functionality appears.
+
+Mixpanel's native feature flags integrate directly with your data, so you can track adoption, performance, and impact without additional setup.
+
+---
+
+## 1. Prepare for Rollout
+
+Feature flagging starts with setup. Your engineering team must enable flag evaluation within your app before flags can be controlled in Mixpanel.
+
+Steps to take:
+
+<Steps>
+
+{ <h3>Implement the Mixpanel SDK</h3> }
+
+Make sure to initialize the library with the config option `flags: true`.
+
+- [JavaScript SDK flags setup →](/docs/tracking-methods/sdks/javascript/javascript-flags) 
+- [iOS / Swift SDK flags setup →](/docs/tracking-methods/sdks/swift/swift-flags)
+- [Android SDK flags setup →](/docs/tracking-methods/sdks/android/android-flags)
+
+
+{ <h3>Define fallback variants in code to prevent errors if the flag fails to resolve.</h3> }
+
+{ <h3>Verify flag evaluation using QA Testers before releasing to real users.</h3> }
+
+</Steps>
+
+- ✅ **Do** confirm the SDK setup and flag evaluation flow with Engineering before creating a feature flag in Mixpanel.
+- ❌ **Do not** create flags in the UI before the SDK is integrated—the flag won't control behavior in your product until the SDK is configured.
+
+<Callout type="warning">
+    **Pitfall:** Skipping SDK setup causes flags to appear “inactive” even if configured correctly in Mixpanel.
+</Callout>
+
+---
+
+## 2. Plan a Safe Rollout
+
+With SDK setup complete, decide how to roll out the feature. Use data-driven rollout strategies to manage risk and learn quickly.
+
+Common rollout types:
+- **Phased Rollout**: Start with 5–10 % of users, expanding gradually.
+- **Cohort-Based Targeting**: Show the feature to specific segments (e.g. power users or new signups).
+- **Platform Segmentation**: Launch to a single platform (like iOS) before web.
+- **Feature Gate**: Keep a kill switch ready for instant rollback.
+
+<Callout type="info">
+    **Pro tip:** Combine a phased rollout with [alerts](/docs/features/alerts) on key metrics—like conversion or retention—to catch regressions early.
+</Callout>
+
+---
+
+## 3. Configure Your Flag in Mixpanel
+
+Once your SDK is live, create and manage feature flags directly in the Mixpanel UI.
+
+Steps to take:
+
+<Steps>
+
+{ <h3>Create a new flag.</h3> }
+
+e.g. `onboarding_v2`
+
+{ <h3>Add a variant and define rollout percentages.</h3> }
+
+{ <h3>Target users by cohort or run-time properties.</h3> }
+
+e.g. `platform = android`
+
+{ <h3>Use QA Testers to assign test variants and confirm logic.</h3> }
+
+{ <h3>Monitor exposure and adoption in real time, adjusting rollout weights as you scale.</h3> }
+
+</Steps>
+
+<Callout type="info">
+    **Pro tip:** Use consistent flag and variant names across systems to keep your analytics clean.
+</Callout>
+
+### How it Works
+
+When your app loads, the Mixpanel SDK automatically fetches active flags and evaluates which variant each user should see. Once a variant is displayed, Mixpanel logs an exposure event (`$experiment_started`), allowing you to track adoption and impact immediately in your reports—no manual tagging needed.
+
+![Experiments_and_FF.png](/Experiments_and_FF.png)
+
+[📖 Full Feature Flags documentation →](/docs/featureflags)
+
+---
+
+## 4. Monitor and Learn
+
+After launch, use Mixpanel analytics to determine whether to expand, iterate, or revert.
+
+**Tools to Help**
+- [Insights](/docs/reports/insights): Measure adoption and engagement by variant.
+- [Funnels](/docs/reports/funnels/funnels-overview): Track conversion rates between control and variant users.
+- [Boards](/docs/boards): Create a shared rollout dashboard with annotations and alerts.
+- [Session Replay](/docs/session-replay): Watch user interactions to diagnose UX issues.
+
+<Callout type="info">
+    **Pro tip:** Use [borrowed properties](/docs/features/custom-properties#borrowed-properties) or [cohorts](/docs/users/cohorts) to track downstream behavior for users exposed to each variant.
+</Callout>
+
+ 👉 **Do this next:** Validate exposure counts and cohort membership before scaling.
+
+ ---
+
+## 5. Govern and Clean Up
+
+Feature flags are powerful, but unmanaged flags become “flag debt.” Maintain hygiene by:
+- Assigning an **owner** for each flag.
+- **Auditing** monthly or quarterly.
+- Keeping flags scoped to one use case.
+- **Documenting** rollout intent and success criteria.
+- **Sunsetting** flags once a feature reaches 100 % rollout.
+
+<Callout type="info">
+**Pro tip:** Add flag cleanup reviews to your sprint rituals to stay organized and efficient.
+</Callout>
+
+---
+
+## Key Takeaways
+
+- Prepare your setup by enabling flag support in your SDK so Mixpanel can control feature visibility.
+- Plan safe roll outs using phased or cohort-based release strategies to manage risk.
+- Configure and control flags directly in Mixpanel—no redeploy required.
+- Monitor adoption and performance with built-in analytics to decide when to expand or revert.
+- Govern and clean up flags regularly to prevent confusion and keep your implementation scalable.
+
+📚 **Go deeper:** [Feature Flags overview in Mixpanel Docs](/docs/featureflags)
diff --git a/pages/guides/guides-by-use-case/grow-your-usership/_meta.ts b/pages/guides/guides-by-use-case/grow-your-usership/_meta.ts
new file mode 100644
index 0000000000..9a88eec25e
--- /dev/null
+++ b/pages/guides/guides-by-use-case/grow-your-usership/_meta.ts
@@ -0,0 +1,3 @@
+export default {
+    "grow-revenue": "Grow Revenue"
+}
\ No newline at end of file
diff --git a/pages/guides/guides-by-use-case/grow-your-usership/grow-revenue.mdx b/pages/guides/guides-by-use-case/grow-your-usership/grow-revenue.mdx
new file mode 100644
index 0000000000..2447ca1148
--- /dev/null
+++ b/pages/guides/guides-by-use-case/grow-your-usership/grow-revenue.mdx
@@ -0,0 +1,148 @@
+import { Callout, Steps } from 'nextra/components'
+
+# Understand and Grow Revenue with Mixpanel
+
+[Revenue analytics](/guides/strategic-playbooks/onboarding-playbook/launch/revenue-analytics) connects product usage to business results—helping you see which actions drive paying customers, where money comes from, and how to increase it.
+
+---
+
+## Before You Begin
+
+Revenue analytics in Mixpanel requires Warehouse Connectors. To analyze revenue, you will need to sync your billing or transactional data (for example, from your payment platform or internal finance systems) into Mixpanel using [Warehouse Connectors](/docs/tracking-methods/warehouse-connectors).
+
+After your warehouse is connected, set up the data structure that fits your business model:
+- **Transactional revenue** (e.g. one-time purchases, orders): Use [Mirror](/docs/tracking-methods/warehouse-connectors#mirror) to bring purchase events from your warehouse into Mixpanel. Mirror automatically syncs new transactions on a scheduled cadence. 
+- **Subscription-based revenue** (e.g. recurring plans, renewals): Use [Profile History](/docs/tracking-methods/warehouse-connectors#user-profiles) to track subscription changes, upgrades, and cancellations over time.
+
+Once your data source is connected, you can link behavioral data (from Mixpanel events) with business data (from Mirror, Profile History, and Warehouse Connectors) to understand how user actions drive revenue outcomes.
+
+📖 [Set up Warehouse Connectors →](/docs/tracking-methods/warehouse-connectors#step-1-connect-a-warehouse)
+
+<Callout type="info">
+    **Pro tip:** Make sure your revenue tables include shared identifiers such as `user_id` or `account_id` so Mixpanel can link purchases back to user actions.
+</Callout>
+
+---
+
+## What Is Revenue Analytics?
+
+Revenue analytics lets you connect product behavior to business impact. In Mixpanel, this means tracking events that represent value exchange (signups, upgrades, purchases, renewals) and tying them to monetary outcomes.
+
+When set up correctly, you can:
+- See which actions or features correlate with higher spend
+- Determine which in-trial actions lead to higher customer lifetime value after conversion
+- Understand retention patterns among paying customers
+- Align product and finance teams on shared metrics
+
+By following the steps in this guide, you will learn how to track, verify, and act on your revenue data to fuel growth.
+
+---
+
+### 1. Capture the Right Revenue Events
+
+Once your warehouse connection is live, focus on the key moments that represent a value exchange—either when money is transferred or when a commitment to future revenue is established.
+
+- ✅ **Do** focus on meaningful milestones like `subscription_created`, `upgrade_completed`, or `payment_success`.
+- ❌ **Do not** log every possible interaction as a revenue event.
+
+Each event should include:
+- `amount` (numeric)
+- `currency` (ISO code)
+- `plan_type` (or equivalent)
+- `user_id` or `account_id`
+
+<Callout type="info">
+    **Pro tip:** For multi-currency transactions, include `base_currency` and `base_ccy_amount` so Mixpanel can convert all revenue to a single base currency for consistent reporting.
+</Callout>
+
+<Callout type="warning">
+    **Pitfall:** Missing any of these properties will prevent Mixpanel from rolling up revenue totals accurately.
+</Callout>
+
+---
+
+### 2. Verify and Define Your Revenue Data
+
+Before you begin analysis, confirm that Mixpanel is reading your data correctly.
+
+Steps to take:
+
+<Steps>
+
+{<h3>Tag your revenue events in Lexicon.</h3>}
+
+Tagging your revenue events make them discoverable and easy to reference across reports.
+
+{<h3>Check event integrity.</h3>}
+
+Look for duplicate event names, missing properties, or inconsistent casing.
+
+{<h3>Compare totals against your source-of-truth.</h3>}
+
+Compare your totals against your finance system warehouse to confirm that imported revenue matches what you expect.
+
+</Steps>
+
+Note: Warehouse Connector data updates on a scheduled sync (not in real time), so totals will reflect the most recent completed sync rather than live revenue changes.
+
+<Callout type="info">
+    **Pro tip:** Ask a finance or data engineer to confirm that your daily imports are up to date and correctly formatted.
+</Callout>
+
+📖 [Learn more about data validation →](/docs/tracking-best-practices/debugging)
+
+---
+
+### 3. Analyze What Drives Revenue
+
+Once your data is verified, you can start exploring what behaviors drive your business outcomes. There are many ways to analyze revenue in Mixpanel—each highlighting a different aspect of user value, conversion, or retention.
+
+One simple but powerful example is **Average Revenue Per User (ARPU).**
+
+**How it is calculated:**
+
+&emsp;  $Average \ Revenue \ Per \ User \ (ARPU) = \frac{Sum \ of \ Revenue \ Over \ Time}{Number \ of \ Unique \ Users}$
+
+
+Tracking ARPU helps you understand how much revenue each active user generates during a given period. It is a great starting point for comparing user segments, evaluating pricing changes, or measuring growth trends over time.
+
+**Tools to Help**
+
+- [Insights](/docs/reports/insights): Visualize ARPU trends and spot spikes or dips after product or pricing changes.
+- [Funnels](/docs/reports/funnels/funnels-overview): See how user behaviors along the purchase path affect downstream revenue.
+- [Cohorts](/docs/users/cohorts): Compare high-value cohorts (e.g. annual plan users) with lower-value ones to identify drivers of growth.
+
+
+**Example:** Explore how ARPU looks in practice in our [E-commerce demo project](https://mixpanel.com/s/300OIR). This sample dashboard uses an **Insights** report to calculate revenue per user over time, helping teams visualize revenue trends in real Mixpanel data.
+
+ARPU is just one approach to revenue analysis.
+
+- For transactional revenue, you can explore metrics like **Revenue per Purchase Event** or **Revenue by Feature Usage** to uncover which actions or products generate the most value.
+- For subscription-based revenue, try tracking **Recurring Revenue Change** or **Churned Revenue** to understand how upgrades, downgrades, and cancellations impact your overall recurring revenue growth.
+
+---
+
+### 4. Connect Insights to Action
+
+Revenue analytics is only valuable if it drives decisions. Once you have identified what moves the needle, turn insights into action across teams.
+
+- Share [Boards](/docs/boards) with product and growth teams to align on revenue drivers.
+- Set up [Alerts](/docs/features/alerts) to notify you of significant revenue drops or spikes.
+- Add [Annotations](/docs/features/annotations) to track launches, pricing changes, or campaigns that may explain revenue shifts.
+
+<Callout type="info">
+    **Pro tip:** When you notice a revenue dip or spike, dig into which user actions changed around the same time—and share those findings with product or marketing so they can act on them quickly.  Set up a quarterly review to ensure data stays current and your insights remain actionable.
+</Callout>
+
+---
+
+## Key Takeaways
+
+- Revenue analytics in Mixpanel requires Warehouse Connectors to import financial data.
+- Track only the key events that represent real value exchange.
+- Always verify totals and event integrity before drawing conclusions.
+- Use Funnels, Insights, and Cohorts to discover what behaviors drive conversions.
+- Refresh and share dashboards regularly to align business and product teams.
+
+
+📚 **Go deeper:** [Mixpanel Docs on Revenue Analytics](/guides/strategic-playbooks/onboarding-playbook/launch/revenue-analytics)
diff --git a/pages/guides/guides-by-workflow/_meta.ts b/pages/guides/guides-by-workflow/_meta.ts
new file mode 100644
index 0000000000..a15f909a74
--- /dev/null
+++ b/pages/guides/guides-by-workflow/_meta.ts
@@ -0,0 +1,4 @@
+export default {
+    "build-tracking-strategy": "Build Tracking Strategy",
+    "ensure-data-quality": "Ensure Data Quality"
+}
\ No newline at end of file
diff --git a/pages/guides/guides-by-use-case/build-a-tracking-strategy.mdx b/pages/guides/guides-by-workflow/build-tracking-strategy.mdx
similarity index 100%
rename from pages/guides/guides-by-use-case/build-a-tracking-strategy.mdx
rename to pages/guides/guides-by-workflow/build-tracking-strategy.mdx
diff --git a/pages/guides/guides-by-use-case/ensuring-data-quality.mdx b/pages/guides/guides-by-workflow/ensure-data-quality.mdx
similarity index 100%
rename from pages/guides/guides-by-use-case/ensuring-data-quality.mdx
rename to pages/guides/guides-by-workflow/ensure-data-quality.mdx
diff --git a/pages/guides/mixpanel-introduction.mdx b/pages/guides/mixpanel-introduction.mdx
new file mode 100644
index 0000000000..1dc86f09e0
--- /dev/null
+++ b/pages/guides/mixpanel-introduction.mdx
@@ -0,0 +1,122 @@
+import { Callout } from 'nextra/components'
+
+# Mixpanel Introduction
+
+Mixpanel is a **digital analytics platform** that helps teams continuously improve their products by turning data into action. At its core, Mixpanel supports a **continuous innovation loop**—helping you observe what users do, analyze why it happens, decide what to do next, and act on those insights.
+
+<Callout type="info">
+  **Why it matters:** Teams use Mixpanel to learn faster, align decisions across functions, and measure the impact of every product change.
+</Callout>
+
+---
+
+## See Mixpanel in Action
+
+<br></br>
+<section id="video" aria-label="Mixpanel overview video" style={{ padding: '8px 16px 32px' }}>
+  <div
+    style={{
+      display: 'flex',
+      flexWrap: 'wrap',
+      gap: 24,
+      alignItems: 'center',
+    }}
+  >
+    {/* Left: video with a min width so it wraps when narrow */}
+    <div style={{ flex: '1 1 480px', minWidth: 320 }}>
+      <div
+        style={{
+          position: 'relative',
+          paddingBottom: '56.25%',
+          height: 0,
+          overflow: 'hidden',
+          borderRadius: '16px',
+          boxShadow: '0 4px 20px rgba(0,0,0,0.08)',
+        }}
+      >
+        <iframe
+          title="Mixpanel Overview"
+          src="https://www.youtube.com/embed/sRQCfmvh3vg"
+          frameBorder="0"
+          allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
+          allowFullScreen
+          style={{ position: 'absolute', top: 0, left: 0, width: '100%', height: '100%', border: 0 }}
+        />
+      </div>
+    </div>
+
+    {/* Right: text with a flexible basis */}
+    <aside style={{ flex: '1 1 320px', minWidth: 280 }}>
+      <h2 style={{ marginTop: 0 }}>**Mixpanel Overview**</h2>
+      <p>
+        In this 5-minute overview, learn how Mixpanel powers the continuous innovation loop––from observation to impact.
+      </p>
+<br></br>
+      <a href="https://youtu.be/sRQCfmvh3vg"
+         target="_blank" rel="noopener noreferrer" style={{ fontWeight: 600 }}>
+        Open in YouTube →
+      </a>
+    </aside>
+  </div>
+</section>
+
+---
+
+## Mixpanel Features That Power Continuous Innovation
+
+<div style={{ display: 'flex', flexWrap: 'wrap', alignItems: 'center', gap: '24px', margin: '32px 0' }}>
+  <div style={{ flex: '1 1 420px', minWidth: '280px' }}>
+
+Mixpanel is built around a simple but powerful framework for continuous improvement: **Observe → Analyze → Decide → Act (OADA)**.
+
+Each stage in the OADA framework connects directly to Mixpanel’s tools, helping you move from data to observation to action–—all in one platform.
+
+  </div>
+
+  <div style={{ flex: '1 1 300px', textAlign: 'center' }}>
+
+![OADA Loop diagram](/oada-loop-simple-wide-fcf9fa.png)
+
+*The cycle of continuous innovation.*
+
+  </div>
+</div>
+
+
+| 👀 **Observe** | 📊 **Analyze** | 💡 **Decide** | 🚀 **Act** |
+|---|---|---|---|
+| See what’s happening in your product with [Session Replay](/docs/session-replay), [Heatmaps](/docs/session-replay/heatmaps), [Autocapture](/docs/tracking-methods/autocapture), and [Alerts](/docs/features/alerts). | Explore [Insights](/docs/reports/insights), [Funnels](/docs/reports/funnels), [Flows](/docs/reports/flows), [Retention](/docs/reports/retention), and [Cohorts](/docs/users/cohorts) to find what moves your metrics. | Align on what to change next with [Metric Trees](/docs/metric_tree), [Boards](/docs/boards), [Annotations](/docs/features/annotations), and shared insights. | Measure impact with [Experiments](/docs/experiments) and ship improvements with [Feature Flags](/docs/featureflags). |
+
+All of this is powered by Mixpanel’s modern data foundation—–bringing together AI-assisted analysis through features like [MCP Server](/docs/features/mcp), robust [data governance](/docs/data-governance) for accuracy and trust, and built-in collaboration tools that help teams move from insight to action faster.
+
+**Learn more:** [Go deeper on the OADA Loop →](/guides/guides-by-topic/continuous-innovation)
+
+---
+
+## Mixpanel Data Model
+
+Everything in Mixpanel starts with **events**––the building blocks of your data model.
+   
+An event represents something a **user** does (like *Signed Up*, *Viewed a Product*, or *Completed Purchase*). Each event can include **properties** that add context, such as the user’s plan type, location, or device. Optionally, you can analyze data at the group level using [Group Analytics](/docs/data-structure/group-analytics).
+
+![Data Model](/Data_Model_with_Group_Analytics.png)
+
+Together, these events and properties form a flexible data model that mirrors how people actually use your product. Once instrumented, you can analyze this data instantly—–without writing SQL or waiting on an analyst.
+
+**Learn more:** [Dive deeper into how Mixpanel structures data →](/docs/data-structure/concepts)
+
+---
+
+## Keep Learning
+
+Keep building your Mixpanel expertise with these resources designed to help you learn, connect, and put insights into action.
+
+| Resource | Purpose | Link |
+|-----------|--------------|------|
+| **Community** | Connect with other Mixpanel users, share ideas, and learn how peers are tackling similar challenges. | [Open →](https://community.mixpanel.com/) |
+| **Developer Docs** | Build and extend Mixpanel with SDKs, APIs, and advanced implementation guides. | [Open →](https://developer.mixpanel.com/reference/overview) |
+| **Docs** | Explore product capabilities, setup guides, and detailed feature references. | [Open →](https://docs.mixpanel.com/) |
+| **Events** | Join live sessions and webinars to explore new features, use cases, and expert-led best practices. | [Open →](https://mixpanel.com/events) |
+| **Guides** | Apply Mixpanel best practices to real-world workflows and use cases. | 📍 You are here |
+
+Wherever you are in your Mixpanel journey, these resources will help you keep learning, stay connected, and keep improving.
diff --git a/pages/guides/self-guided-tours.mdx b/pages/guides/self-guided-tours.mdx
new file mode 100644
index 0000000000..6344474de4
--- /dev/null
+++ b/pages/guides/self-guided-tours.mdx
@@ -0,0 +1,119 @@
+import SelfGuidedTours from '../../components/SelfGuidedTours'
+
+# Self-Guided Product Tours
+
+Discover Mixpanel’s core features through quick, self-guided tours.
+Select any card below to explore interactive walkthroughs of key workflows.
+
+{/*
+  Cards API (examples):
+
+  {
+    badge: 'PRODUCT OVERVIEWS',            // Pill label shown above the title
+    title: 'Mixpanel Experiments',         // Main title
+    blurb: 'Setup a Mixpanel Experiment',  // Short supporting text (optional)
+    img: '/navattic/launch-an-experiment.png', //Image src (public/… 314x139 pixels)
+    navatticOpen: 'cmfkxwfa5000004lc8408f5wi', // Navattic demo id (popup)
+    navatticTitle: 'Launch an Experiment',     // Optional: popup title
+    // href: 'https://example.com'        // (Alternative) card links out if provided
+  }
+
+  Notes:
+  - If `navatticOpen` is present, the card triggers a Navattic popup.
+  - If `img` is omitted, a dark placeholder fills the image area.
+  - If `href` is provided (and `navatticOpen` is not), the card becomes a link.
+  - Images should live under /public/navattic/ for easy referencing.
+*/}
+
+<SelfGuidedTours
+  cards={[
+    {
+      badge: 'PRODUCT OVERVIEWS',
+      title: 'Overview Tour',
+      blurb: 'Tour the Mixpanel UI',
+      img: '/navattic/01_OverviewTour_314x139.png',
+      navatticOpen: 'cmdrjulgv000004js7zwaeqor',
+      navatticTitle: 'Overview Tour',
+    },
+    {
+      badge: 'ANALYSIS',
+      title: 'Visualize Trends',
+      blurb: 'Create an Insights report',
+      img: '/navattic/02_Insights_314x139.png',
+      navatticOpen: 'cmead9fmz000004l5ff34hgwo',
+      navatticTitle: 'Visualize Trends with Data',
+    },
+    {
+      badge: 'ANALYSIS',
+      title: 'Optimize User Conversion',
+      blurb: 'Create a Funnels report',
+      img: '/navattic/03_Funnels_314x139.png',
+      navatticOpen: 'cmer30mzn000104i52cqv05al',
+      navatticTitle: 'Optimize User Conversion',
+    },
+    {
+      badge: 'AUTOCAPTURE',
+      title: 'Analyze Autocaptured Data',
+      blurb: 'Utilize Custom Events',
+      img: '/navattic/04_Autocapture_314x139.png',
+      navatticOpen: 'cmbrua13y000004l47jkmbvpg',
+      navatticTitle: 'Analyzing Autocaptured Data',
+    },
+    {
+      badge: 'SESSION REPLAY',
+      title: 'Watch Playbacks',
+      blurb: 'See why customers drop off',
+      img: '/navattic/05_SessionReplay_314x139.png',
+      navatticOpen: 'cmapktdk2000104lb976zabd1',
+      navatticTitle: 'Watch Playbacks of Digital Experiences',
+    },
+    {
+      badge: 'EXPERIMENTS',
+      title: 'Conduct Experiments',
+      blurb: 'Measure the impact of multivariate testing',
+      img: '/navattic/06_Experiments_314x139.png',
+      navatticOpen: 'cmfciul3m000004jr47ov9ji6',
+      navatticTitle: 'Evaluate Experiment Results',
+    },
+  ]}
+/>
+
+{/* Section CTA — content lives in MDX so it’s easy to change or A/B test */}
+<div style={{ textAlign: 'center', marginTop: '28px' }}>
+  <a
+    href="https://mixpanel.com/contact-us/sales/"
+    className="sgt-cta"
+    style={{
+      display: 'inline-flex',
+      alignItems: 'center',
+      gap: '8px',
+      fontWeight: 600,
+      fontSize: '15px',
+      padding: '10px 14px',
+      borderRadius: '10px',
+      border: '1px solid rgb(139, 92, 246)',
+      color: 'var(--sgt-title)',
+      background: 'var(--sgt-card-bg)',
+      textDecoration: 'none',
+      boxShadow: '0 4px 16px rgba(0,0,0,.12)',
+      transition: 'transform .2s ease, box-shadow .2s ease, background .2s ease',
+    }}
+  >
+    Want a guided demo instead?
+    <span aria-hidden>→</span>
+  </a>
+</div>
+
+<style jsx global>{`
+  /* CTA interactions reuse component look & feel */
+  .sgt-cta:hover {
+    transform: translateY(-1px);
+    box-shadow: 0 8px 20px rgba(139, 92, 246, 0.18);
+    background: rgba(139, 92, 246, 0.08);
+  }
+  .sgt-cta:focus-visible {
+    outline: 2px solid rgb(139, 92, 246);
+    outline-offset: 3px;
+    border-radius: 10px;
+  }
+`}</style>
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/_meta.ts b/pages/guides/strategic-playbooks/onboarding-playbook/launch/_meta.ts
index 6d4a964c19..4e0130f879 100644
--- a/pages/guides/strategic-playbooks/onboarding-playbook/launch/_meta.ts
+++ b/pages/guides/strategic-playbooks/onboarding-playbook/launch/_meta.ts
@@ -1,9 +1,5 @@
 export default {
-	"create-boards": "Create Boards",
-	"discover-insights": "Discover Insights",
-	"analyze-conversions": "Analyze Conversions",
-	"build-user-flows": "Build User Flows",
-	"track-user-retention": "Track User Retention",
-	"define-cohorts": "Define Cohorts",
-	"revenue-analytics": "Revenue Analytics"
-}
+    "roll-out": "Roll Out",
+    "train-users": "Train Users",
+    "drive-adoption": "Drive Adoption",
+}
\ No newline at end of file
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/drive-adoption.mdx b/pages/guides/strategic-playbooks/onboarding-playbook/launch/drive-adoption.mdx
new file mode 100644
index 0000000000..cf37466f9f
--- /dev/null
+++ b/pages/guides/strategic-playbooks/onboarding-playbook/launch/drive-adoption.mdx
@@ -0,0 +1,93 @@
+import { Callout } from 'nextra/components'
+
+# Activate Your Analytics Culture: A Guide to Driving Mixpanel Adoption
+
+Rolling out Mixpanel is just the beginning. True success happens when your teams use data to make faster, smarter decisions every day.
+
+This guide walks you through how to **execute an adoption plan** that builds lasting habits, empowers champions, and turns analytics into action.
+
+---
+
+## What Is an Adoption Plan?
+
+An adoption plan ensures your Mixpanel rollout becomes part of how your organization *thinks and works*, not just another tool to log into.
+
+Without one, teams often stall after setup—reports go unused, dashboards get stale, and decisions revert to intuition. With a strong plan, Mixpanel becomes a daily part of your company’s operating rhythm.
+
+---
+
+## Select Your Adoption Approach
+
+Organizations typically scale Mixpanel adoption in one of two ways:
+
+### Team-by-Team Approach
+
+If you’re just getting started, it usually makes sense to start small.
+
+- Start with one or two high-impact teams—often Product, Growth, or Engineering.
+- Focus on clear use cases that demonstrate value quickly, like activation or retention analysis.
+- Use early wins to refine your training, data setup, and communication plan.
+    - ✅ **Best when**: You are building confidence and proving Mixpanel’s value before scaling.
+    - ⚠️ **Watch out for**: Expanding too fast before teams have strong habits or success stories to share.
+
+### Multi-Team Approach
+
+If your organization is ready for broader rollout, expand adoption across several teams in parallel.
+
+- Ensure your tracking plan, taxonomy, and enablement materials are consistent.
+- Host joint enablement sessions to align teams on shared metrics and best practices.
+- Encourage collaboration across teams to compare insights and share dashboards.
+    - ✅ **Best when**: Mixpanel foundations are solid and multiple teams are data-curious.
+    - ⚠️ **Watch out for**: Misalignment—without a shared data language, multi-team adoption can fragment quickly.
+
+<Callout type="info">
+    **Pro tip:** Most organizations start team-by-team to learn what works, then graduate to a multi-team rollout once data structures and champions are established.
+</Callout>
+
+---
+
+## Keep Momentum and Build a Data Habit
+
+Adoption isn't a one-time event—it's a practice. The goal is to weave Mixpanel into everyday decision-making.
+
+**Here is how to sustain it:**
+
+- **Celebrate data wins.** Highlight teams that made impactful decisions using Mixpanel.
+- **Automate reminders.** Use [alerts](/docs/features/alerts) to deliver insights automatically.
+- **Document learnings.** Add [annotations](/docs/features/annotations) to track what happened when metrics changed.
+- **Review usage trends.** Periodically review Mixpanel usage to see which reports or dashboards are most valuable.
+
+<Callout type="warning">
+    **Pitfall:** Without continuous reinforcement, adoption can fade quickly after launch.
+</Callout>
+
+👉 **Do this next:** Schedule regular check-ins with champions and leadership to review wins and adjust enablement priorities.
+
+---
+
+## Scale What Works
+
+Once your pilot teams are thriving, scale adoption intentionally—not all at once. Use data and feedback from early adopters to refine your approach.
+
+**Steps to take:**
+
+- **Document Lessons Learned**: Capture what worked and what didn't during early rollout.
+- **Build Internal Templates**: Standardize dashboards or funnels that new teams can copy.
+- **Onboard New Teams**: Host shorter, team-specific intros that highlight relevant Mixpanel use cases.
+- **Measure Progress**: Track organization-wide adoption metrics—e.g. % of active Mixpanel users, reports viewed, or alerts configured.
+
+<Callout type="info">
+    **Pro tip:** Make Mixpanel part of your onboarding for every new employee—one login session and one “first insight” is all it takes to build the habit.
+</Callout>
+
+---
+
+## Key Takeaways
+
+Adopting Mixpanel is about more than setup—it’s about creating lasting data habits that shape how teams work.
+
+- It's often a good idea to start small, prove value, then scale to more teams.
+- Celebrate wins and make data part of daily work.
+- Standardize success and track adoption over time.
+
+👉 **Do this next:** Ready to put this into practice? Download the [Mixpanel Adoption Plan](https://docs.google.com/spreadsheets/d/12FJDLLTpOgw-5B4_EoA9coUkp6eM1kKAwr2mAgiNrds/edit?gid=1651252994#gid=1651252994) to outline, track, and measure your adoption journey.
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/roll-out.mdx b/pages/guides/strategic-playbooks/onboarding-playbook/launch/roll-out.mdx
new file mode 100644
index 0000000000..8c286e854d
--- /dev/null
+++ b/pages/guides/strategic-playbooks/onboarding-playbook/launch/roll-out.mdx
@@ -0,0 +1,115 @@
+import { Callout } from 'nextra/components'
+
+# Roll Out Mixpanel with Confidence
+
+Move from implementation to adoption with a clear plan for deploying, rolling out, and rallying your teams.
+
+---
+
+## Deploy to Production
+Your Mixpanel setup is complete—now it's time to take it live. Deploying to production means you are connecting your tested implementation to your real, live user data.
+
+### Reiterate Benefits
+
+When you go live with Mixpanel, you enable your teams to:
+
+- See **real user behavior** as it happens.
+- Track **key activation and retention metrics**.
+- Test **hypotheses quickly** with data-backed evidence.
+- Build a **shared understanding** of product performance across teams.
+
+Before rollout, remind stakeholders that this phase turns your tracking plan into tangible value. It's where insight begins.
+
+### Deployment Checklist
+
+For deployment, confirm that you’ve:
+
+- [Completed QA](/guides/guides-by-use-case/ensuring-data-quality) in your staging project.
+- Prepared your [production project](/docs/orgs-and-projects/managing-projects#creating-projects).
+- [Enabled tracking](/docs/quickstart/capture-events/track-events) in your production project.
+- Triggered historical backfilling (if necessary).
+- Monitored live data for any potential anomalies.
+- Implemented your [data governance strategy](/docs/data-governance).
+- [Granted production access](/docs/orgs-and-projects/roles-and-permissions#invite-users) to the correct users.
+
+For a detailed, step-by-step version of this list, check out the full [Mixpanel Production Deployment Checklist](https://docs.google.com/spreadsheets/d/12FJDLLTpOgw-5B4_EoA9coUkp6eM1kKAwr2mAgiNrds/edit?gid=751571839#gid=751571839). It covers everything from validation in staging to go-live monitoring.
+
+<Callout type="info">
+    **Pro tip:** Keep a small monitoring window after deployment (24–48 hours) to catch any anomalies before promoting org-wide usage.
+</Callout>
+
+---
+
+## Roll Out Mixpanel
+
+Once your production deployment is verified, the focus shifts to planning for adoption—getting the right people using Mixpanel effectively.
+
+### Plan Your Adoption
+
+Start with a short plan that outlines:
+
+- **Key success metrics:** Decide what adoption looks like—e.g. weekly active Mixpanel users, reports viewed, or dashboard subscriptions.
+- **Your launch goal:** For example, “Every PM and designer logs into Mixpanel and saves a report within 1 week.”
+- **Timeline:** Who needs access first, what happens on launch day, and how you'll follow up.
+
+<Callout type="info">
+    **Pro tip:** Use the Mixpanel Usage report in Mixpanel Settings to monitor which teammates are actively using Mixpanel.
+</Callout>
+
+---
+
+### Identify Stakeholders and Champions
+
+A strong rollout is driven by the right people:
+
+| Role               | Responsibility                                                                                                                                                      |
+|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Executive Sponsor**  | Drives Mixpanel adoption by securing resources, removing roadblocks, and ensuring alignment with company goals.                                                     |
+| **Team Leads**         | Leads Mixpanel adoption within their team by setting KPIs, providing training and resources, and reinforcing data-driven decisions through regular use of Mixpanel. |
+| **Mixpanel Champions** | Enthusiastic Mixpanel advocates who inspire peer adoption, answer questions, provide training, and share best practices.                                            |
+
+Encourage each team to nominate a *Mixpanel Champion* who can model usage and surface success stories.
+
+👉 **Do this next:** Establish a cadence—monthly data reviews or shared “insight of the week—to keep Mixpanel relevant.
+
+---
+
+## Communicate the Launch
+
+Treat your rollout like a product launch. Build excitement, show value, and invite participation.
+
+**Before Launch**
+
+- Share a message from your sponsor or product lead explaining why Mixpanel is being introduced.
+- Preview what teams will gain (“We’ll be able to answer questions like where users drop off in signup").
+- Point to a “Start Here” dashboard and short walkthrough.
+
+**Launch Day**
+
+- Host a short demo or all-hands to introduce Mixpanel.
+- Encourage each team to explore one key report.
+- Celebrate first discoveries in Slack or during standups.
+
+**After Launch**
+
+- Share early insights (“We discovered our activation rate doubled after signup simplification”).
+- Ask for feedback and use it to refine your dashboards or events.
+- Reinforce success in monthly reviews.
+
+<Callout type="info">
+    **Pro tip:** Save your launch message and templates—you can reuse them for new teams or product lines later.
+</Callout>
+
+👉 **Do this next:** Download the [Mixpanel Adoption Execution Checklist](https://docs.google.com/spreadsheets/d/12FJDLLTpOgw-5B4_EoA9coUkp6eM1kKAwr2mAgiNrds/edit?gid=2005429816#gid=2005429816) and use it to help guide your rollout beyond launch. It covers how to communicate progress, celebrate team successes, and keep momentum strong through ongoing education and evangelism.
+
+---
+
+## Key Takeaways
+
+- When you deploy Mixpanel to production, you bring your implementation to life. When you roll it out thoughtfully, you build a data-driven culture.
+- Verify your setup in production before rolling out broadly.
+- Align on adoption goals and track them from day one.
+- Appoint champions to sustain usage across teams.
+- Communicate clearly and celebrate early wins.
+
+👉 **Do this next:** Make a copy of the [Mixpanel Production Deployment Checklist](https://docs.google.com/spreadsheets/d/12FJDLLTpOgw-5B4_EoA9coUkp6eM1kKAwr2mAgiNrds/edit?gid=751571839#gid=751571839) and use it to validate your setup before rollout. It’s the fastest way to confirm your setup is complete and Mixpanel is ready for production.
\ No newline at end of file
diff --git a/pages/guides/strategic-playbooks/onboarding-playbook/launch/train-users.mdx b/pages/guides/strategic-playbooks/onboarding-playbook/launch/train-users.mdx
new file mode 100644
index 0000000000..3e15139a8e
--- /dev/null
+++ b/pages/guides/strategic-playbooks/onboarding-playbook/launch/train-users.mdx
@@ -0,0 +1,78 @@
+import { Callout, Steps } from 'nextra/components'
+
+# Train Your Team to Use Mixpanel Effectively
+
+Learn how to onboard, train, and scale Mixpanel knowledge across your organization using built-in Mixpanel tools and free public resources.
+
+---
+
+## What is This Guide About
+
+Whether you are just starting out or expanding Mixpanel usage to new teams, effective training ensures consistent data literacy, faster adoption, and better ROI. This guide helps you set up a repeatable internal enablement process.
+
+---
+
+## 1. Start with the Fundamentals
+
+Establish a shared understanding of Mixpanel’s purpose, value, and core workflows.
+
+- ✅ **Do** provide a unified introduction to Mixpanel’s “why” and “how.”
+- ❌ **Do not** assume each team member will figure it out on their own.
+
+**Steps to take:**
+
+1. Share Mixpanel's overview resources like the [Mixpanel Introduction](/guides/mixpanel-introduction).
+
+2. Encourage teams to explore the [Docs home page](/docs/what-is-mixpanel) for guided discovery.
+
+3. Highlight the [Mixpanel Community](https://community.mixpanel.com/) for Q&A and inspiration from peers.
+
+4. Review training videos on [Mixpanel's Core Reports](/guides/guides-by-topic/core-reports).
+
+
+<Callout type="warning">
+    **Pitfall:** Skipping this step leads to inconsistent understanding of Mixpanel concepts across departments.
+</Callout>
+
+---
+
+## 2. Tailor Training by Role
+
+Different teams use Mixpanel differently; PMs ask questions, engineers instrument data, analysts interpret results.
+
+**Steps to take:**
+
+1. Identify each team's Mixpanel use cases.
+2. Pair each with relevant public resources (Docs, Community posts, blogs). Here are a few to get you started:
+    - **PMs & Analysts:** [Insights](/docs/reports/insights), [Funnels](/docs/reports/funnels), [Retention](/docs/reports/retention), [Cohorts](/docs/users/cohorts), [Experiments](/docs/experiments).
+    - **Engineers:** [SDK setup](/docs/quickstart/install-mixpanel), [Event tracking](/docs/quickstart/capture-events), [Feature Flags](/docs/featureflags).
+
+<Callout type="info">
+    **Pro tip:** Create internal “office hours” where each team shares how they are using Mixpanel and what they have learned.
+</Callout>
+
+---
+
+## 3. Reinforce and Scale
+
+Make Mixpanel learning continuous, not one-and-done.
+
+**Tools to Help**
+
+- [Mixpanel Community](https://community.mixpanel.com/): Stay connected with updates, webinars, and expert threads.
+- [Mixpanel Blog](https://mixpanel.com/blog/): Discover real-world use cases and product deep dives.
+- [Mixpanel Changelog](/changelogs): Keep teams up to date on new features.
+
+Ongoing engagement keeps Mixpanel top of mind and helps your team continuously improve.
+
+---
+
+## Key Takeaways
+
+- Anchor everyone in the why behind Mixpanel.
+- Customize learning by role.
+- Use Docs and Community for ongoing learning.
+- Make training a repeatable part of onboarding and growth.
+
+
+🌐 **Stay connected**: Join the [Mixpanel Community](https://community.mixpanel.com/) to share how you are driving adoption and learn from other champions rolling Mixpanel out across their organizations.
\ No newline at end of file
diff --git a/pages/guides/what-is-mixpanel.mdx b/pages/guides/what-is-mixpanel.mdx
deleted file mode 100644
index 61ef0b338d..0000000000
--- a/pages/guides/what-is-mixpanel.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
-import ExtendedButton from "/components/ExtendedButton/ExtendedButton";
-
-# What is Mixpanel?
-
-Mixpanel will help you better understand your customers and answer questions about your product.
-It enables you to track how users engage with your product and analyze this data with interactive reports
-that let you query and visualize the results with just a few clicks.
-
-Mixpanel is built on three key concepts: [**Events**](#events), [**Users**](#users), and [**Properties**](#properties).
-
-<br></br>
-<div
-  style={{
-    position: "relative",
-    paddingBottom: "64.90384615384616%",
-    height: 0,
-  }}
->
-  <p>
-    <iframe
-      src="https://www.youtube.com/embed/sRQCfmvh3vg"
-      frameBorder="0"
-      webkitallowfullscreen="true"
-      mozallowfullscreen="true"
-      allowFullScreen
-      style={{
-        position: "absolute",
-        top: 0,
-        left: 0,
-        width: "100%",
-        height: "100%",
-        borderRadius: "16px",
-      }}
-    ></iframe>
-  </p>
-</div>
-
-## Concepts
-
-Before you get started, you should know three Mixpanel concepts:
-
-    - **Events** are actions that happen in your product
-    - **Users** are the people who use your product
-    - **Properties** are the attributes of your users and events
-
-### Events
-
-An event is a data point that represents an interaction between a user and your product. Events can be a wide range of interactions.
-
-Imagine you run a cafe where customers can purchase a coffee via an app. Each purchase is an event that can be tracked in Mixpanel.
-
-![image](/event-1.svg)
-
-### Users
-
-On the other side of an event is a user — the specific individual who completed an interaction with your product.
-
-Each user has a unique identifier that you can use to track their activity. This identifier can be an email address, a username, or a unique ID. Mixpanel uses a unique ID to identify users.
-
-![image](/events-and-users.svg)
-
-### Properties
-
-You can track additional information about **users** and **events**. These details are called **properties**.
-
-An **Event Property** describes an event. For a coffee purchase, the event would be _Purchased Item_ and the event properties could be _type_ (in this case a Coffee) and _price_ (in this case $2.50).
-
-![image](/event.svg)
-
-A **User Property** describes a User. This could be their name, email, age, etc.
-
-![image](/user-profile.svg)
-
-Properties allow you to create groups of users (aka [cohorts](/docs/users/cohorts)) and also enable you to filter for certain events or users. These
-powerful features make it easy to identify trends and new customer insights.
\ No newline at end of file
diff --git a/pages/overrides.scss b/pages/overrides.scss
index 05eada3fd2..56b1cc4ba2 100644
--- a/pages/overrides.scss
+++ b/pages/overrides.scss
@@ -696,6 +696,13 @@ article {
       //     opacity: 0.4;
       //   }
     }
+
+    // Modify Steps
+    .nextra-steps h2:before,.nextra-steps h3:before,.nextra-steps h4:before{
+        background-color: colors.$purple20;
+        color: colors.$purple140;
+    }
+
     //####Light Theme Code Syntax and Box####
     code,
     kbd,
@@ -1440,6 +1447,13 @@ article {
       }
     }
 
+    // Modify steps
+    .nextra-steps h2:before,.nextra-steps h3:before,.nextra-steps h4:before{
+        background-color: colors.$purple140;
+        color: colors.$purple20;
+        border-color: colors.$purple140;
+    }
+
     //ID management banner style
     .idManagementBanner {
       .nextra-callout {
diff --git a/public/Data_Model_with_Group_Analytics.png b/public/Data_Model_with_Group_Analytics.png
new file mode 100644
index 0000000000..6dccea66c4
Binary files /dev/null and b/public/Data_Model_with_Group_Analytics.png differ
diff --git a/public/Experiments_and_FF.png b/public/Experiments_and_FF.png
new file mode 100644
index 0000000000..44d2e7b369
Binary files /dev/null and b/public/Experiments_and_FF.png differ
diff --git a/public/navattic/01_OverviewTour_314x139.png b/public/navattic/01_OverviewTour_314x139.png
new file mode 100644
index 0000000000..2104ebd1d3
Binary files /dev/null and b/public/navattic/01_OverviewTour_314x139.png differ
diff --git a/public/navattic/02_Insights_314x139.png b/public/navattic/02_Insights_314x139.png
new file mode 100644
index 0000000000..a3dd180ad8
Binary files /dev/null and b/public/navattic/02_Insights_314x139.png differ
diff --git a/public/navattic/03_Funnels_314x139.png b/public/navattic/03_Funnels_314x139.png
new file mode 100644
index 0000000000..86d4977681
Binary files /dev/null and b/public/navattic/03_Funnels_314x139.png differ
diff --git a/public/navattic/04_Autocapture_314x139.png b/public/navattic/04_Autocapture_314x139.png
new file mode 100644
index 0000000000..f066c72042
Binary files /dev/null and b/public/navattic/04_Autocapture_314x139.png differ
diff --git a/public/navattic/05_SessionReplay_314x139.png b/public/navattic/05_SessionReplay_314x139.png
new file mode 100644
index 0000000000..9570236093
Binary files /dev/null and b/public/navattic/05_SessionReplay_314x139.png differ
diff --git a/public/navattic/06_Experiments_314x139.png b/public/navattic/06_Experiments_314x139.png
new file mode 100644
index 0000000000..7baefb66d1
Binary files /dev/null and b/public/navattic/06_Experiments_314x139.png differ
diff --git a/public/oada-loop-detail.png b/public/oada-loop-detail.png
new file mode 100644
index 0000000000..d2aaaf24e4
Binary files /dev/null and b/public/oada-loop-detail.png differ
diff --git a/public/oada-loop-simple-wide-fcf9fa.png b/public/oada-loop-simple-wide-fcf9fa.png
new file mode 100644
index 0000000000..9e488230c2
Binary files /dev/null and b/public/oada-loop-simple-wide-fcf9fa.png differ
diff --git a/redirects/local.txt b/redirects/local.txt
index 723dd98181..6673e988bc 100644
--- a/redirects/local.txt
+++ b/redirects/local.txt
@@ -293,4 +293,15 @@
 /guides/launch/track-user-retention /guides/strategic-playbooks/onboarding-playbook/launch/track-user-retention
 /guides/launch/define-cohorts /guides/strategic-playbooks/onboarding-playbook/launch/define-cohorts
 /guides/launch/revenue-analytics /guides/strategic-playbooks/onboarding-playbook/launch/revenue-analytics
-/guides/beyond-onboarding /guides/strategic-playbooks/onboarding-playbook/beyond-onboarding
\ No newline at end of file
+/guides/beyond-onboarding /guides/strategic-playbooks/onboarding-playbook/beyond-onboarding
+/guides/what-is-mixpanel /guides/mixpanel-introduction
+/guides/guides-by-use-case/driving-product-innovation /guides/guides-by-use-case/engage-your-users/drive-product-innovation
+/guides/guides-by-use-case/ensuring-data-quality /guides/guides-by-workflow/ensure-data-quality
+/guides/guides-by-use-case/build-a-tracking-strategy /guides/guides-by-workflow/build-tracking-strategy
+/guides/strategic-playbooks/onboarding-playbook/launch/create-boards /guides/guides-by-topic/core-reports/create-boards
+/guides/strategic-playbooks/onboarding-playbook/launch/discover-insights /guides/guides-by-topic/core-reports/discover-insights
+/guides/strategic-playbooks/onboarding-playbook/launch/analyze-conversions /guides/guides-by-topic/core-reports/analyze-conversions
+/guides/strategic-playbooks/onboarding-playbook/launch/build-user-flows /guides/guides-by-topic/core-reports/build-user-flows
+/guides/strategic-playbooks/onboarding-playbook/launch/define-cohorts /guides/guides-by-topic/core-reports/define-cohorts
+/guides/strategic-playbooks/onboarding-playbook/launch/track-user-retention /guides/guides-by-topic/core-reports/track-user-retention
+/guides/strategic-playbooks/onboarding-playbook/launch/revenue-analytics /docs/features/revenue-analytics
\ No newline at end of file