Hi Team,
Can someone help explain why the daily numbers for D1-6 retention don’t match the averages at the top row. I have added an offset as well in the date range so that we do not have incomplete data.
Hey @Diksha Parti, this mismatch is expected: the top-row “Overall” retention is an aggregate across all eligible cohorts (effectively weighted by cohort size), while the daily row values are per-cohort percentages for that cohort-of-day. Even with a date range offset, D6 will still exclude the most recent cohorts that haven’t yet “matured,” so the top row won’t equal the simple average of the daily rows. Your “Return On” setting (e.g., Day X vs. Day 0–6) and eligibility windows further affect which users are counted in the top row versus each daily cohort row.
Hello! In React-Native mobile project we have error: Amplitude Logger [Error]: Failed to set cookie for key: AMP_TEST. Error: Cannot set property 'cookie' of undefined Error Component Stack: ``` The package version is "@amplitude/analytics-react-native": "1.5.1", Steps to Reproduce: * Initialize Amplitude with our API key…
We implemented first party tracking using the basic JS SDK on the browser and pointing the payload to our servers like this: amplitude.init(AMPLITUDE_API_KEY, { serverUrl: serverUrl, autocapture: { attribution: { excludeReferrers: [/domain1\.com$/, /domain2\.com$/], }, formInteractions: false, fileDownloads: false, }, });…
My Android app is primarily a background app. Does Amplitude track events for such an app? Please let me know.
here is the referance graph: https://app.amplitude.com/analytics/demo/chart/new/363tk5og In this graph, retention is currently being calculated based on the next day, but I want to analyze it based on the previous day instead. Example: For July 27, we should compare retention against July 26, not July 28. * So for 1-day…
Hi everybody! I need your help with a client request: my client is used to analyze landing pages performance with the standard report from GA4 and I need to create something similar in Amplitude. What I already have: * session entries grouped by page URL * purchase event calculated as session totals grouped by page URL and…
