# product analytics

Product analytics is a discipline and software category that analyzes user interactions with digital products using behavioral event data.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Introducing Stitch Loop: A new way to build and evolve products

DevFeed: [Introducing Stitch Loop: A new way to build and evolve products](<https://devfeed.tech/articles/introducing-stitch-loop-a-new-way-to-build-and-evolve-products-141507.md>)

Original publisher: [Read original article](<https://blog.google/innovation-and-ai/models-and-research/google-labs/stitch-loop/>)

Author: Justin Toupin

Published: 2026-11-18T17:00:00Z

Content type: release

Language: en

Sources: [Google Labs](<https://devfeed.tech/sources/google-labs.md>)

Topics: [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [antigravity](<https://devfeed.tech/tags/antigravity.md>), [automate](<https://devfeed.tech/tags/automate.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [build](<https://devfeed.tech/tags/build.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [checkout-conversion](<https://devfeed.tech/tags/checkout-conversion.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [code-security](<https://devfeed.tech/tags/code-security.md>), [google-labs](<https://devfeed.tech/tags/google-labs.md>), [latency](<https://devfeed.tech/tags/latency.md>), [none](<https://devfeed.tech/tags/none.md>), [products](<https://devfeed.tech/tags/products.md>), [security](<https://devfeed.tech/tags/security.md>), [stitch](<https://devfeed.tech/tags/stitch.md>)

### AI overview

Stitch Loop is a Google Labs product agent that connects a codebase with product context and live metrics, then repeatedly proposes and builds improvements toward measurable goals. Its workflow presents evidence-backed suggestions and scoped solutions with tradeoffs, writes selected changes in an isolated cloud sandbox, and opens a GitHub pull request for human review; nothing merges without approval. It monitors results and continues watching after a goal is met. The text describes built-in security, latency, and accessibility loops, plus custom loops. Its security loop pairs Gemini 4 Carbon with CodeMender to find vulnerabilities and propose fixes in reviewable PRs. Stitch Loop can also provide persistent product context to coding agents through Stitch CLI and MCP, and supports Slack digests and loop creation. Access is via a waitlist, with eligible Google AI Ultra users receiving priority.

### Source excerpt

Arrow, reload, and message icons. At the bottom are the text "Security", "Latency", "Accessibility", "Stitch Loop"

## Using Analytics to Disrupt the Home Insurance Industry | Blog | Fivetran

DevFeed: [Using Analytics to Disrupt the Home Insurance Industry | Blog | Fivetran](<https://devfeed.tech/articles/using-analytics-to-disrupt-the-home-insurance-industry-blog-fivetran-141346.md>)

Original publisher: [Read original article](<https://wf.fivetran.com/blog/using-analytics-to-disrupt-the-home-insurance-industry>)

Author: Fivetran

Published: 2026-11-18T06:13:15Z

Content type: news

Language: en

Sources: [Fivetran Blog](<https://devfeed.tech/sources/fivetran-blog.md>)

Topics: [analytics stack](<https://devfeed.tech/topics/analytics-stack.md>), [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>), [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>)

Tags: [analysis](<https://devfeed.tech/tags/analysis.md>), [analyst](<https://devfeed.tech/tags/analyst.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [blog](<https://devfeed.tech/tags/blog.md>), [business](<https://devfeed.tech/tags/business.md>), [data](<https://devfeed.tech/tags/data.md>), [data-stack](<https://devfeed.tech/tags/data-stack.md>), [disrupt](<https://devfeed.tech/tags/disrupt.md>), [fivetran](<https://devfeed.tech/tags/fivetran.md>), [home](<https://devfeed.tech/tags/home.md>), [industry](<https://devfeed.tech/tags/industry.md>), [insurance](<https://devfeed.tech/tags/insurance.md>), [leveraging](<https://devfeed.tech/tags/leveraging.md>), [model](<https://devfeed.tech/tags/model.md>), [modern](<https://devfeed.tech/tags/modern.md>), [modern-data](<https://devfeed.tech/tags/modern-data.md>), [modern-data-stack](<https://devfeed.tech/tags/modern-data-stack.md>), [stack](<https://devfeed.tech/tags/stack.md>), [startup](<https://devfeed.tech/tags/startup.md>), [using](<https://devfeed.tech/tags/using.md>)

### AI overview

Luko uses centralized data and analytics to support a preventive home insurance model focused on reducing claims. Its data stack brings together finance, claims, customer support and IoT data, giving teams a more reliable shared view for daily performance tracking and decisions. The article credits Fivetran connectors and dbt with making ingestion and transformation manageable for a company without data engineers, helping it measure services and automate Giveback calculations. Luko says it can nearly forecast claim reimbursements in real time; its previous year's Giveback totaled EUR 100,000.

### Source excerpt

A French startup is leveraging its modern data stack to overturn a longstanding business model.

## Powered By Fivetran Fuels Savvy Data Insights Platforms and Agencies | Blog | Fivetran

DevFeed: [Powered By Fivetran Fuels Savvy Data Insights Platforms and Agencies | Blog | Fivetran](<https://devfeed.tech/articles/powered-by-fivetran-fuels-savvy-data-insights-platforms-and-agencies-blog-fivetran-140250.md>)

Original publisher: [Read original article](<https://wf.fivetran.com/blog/powered-by-fivetran-agencies>)

Author: Fivetran

Published: 2026-11-18T02:46:08Z

Content type: release

Language: en

Sources: [Fivetran Blog](<https://devfeed.tech/sources/fivetran-blog.md>)

Topics: [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>)

Tags: [agencies](<https://devfeed.tech/tags/agencies.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [api](<https://devfeed.tech/tags/api.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automated](<https://devfeed.tech/tags/automated.md>), [blog](<https://devfeed.tech/tags/blog.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [building-products](<https://devfeed.tech/tags/building-products.md>), [business](<https://devfeed.tech/tags/business.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [config](<https://devfeed.tech/tags/config.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [connect](<https://devfeed.tech/tags/connect.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [data](<https://devfeed.tech/tags/data.md>), [fivetran](<https://devfeed.tech/tags/fivetran.md>), [insights](<https://devfeed.tech/tags/insights.md>), [platforms](<https://devfeed.tech/tags/platforms.md>)

### AI overview

Powered by Fivetran helps analytics product teams embed automated data integrations instead of building and maintaining direct source integrations themselves. Its Connect Card lets end users submit and authenticate credentials to Fivetran over HTTPS without passing through the product team's servers; it includes setup instructions, configuration tests and troubleshooting feedback. Developers embed it using two REST API calls and a redirect URL. The API also supports destination management, programmatic group creation for customers, more than 148 supported sources through the Connector Management API, and programmatic table configuration for custom schemas. The excerpt describes these capabilities and invites readers to try the service; it does not provide comparative performance or security details beyond the HTTPS credential flow.

### Source excerpt

Provide real insights and not just a report card - with Fivetran's list of connectors

## Why Front migrated from Elasticsearch to ClickHouse for "pixel-perfect" analytics at scale

DevFeed: [Why Front migrated from Elasticsearch to ClickHouse for "pixel-perfect" analytics at scale](<https://devfeed.tech/articles/why-front-migrated-from-elasticsearch-to-clickhouse-for-pixel-perfect-analytics-at-scale-144379.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/front-elasticsearch-clickhouse>)

Author: ClickHouse

Published: 2026-11-18T00:00:00Z

Content type: news

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>), [metric-standardization](<https://devfeed.tech/topics/metric-standardization.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>)

Tags: [aggregation](<https://devfeed.tech/tags/aggregation.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [aws](<https://devfeed.tech/tags/aws.md>), [b2b](<https://devfeed.tech/tags/b2b.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [customer](<https://devfeed.tech/tags/customer.md>), [data](<https://devfeed.tech/tags/data.md>), [days](<https://devfeed.tech/tags/days.md>), [development](<https://devfeed.tech/tags/development.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [metric](<https://devfeed.tech/tags/metric.md>), [more](<https://devfeed.tech/tags/more.md>), [pixel](<https://devfeed.tech/tags/pixel.md>), [scale](<https://devfeed.tech/tags/scale.md>)

### AI overview

Front moved customer-facing analytics from Elasticsearch to ClickHouse Cloud as its 25 TB workload and specialized Painless queries made new metrics slow and dependent on senior analytics engineers. It migrated gradually, writing each new event to both systems and comparing metrics, then defined each metric once in a shared framework that generates visualizations. For mutable conversations, VersionedCollapsingMergeTree reconciles changes such as deleted messages and merged threads. In one large customer's tag report, a 30-second query grew from 11 days of history in Elasticsearch to a month and a half in ClickHouse, using half as many machines of equal performance. The first metric built in the new framework took a junior engineer three days, versus several weeks for a senior engineer with Elasticsearch. The account also reports cloud-region moves dropping from days to minutes. Front says the change enables more flexible dashboards and plans to explore backlog metrics and AI-assisted metric creation.

### Source excerpt

Front powers customer-facing analytics for 9,000+ B2B companies with ClickHouse Cloud, cutting metric development from three weeks to three days and querying 4x more historical data.

## How Amplitude ships product improvements in 1-2 days with OpenAI

DevFeed: [How Amplitude ships product improvements in 1-2 days with OpenAI](<https://devfeed.tech/articles/how-amplitude-ships-product-improvements-in-1-2-days-with-openai-131631.md>)

Original publisher: [Read original article](<https://openai.com/business/customer-stories/amplitude>)

Published: 2026-11-12T20:00:00Z

Content type: news

Language: en

Sources: [OpenAI News](<https://devfeed.tech/sources/openai-news.md>)

Topics: [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [product-experimentation](<https://devfeed.tech/topics/product-experimentation.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>), [codex](<https://devfeed.tech/topics/codex.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>), [implementation](<https://devfeed.tech/topics/implementation.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [amplitude](<https://devfeed.tech/tags/amplitude.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [days](<https://devfeed.tech/tags/days.md>), [impact](<https://devfeed.tech/tags/impact.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [models](<https://devfeed.tech/tags/models.md>), [openai](<https://devfeed.tech/tags/openai.md>), [openai-models](<https://devfeed.tech/tags/openai-models.md>), [proactive](<https://devfeed.tech/tags/proactive.md>), [product](<https://devfeed.tech/tags/product.md>), [ship](<https://devfeed.tech/tags/ship.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

Amplitude's Wave analyzes product analytics, session replays, customer feedback, and code to find improvement opportunities, prepare implementation plans and acceptance criteria, and track results. Teams can route work to coding agents such as Codex, with human review varying by change type. On Amplitude's homepage, Wave proposed personalizing suggestion cards after finding that 80 of 100 sampled users typed their own questions while 12 chose a suggestion; a team-reviewed, A/B-tested change increased card-driven sends by 160% versus control after one day. Amplitude assigns models by task: GPT-6.1 Sol for deeper investigations, GPT-6 Luna for frequent lower-cost checks, and GPT-Image-2.5 Flare for mockups. Evaluations report GPT-6.1 Sol leading Amplitude's Opportunity Investigator comparison, while its Data Science Agent score was slightly below another model's (67.5 vs. 69.3) at lower mean model cost per dispatch ($1.28 vs. $2.63). Amplitude estimates Wave can help ship improvements in 1-2 days rather than roughly a month; among customer-launched work, one quarter went live the same day an opportunity surfaced, half within four days, and two thirds within a week.

### Source excerpt

Built primarily on OpenAI models, Amplitude's proactive product agent, Wave, identifies what to build, helps teams ship changes with coding agents, and measures the impact.

## What will you build with infinite engineers?

DevFeed: [What will you build with infinite engineers?](<https://devfeed.tech/articles/what-will-you-build-with-infinite-engineers-130652.md>)

Original publisher: [Read original article](<https://amplitude.com/blog/wave-launch>)

Author: Darshil Gandhi

Published: 2026-11-12T00:00:00Z

Content type: release

Language: en

Sources: [Amplitude](<https://devfeed.tech/sources/amplitude.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [product-experimentation](<https://devfeed.tech/topics/product-experimentation.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ambition](<https://devfeed.tech/tags/ambition.md>), [amplitude](<https://devfeed.tech/tags/amplitude.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analyst](<https://devfeed.tech/tags/analyst.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [approach](<https://devfeed.tech/tags/approach.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [area](<https://devfeed.tech/tags/area.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [customer](<https://devfeed.tech/tags/customer.md>), [decision](<https://devfeed.tech/tags/decision.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [next](<https://devfeed.tech/tags/next.md>), [product](<https://devfeed.tech/tags/product.md>), [results](<https://devfeed.tech/tags/results.md>), [ship](<https://devfeed.tech/tags/ship.md>)

### AI overview

Amplitude Wave connects product investigation and impact measurement to AI accelerated building. Teams set a business goal; Wave analyzes behavioral data, session replays, and customer feedback to identify Opportunities, recommend changes and test hypotheses, then measure results. Teams retain control over priorities and what reaches customers, while using product judgment to adapt recommendations. In examples, PixAI adapted a suggestion to guide new users to its Missions feature and reported higher Missions opens, publishing, and Day 1 retention. Amplitude used replay analysis to identify generic prompts that users rarely selected, then tested personalized suggestions, reporting about 160% more suggestion sends. DigitalOcean uses ranked Opportunities with experiment plans and can create Jira tickets from Wave. Wave is a paid offering for Growth and Enterprise customers; getting started includes assessing analytics and replay data. The excerpt presents these as company-reported examples and results.

### Source excerpt

Turn customer behavior into your next product decision with Amplitude Wave. Investigate opportunities, ship improvements, and measure results.

## Machine Learning to Predict Digital Frustration from Clickstream Data

DevFeed: [Machine Learning to Predict Digital Frustration from Clickstream Data](<https://devfeed.tech/articles/machine-learning-to-predict-digital-frustration-from-clickstream-data-128497.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2512.20438>)

Author: Jibin Joseph

Published: 2026-11-11T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [Predictive AI](<https://devfeed.tech/topics/predictive-ai.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [Feature Engineering](<https://devfeed.tech/topics/feature-engineering.md>), [Neural Network](<https://devfeed.tech/topics/neural-network.md>)

Tags: [apps](<https://devfeed.tech/tags/apps.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [data](<https://devfeed.tech/tags/data.md>), [e-commerce](<https://devfeed.tech/tags/e-commerce.md>), [event](<https://devfeed.tech/tags/event.md>), [lstm](<https://devfeed.tech/tags/lstm.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [roc-auc](<https://devfeed.tech/tags/roc-auc.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [user-frustration](<https://devfeed.tech/tags/user-frustration.md>)

### AI overview

Using 5.4 million events from 304,881 sessions on a real e-commerce site, the study labels frustration through rules involving rage bursts, back-and-forth navigation, cart churn, search struggle, and long wandering sessions. XGBoost reaches about 90% accuracy and 0.9579 ROC AUC; a sequence-based LSTM performs better at about 91% accuracy and 0.9705 ROC AUC. The abstract also reports that the LSTM can predict frustration reliably from the first 20-30 interactions.

### Source excerpt

arXiv:2512.20438v2 Announce Type: replace Abstract: Many businesses depend on their mobile apps and websites, so user frustration while trying to complete a task on these channels can cause lost sales and complaints. In this research, I use clickstream data from a real e-commerce site to predict whether a session is frustrated or not. Frustration is defined using certain rules based on rage bursts, back and forth navigation (U turns), cart churn, search struggle, and long wandering sessions, and applies these rules to 5.4 million raw clickstream events (304,881 sessions). From each session, I build tabular features and train standard classifier models. I also use the full event sequence to train a discriminative LSTM classifier. XGBoost reaches about 90% accuracy, ROC AUC of 0.9579, while the LSTM performs best with about 91% accuracy and a ROC AUC of 0.9705. Finally, the research shows that with only the first 20 to 30 interactions, the LSTM already predicts frustration reliably.

## Stuck with MongoDB? 5 Ways to Keep Analytics Possible

DevFeed: [Stuck with MongoDB? 5 Ways to Keep Analytics Possible](<https://devfeed.tech/articles/stuck-with-mongodb-5-ways-to-keep-analytics-possible-128947.md>)

Original publisher: [Read original article](<https://spin.atomicobject.com/mongodb-analytics/>)

Author: Jing Fan

Published: 2026-11-10T13:00:29Z

Content type: article

Language: en

Sources: [Atomic Object](<https://devfeed.tech/sources/atomic-object.md>)

Topics: [MongoDB](<https://devfeed.tech/topics/mongodb.md>), [analytics stack](<https://devfeed.tech/topics/analytics-stack.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [metric-standardization](<https://devfeed.tech/topics/metric-standardization.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [database](<https://devfeed.tech/tags/database.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [the-software-life](<https://devfeed.tech/tags/the-software-life.md>)

### AI overview

The article's practical takeaway is to shape MongoDB data for aggregation and record history as changes happen, so analytics do not depend on reconstructing past states from current documents. It recommends keeping an event collection for audit history and UI activity feeds; tagging documents with schema versions because old and new shapes can coexist; using enums for reason codes, with Zod to flag unintended changes before storage; storing metric definitions in a collection so reports can change without a code release; and capturing timestamps, promised dates, actual dates, and response times before charts are requested. The excerpt frames upfront recording as easier than trying to recover missing history later.

### Source excerpt

Sometimes the database gets picked before you write a line of code. On my current project, the rest of the company already runs on MongoDB, and no one wants a second stack to maintain. However, we can't get away from analytics or the need to aggregate data. Mongo answers those questions fine if the data [...] The post Stuck with MongoDB? 5 Ways to Keep Analytics Possible appeared first on Atomic Spin.

## How to Prioritize Product Feedback by Revenue at Risk

DevFeed: [How to Prioritize Product Feedback by Revenue at Risk](<https://devfeed.tech/articles/how-to-prioritize-product-feedback-by-revenue-at-risk-122204.md>)

Original publisher: [Read original article](<https://towardsdatascience.com/how-to-prioritize-product-feedback-by-revenue-at-risk/>)

Author: Yassin Zehar

Published: 2026-11-07T13:00:00Z

Content type: article

Language: en

Sources: [Towards Data Science](<https://devfeed.tech/sources/towards-data-science.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>)

Tags: [ai-product-management](<https://devfeed.tech/tags/ai-product-management.md>), [crm](<https://devfeed.tech/tags/crm.md>), [data](<https://devfeed.tech/tags/data.md>), [data-sciecne](<https://devfeed.tech/tags/data-sciecne.md>), [data-science](<https://devfeed.tech/tags/data-science.md>), [editor-s-picks](<https://devfeed.tech/tags/editor-s-picks.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [product](<https://devfeed.tech/tags/product.md>), [product-feedback](<https://devfeed.tech/tags/product-feedback.md>), [product-management](<https://devfeed.tech/tags/product-management.md>), [ranking](<https://devfeed.tech/tags/ranking.md>), [revenue](<https://devfeed.tech/tags/revenue.md>), [revenue-analysis](<https://devfeed.tech/tags/revenue-analysis.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [risk](<https://devfeed.tech/tags/risk.md>), [sales](<https://devfeed.tech/tags/sales.md>), [support](<https://devfeed.tech/tags/support.md>), [synthetic](<https://devfeed.tech/tags/synthetic.md>), [tests](<https://devfeed.tech/tags/tests.md>), [tickets](<https://devfeed.tech/tags/tickets.md>)

### AI overview

Bellwether joins feedback signals to CRM accounts and ranks themes by estimated revenue at risk, using account ARR, the share of signals raised in churn, renewal, or competitive contexts, and renewal proximity. In the fictional Volta corpus, SSO & SCIM rises from eighth by mentions to first by revenue risk, while dark mode falls from second to last; the four most-requested themes account for 75% of mentions but 8.5% of estimated risk. The ranking stays the same under three tested renewal-proximity functions, but losing account attribution can leave mentions visible while their revenue is unpriced, so the priced share should accompany the score. Ingestion, clustering, accounts, and figures are synthetic; the experiments test scoring on generated data, not real-world clustering. The author also flags double counting across themes, point estimates without intervals in the interface, and ARR-only weighting.

### Source excerpt

Bellwether joins support tickets, store reviews, sales calls, and NPS to CRM accounts, then stress-tests the ranking on 6,693 synthetic signals. The post How to Prioritize Product Feedback by Revenue at Risk appeared first on Towards Data Science.

## Get Your Ecommerce Data Ready Before Holiday Traffic Arrives

DevFeed: [Get Your Ecommerce Data Ready Before Holiday Traffic Arrives](<https://devfeed.tech/articles/get-your-ecommerce-data-ready-before-holiday-traffic-arrives-121115.md>)

Original publisher: [Read original article](<https://amplitude.com/blog/holiday-ecommerce-data>)

Author: Michele Morales

Published: 2026-11-04T00:00:00Z

Content type: tutorial

Language: en

Sources: [Amplitude](<https://devfeed.tech/sources/amplitude.md>)

Topics: [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [data](<https://devfeed.tech/topics/data.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>)

Tags: [amplitude](<https://devfeed.tech/tags/amplitude.md>), [arrays](<https://devfeed.tech/tags/arrays.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [configure](<https://devfeed.tech/tags/configure.md>), [data](<https://devfeed.tech/tags/data.md>), [ecommerce](<https://devfeed.tech/tags/ecommerce.md>), [events](<https://devfeed.tech/tags/events.md>), [funnels](<https://devfeed.tech/tags/funnels.md>), [holiday](<https://devfeed.tech/tags/holiday.md>), [hub](<https://devfeed.tech/tags/hub.md>), [product](<https://devfeed.tech/tags/product.md>), [shopping](<https://devfeed.tech/tags/shopping.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

Trustworthy ecommerce analysis during holiday traffic depends on validating tracking and configuration before the sale. Test shopping journeys across devices and payment paths, reconcile purchases and revenue with the order system, and check for missing or duplicate events and identifier gaps. Verify purchase product arrays and item properties; validate item-level revenue separately from order-level revenue, and use the order system if the calculation cannot be confirmed. Configure discovery context and persisted properties with explicit attribution rules, keeping onsite discovery distinct from acquisition channel. Then validate Amplitude's Purchase by Product and Product Discovery views against known journeys, and test funnel alerts, delivery delay, and escalation ownership. Server-side or hybrid tracking needs checks for identifiers, properties, retries, deduplication, and whether browser or discovery context is available. The excerpt recommends testing configuration changes outside production and scheduling untested structural changes early enough to validate.

### Source excerpt

Prepare your ecommerce data for holiday shopping. Validate events, product arrays, attribution, and funnels, then configure your Amplitude ecommerce hub.

## Feature Theater: The AI Industry's Real Product Is Mediocrity at Scale

DevFeed: [Feature Theater: The AI Industry's Real Product Is Mediocrity at Scale](<https://devfeed.tech/articles/feature-theater-the-ai-industry-s-real-product-is-mediocrity-at-scale-114851.md>)

Original publisher: [Read original article](<https://hackernoon.com/feature-theater-the-ai-industrys-real-product-is-mediocrity-at-scale?source=rss>)

Author: Andrew Schwabe

Published: 2026-11-03T11:43:04Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [product-experimentation](<https://devfeed.tech/topics/product-experimentation.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [trust](<https://devfeed.tech/topics/trust.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-industry](<https://devfeed.tech/tags/ai-industry.md>), [ai-product-management](<https://devfeed.tech/tags/ai-product-management.md>), [developer-productivity](<https://devfeed.tech/tags/developer-productivity.md>), [engineering-leadership](<https://devfeed.tech/tags/engineering-leadership.md>), [feature](<https://devfeed.tech/tags/feature.md>), [industry](<https://devfeed.tech/tags/industry.md>), [product](<https://devfeed.tech/tags/product.md>), [product-management](<https://devfeed.tech/tags/product-management.md>), [scale](<https://devfeed.tech/tags/scale.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The article argues that AI has made building features cheap without making product decisions easier, rewarding visible shipping and adoption over customer outcomes. It calls this "Feature Theater": teams add features because they are easy to build, measure clicks or demos, and often fail to check whether work improved. The author points to examples and studies that qualify the promise, including METR's early-2025 finding that experienced developers using AI took 19% longer on studied tasks despite believing they were faster; METR later said the result was outdated and newer data was inconclusive. The proposed response is to require a written spec before coding, resolve its concerns, define a measurable outcome for each feature, keep diffs small enough for real review, track time spent verifying AI output, and remove features that do not help. The article also lists warning signs such as adoption-only KPIs, post hoc specs, and demos treated as deliverables.

### Source excerpt

AI made building features nearly free. It didn't make deciding cheaper. So we ship more, measure less, and call it progress. That's Feature Theater.

## Does AI actually save employees time? Data is contradictory

DevFeed: [Does AI actually save employees time? Data is contradictory](<https://devfeed.tech/articles/does-ai-actually-save-employees-time-data-is-contradictory-113718.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4243615/does-ai-actually-save-employees-time-data-is-contradictory.html>)

Author: Taryn Plumb

Published: 2026-11-03T05:09:10Z

Content type: article

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-assisted-work](<https://devfeed.tech/tags/ai-assisted-work.md>), [ai-use](<https://devfeed.tech/tags/ai-use.md>), [apps](<https://devfeed.tech/tags/apps.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-employee-experience-it-management](<https://devfeed.tech/tags/artificial-intelligence-employee-experience-it-management.md>), [attention](<https://devfeed.tech/tags/attention.md>), [critical-thinking](<https://devfeed.tech/tags/critical-thinking.md>), [data](<https://devfeed.tech/tags/data.md>), [data-collection](<https://devfeed.tech/tags/data-collection.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [employee-experience](<https://devfeed.tech/tags/employee-experience.md>), [employees](<https://devfeed.tech/tags/employees.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [focus](<https://devfeed.tech/tags/focus.md>), [it-management](<https://devfeed.tech/tags/it-management.md>), [knowledge](<https://devfeed.tech/tags/knowledge.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [latest](<https://devfeed.tech/tags/latest.md>), [less](<https://devfeed.tech/tags/less.md>), [light](<https://devfeed.tech/tags/light.md>), [manager](<https://devfeed.tech/tags/manager.md>), [measuring](<https://devfeed.tech/tags/measuring.md>), [save](<https://devfeed.tech/tags/save.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

ActivTrak's studies give conflicting signals about whether AI saves employees time: its newer, five-month study of 9,140 workers found heavy AI users worked 8.42-9.08 hours daily, versus 7.58 hours for nonusers, while an earlier, larger three-year study found workdays shortened by about nine minutes. The newer study also found heavy users had shorter focus sessions than light users (37.8 versus 48.2 minutes) and switched apps more often. Embedded AI users switched apps less frequently than web-AI users (0.6 versus 1.7-4.2 times per hour). The earlier study also reported more productive time and longer productive sessions, despite lower focus efficiency and more multitasking. Different study periods and sample sizes may help explain the discrepancy. The excerpt cautions that tracking misses some AI use and work outside managed devices, and app switching does not capture attention changes within an app. Any time saved may also become additional workload if managers do not set boundaries.

### Source excerpt

It's early days for AI-assisted work, and sentiments are mixed about its benefits: Does AI actually bring value and save employees time, or does it bog them down and add unnecessary activities? Data from ActivTrak seems to vacillate between those two potential realities: The latest research from the productivity tracking software company says employees who use AI most heavily are working up to 90 minutes longer each day, yet its previous research, published earlier this year, found that they are actually working less. The discrepancy may be due in part to the timespan and sample sizes of the data collection for the two reports, but it indicates that enterprises should still be wary of vendor claims about AI-related productivity gains. Measuring them remains incredibly difficult. AI use compared ActivTrak's current findings are based on behavioral work data gathered from 9,140 knowledge workers across 467 enterprises over a five month period (April 1 to September 25, 2026). This sample is much smaller than that of its previous report based on 443 million hours of work performed by 163,638 employees across 1,111 organizations over a three year period (January 1, 2023 through December 31, 2025). According to the latest findings, heavy AI users are working between 8.42 and 9.08 hours per day, compared to 7.58 hours for those not using AI. This contradicts ActivTrak's previous finding that average workdays had decreased by roughly 9 minutes (a 2% decline) thanks to AI. On the productivity front, heavy AI users have 22% shorter focus sessions than light users (37.8 minutes versus 48.2), suggesting their work is more fragmented due to AI use; further, they switch apps 15% more frequently. "Over time, those interruptions add friction to high-value work that requires concentration, critical thinking, and sustained attention," Sarah Altemus, manager of the ActivTrak Productivity Lab, said in a blog post describing the latest findings. ActivTrak's previous report had found tha

## CoGSeq-LTV: Scalable Missing-Aware Graph-Sequence Modeling for Multi-Business Transaction Analytics

DevFeed: [CoGSeq-LTV: Scalable Missing-Aware Graph-Sequence Modeling for Multi-Business Transaction Analytics](<https://devfeed.tech/articles/cogseq-ltv-scalable-missing-aware-graph-sequence-modeling-for-multi-business-transaction-analytics-115218.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.01817>)

Author: Ziyang Su, Yao Zhou, Kelin Liu, Guanjie Zheng, Linghe Kong

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [Graph Mining](<https://devfeed.tech/topics/graph-mining.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>)

Tags: [alignment](<https://devfeed.tech/tags/alignment.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [batch](<https://devfeed.tech/tags/batch.md>), [business](<https://devfeed.tech/tags/business.md>), [context](<https://devfeed.tech/tags/context.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [data](<https://devfeed.tech/tags/data.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [future](<https://devfeed.tech/tags/future.md>), [global](<https://devfeed.tech/tags/global.md>), [graph](<https://devfeed.tech/tags/graph.md>), [handle](<https://devfeed.tech/tags/handle.md>), [handling](<https://devfeed.tech/tags/handling.md>), [horizon](<https://devfeed.tech/tags/horizon.md>), [large](<https://devfeed.tech/tags/large.md>), [logs](<https://devfeed.tech/tags/logs.md>), [modeling](<https://devfeed.tech/tags/modeling.md>), [sequence](<https://devfeed.tech/tags/sequence.md>), [transaction](<https://devfeed.tech/tags/transaction.md>), [transaction-analytics](<https://devfeed.tech/tags/transaction-analytics.md>)

### AI overview

CoGSeq-LTV combines a batch-induced user-item graph, business-aware transaction sequence encoders, and cross-view contrastive alignment to predict customer value across businesses and time horizons. Reserved unknown-item handling accommodates missing item identifiers, while the sequence encoders retain recency, event gaps, payment context, and goods-table availability. For sparse, zero-inflated, heavy-tailed cumulative targets, it uses a zero-inflated mixture log-normal output with MAE-aligned point supervision and validation-calibrated zero-aware inference. On the BiBiSheng dataset, the authors report improvements over representative LTV baselines across businesses and horizons, including in a later out-of-time evaluation window; the excerpt provides no metric details.

### Source excerpt

arXiv:2611.01817v1 Announce Type: new Abstract: Large-scale super-apps generate heterogeneous transaction logs in which users interact with multiple businesses, item identifiers are only partially available, and future value targets are sparse, heavy-tailed, and cumulative over time. We study multi-business, multi-horizon value prediction as a data-intensive analytics problem over such logs, rather than as a single-table task. (i) a batch-induced user-item graph that provides collaborative signals without materializing a global graph and remains applicable when item identifiers are missing through reserved unknown-item handling, (ii) business-aware sequence encoders that preserve recency, inter-event gaps, payment context, and goods-table availability, and (iii) cross-view contrastive alignment that transfers user-level intent across businesses while retaining business-specific temporal patterns. To handle zero-inflated and long-tailed cumulative targets, CoGSeq-LTV adopts a zero-inflated mixture log-normal head with MAE-aligned point supervision and validation-calibrated zero-aware inference. Experiments on the BiBiSheng transaction-log dataset show that CoGSeq-LTV improves over representative LTV baselines across businesses and horizons, including under a later out-of-time evaluation window.

## How Product Teams Can Use AI User Research to Test Assumptions Before Sprint Planning

DevFeed: [How Product Teams Can Use AI User Research to Test Assumptions Before Sprint Planning](<https://devfeed.tech/articles/how-product-teams-can-use-ai-user-research-to-test-assumptions-before-sprint-planning-112455.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/how-product-teams-can-use-ai-user-research-to-test-assumptions-before-sprint-planning/>)

Author: Div John

Published: 2026-11-02T07:38:49Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>), [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>)

Tags: [2019](<https://devfeed.tech/tags/2019.md>), [about](<https://devfeed.tech/tags/about.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-answers](<https://devfeed.tech/tags/ai-answers.md>), [also](<https://devfeed.tech/tags/also.md>), [alter](<https://devfeed.tech/tags/alter.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analysts](<https://devfeed.tech/tags/analysts.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [business](<https://devfeed.tech/tags/business.md>), [can](<https://devfeed.tech/tags/can.md>), [planning](<https://devfeed.tech/tags/planning.md>), [product](<https://devfeed.tech/tags/product.md>), [reading](<https://devfeed.tech/tags/reading.md>), [research](<https://devfeed.tech/tags/research.md>), [sprint](<https://devfeed.tech/tags/sprint.md>), [teams](<https://devfeed.tech/tags/teams.md>), [test](<https://devfeed.tech/tags/test.md>), [user](<https://devfeed.tech/tags/user.md>), [user-research](<https://devfeed.tech/tags/user-research.md>)

### AI overview

AI user research can help product teams check risky backlog assumptions before sprint planning, but modeled responses are hypotheses, not proof of demand or behavior. The guide recommends writing three to five assumption cards that state the belief, the cost of being wrong, and the decision it affects. In a two-day routine, ask modeled audiences neutral, open questions, then compare answers with existing support and analytics evidence and mark conclusions supported, contradicted, or unclear. AI can also analyze real support tickets and interview transcripts; its main risk there is poor summarization. Simulated users may help refine interview questions and spot message comprehension issues, but tend to agree, cannot verify willingness to pay or task completion, and are unreliable for niche populations. Label evidence as modeled, observed, or reported. Cut or reduce contradicted tickets; keep unclear items from receiving full scope; and schedule a real-user check before building from assumptions supported only by simulation.

### Source excerpt

null Continue reading How Product Teams Can Use AI User Research to Test Assumptions Before Sprint Planning on SitePoint.

## Export RUM and Product Analytics data with Export Pipelines

DevFeed: [Export RUM and Product Analytics data with Export Pipelines](<https://devfeed.tech/articles/export-rum-and-product-analytics-data-with-export-pipelines-113321.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/export-pipelines/>)

Author: Stella Ma; Quentin Sellem

Published: 2026-11-02T00:00:00Z

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [BigQuery](<https://devfeed.tech/topics/bigquery.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [analysis](<https://devfeed.tech/tags/analysis.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-storage](<https://devfeed.tech/tags/cloud-storage.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [data](<https://devfeed.tech/tags/data.md>), [data-analysis](<https://devfeed.tech/tags/data-analysis.md>), [data-analytics](<https://devfeed.tech/tags/data-analytics.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [digital-experience-monitoring](<https://devfeed.tech/tags/digital-experience-monitoring.md>), [events](<https://devfeed.tech/tags/events.md>), [export](<https://devfeed.tech/tags/export.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [ml](<https://devfeed.tech/tags/ml.md>), [model](<https://devfeed.tech/tags/model.md>), [model-training](<https://devfeed.tech/tags/model-training.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [product-analytics](<https://devfeed.tech/tags/product-analytics.md>), [real-user-monitoring](<https://devfeed.tech/tags/real-user-monitoring.md>), [rum](<https://devfeed.tech/tags/rum.md>), [send](<https://devfeed.tech/tags/send.md>), [storage](<https://devfeed.tech/tags/storage.md>), [training](<https://devfeed.tech/tags/training.md>)

### AI overview

Datadog Export Pipelines continuously send selected RUM and Product Analytics events to Amazon S3, Azure Blob Storage, or Google Cloud Storage, configured in the Datadog UI. They support Parquet, which the source says loads directly into Snowflake, BigQuery, and Databricks without preprocessing, and JSON for custom processing pipelines or a flexible event representation. Files are organized by date and hour; pipelines can be enabled, disabled, or updated, with states shown as Active, Error, Pending, or Paused. Exported data can support warehouse analysis, ML workflows, or long-term retention under an organization's own storage and lifecycle policies. The source states standard RUM retention is 30 days, with a six-month RUM Managed Archive option, while Product Analytics retention is 15 months.

### Source excerpt

Send Datadog RUM and Product Analytics events to your cloud storage for data analysis, ML model training, and long-term data access.

## From using AI to operating with AI: What changes in product management when the bottlenecks disappear

DevFeed: [From using AI to operating with AI: What changes in product management when the bottlenecks disappear](<https://devfeed.tech/articles/from-using-ai-to-operating-with-ai-what-changes-in-product-management-when-the-bottlenecks-disappear-106921.md>)

Original publisher: [Read original article](<https://building.nu.com/from-using-ai-to-operating-with-ai-what-changes-in-product-management-when-the-bottlenecks-disappear/>)

Author: Nubank Editorial

Published: 2026-10-29T16:30:40Z

Content type: article

Language: en

Sources: [Building Nubank](<https://devfeed.tech/sources/building-nubank.md>), [Nubank](<https://devfeed.tech/sources/nubank.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Spec Driven Development](<https://devfeed.tech/topics/spec-driven-development.md>), [Internationalization (i18n)](<https://devfeed.tech/topics/i18n.md>), [Google Calendar](<https://devfeed.tech/topics/google-calendar.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-coding-assistant](<https://devfeed.tech/tags/ai-coding-assistant.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [claude-cowork](<https://devfeed.tech/tags/claude-cowork.md>), [product](<https://devfeed.tech/tags/product.md>), [product-management](<https://devfeed.tech/tags/product-management.md>)

### AI overview

Cinthia Scarlatti's examples show how product managers can use AI to reduce execution delays while keeping problem definition, validation and decisions in human hands. For a Mexico-specific customer support correction, she gave Cursor a Jira-style description of the problem, desired behavior and constraints; it proposed options, implemented the selected change and opened a pull request for engineering approval. Reported lead time fell from over a week to under a day. In another case, Cursor used Glean documentation to configure Databricks access, found suitable datasets and analyzed example chats in minutes, helping identify a training issue rather than a technical bug. Scarlatti stresses checking data sources, filters and results before acting. Her Claude Cowork Daily Digest gathers project questions, Slack threads, notes and meeting transcripts into daily summaries, updated documentation and a draft status post; she estimates it saves about an hour per day. The approach depends on clear requirements, relevant company context and review, and she presents the examples as adaptable rather than a universal recipe.

### Source excerpt

How a Lead Product Manager at Nubank turned problem definition into her main tool for working with AI agents, and why judgment stays with the PM The post From using AI to operating with AI: What changes in product management when the bottlenecks disappear appeared first on Building Nubank.

## Difference-in-Differences vs Lagged-Outcome Regression

DevFeed: [Difference-in-Differences vs Lagged-Outcome Regression](<https://devfeed.tech/articles/difference-in-differences-vs-lagged-outcome-regression-106580.md>)

Original publisher: [Read original article](<https://towardsdatascience.com/difference-in-differences-vs-lagged-outcome-regression/>)

Author: Ryan OSullivan

Published: 2026-10-29T14:00:00Z

Content type: comparison

Language: en

Sources: [Towards Data Science](<https://devfeed.tech/sources/towards-data-science.md>)

Topics: [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [product-experimentation](<https://devfeed.tech/topics/product-experimentation.md>), [doubleml](<https://devfeed.tech/topics/doubleml.md>)

Tags: [data-science](<https://devfeed.tech/tags/data-science.md>), [difference-in-differences](<https://devfeed.tech/tags/difference-in-differences.md>), [editor-s-picks](<https://devfeed.tech/tags/editor-s-picks.md>), [product-analytics](<https://devfeed.tech/tags/product-analytics.md>), [product-management](<https://devfeed.tech/tags/product-management.md>), [regression](<https://devfeed.tech/tags/regression.md>), [simulation](<https://devfeed.tech/tags/simulation.md>)

### AI overview

The study's choice between lagged-outcome regression and difference-in-differences (DiD) depends on how users self-select into treatment: lagged-outcome regression assumes no unobserved confounding after conditioning on outcome history and covariates, while DiD assumes parallel trends. In simulations of weekly engagement, DiD handled stable unobserved level differences but overstated effects when treated users opted in during a temporary dip; lagged-outcome regression handled the dip but was biased by stable unobserved confounding. A pre-trend check modeled on DiD detected the simulated dips and supports choosing DiD when flat or lagged-outcome regression when it dips, though a flat check does not prove parallel trends and can miss violations outside its window or in noisy, small samples. The authors advise reporting both estimates when the check dips, with conclusions treated cautiously. The results come from one simulated setting and do not establish how common these patterns are in real products; DiD is also not directly suitable for absorbing outcomes such as churn.

### Source excerpt

A simulation study and a pre-period check for choosing the right design for self-selected treatments in product analytics. The post Difference-in-Differences vs Lagged-Outcome Regression appeared first on Towards Data Science.

## App Architecture: Analytics

DevFeed: [App Architecture: Analytics](<https://devfeed.tech/articles/app-architecture-analytics-103675.md>)

Original publisher: [Read original article](<https://proandroiddev.com/app-architecture-analytics-ec3471ca619b?source=rss----c72404660798---4>)

Author: Mkhytar Mkhoian

Published: 2026-10-27T23:25:11Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [architecture-components](<https://devfeed.tech/topics/architecture-components.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [Dependency Inversion](<https://devfeed.tech/topics/dependency-inversion.md>), [Dependency injection](<https://devfeed.tech/topics/dependency-injection.md>), [adapter pattern](<https://devfeed.tech/topics/adapter-pattern.md>), [async](<https://devfeed.tech/topics/async.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [app-architecture](<https://devfeed.tech/tags/app-architecture.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>)

### AI overview

The article proposes keeping analytics vendors out of feature code: features emit app-defined events and user properties, while vendor-specific factories map events and trackers call SDKs. A dispatcher forwards calls off the main thread so one vendor's crash does not prevent others from receiving an event. In modular apps, features own their events and factories, DI collects them, and only the app module sees the full graph. The approach aims to avoid a central analytics god object, isolate vendor changes, preserve parameter types, and give ViewModels small interfaces that are easy to test. The author says the open-source Herald library implements this design.

### Source excerpt

Photo by Hunter Harritt on Unsplash It's been a while since the last time I covered app architecture topics. Today I am back with a new one. This time it's analytics and everything around it. The problem We engineers often treat analytics as a secondary piece of software. We spend so much time on the architecture design of the main parts and so little on designing analytics as part of the program that it always leads to a bad cocktail. This cocktail brings a bad smell to the code, some workarounds, and forces us to make exceptions to the architecture rules. In practice, developers spend time thinking about general architecture; no one thinks about analytics at that moment. Then business comes and asks to track this and that. Send a couple of events to a third-party analytics vendor, and devs start thinking about how to do that and integrate analytics. After some time, business asks to add more events for a new vendor. Now you need to not only track it, but also manage vendors and decide which event goes where. In code, it looks like one AnalyticsRepository or AnalyticsManager class that contains all analytics-related stuff, a huge list of methods where each of them calls due to tracking events. A god object class engineers drag across the codebase and make different components and layers depend on it. And here we are, holding a bad cocktail in our hand. The idea So how to stop making this cocktail? I came to a simple idea: the app should not know which analytics vendors exist. Feature code doesn't need to care if an event goes to Firebase, Mixpanel, AppsFlyer or all of them. It should only say what happened, in the app's own words. "Ticket purchased", "Settings screen opened". Where the event goes and in what format each vendor wants it is a different job, and it should live in a different place. Instead of one god object that knows everything, let's split the work into small pieces, and each piece has one job: The Event Event describes what happened, in the app's w

## How to steal your way to a hit product, with Mark Pincus (founder, Zynga)

DevFeed: [How to steal your way to a hit product, with Mark Pincus (founder, Zynga)](<https://devfeed.tech/articles/how-to-steal-your-way-to-a-hit-product-with-mark-pincus-founder-zynga-102386.md>)

Original publisher: [Read original article](<https://www.news.aakashg.com/p/how-to-steal-your-way-to-a-hit-product>)

Author: Aakash Gupta

Published: 2026-10-26T23:31:46Z

Content type: article

Language: en

Sources: [Product Growth](<https://devfeed.tech/sources/product-growth.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>)

Tags: [acquisition](<https://devfeed.tech/tags/acquisition.md>), [ads](<https://devfeed.tech/tags/ads.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [ai-strategy](<https://devfeed.tech/tags/ai-strategy.md>), [app](<https://devfeed.tech/tags/app.md>), [app-store](<https://devfeed.tech/tags/app-store.md>), [apple](<https://devfeed.tech/tags/apple.md>), [audio](<https://devfeed.tech/tags/audio.md>), [batch](<https://devfeed.tech/tags/batch.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [better](<https://devfeed.tech/tags/better.md>), [build](<https://devfeed.tech/tags/build.md>), [copy](<https://devfeed.tech/tags/copy.md>), [demand](<https://devfeed.tech/tags/demand.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [product](<https://devfeed.tech/tags/product.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

Mark Pincus's Proven/Better/New framework recommends copying elements already proven for the same audience and platform, isolating one novel idea per launch, and treating changes only the builder prefers as "new," not "better." The article suggests labeling roadmap items by category, cutting launches with multiple new elements, and expecting new ideas to fail while watching for those that gain market traction. For early platform shifts, it advises pursuing less novelty and improving what already works; later in a cycle, more novelty may be needed. To test demand before building a product, the described process is to detail a competitor's proven experience, generate concept names and value propositions, make a simple landing page, and run ads against a preselected click-through threshold. Results should be judged against both an absolute quality bar and relative performance across variants. The article notes that mobile ad platforms may require an App Store listing, and that thresholds should come from the product's own funnel.

### Source excerpt

Zynga founder Mark Pincus teaches Proven Better New at the whiteboard: what to copy, how to tell better from new, and how to test demand before you build.

## How AI is changing software pricing

DevFeed: [How AI is changing software pricing](<https://devfeed.tech/articles/how-ai-is-changing-software-pricing-92444.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4237997/how-ai-is-changing-software-pricing.html>)

Author: Nicole Segerer

Published: 2026-10-21T09:00:00Z

Content type: article

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [API Business Models](<https://devfeed.tech/topics/api-business-models.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-features](<https://devfeed.tech/tags/ai-features.md>), [ai-leaders](<https://devfeed.tech/tags/ai-leaders.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [ai-pricing](<https://devfeed.tech/tags/ai-pricing.md>), [ai-pricing-models](<https://devfeed.tech/tags/ai-pricing-models.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-software-providers-technology-industry](<https://devfeed.tech/tags/artificial-intelligence-software-providers-technology-industry.md>), [based](<https://devfeed.tech/tags/based.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [chatbots](<https://devfeed.tech/tags/chatbots.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [cost](<https://devfeed.tech/tags/cost.md>), [customers](<https://devfeed.tech/tags/customers.md>), [device](<https://devfeed.tech/tags/device.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [software](<https://devfeed.tech/tags/software.md>), [software-providers](<https://devfeed.tech/tags/software-providers.md>), [storytype-feature](<https://devfeed.tech/tags/storytype-feature.md>), [technology-industry](<https://devfeed.tech/tags/technology-industry.md>)

### AI overview

AI pricing at established software firms is evolving around customer cost predictability and existing products, rather than shifting wholesale to pure usage billing. In a survey of 415 product and technology leaders, AI use in products rose from 80% to 96%, yet almost half reported limited or low adoption of their AI features. Only 7% reported AI-related seat losses, while nearly half saw downward pricing pressure. Common approaches include placing AI in a higher-priced subscription tier, including it at no extra charge, or combining subscriptions with usage or outcome pricing; firms expect predictability-oriented models to grow faster than pure usage pricing over the next 18 months. AI can raise revenue while delivery and cloud costs pressure margins. Many firms also lack clear usage data, making it harder to choose pricing metrics and assess feature value. The article describes a possible staged approach--from free inclusion to higher tiers with usage limits and, as usage becomes predictable, hybrid pricing--while emphasizing that products may move at different rates.

### Source excerpt

In 2026, the AI monetization conversation has shifted quickly from one concern to the next. Early in the year, fears that AI agents would erode software seats helped trigger a selloff of software stocks dubbed the "SaaSpocalypse." Since then, attention has turned to a different disruption, as AI leaders including Anthropic, OpenAI, and GitHub lean heavily on usage-based pricing to better align revenue with the cost of delivering AI. It would be easy to conclude that software monetization is shifting wholesale from seats and subscriptions to tokens, credits, and consumption. But look across a broader cross-section of the software industry, and a different picture emerges. Most software companies aren't AI-native businesses designing pricing from scratch. They have existing products, customers, contracts, and pricing structures. They're adding AI to portfolios that may already span dozens of products and multiple monetization models. And they have to balance the economics of AI with something customers still value enormously: predictability. That tension came through clearly in our new Revenera Monetization Monitor: Software and AI Pricing Models and Strategies 2027 report of 415 product and technology leaders at established software producers and intelligent device manufacturers. Nearly all are adding AI capabilities to at least some products. The way they're monetizing those capabilities, though, is considerably more pragmatic than the headlines might suggest. AI features are widespread, but adoption is lagging AI capabilities have gone mainstream. The share of software producers incorporating AI into their products jumped from 80% last year to 96% today. Getting AI into the product, however, is only the first step. The widespread use of chatbots can create the impression that everyone is using AI. That isn't yet true inside established software products. Almost half of respondents say that adoption of their AI features is limited or low. For many vendors, that make

## Organizing LLM Inference for Aggregate Predictions from Behavioral Data

DevFeed: [Organizing LLM Inference for Aggregate Predictions from Behavioral Data](<https://devfeed.tech/articles/organizing-llm-inference-for-aggregate-predictions-from-behavioral-data-93199.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.23934>)

Author: Varun Gupta, Vijay Kamble

Published: 2026-10-21T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [generalization in machine learning](<https://devfeed.tech/topics/generalization-in-machine-learning.md>)

Tags: [aggregate](<https://devfeed.tech/tags/aggregate.md>), [bayesian](<https://devfeed.tech/tags/bayesian.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [bias](<https://devfeed.tech/tags/bias.md>), [browsing](<https://devfeed.tech/tags/browsing.md>), [commerce](<https://devfeed.tech/tags/commerce.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [context](<https://devfeed.tech/tags/context.md>), [conversion](<https://devfeed.tech/tags/conversion.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [datasets](<https://devfeed.tech/tags/datasets.md>), [econ-em](<https://devfeed.tech/tags/econ-em.md>), [inference](<https://devfeed.tech/tags/inference.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-inference](<https://devfeed.tech/tags/llm-inference.md>), [predictions](<https://devfeed.tech/tags/predictions.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [study](<https://devfeed.tech/tags/study.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

For product-level e-commerce conversion prediction, evaluating products together makes session summaries more effective than predicting individual browsing sessions and averaging. Across five LLMs and two datasets, individual-session predictions performed better when products were evaluated separately, while comparative summaries led when products were evaluated together, achieving the highest Spearman correlation in 12 of 15 settings with no alternative significantly better. Summaries reduce inference cost but can lose predictive detail; comparison can reduce bias while adding noise from the choice of accompanying products. A Bayesian analysis suggests comparison helps more when prompt inputs reveal differences across products. Comparative summaries used a small fraction of session-method inference cost and reached 66-89% of the best supervised benchmark's correlation.

### Source excerpt

arXiv:2610.23934v1 Announce Type: new Abstract: When using a large language model (LLM) to simulate a user population, how should we combine individual behavioral histories to predict the fraction of users who take a particular action? We study this question in e-commerce, predicting observed product-level conversion rates from browsing sessions without task-specific model training. We vary two design choices, each involving a bias-variance tradeoff. Summarizing a product's sessions before inference reduces cost but can discard predictive detail, adding bias, whereas predicting outcomes for individual sessions and averaging afterward preserves that detail but requires many calls to reduce variance. Evaluating products together in one prompt can help the model infer what is typical in the setting, reducing bias, but also makes each prediction depend on which other products appear alongside it, adding noise. We evaluate both choices across five LLMs and two datasets. Our main finding is that predictions from individual sessions outperform predictions from summaries when products are evaluated separately, but summaries lead when products are evaluated together. Comparative summaries achieve the highest Spearman correlation with observed rates in 12 of 15 settings, with no alternative significantly better. Comparison thus helps summaries far more than session predictions, overcoming the advantage of behavioral detail. We interpret this difference through a Bayesian model of the second tradeoff, which suggests that comparison helps more when the inputs in a prompt reveal more about differences across products, consistent with our results for four types of comparative context. Comparative summaries also incur a small fraction of the inference cost of the session methods. With the best model for each outcome, they attain 66-89% of the correlation of the best supervised benchmark trained on thousands of labeled products.

## Amplitude + GitHub Agents: Closing the Product Learning Loop

DevFeed: [Amplitude + GitHub Agents: Closing the Product Learning Loop](<https://devfeed.tech/articles/amplitude-github-agents-closing-the-product-learning-loop-90087.md>)

Original publisher: [Read original article](<https://amplitude.com/blog/amplitude-github-learning-loop>)

Author: Christina Nguyen

Published: 2026-10-19T00:00:00Z

Content type: article

Language: en

Sources: [Amplitude](<https://devfeed.tech/sources/amplitude.md>)

Topics: [product-experimentation](<https://devfeed.tech/topics/product-experimentation.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [GitHub Copilot](<https://devfeed.tech/topics/github-copilot.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>)

Tags: [activation](<https://devfeed.tech/tags/activation.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amplitude](<https://devfeed.tech/tags/amplitude.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [experiment](<https://devfeed.tech/tags/experiment.md>), [feature](<https://devfeed.tech/tags/feature.md>), [github](<https://devfeed.tech/tags/github.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [github-issue](<https://devfeed.tech/tags/github-issue.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [ideas](<https://devfeed.tech/tags/ideas.md>), [impact](<https://devfeed.tech/tags/impact.md>), [integration](<https://devfeed.tech/tags/integration.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

The article describes a product learning loop connecting Amplitude Wave, GitHub Copilot, and Statsig. Wave uses behavioral analytics and session replays to identify onboarding friction and propose a fix; Copilot turns the proposal into a pull request for engineering review; and Statsig feature gates and randomized experiments measure the change before broader rollout.

### Source excerpt

How teams are building the right thing at AI speed with GitHub Copilot, Amplitude Wave, and Statsig

## Tim Herbig on product strategy, AI differentiation and customer value metrics

DevFeed: [Tim Herbig on product strategy, AI differentiation and customer value metrics](<https://devfeed.tech/articles/how-you-need-to-think-about-product-strategy-in-the-age-of-ai-87524.md>)

Original publisher: [Read original article](<https://www.news.aakashg.com/p/how-the-best-pms-think-about-product-strategy>)

Author: Aakash Gupta

Published: 2026-10-14T22:00:44Z

Content type: article

Language: en

Sources: [Product Growth](<https://devfeed.tech/sources/product-growth.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>)

Tags: [ai-product-strategy](<https://devfeed.tech/tags/ai-product-strategy.md>), [product-strategy](<https://devfeed.tech/tags/product-strategy.md>)

### AI overview

Tim Herbig explains how product teams can make explicit strategic choices as AI accelerates feature delivery. Using a hypothetical used-car marketplace, he demonstrates how to narrow audiences, test meaningful alternatives and choose durable differentiators. He recommends using AI to support research and evaluating strategy through customer behavior and experienced value rather than output or token usage.

### Source excerpt

Tim Herbig shows how to build a product strategy that helps you say no, using a made-up used-car marketplace.

## A practical guide to real-time analytics in 2026

DevFeed: [A practical guide to real-time analytics in 2026](<https://devfeed.tech/articles/a-practical-guide-to-real-time-analytics-in-2026-86529.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/practical-guide-real-time-analytics-2026>)

Author: Jeremy Lewallen; Tad Rosenberg; Kaitlin Baumgardner

Published: 2026-10-13T19:17:26Z

Content type: article

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [real-time](<https://devfeed.tech/topics/real-time.md>), [clickhouse](<https://devfeed.tech/topics/clickhouse.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>), [olap](<https://devfeed.tech/topics/olap.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [batch-processing](<https://devfeed.tech/tags/batch-processing.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [data](<https://devfeed.tech/tags/data.md>), [data-analytics](<https://devfeed.tech/tags/data-analytics.md>), [decision-making](<https://devfeed.tech/tags/decision-making.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [real-time-analytics](<https://devfeed.tech/tags/real-time-analytics.md>)

### AI overview

Real-time analytics helps teams query fresh data with low latency and high concurrency. This guide explains how to assess workloads across those dimensions, compares real-time and batch analytics, and describes the operational overhead of separate serving layers. It presents a lakehouse approach for running real-time and traditional analytics on shared data and governance, with Databricks Lakehouse//RT as an example.

### Source excerpt

Data has always been central to business decision-making, and most analytical workloads...

[Next page](<https://devfeed.tech/topics/product-analytics.md?cursor=WyIyMDI2LTEwLTEzVDE5OjE3OjI2KzAwOjAwIiwgIjQ2MzgwNzdkLTEzNzMtNGNkMC1hNzU0LTMyNTE0YTcxZjJmMiJd>)