Telecom Subscriber Insights
Customer-hosted models forecasting subscriber churn, upgrades and next best offers.
- Provider
- gcp
- Kind
- AI service
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| auth | enum | api-key | oauth | iam | none | no | — | ▸ iam |
| contentFiltering | boolean | — | no | — | inherited |
| customerManagedKeys | boolean | — | no | — | inherited |
| dataResidency | enum | us | eu | asia | global | no | — | inherited |
| dataRetentionDays | integer | — | no | — | inherited |
| deployment | enum | customer-hosted | no | customer-hosted | inherited |
| ingestion | enum | batch | streaming | no | batch | inherited |
| keyStore | boolean | — | no | false | inherited |
| managed | boolean | — | no | false | ▸ false |
| modality | enum | text | vision | speech | multimodal | structured | image | video | audio | embedding | rerank | no | — | ▸ structured |
| output | enum | churn-propensity | upgrade-propensity | next-best-offer | segment | no | churn-propensity | inherited |
| publicEndpoint | boolean | — | no | — | ▸ false |
| quotaUnitsPerMinute | integer | — | no | — | inherited |
| rateLimitRpm | integer | — | no | — | inherited |
| rateLimitTpm | integer | — | no | — | inherited |
| viaGateway | boolean | — | no | false | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.
- — all of these hold:
- — the node's `auth` is "api-key"
- — the node's `keyStore` is false
- — the node has at least one incoming edge from an app-server, worker or client
- — this does not hold:
- — the design contains a node of kind key-management
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "telecom-subscriber-insights", component: "google-telecom-subscriber-insights" }# yaml-language-server: $schema=../../schema/component.schema.json # Telecom Subscriber Insights: forecasts churn and upgrade propensity and recommends next # best offers for a carrier's subscriber base. "Telecom Subscriber Insights documentation": # usage records, billing, CRM and app data are ingested into BigQuery and normalised to # predefined data models; the product ships as a Google Cloud project that is built and # transferred to the customer, who then hosts and operates it. schemaVersion: "1" type: "component" id: "google-telecom-subscriber-insights" kind: "ai-service" provider: "gcp" docs: "https://docs.cloud.google.com/telecom-subscriber-insights/docs" defaults: auth: "iam" modality: "structured" publicEndpoint: false managed: false properties: deployment: type: "enum" values: ["customer-hosted"] default: "customer-hosted" ingestion: type: "enum" values: ["batch", "streaming"] default: "batch" output: type: "enum" values: ["churn-propensity", "upgrade-propensity", "next-best-offer", "segment"] default: "churn-propensity"