Feature requests

Description: Customers want to report on revenue from Shopify's agentic commerce channels: orders placed through AI agents such as ChatGPT, Microsoft Copilot, Google AI Mode and Gemini via Shopify Agentic Storefronts. Shopify's admin now reports AI-channel orders, but Polar has no way to isolate this revenue. Current gap: Agentic orders do not appear as a distinct value in Polar's Order Sales Channel dimension, so customers can't build a custom metric or view to break out agentic sales. (We confirmed this doesn't work; it's not yet known whether Shopify's AI-channel tag isn't ingested or isn't mapped.) ChatGPT purchases hand off to the merchant's own Online Store checkout, so a sales-channel field wouldn't capture those orders. They could only be identified through attribution ( chatgpt.com referrer / UTM). What's needed: Ingest and expose Shopify's agentic / AI-channel attribution on orders (e.g. as a sales channel or a dedicated dimension). A ready-made "Agentic Sales" or AI-channel revenue metric/breakdown. Pixel/attribution handling for AI-assistant referral traffic (ChatGPT, Perplexity, etc.) so handoff orders can be attributed to AI channels. First requested by SAMA Labs (agency), Pylon #12250.

Problem Customers want a 7-day moving average of key metrics, such as Total Sales and MER, delivered to Slack or email on a schedule. They use it to see how performance responds when they increase or decrease ad spend. Daily figures are too noisy for this, and weekly totals don't show the smoothed day-by-day trend. Today there is no way to automate this: Standard reports and custom metrics can't calculate a rolling or moving average. Custom HTML blocks can show a moving average on a dashboard, because they calculate it in the browser. Automations can't snapshot HTML blocks, so they can't be selected in the Send snapshots block picker. The selection appears empty, with no message explaining why. Automations can't send charts as images. When we tested a Run instructions automation as a workaround, the AI-calculated moving averages were inaccurate (27 of 28 days were wrong, by up to 18%), and nothing posted to Slack. Requested solution Native rolling calculations in reports and custom metrics: an N-day moving average (for example, 7 or 14 days) for any metric, calculated on the server so it can be included in automations. Support for HTML blocks in Send snapshots automations, by rendering the block and sending it as an image. Until either of these is available, a message in the automation block picker explaining that HTML and text blocks can't be added, instead of silently showing an empty selection. Impact Customers who build moving average visuals with the AI assistant expect to schedule them like any other dashboard block. When they can't, it leads to repeated support tickets and frustration, and there is no workaround we can recommend.

Update a Connector's Account name from the Connectors page to make it easier to organize Views.

Polar doesn't currently import Klaviyo signup forms, so there's no way to see which form a subscriber signed up through. Brands run many forms at once (welcome popups, footer signups, quizzes, per-market variants) and need to compare their performance: submissions, signups, and downstream revenue by form. Requested: Klaviyo Form ID and Form Name as breakdowns/filters Form submission metrics (e.g. "Form submitted by profile") Ideally, the ability to attribute list signups to the form they came from

Problem On Polar Pixel Events, custom events (sent via the SDK’s custom() / shopifyEventName) are only exposed through the first_event_name and last_event_name session flags. The built-in funnel events (add_to_cart, collection_view, product_page_view) each have a session-level flag computed at query time, so they’re countable and attributable wherever they occur. Custom events don’t, so any mid-session occurrence is invisible to self-serve reporting. Live impact (Spring Sleep): of 140 occurrences of their questionnaire_ts_eligible event over ~2.5 weeks, only 9 were visible via the first/last flags. The other 131 were mid-session and unreachable, despite the data being fully attributable (every event joins cleanly to its session’s channel, campaign, ad, and UTMs). Getting the breakdown required a manual warehouse pull. Who it affects Any tenant sending a custom pixel event who wants to count or attribute it. Not account-specific; it surfaces for every custom-event use case. Requested behavior Allow filtering and breakdown of polar_pixel_events by the event’s own name at the event grain, carrying the session’s existing attribution dimensions, the same way the funnel events work. Engineering note Per the pixel team’s investigation, an event_name dimension is already declared in dimensions.json but wired to no table. Hooking it up on Polar Pixel Events was described as ~a one-line synth-config change plus a test, in a normal deploy, with no enrichment work, dbt change, or backfill. Because it’s computed at query time, history is covered on ship. Flagged as a product-level change benefiting all tenants, not a per-account build; suggested benchmarking query cost first. Out of scope Session-scoped attribution only (each event inherits its landing session’s values), consistent with the funnel events. Not a request for first/last/multi-touch model credit.

Track tags and mentions from influencers on social media and provide data on impressions and engagements on those influencer posts

Recharge subscription metrics (Active Subscriptions, New Subscriptions, Churned/Cancelled Subscriptions, and other lifecycle metrics) can currently only be viewed at a total or store level. There's no geographic breakdown. Brands selling subscriptions in multiple countries need to track subscriber growth, churn, and active base by market, consistent with the country reporting already available for Shopify, GA4, and ad platforms. Requested: Subscription country and region (based on the subscription's shipping address) as breakdowns and filters on all Recharge subscription lifecycle metrics

Today, Klaviyo signup metrics (New Subscribers / Subscribed to List) can only be broken down by list and store. Campaign and flow metrics already support a Country breakdown based on the Klaviyo profile, but signups don't. Brands selling across several markets need to see where their new subscribers come from: for example, how many signups came from the UK vs Italy vs Spain this week, and how that trend compares to orders and ad spend by market. Requested: Profile country as a breakdown and filter on Klaviyo signup metrics Profile region / state as a breakdown and filter on Klaviyo signup, campaign and flow metrics Ideally, country values normalised to a consistent format (today both "United Kingdom" and "GB" appear)

Description: Customers want to escalate to the support team from inside Ask Polar, without leaving to find the support chatbot on another page. Right now, when Ask Polar can't answer a question confidently, the customer has to leave the interface and start over with the support chatbot (Polly) somewhere else. That means re-explaining the question, losing the context of the Ask Polar conversation, and dealing with an extra step at the moment they're already stuck. Proposed solution: Add a "Contact support" or "Submit a ticket" option inside Ask Polar. It would be most useful when Ask Polar can't give a confident answer, but it should also be available anytime. Ideally the ticket would automatically include the customer's question and the Ask Polar conversation so support has full context and the customer doesn't have to repeat themselves. Benefits: Customers get help faster, with fewer steps. Support gets better tickets because the question and the attempted answer are already attached. Ask Polar and human support feel like one experience instead of two separate tools. Requested by: Howie (customer)