Guide
Estimated vs Verified
Every headline metric on Appkitekt AI ships with two numbers. The estimated figure comes from our Latent Demand Engine — it's always available, but it's a model. The verified figure comes from a first-party console you've connected — it's the exact number your provider reports. When both exist, we show both, side by side, so you can see the delta.
How the labels work
Modeled figure from the Latent Demand Engine. Always available. Confidence tier capped at Medium when a modeled figure is what drives the score.
Direct reading from a first-party console. Overrides the modeled figure when it's fresh (default gate: 14 days). Unlocks the High confidence tier.
Which console unlocks which metric
| Metric | Category | Verified by | Fresh window |
|---|---|---|---|
Search impressions How often the brand appeared in a web search result. Google + Bing. | web | Google Search Console · Bing Webmaster | 14d |
Search clicks Clicks from search-result pages to the brand's site. | web | Google Search Console · Bing Webmaster | 14d |
Bing AI (Copilot) clicks Clicks attributed by Bing to AI-answer surfaces (Copilot). | agent | Bing Webmaster | 14d |
Web sessions Distinct sessions on the brand's site as measured by GA4. | web | Google Analytics 4 | 7d |
App Store impressions App Store product-page + search impressions. | app | App Store Connect | 14d |
Play Store impressions Play Console store-listing impressions. | app | Google Play Console | 14d |
Conversion rate Purchases / sessions from the connected commerce system. | revenue | Stripe · Shopify · Google Analytics 4 | 14d |
Revenue Realised revenue from the connected commerce system. | revenue | Stripe · Shopify | 14d |
Connecting a console
The Appkitekt Agent walks you through each connection. Click the console name in any pillar report to open the guided wizard. If you already know the drill, here's the short version:
Sign in at search.google.com/search-console with the account that owns the property. The Appkitekt Agent walks you through DNS or meta-tag verification if the property isn't verified yet.
Sign in at bing.com/webmasters, generate an API key from Settings → API access, and paste it into the connection form.
Sign in at analytics.google.com with an account that has Viewer access to the property, then approve the read-only scopes.
In App Store Connect → Users & Access → Keys, create an Analytics-scoped key (.p8), then paste the key ID + issuer ID + file contents.
In Play Console → Setup → API access, link a Google Cloud service account with Statistics permission and paste the JSON key.
Sign in at dashboard.stripe.com and approve the read-only OAuth flow (charges + payouts).
In the Shopify admin, install the Appkitekt read-only app and approve the analytics + orders scopes.
Why we keep both numbers
- Coverage. A modeled figure exists for every brand, even before any console is connected. The verified figure only exists once you connect the right console.
- Cross-check. A wide gap between Est. and Verified is a signal in itself — usually a model calibration gap or a console attribution quirk worth investigating.
- Honesty. We would rather show two numbers with clear labels than launder a modeled figure into a "real" one.