Hi @Rim ,   You're using:   window.s_c_il[0].tl();   But instead of firing an event call (non-pageview), it's sending a pageview hit (s.t() call). This is not expected, since s.tl() should only send a custom link/event hit (like for downloads, outbound links, etc.).   What s.tl() Needs to Work Prope...

Hi @MichaelCu5 ,   Key Misunderstanding: The total average is not a simple arithmetic average of the row-wise "Average Time on Site" values. Instead, most analytics platforms (like Adobe Analytics or GA) calculate overall average time using a weighted average based on total time and visit count — no...

Discover key features of Adobe Customer Journey Analytics (CJA)—from unified cross-channel insights to Freeform Analysis, real-time data, and the new Data Dictionary. Make every journey count!

Navigating complex datasets just got easier! Adobe Customer Journey Analytics now offers a Data Dictionary: your go-to reference to explore and understand every dimension, metric, and component used in your projects. Why it matters: Simplifies data governance Enables collaboration across teams Pr...

Hi @RyanLG ,   This is a known issue in the new Adobe Target UI for Automated Personalization (AP) activities.   Several Adobe Target users have flagged this issue. If this is critical for your org: Raise a ticket with Adobe. Ask them to provide an internal mapping or offer export. Mention your A...

Hi @RajalakshmiMathiazhagan ,   You can calculate time difference between events using Time Between Events metric builder in CJA.  Make Sure the Events Are Properly Captured You must ensure: product section viewed and product card clicked are distinct events (e.g., custom events or specific event n...

Hi @user29588 ,   You're encountering a known limitation in Adobe Analytics Workspace scheduling, and you're not missing anything—it’s just how Adobe handles rolling dates in scheduled exports. Use Rolling Date Range Instead of Fixed Dates Instead of selecting "Today" as a specific fixed date: In y...

Hi @Shashi15 ,   Top causes: Activity Is in “Draft” But Content Was Already Saved to Page via VEC When using Visual Experience Composer (VEC), especially with single-page applications (SPAs), Target might store DOM modifications locally or in browser memory.If you previewed the experience and that p...

Hi @subha2 ,   This is a common and frustrating issue in Adobe Target’s Visual Experience Composer (VEC) — where modifications made in one experience (e.g., Experience B) mysteriously apply to Experience A and vice versa. It’s usually tied to DOM caching issues, improper selector handling, or sessio...

Hi @bjoern__koth ,   Adobe Analytics does not offer an out-of-the-box metric that gives you the number of visits between two custom events or conditions (e.g., campaign click-through → conversion) across multiple sessions. If you have CJA (Adobe Experience Platform): CJA supports cross-visit stitchi...