Glossary todos

Issues found while running detect-related-terms on 10 random articles (2026-08-31).

Missing glossary entries

These terms were requested via snr-ModelRequestedTerms across multiple articles. Importance will be calculated later from corpus-wide occurrence counts and positions.

• dynamic-content — Dynamic content (Insert objects, web layers, popups) is a major Experience Hub feature with no glossary entry. Referenced by css-selectors.md, introduction-to-dynamic-content.md, shopify-integration.md, and likely many other campaign articles.
• mobile-push — Mobile push notifications are a distinct campaign type with their own templates, SDK requirements, and delivery logic. No glossary entry exists. Referenced by mobile-push-visual-builder.md, android-listeners.md, flutter.md (push config), ios.md (push config).
• in-app-message — In-app messages are a distinct campaign type with their own templates, SDK requirements, and display logic. No glossary entry exists. Referenced by inapp-drag-and-drop.md and android-listeners.md.
• screen-view — A campaign type that displays documents to users in mobile applications, with feeds, scheduling, and priority. No glossary entry. Referenced by whats-new.md (screen views).
• organization — The entity that groups workspaces in Synerise, with its own user management, roles (Administrator, Member), and consumption reports. No glossary entry. Referenced by users.md (organization users).
• brickworks — The content management system within Data Modeling Hub (schemas, records, external sources). No standalone glossary entry. Referenced by creating-external-source.md.
• loyalty-points — Points in a loyalty program that can be earned, transferred between customers, and redeemed. No glossary entry. Referenced by scenarios.md (loyalty lesson 3).
• external-source — Fetching live data from external APIs into Brickworks records. No glossary entry. Referenced by creating-external-source.md.
• document — A content unit (JSON structure) used in screen view campaigns and mobile SDK content delivery. No glossary entry. Referenced by whats-new.md (screen views).
• data-transformation-rule-node — Data transformation nodes (Data Input, Rename Column, Decrypt Data, Data Output, etc.) are explicitly "different than automation nodes" per the data-transformation glossary entry, but have no entry of their own. Referenced by rename-columns.md and decrypt-data.md.
• insert — Jinjava-based dynamic content tags used in templates to reference customer data, recommendations, aggregates, etc. No glossary entry. Referenced by mobile-push-visual-builder.md, update-dynamic-discount-value.md.
• ai-hub — The AI Hub component housing recommendations, predictions, AI search, and promotions. No glossary entry. Referenced by introduction-to-ai-promotions.md, discover-customers-for-new-shop-branch.md.
• snippet — Reusable code segments used in templates and configuration fields. No glossary entry. Referenced by creating-external-source.md.
• whatsapp — The WhatsApp Send Template Message integration node in Automation Hub. No glossary entry. Referenced by whatsapp-abandoned-cart.md.
• ai-assistant — The Customer AI Assistant, a conversational shopping tool embedded in stores. No glossary entry. Referenced by ai-assistant.md.
• api-consumption — API call monitoring and statistics at the organization level. No glossary entry. Referenced by api-calls.md.
• web-push — Web push notifications are a distinct campaign channel with their own templates, TTL/lifespan settings, and subscriber requirements. No glossary entry. Referenced by send-webpush-node.md.
• funnel — A sequence of steps used to analyze conversion drop-off across events. A core Decision Hub analytics feature with its own UI. No glossary entry. Referenced by faq_analytics.md.
• histogram — A Decision Hub analytics type that visualizes distribution of event parameter or attribute values across buckets. No glossary entry. Referenced by removing-histograms.md.
• sms — SMS is a distinct campaign channel with its own gateway configuration, sender name verification, and delivery rules. No glossary entry. Referenced by cant-send-sms-with-custom-sender-name.md.
• dashboard — A visual analytics tool in Decision Hub that combines metrics, reports, trends, segmentations, aggregates, and other analyses into a unified view. No glossary entry. Referenced by customer-dashboard-call-center.md.

Semantic mismatches

Cases where a glossary term's title matches a word used in articles, but the glossary definition doesn't cover the article's meaning. These cause incorrect term matching if not addressed.

Resolution pattern: Create disambiguated entries following the existing convention — add context in parentheses to the title, and optionally a module/feature suffix to the id. Examples already in the glossary: schema "Schema (brickworks)" vs. schema-automation "Schema"; statistics-automation "Statistics".

filter

• Glossary definition: "A funnel—a sequence of one or more conditions—that selects profiles by attributes, events, or other analyses" (Decision Hub concept).
• Mismatched usage: AI Search articles use "filter" for item attribute filtering (including/excluding search results by attribute values). This is a different mechanism in a different module.
• Suggested entry: filter-ai-search with title "Filter (AI Search)" — item attribute filtering for including/excluding search results.

distinct-filters

• Glossary definition: "A filter that increases item variety in a recommendation slot" — scoped to AI Recommendations only.
• Mismatched usage: define-attributes.md (AI Search) describes "distinct attributes" applied as distinct filters to "increase result variety or deduplicate item variants" in search results. Same mechanism name, different module.
• Suggested entry: distinct-filters-ai-search with title "Distinct filters (AI Search)" — distinct attributes applied to search results to increase variety or deduplicate variants.

node

• Glossary definition: "A building element of the workflow" — specifically automation workflow nodes (triggers, flow control, conditions, actions, integrations).
• Mismatched usage: Data transformation articles reference "nodes" (Data Input, Rename Column, Decrypt Data, etc.) that are explicitly noted as "different than automation nodes" in the data-transformation entry. Mapping these to the node glossary ID would give an AI model the wrong definition.
• Suggested entry: data-transformation-rule-node with title "Node (data transformation)" — a building element of a data transformation rule (Data Input, Rename Column, Decrypt Data, Data Output, etc.), distinct from automation workflow nodes.

integration (systemic)

• Glossary definition: "A node that lets you connect a workflow with an external service or system" — specifically an automation workflow node category.
• Mismatched usage: Many articles across Settings, use cases, and Developers use "integration" for platform-level connections between Synerise and third-party services, configured in Settings > Apps & Services. No workflow is involved — it's a workspace-level configuration. This affects every third-party service article (Shopify, Salesforce, Google Cloud, etc.), not just isolated cases.
• Examples of the mismatch:
  • shopify-integration.md: "Click New integration" in Settings > Apps & Services — a workspace-level Shopify connection, not a workflow node.
  • creating-external-source.md: "The connection you created can be used later in Workflows and Brickworks external sources" — a reusable connection object, not a node.
  • Any article linking to Settings > Apps & Services for a third-party service setup.
• Suggested entry: integration-platform with title "Integration (platform)" — a platform-level connection between Synerise and a third-party service, configured in Settings > Apps & Services, distinct from automation workflow integration nodes.

tag

• Glossary definition: A label assigned to a customer profile for segmentation and targeting purposes (profile tag).
• Mismatched usage: Campaign-related articles (e.g., campaign-limits.md, tagging-campaigns.md) use "tag" for campaign tags — labels assigned to campaigns to group them for communication limiting, reporting, and organization. These are configured in a dedicated "campaigns" tag folder and applied per campaign, not per profile.
• Suggested entry: tag-campaign with title "Tag (campaign)" — a label assigned to a campaign for communication limiting and organizational purposes, distinct from profile tags.