# Setting up your brand Source: https://user-guides.demand-genius.com/ai-search-intelligence/brands Create your own brand, add other own brands and competitors, set the default, and enrich competitor records with AI. Everything in AI Search Intelligence starts here. Brands are the subjects the platform reasons about. Every workspace has one default own brand. You can add further own brands (a product line, a regional brand, a sub-brand) and any number of competitors. Perception benchmarks you against the competitors; Visibility tracks all of them; Segments pick which own brand to track. ## Set up your first brand If you signed up self-serve, a draft brand was created for you. If the Brands tab is empty, you will see **Set up your first brand**. Click the Settings cog at the bottom of the sidebar, then **Brands** under AI Search Intelligence. Image 10 09 2026 At 18 32 Use the name as buyers would say it and the bare domain, for example `acme.com`. It should be auto-filled, but make sure it's correct.  You will see **Generating your brand** while the platform reads your site, drafts a description, proposes your entities and maps the competitors AI files you alongside. This usually takes under a minute. Image 10 09 2026 At 18 32 (1) Check the description and the entity lists - these are the custom entities beyond your brand name that we'll pick out in AI responses, to track your brand presence. Everything is editable later. Save to create the brand; it becomes your default automatically. ## The Brands screen Image 10 09 2026 At 18 02 The top card is your default own brand, marked **Default brand**. Its **Entity home** lists the people, trademarks, products, methods and terms attached to it. Below sit **Other own brands** and **Competitors**. Each card shows the context badge (Own or Competitor), the domain and the entity counts. ## Add another own brand or a competitor The brand editor opens. Image 10 09 2026 At 19 02 The domain is used for research and for matching citations back to the brand. **Own** for a brand you control, including sub-brands or sister brands. **Competitor** for anyone you want to be benchmarked against. A short description helps the models frame their answers. The five entity lists are covered in [Custom entities](/ai-search-intelligence/custom-entities). **Leave them empty for now if you prefer; you can enrich with AI later.** Adding a brand never changes which brand is the default. ## Enrich a competitor with AI The platform adds competitors it finds while running, so newly created or auto-detected competitor cards start thin and show **Nothing researched yet**. Click **Enrich with AI** on the card. The platform researches the domain and proposes a description and entities for you to review before they are applied. If it finds little, the record is left unchanged and you are told so. Image 10 09 2026 At 19 02 (1) ## Change the default brand Only own brands can be the default, and exactly one is at any time. On a non-default own brand's card, choose **Set as default**. Segments that track "the default brand" follow the change; segments pinned to a specific brand do not. ## Delete a brand Use the delete action on the card and confirm **Delete this brand?**. Deleting the default promotes your oldest remaining own brand. Competitor brands removed here also drop out of the Perception benchmark on the next run. ## How brands feed the modules * **Perception** uses the default own brand as the subject and every Competitor-context brand as the benchmark. Competitors sync into the Perception scope automatically. * **Visibility** scans answers for every brand and its entities. Each segment names one **Tracked brand**; if none is set, the default is used. * **Stakeholders** scores the tracked brand of each segment. The data model also has a sub-brand context, but the Brands screen creates only Own and Competitor. Treat a sub-brand as another own brand. # Building the buying committee Source: https://user-guides.demand-genius.com/ai-search-intelligence/buying-committee Define the criteria a segment weighs a decision on, the buyers who weigh in, and which criteria each buyer cares about. This is what Stakeholders scores you against. B2B decisions are made by groups. A CMO, a head of SEO and a marketing manager each ask AI different questions before a shortlist exists. The buying committee captures who those people are in a segment and what each of them cares about, so [Stakeholders](/ai-search-intelligence/stakeholders) can tell you which of them you are winning and which you are not. The committee is set per segment, from the segment's card in **Settings > Segments**. ## Build the committee On the segment card, the platform will have auto-generated an initial buying committee, but we'd recommend doing this yourself. Open the segment card, and select "Edit Committee". Image 11 09 2026 At 08 25 If you have any pre-existing internal ICP and buyer persona mapping, then we'd recommend grabbing it so that you can align your AI tracking to the way you view your buyer personas.  First, add the critical buying criteria for **that market segment** specifically. Type a criterion, for example "Ease of setup", and press Add. Cost predictability, responsiveness and information security are typical for a services buyer; integrations and migration effort for software. \_For a start, click "Enrich with AI" in the top right corner. This will auto-generate an initial version of the stakeholders that you can refine. \_ Image 11 09 2026 At 08 28 Add all the personas that influence a buying decision in that segment, including both decision makers and end users. For example "VP Sales" or "Head of Marketing". Image 11 09 2026 At 08 30 Link each buyer to the criteria they care about. Each buyer must have at least one criteria (or else they shouldn't be considered part of the buying committee!). Most buyers care about two or three things; resist linking everyone to everything. To link a criterion to a buyer, click the criterion at the bottom and select the relevant buyer.  Reorder the criteria so that each buyer's needs are ranked from most to least important - this will inform the risks we flag in the stakeholder map.  Image 11 09 2026 At 08 33 The review shows counts for **Criteria**, **Buyers** and **Links**, and lists any buyer with **No criteria assigned**. Confirm to save the committee to the segment. Image 11 09 2026 At 08 36 ## Let AI draft it At any step, the **Suggest more criteria, buyers and links from this segment's market** action drafts additions from the segment's profile. Suggestions are added to the lists for you to edit or remove; nothing is saved until you confirm the review step. Draft with AI, then correct from what you know. Your sales team's view of who blocks a deal is more accurate than any model's. ## Editing later Open the segment card and re-enter the committee setup. Saving a changed committee marks completed Stakeholders analyses for re-scoring; the dashboard refreshes when the re-analysis finishes. ## Troubleshooting * **Stakeholders shows "No stakeholder data yet".** The segment has no saved committee, or the first analysis has not run. Check the segment card, then **Run analysis** on the Stakeholders dashboard. * **A buyer shows no score.** They have no criteria linked. Go back to **Who weighs what**. * **Criteria limits.** The number of buyer roles scored can be limited per workspace by Demand-Genius. If a role is missing from the dashboard, ask. # Custom entities Source: https://user-guides.demand-genius.com/ai-search-intelligence/custom-entities The people, trademarks, products, methods and terms attached to a brand, why they matter for Visibility, and how to maintain them. AI does not always say your brand name. It might name your founder, quote a framework you coined, or recommend a product without the company behind it. Custom entities let the platform catch those mentions and credit them to you. They also flag the reverse: a trademark of yours credited to a competitor. Entities live on each brand record in **Settings > Brands**. They are not a separate screen. ## The five lists | List | What to add | Why it matters | | ----------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------- | | **People** | Founders, executives and named experts AI should associate with this brand | Personal brands often outrank company brands in AI answers | | **Trademarks** | Named IP this brand owns | Watched for AI crediting it to a competitor | | **Products & features** | What should be surfaced in AI answers about this brand | Product-level mentions count towards visibility | | **Methodology** | The signature approaches this brand is known for | Methods get recommended without the vendor being named | | **Terminology** | The category framing and phrasing this brand owns | Tells you whether your language has entered the market's vocabulary | ## Add or edit entities Go to **Settings > Brands** and open the brand you want to edit. Image 11 09 2026 At 08 08 Each list accepts one entry at a time. Use the form buyers and journalists actually use; the scan is for the text as written. Click the cross on an entry to remove it. Former employees and retired products create false positives. Changes apply from the next run. **Enrich with AI** on a brand card drafts all five lists from the brand's website. Use it as a starting point, then prune. The drafts are proposals until you apply them. ## Where entities appear * In **Visibility**, the leaderboard and the **Tracked entities** filter group them as Companies, Products, People and Trademarks. This allows you to detect whether other brand elements beyond your name are showing up in tracked AI conversations. Image 11 09 2026 At 09 21 ## Tips * Add competitors' entities too. Seeing a rival's methodology recommended in your segment is as useful as seeing your own. * Keep terminology to phrases you genuinely own. Generic category terms will match everywhere and tell you nothing. * Entity limits, where they apply, are set per workspace by Demand-Genius. # Perception Source: https://user-guides.demand-genius.com/ai-search-intelligence/perception How AI assistants describe your brand and your competitors: sentiment, strengths, weaknesses and the sources shaping them. What the scores mean and how to change the scope. Perception answers the question "how does AI talk about us?" The platform asks each AI model directly about your brand and about each named competitor, runs sentiment analysis on the answers, and shows you the strengths and weaknesses it keeps returning to and the sources it cites when it does. Where [Visibility](/ai-search-intelligence/visibility) asks *whether* you appear, Perception asks *how* you are described. ## Before you start Perception runs off the brands in **Settings > Brands**. Your default own brand is the subject; competitor brands become the benchmark. Set those up first: [Setting up your brand](/ai-search-intelligence/brands). ## Reading the dashboard Open **Perception** under AI Search Intelligence in the sidebar. Image 11 09 2026 At 08 42 **Overall** is your AI Sentiment Index (ASI), a weighted average across all the models. Positive values mean AI describes you favourably, negative values unfavourably. AI models are positive by default, so the index is adjusted rather than raw. Three metrics sit alongside it: | Metric | What it tells you | | ------------------- | ---------------------------------------------------------------------------------- | | **Signal Strength** | How confident the analysis is in the estimate. Higher is more reliable. | | **Conviction** | How direct and decisive the sentiment language is. Higher means stronger opinions. | | **Inflation** | How much the expressed sentiment may overstate actual perception. Lower is better. | **Change over Time** charts the index per model across runs. **Details** breaks the current run down by model. ### Competitors Benchmarks your brand's sentiment vs. competiEach competitor gets the same metrics plus **Advantage**: a comparative score relative to your brand. Positive means the model views them more favourably than you. ### Strengths and weaknesses Select a brand to see the themed strengths and weaknesses the models return, each with a sentiment score and the number of times it was mentioned across responses. This is the list to take into a positioning discussion: a weakness mentioned often with a low score is where the market narrative is working against you. Image 11 09 2026 At 08 44 ### Sources This shows you which domains are defining the way AI views and presents the different brands in your category. See how influential your own site is (are you the defining authority on how AI views you?) and which third party sites (reviews, comparisons, industry publications) you need to prioritise. Image 11 09 2026 At 08 46 ## When it refreshes Runs are scheduled per workspace, weekly by default. Any change to the scope triggers a fresh run at the next scheduled pass. Progress appears in **Settings > Jobs** under Prompt Execution and Analysis Pipeline. ## Troubleshooting * **No perception data yet.** The first run has not completed. Check **Settings > Jobs** for a Prompt Execution or Analysis Pipeline job in progress. If nothing is listed, confirm an own brand exists in Settings > Brands. * **Budget limit reached** on a job. The workspace's daily token budget for AI calls was hit. The run resumes on the next scheduled pass; contact Demand-Genius if it recurs. * **A competitor is missing.** Check it exists in Settings > Brands with context Competitor, or add it directly in the scope editor. * **A model shows no data.** Not every model is enabled for every workspace. Google AI Overviews in particular is a Visibility engine and does not produce Perception results. # Prompt clusters Source: https://user-guides.demand-genius.com/ai-search-intelligence/prompt-clusters Group the prompts a buyer might ask around one job to be done, generate them from a description or write them by hand, import from CSV, and attach clusters to segments. A prompt cluster is a group of prompts that all express the same buyer intent: shortlisting a supplier, comparing fees, checking a regulatory change. There are dozens of ways a founder might ask an assistant to recommend a development agency; the cluster holds them all, and Visibility reports on the cluster rather than on a hundred individual lines. Clusters are created in **Settings > Prompt Clusters** and attached to segments in **Settings > Segments**. A cluster can be attached to several segments; each segment runs it with its own context. ## Generate a cluster from a description Image 11 09 2026 At 08 12 One or two sentences about who is asking and what they are trying to decide. The placeholder shows the level of detail: "Founders comparing modern CRMs on data model, pricing and migration effort before switching off a spreadsheet". Image 11 09 2026 At 08 14 This usually takes around 15 seconds. The result is marked **AI assembled**. Edit the **Cluster name** and **Description**, then read every prompt. Rewrite any that a real buyer would not type, remove duplicates, add the phrasing your sales team hears. Image 11 09 2026 At 08 15 The cluster appears in the list with its prompt count. ## Write a cluster by hand Open a cluster, or create one without generating, to use the editor directly. * **Name**, for example "Pricing and cost". * **Description** (optional): what buyer intent this cluster represents. * **Prompts**: add one per line, for example "How much does X cost compared to Y?". Use the cross to remove a prompt. * **Import prompts from CSV** adds prompts in bulk from a file with one prompt per row. Each CSV should contain a single column, with a single cluster. Image 11 09 2026 At 08 16 ## Attach a cluster to a segment You might not want to track every cluster in every segment. For example, a cluster around Enterprise Security and Compliance might be relevant to your Enterprise segment, but not your Mid-market segment. For this reason, the final step is to attach your clusters to the relevant segments. You'll find it under "AI Search Intelligence" in the left-hand panel.  It lists attached clusters and shows **No prompt clusters yet** if none are. Use **Search clusters** to find a cluster and attach it. Detach with the cross on the cluster chip. Image 11 09 2026 At 08 19 The next Visibility run for the segment includes the cluster. ## Writing good prompts * Write as the buyer types, not as a marketer describes them. "best contract software for a five-person legal team" beats "CLM solutions for SMB legal departments". * One intent per cluster. If a cluster mixes "compare prices" with "is this compliant", split it. * Cover the buyer's stage. Early prompts name the problem, not the category; late prompts name competitors. A segment usually needs both kinds. * Do not put your brand name in the prompts. The point is to see whether you appear unprompted, not to bias the prompt-set to your brand. ## Delete a cluster Use the delete action and confirm **Delete this cluster?**. Segments that reference it keep the link until you update them, so open each affected segment and detach it. ## Troubleshooting * **A cluster shows "No prompts yet".** It was created without prompts. Open it and add some; empty clusters produce no visibility data. * **Prompt or cluster limits.** Limits per cluster and per segment, where applied, are set per workspace by Demand-Genius. # Creating a segment Source: https://user-guides.demand-genius.com/ai-search-intelligence/segments Define a buyer type from a one-line brief, review the AI-assembled profile, choose the tracked brand and competitors, and complete the checklist so Visibility can run. A segment is a buyer type: who they are, where they are and what they weigh. Every Visibility run and every Stakeholders analysis is scoped to one. AI answers depend heavily on the asker's context, so the segment is what turns a category average into what your actual buyer sees. Create one segment per genuinely different buyer. A law firm might have "UK real estate companies" and "UK financial services companies". A software company might split founders buying for the first time from enterprises adding capacity. ## Before you start You need an own brand. If none exists the Segments tab tells you to **Add your own brand first**. See [Setting up your brand](/ai-search-intelligence/brands). ## Create a segment Image 10 09 2026 At 19 34 Write one or two sentences as you would say them to a colleague. The placeholder gives the shape: "VC and investment firms in EMEA managing deal flow, weighing us against Affinity and Salesforce". Include the buyer, the region and the alternatives they compare you with. Image 10 09 2026 At 19 34 1 This usually takes around 5-15 seconds as it builds the description and attributes.  Refine anything before you save: * **Segment name** and **Description** * **Ideal customer profile**: Industry, Company size, Buyer persona, Use case. Add or remove values on each row. * **Region**: global, a bloc or a country. * **Tracked brand**: which of your own brands this segment measures. Defaults to your default brand. * **Competitors**: pick from your Brands or type a new one. Image 10 09 2026 At 19 36 The segment appears as a card with a three-item checklist. ## Complete the checklist Each segment card shows what is still needed before it can run. A card marked **Partially configured** is missing at least one. Image 10 09 2026 At 19 38 1 | Checklist item | Where to do it | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Segment defined** | Done when you save the profile above | | **Buying committee defined** | Open the segment and follow [Building the buying committee](/ai-search-intelligence/buying-committee) | | **Prompt clusters attached** | Open the segment, find the prompt clusters section and use **Search clusters** to attach existing clusters. Create clusters under [Prompt clusters](/ai-search-intelligence/prompt-clusters) | ## Edit a segment Open the card. The edit view repeats the profile fields and adds two sections: * **Who AI files you alongside**: the competitor brands scanned for in this segment's answers. * **Prompt clusters**: attach or detach clusters. Detaching removes the cluster from future runs; it does not delete the cluster. If you leave with unsaved changes you will be asked **Save your changes first?**. Image 10 09 2026 At 19 38 2 ## Delete a segment Use the delete action on the card and confirm **Delete this segment?**. Past runs for that segment leave the dashboard. ## Troubleshooting * **The brief produced a profile for the wrong market.** Edit the ICP rows directly rather than re-generating; the fields are the source of truth, the brief is only a starting point. * **Tracked brand shows the wrong brand.** Change it on the segment. Only own brands are offered. * **Visibility still says no data after configuration.** Runs are scheduled; use **Run analysis** on the Visibility dashboard to start one now. # Stakeholders Source: https://user-guides.demand-genius.com/ai-search-intelligence/stakeholders How well AI presents your brand against the criteria each member of a buying committee cares about, segment by segment. Reading the map and running an analysis. Stakeholders goes one level deeper than [Perception](/ai-search-intelligence/perception). Instead of asking how AI describes you in general, it asks how well you are presented against the specific criteria each buyer in a segment weighs a decision on. A general counsel and a head of IT ask AI different questions and get different shortlists. Stakeholders shows you which of those people you are strong for, which you are at risk with, and why. ## Before you start Stakeholders is driven by the buying committee on each segment. Without a committee there is nothing to score. Set one up first: [Building the buying committee](/ai-search-intelligence/buying-committee). ## Reading the dashboard Open **Stakeholders** under AI Search Intelligence and choose a segment from the selector. Image 11 09 2026 At 08 56 **Alignment** answers "does AI think you're a good fit for this segment?". We show you whether it considers the industry, key use cases and organisation size / type to align with what AI considers to be your strengths. ### The stakeholder map The stakeholder map helps you flag critical AI risks that can hold up or even kill a big deal. Each of the criteria you have configured in this segment is analysed - we query AI to ask how strong it considers your brand to be in this regard, running sentiment analysis on the response to generate a score. These scores are then mapped to what each buyer cares about, based on your configuration of your personas, to flag any critical risks. Scores will be lower where we see obvious red flags, particularly if they map to a buyer's "most important" criteria. ## Running an analysis Analyses run on the workspace schedule, typically weekly (can vary depending on your plan). To run one now, click **Run analysis** at the top of the dashboard. The button is disabled while a run is in progress. Progress shows in **Settings > Jobs**. Editing a committee (adding a criterion, changing who weighs what) marks completed analyses for re-scoring. The dashboard updates once the re-analysis finishes. ## Troubleshooting * **No stakeholder data yet** with a prompt to go to settings. The selected segment has no buying committee. Add one under **Settings > Segments**. * **First analysis in progress.** The run has been queued but not finished. Check Settings > Jobs; large committees take longer. * **Scores changed after editing the committee.** Expected. Coverage and sentiment are recalculated against the new criteria. * **A buyer you removed still shows.** The dashboard reflects the last completed analysis. Run again. # Visibility Source: https://user-guides.demand-genius.com/ai-search-intelligence/visibility How often your brand and entities appear in AI answers, segment by segment: leaderboard, cited sources, prompt clusters, filters, running and exporting. Visibility answers "when a buyer in this segment asks AI about the things we want to be known for, do we show up?". It runs every prompt in each attached prompt cluster against the AI engines, with the segment configuration used as a "system prompt". The result is a clear picture of exactly what *that specific ICP* sees in AI conversations: a leaderboard, the sources driving the answers and the individual prompts behind them. Reporting is primarily at a "cluster-level" to give you a high level picture you can share internally, but you can drill into the prompt-level data, and export all the results for off-platform analysis (Claude is good at this!). Our segment-based visibility tracking is all built on our original research, which showed the impact each buyer's specific context has on what they see in AI conversations, and how likely your brand is to show up. We highly recommend reading the full research here: [How conversational context impacts AI responses. ](https://demand-genius.com/research/reports/your-ai-visibility-metrics-are-lying-to-you-how-conversational-context-shapes-ai-responses) ## Before you start A segment needs three things before it can run: a definition, a buying committee and at least one prompt cluster. The checklist on each segment card in **Settings > Segments** shows what is missing. See [Segments](/ai-search-intelligence/segments) and [Prompt clusters](/ai-search-intelligence/prompt-clusters). ## Reading the dashboard Open **Visibility** under AI Search Intelligence. Use the **segment** selector at the top to pick a segment, or **All segments** for the workspace rollup. Image 11 09 2026 At 09 12 ### Leaderboard Every tracked entity ranked by visibility over the last 30 days, with **Score**, **Trend**, **Mentions** and **Citations**. Your brand is marked **You**; the segment's tracked brand carries the **PRIMARY** badge. A mention is the entity named in an answer; a citation is a link to it. Scores are banded Strong, Mixed or Weak. ### Visibility over time The score per entity, zero to one hundred, across the last eight months. ### Top Cited Sources The domains the engines link to when answering this segment's prompts, with citation counts and share of total. Expand a source to see the **Cited pages**. These are the pages doing the work in the answers; if none of them are yours, that is the gap. ### Prompt clusters One row per cluster with **Sentiment score**, the **Entities** found and the **Top source**. Open a cluster to see the prompts and **Sample AI responses**, an example of the actual answer text the engines returned. ### Filters The **Filters** panel narrows everything on the page by **AI engines**, **Prompt clusters**, **Tracked entities** (Companies, Products, People, Trademarks) and individual **Prompts**. Use it to see how one engine treats you, or how a single cluster performs. Image 11 09 2026 At 09 17 ## Running an analysis Runs are scheduled per segment by Demand-Genius, weekly by default. We do not find that there is much benefit to daily prompt tracking outside of high volume or extremely fast moving (e.g. consumer goods) sectors. You can see exactly when it was last run, and when the next run is scheduled, in **Settings > Jobs**. ## Exporting **Export** downloads the current segment's results as CSV inside a ZIP, using the same window as the dashboard. If no run has completed yet you will see **No completed run to export yet**. ## AI engines covered We currently track ChatGPT, CoPilot, Claude, Perplexity, Gemini and Google AI Overviews. We track all models as standard. If there are additional models that you feel are important for your brand to track, get in touch ([tom@demand-genius.com](mailto:tom@demand-genius.com)) and we are happy to consider adding them. ## Troubleshooting * **No visibility data yet.** Either the segment is not fully configured (check its card in Settings > Segments for the three-item checklist) or the first run has not completed (check Settings > Jobs for Scheduled Run or Sitemap Scan jobs). * **Run analysis is disabled.** A run is already in progress or queued. Wait for it to finish. * **All segments is slow to load.** The rollup folds every segment's results. If you have several large segments, view them one at a time. * **A competitor is not on the leaderboard.** Check it is listed under **Who AI files you alongside** on the segment, or add it in Settings > Brands. * **An engine returns nothing.** A single engine failing does not fail the run; its column stays empty for that run. If it persists, contact Demand-Genius. # Adding and managing directories Source: https://user-guides.demand-genius.com/content-intelligence/directories Add a competitor site as its own content library, choose its update day, attach crawler headers, and manage the update schedule for your main site. Your main site is the default library. A directory is an additional library, typically a competitor's site, crawled and tagged the same way so you can compare content side by side and run Smart Columns across both. Each directory has its own update schedule and its own crawler headers. ## Add a directory The scope picker at the top of the Library lists **Main Site** and any directories. The plus button next to it opens **Add Content Library**. Image 11 09 2026 At 10 08 1 The domain of the site to crawl, and a friendly name such as "Main Competitor". Image 11 09 2026 At 10 08 How this directory relates to your main site. **Competitor** is the option offered today. Turn auto-update on to re-crawl the directory on a schedule, then pick the **Auto-Update Day**. Turn it off to crawl only when you click Update. Some sites (e.g. Shopify) block or throttle crawlers. Add HTTP headers here that are sent only when crawling this directory. This is only possible for owned sub-brands, not for competitor sites.  See [Troubleshooting](/content-intelligence/troubleshooting) for when this is needed. The first crawl starts. The directory appears as a tab in the scope picker; pages fill in as they are processed. ## Switch between libraries Use the scope picker to view **Main Site**, a single directory, or several at once. Smart Columns have an **Apply To** control that uses the same list. ## Content update schedule Click **Update** on the toolbar to open the **Content Update Schedule** popover for the current library. * **Auto-Update** on a specific day of the week. * **Last Update**, **Status** and **URLs Found** for the most recent crawl. Status is success, partial failure, error or no new content. * **Next Update** when the next automatic crawl is due. * **Update now** runs a crawl immediately. Manual updates have a cooldown, seven days by default, so the button is unavailable until the cooldown passes. The same popover exists for the main site. ## Edit or delete a directory From the directory's tab, choose **Edit** to change the display name, context type, schedule or headers. The URL cannot be changed; add a new directory instead. Choose **Delete** and confirm to remove the directory and its pages from the Library. ## Limits The number of directories a workspace can hold is set by Demand-Genius per customer. If the Add button is unavailable, ask. ## Troubleshooting * **The directory shows no pages after the first crawl.** Check the site has a readable sitemap and is not blocking crawlers. See [Troubleshooting](/content-intelligence/troubleshooting). * **Status shows partial failure.** Some pages returned errors. Open the directory and sort by Page Status to find them. * **Update is disabled.** The manual cooldown has not passed since the last run, or a crawl is already in progress. # How Content Intelligence works Source: https://user-guides.demand-genius.com/content-intelligence/how-it-works How your site is crawled, tagged and scored: the Library grid, the five KPIs and twelve signals, page status, refresh cadence, Insights and Tree. Content Intelligence is a qualitative content audit run at scale. Every page the crawler finds on your site is read by AI, tagged by what it is and who it is for, and scored against the things that decide whether an AI assistant is likely to pick it up, quote it and recommend you off the back of it. Those scores refresh on a schedule, so a subjective judgement about content quality becomes a KPI you can track and improve. AI Search Intelligence tells you how AI talks about you today. Content Intelligence tells you how you are influencing that, where the gaps are and which pages to work on first. ## The Library Open **Library** under Content Intelligence. This is a database of all your content, which our AI indexes and evaluates. Each row is a page on your site; each column is something the platform knows about it from our AI analysis. Image 11 09 2026 At 09 50 ### Standard columns | Column | What it holds | | ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Title**, **URL** | The page | | **Scrapable** | Deselect this to stop us analysing that page. | | **Page Status** | Indexed, noindex, 301, 404 or 503, from a status probe on each crawl | | **Content Type**, **Topic**, **Funnel Stage**, **Industry**, **Page Type**, **Primary Audience** | AI classification tags, editable | | **Marketing Content** | Whether the page is marketing content or utility (legal, login, careers). Useful for filtering. | | **Language**, **Word Count**, **Date Published**, **Date Modified** | Read from the page - this pulls directly from the metadata. If no published or modified date is shown, this is something to update in your CMS. | | **Description**, **Summary** | Meta description and an AI summary | | **Confidence**, **Explanation** | How sure the classifier was and why | | **Quality, Extractability, Citation Likelihood, Strategic Differentiation, Accuracy & Currency** | Subjective, AI analysis of critical content attributes that drive AI-era performance. Each is composed of 2-4 specific attributes, which we roll up to a score. Expand the column to see the underlying analysis. | Tag values can be edited inline and in bulk for selected rows. **Manage Columns** shows and hides columns and sets their order. **Export CSV** downloads everything or the filtered view. Image 11 09 2026 At 09 56 ### KPI column groups Five collapsible column groups hold the content scores. Collapsed, each shows a score from 0 to 100, its band, the change since the previous capture and a sparkline. Expanded, it shows the underlying signals as labels. Image 11 09 2026 At 09 54 | KPI | Signals | | ----------------------------- | --------------------------------------------------------- | | **Content Quality** | Definition Clarity, Content Depth, Keyword Optimisation | | **AI Extractability** | Content Structure, AI Extractability | | **Citation Likelihood** | Brand Assertion, Authority Signals | | **Strategic Differentiation** | Narrative Ownership, Information Gain | | **Accuracy & Currency** | Information Currency, Product Mention, Product Validation | ## How scores are produced Each page is read in full and each of the twelve signals is given a three-level label by the model, using a fixed rubric. Labels map to 2, 1 or 0. A KPI's score is the sum of its signal values divided by the maximum possible, as a percentage. A signal the model could not assess is left out of both sides rather than guessed. | Band | Score | | -------------- | ------------ | | **Strong** | 67 and above | | **Developing** | 45 to 66 | | **At risk** | below 45 | An **Overall** bar above the grid summarises the library. Because the scoring is done by AI it is directional rather than exact: good enough to justify a recommendation and to show that work moved something, not a laboratory measurement. If the KPI cells show an **Off** chip, KPI scoring has not been switched on for your workspace. Ask Demand-Genius to enable it ([tom@demand-genius.com](mailto:tom@demand-genius.com)). A dash means the page has not been scored yet; a zero is a real zero. ## When things refresh Two schedules run independently. **Content discovery.** The crawler re-reads your sitemap on the auto-update day set for the library (see [Directories](/content-intelligence/directories)), adds new pages and re-checks page status. **KPI scoring.** A nightly job scores pages that are due. How often a page is re-scored depends on your plan: some plans score each page once, others quarterly or monthly. A per-page **Re-run** action scores a single page on demand, limited to once every five minutes per page and thirty pages an hour per workspace. This is intended to let you kick off single-page rescores where you feel the AI may have hallucinated, or have updated a page and want to see if it's improved the score, and is subject to fair usage. Scoring history is kept, which is what the deltas and trendlines draw on. ## Insights **Insights** charts the library across its tags: **Content Volume by Type**, **Content Volume by Topic**, **Publishing Frequency** (how often you publish new content) and **Modified Frequency** (how often you refresh existing content), plus a heatmap you can pivot by Topic, Content Type, Industry, Audience, Funnel Stage or any Smart Column. This helps you see where your authority lies, and can help to contextualise AI visibility trends and identify opportunities. Image 11 09 2026 At 10 00 ## Tree **Tree** shows the same pages as a site hierarchy, so you can see where content sits and expand or collapse branches. It is a navigation aid rather than a report. ## Performance columns If Performance is enabled for your workspace, the grid also carries a **Performance** group: **Traffic Total** and **Influenced MQL / SQL / Closed Won** per page, fed by the tracking script and your CRM. See [Performance tracking](/content-intelligence/performance-tracking). ## Next Run your own analysis across the library. Traffic and pipeline influence per page. Add competitor libraries and set update schedules. Missing pages, blocked crawlers, Shopify. # Performance tracking Source: https://user-guides.demand-genius.com/content-intelligence/performance-tracking The Performance columns in the Library: traffic, influenced MQLs, SQLs and closed-won revenue per page, what feeds them, the time-window and pipeline controls, and how influence is decided. Performance tracking answers "what pieces of content are influencing pipeline?", and helps you make sure your content audit doesn't risk removing pages that drive traffic. It lives inside the Content Intelligence Library as a column group, so the same grid that tells you how well a page is written also tells you how it is performing against the metrics your leadership care about. Sort by any of those columns and you have your answer to which pages are doing the work. The intent is influence measurement, not credit allocation. A page counts as influencing a deal when someone from that account read it in the run-up to the stage change. The output tells you which content to prioritise, not whether a piece directly caused a sale - we're not a full blown attribution solution! ## What you need 1. The tracking script on every page of your site. It records the page views. See [Website and tracking script](/integrations/cms-integration). 2. A CRM connection, with pipelines and a closed-won stage configured, so the platform knows who became a contact and which deals they were part of. See [Connect HubSpot](/integrations/hubspot) or [Connect Salesforce](/integrations/salesforce). 3. Performance enabled on your workspace by Demand-Genius. Until then the columns show an **Off** chip. ## The Performance columns Open **Library** under Content Intelligence. The **Performance** group sits to the right of the KPI groups. Collapsed, it shows one summary column; expand it for the four columns. Image 11 09 2026 At 10 04 | Column | What it counts | | ------------------------- | ------------------------------------------------------------------------------- | | **Traffic Total** | Page views recorded by the tracking script in the selected time window | | **Influenced MQL** | Contacts who became an MQL after viewing this page | | **Influenced SQL** | Deals that reached SQL where someone on the account had viewed this page | | **Influenced Closed Won** | Closed-won deals, as revenue, where someone on the account had viewed this page | ### Reading it * **Sort** by Influenced Closed Won to rank pages by revenue touched; by Traffic Total to see reach; by both to find high-traffic pages that never reach pipeline, and low-traffic pages that do. * **Filter** by any tag column first to answer a narrower question: which content type, topic or funnel stage influences SQLs, for example. Smart Column tags work the same way. * **Export CSV** to total the columns or chart them elsewhere. ### Controls above the grid Image 11 09 2026 At 10 06 * **Traffic window** sets the period the Traffic Total column counts: **1 day**, **7 days**, **30 days** or **All history**. It defaults to 30 days and applies to traffic only. * **Pipeline** appears when you have more than one CRM pipeline configured. **All pipelines** sums the Influenced columns across every pipeline; choosing one shows that pipeline's contribution alone. * **Computed** shows when the Influenced values were last calculated. They are as of that time, not live. ## How influence is decided The rules live in **Settings > Attribution**. They decide how far back a page view counts and what a deal needs before a page is credited with influencing it. Image 11 09 2026 At 10 06 1 | Section | Setting | What it does | | -------------- | ---------------------------------- | -------------------------------------------------------------- | | **SQL** | Automatically include MQLs | Content that influenced the MQL also counts towards the SQL | | **SQL** | Attribution window | How far back before the stage change page views count | | **Closed Won** | Automatically include SQLs | Content that influenced the SQL also counts towards closed won | | **Closed Won** | Number of content interactions | Minimum page views before a page counts | | **Closed Won** | Require interaction at every stage | Only count content seen at MQL, SQL and closed won | | **Closed Won** | Number of stakeholders engaged | Minimum distinct people from the account who viewed content | Save applies the definitions from the next recompute. **Reset** discards unsaved changes. ## When the numbers update * CRM data syncs once a day. A deal that changed stage today appears tomorrow. * Influenced values are precomputed nightly over a fixed rolling 30-day window, and again after a crawl. The **Computed** stamp tells you which run you are looking at. * Traffic Total is precomputed per window, so switching the Traffic window is instant. ## What the empty states mean | What you see | What it means | What to do | | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------- | ------------------------------ | | **Off** chip | Performance is not enabled for the workspace | Ask Demand-Genius to enable it | | Dash, or **Not yet computed. Values appear after the next nightly run.** | Enabled, but the first calculation has not run | Wait for the overnight run | | **0** | A real zero: the page was viewed by nobody who later converted in the window | Nothing to fix | ## Troubleshooting * **Everything is zero.** Check Settings > Website shows the domain as **Verified**, the CRM shows **Connected**, and at least one pipeline has a closed-won stage set. * **Closed Won is empty for one pipeline.** Its closed-won stage is **Not set** in the CRM configuration. Deals from that pipeline are excluded until you set one. * **Numbers changed after adding a pipeline.** Expected. With **All pipelines** selected the Influenced columns sum across every configured pipeline. * **Traffic looks low.** Check the Traffic window; the default is 30 days. Then check the script is in a site-wide footer, not a single page template. * **Salesforce figures look incomplete.** Salesforce runs through the shared sync path and parity with HubSpot has not been verified end to end. Tell Demand-Genius what you see. Earlier versions of the platform had a separate Performance dashboard with Attribution and Journey views. It has been retired. The data and the setup are the same; the Library columns are now the only view. # Creating Smart Columns Source: https://user-guides.demand-genius.com/content-intelligence/smart-columns Run your own analysis across the library with a custom prompt or a template, choose output type and sample size, test on ten rows, and understand what it costs in credits. The standard KPIs answer a fixed set of questions about every page. A Smart Column answers yours. Write a prompt, choose whether you want a tag or free text back, pick how much of each page the model reads, and run it across ten pages, a filtered set or the whole library. Tone of voice, authority signals, product mentions, competitor references: anything you can describe, you can score. Smart Columns are the only feature that uses credits. Everything else, including KPI scoring, runs outside the credit system. ## Create a Smart Column The **Add Smart Column** dialog opens on the **Template** tab. Image 11 09 2026 At 10 13 Templates are pre-built prompts maintained by Demand-Genius, filterable by persona and purpose. Choosing **Use** on a template switches to the **Custom** tab with the form pre-filled so you can adjust it. Or select **Custom** to start blank. The prompt runs against every page in scope, so be specific. The hint on the field says it well: think task, then context, then output. Two help links sit on the left of the dialog: general prompt guidance and a Demand-Genius prompt-builder GPT. [You can access the prompt-builder GPT directly here](https://chatgpt.com/g/g-68bea35c87808191b2ab5850ed1d6c97-demand-genius-promptbuilder) → enter your use case or goal, and it'll help you work towards an effective prompt.  Image 11 09 2026 At 10 16 **Tag** returns a defined label per page, giving clean data you can filter, chart and compare. It's great for assessing and quantifying problems or trends in your content library. **Text** returns more detail per page, for analysis and nuance - for example, if you'd like AI to suggest possible improvements to a piece. Under Tag, **Reporting Tag** makes the tag available to [Performance tracking](/content-intelligence/performance-tracking) so you can filter the Performance columns by it; it needs Performance enabled on your workspace. **400 Words** reads the opening of each page; fast and cheap, enough for tone or topic. **Full Page** reads everything; needed for anything about completeness or specific mentions. **10 rows** runs on a sample. **Selected rows** runs on the rows you ticked in the grid. **Filtered rows** runs on the current filter. **All rows** runs on the whole library. Tick **skip rows that already have a value** to avoid re-running pages you have already scored. Image 11 09 2026 At 10 19 If you have multiple directories, pick which libraries the column runs across. The footer shows **credits/row**, the estimated total and your balance. **Run** starts the job. **Save** stores the column definition without running it. \*\*The column will appear to the right of the database, with the relevant cells highlighted while the AI runs. \*\* Test every new prompt on 10 rows first. Read the output, tighten the prompt, then run the full library. The dialog says the same thing and it is the single biggest way to avoid wasting credits. ## What it costs | Output type | Sample size | Credits per row | | ----------- | ----------- | --------------- | | Text | Full Page | 6 | | Text | 400 Words | 4 | | Tag | Full Page | 3 | | Tag | 400 Words | 1 | Your balance shows at the bottom of the sidebar and under **Settings > Billing**. Credits are allocated to your workspace by Demand-Genius. If you start a run with too few credits you are warned that it will complete partially: rows are processed until the balance runs out. Image 11 09 2026 At 10 21 ## Working with the results * We recommend treating the database like a **waterfall**. Use **tags** to narrow down issues. For example, progressively narrow down 1,000 pieces to the 20 that you'd like to prioritise in light of a given goal. Then use **text** to help you figure out the exact actions / updates that are needed. * Tag columns behave like any other tag: filter the grid by them, pivot the Insights heatmap on them, export them. * **Edit Column** on the column header changes the name or the prompt. Re-run to apply a changed prompt to existing rows. * **Re-run classification** from the row action bar re-scores selected rows for a column. * Delete a column from its header menu. The values go with it. ## Troubleshooting * **Some rows came back empty.** The run hit the credit balance, or the page was not scrapable. Check the Scrapable column and your balance. * **The tag values are inconsistent.** Tag prompts work best when the prompt lists the allowed values explicitly. Edit the prompt and re-run on 10 rows. * **A job seems stuck.** Check **Settings > Jobs** for a Category Classification job. Use **Stop classification** on the row action bar if you need to halt it. # Content Intelligence troubleshooting Source: https://user-guides.demand-genius.com/content-intelligence/troubleshooting Pages missing from the Library, an unreadable sitemap, crawlers blocked by Shopify or a CDN, stuck classification and empty KPI cells. ## Content not found A page you expect is not in the Library. The crawler discovers pages from your `sitemap.xml`. Open `https://yourdomain.com/sitemap.xml` in a browser. If the page is not listed there, or the sitemap does not load, that is the cause. Fix the sitemap in your CMS, then click **Update** on the Library toolbar. Pages behind a login, or blocked by `robots.txt`, cannot be read. If the page returns an error, the Page Status column shows 404 or 503. If it is a one-off, such as a gated asset or a landing page not in the sitemap, use **Add content** on the toolbar. Choose the **Domain**, enter the **Path** or the full **Content URL** and a **Title**. The page is crawled and tagged like any other. Image 11 09 2026 At 10 22 If there is no sitemap and the site is large, contact Demand-Genius. We can look at the site structure and agree how to build the library. We can usually find a way, even if it's doing a manual scrape and uploading via the backend.  ## Sitemap unreadable during sign-up The sign-up flow reads your sitemap before creating the workspace. If it cannot, you see **Sitemap unreadable** with three options: **Talk to us** books a call, **Try another URL** lets you correct the domain, and an email link pre-fills a message to [hello@demand-genius.com](mailto:hello@demand-genius.com). Most AI crawlers rely on the sitemap too, so fixing it helps beyond Demand-Genius. ## Shopify and other sites that block crawlers Some platforms return errors to unknown crawlers or throttle them at the edge. Shopify storefronts are the common case: the crawl runs for a while, then pages start coming back as 503. The fix is to attach custom HTTP headers that the crawler sends only when fetching your site. Shopify and most CDNs let you allow a crawler by a specific User-Agent string or a custom header and value. Get the exact header name and value from whoever manages your storefront or CDN. Image 11 09 2026 At 10 23 Under **Live-site crawler headers**, enter each **Header name** and **Value**. A custom `User-Agent` replaces the default one, which is `Mozilla/5.0 (compatible; SitemapBot/1.0)`. Up to 20 headers can be set; names may contain letters, digits and hyphens only; values are capped at 1024 characters. Hop-by-hop headers and `Cookie` are not allowed. If your site is a Shopify site, which is where we most often see this, [instructions to configure your headers in Shopify are here.](https://help.shopify.com/en/manual/promoting-marketing/seo/crawling-your-store)  Headers are replaced wholesale on save, so an empty editor clears them. Then click **Update** on the Library to re-crawl. For a competitor directory, the same headers editor sits in the **Add Content Library** and **Edit Directory** dialogs and applies to that directory only. ## Classification is stuck or wrong * **A spinner never resolves.** Check **Settings > Jobs**. A Sitemap Scan or Directory Classification job should be listed as running. If nothing is running, use **Re-run classification** from the row action bar; if a job is running but stale, **Stop classification** and re-run. * **A tag is wrong.** Edit it inline. Manual edits are kept. * **A page shows Error status or is not Scrapable.** The page returned an error or blocked the crawler when fetched. Check the Explanation column, fix the page or its access, then re-run that row. * **Bulk re-classification failed on a custom column.** An older issue where unexpected tag values failed the whole page has been fixed; a bad value now costs only that column. Re-run. ## KPI cells are empty | What you see | What it means | What to do | | ----------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------ | | **Off** chip | KPI scoring is not enabled for the workspace | Ask Demand-Genius to enable it | | Dash | Page not yet scored | Wait for the nightly sweep, or use the per-page Re-run | | Blank signal inside an expanded KPI | The model returned an invalid label twice | Stored as unscored by design; re-run later | | **Too many requests** on Re-run | Per-page cooldown (five minutes) or hourly limit (thirty pages) hit | Wait the time shown | ## Where to look first **Settings > Jobs** lists recent background jobs by type: Sitemap Scan, Directory Classification, Category Classification (Smart Columns), Content Intelligence Scoring, and the AI Search Intelligence runs. A job with **Budget limit reached** hit the workspace's daily AI budget and will resume on the next pass. # Frequently asked questions Source: https://user-guides.demand-genius.com/faq Short answers to the questions customers ask about AI Search Intelligence, Content Intelligence, Performance and setup. ## AI Search Intelligence The engine picker currently offers ChatGPT, Gemini, Claude, Perplexity, CoPilot and Google AI Overviews. Coverage is configured per segment by Demand-Genius and is not a pricing variable. We are happy to consider adding additional models on request.  Perception, Stakeholders and Visibility run on a schedule set for your workspace, weekly by default. You can start a run at any time with **Run analysis**. Content Intelligence scores refresh on your plan's cadence, typically quarterly, and content discovery runs on the auto-update day you choose. AI assistants tailor answers to who is asking, and our [Conversational Context research](https://demand-genius.com/research/reports/your-ai-visibility-metrics-are-lying-to-you-how-conversational-context-shapes-ai-responses) showed this to have a big impact on your visibility. An enterprise Fintech buyer and a mid-market retail buyer typing the same prompt get different shortlists. Running with the segment as context shows what your actual buyer sees rather than a category average. A sentiment score adjusted for confidence, hedging and known model patterns. Models are positive by default, so a raw score overstates how favourably you are seen. Signal Strength, Conviction and Inflation show how much to trust it, and we wrap these into a more reliable metric. Basically, it's sentiment, just a bit more accurate than your standard score!  Yes. People, trademarks, products and features, methodologies and terminology attached to a brand are picked out of AI answers. See [Custom entities](/ai-search-intelligence/custom-entities). This is important - brand mentioned are rare at the top and middle of funnel (see our [Dark AI research](https://demand-genius.com/research/reports/dark-ai-and-what-actually-drives-aeo-influence)), but there are other signals you can watch out for to demonstrate brand influence.  Some you added; some the platform found while running and added to Brands with a note that nothing has been researched yet. Enrich or delete them in Settings > Brands. ## Content Intelligence Twelve signals rolled into five KPIs: Content Quality, AI Extractability, Citation Likelihood, Strategic Differentiation, and Accuracy & Currency. Each signal gets a three-level label; the KPI is the percentage of the maximum. See [How it works](/content-intelligence/how-it-works). The crawler discovers pages from your sitemap. If a page is not in the sitemap, is behind a login or returns an error, it will not appear. Add it with **Add content** or fix the sitemap. See [Troubleshooting](/content-intelligence/troubleshooting). Yes, with Smart Columns: a custom prompt or a template, returning a tag or text, on a 400-word sample or the full page, across 10 rows, a selection, a filter or the whole library. Smart Columns are the only thing that uses credits. Between 1 and 6 credits per row depending on output type and sample size. Test on 10 rows first. See [Smart Columns](/content-intelligence/smart-columns). Yes. Edit any tag inline or in bulk. Manual edits are kept. ## Performance and integrations Yes, any CMS. The integration is a single JavaScript snippet added once, about two minutes with CMS access. There is no per-platform connector to wait for. See [Website and tracking script](/integrations/cms-integration). HubSpot and Salesforce. Both read deal-stage progression. No other connectors exist today; others can added when a customer needs one, so feel free to reach out.  No. Model-source and UTM tracking is not built. It's on our roadmap, so do reach out if this is critical for you and we are happy to discuss.  CRM data syncs once a day and per-page figures are recomputed overnight. Yes, if you use Hubspot. Add each pipeline in the CRM configuration with its own deal value property and closed-won stage. Figures are summed across pipelines unless you filter to one. ## Setup and account You define the brand, segments and prompt clusters with AI drafting each step. Five to thirty minutes if your ICP is already documented. Demand-Genius usually configures the first version with you, though, as part of our service-led offering.  No. It measures and diagnoses. It is not a CRM or a CMS, does not write or publish, and does not do PR or reputation outreach. No. Permissions are workspace-wide and module-level. Use a separate workspace for that. See [Fix the Missing reCAPTCHA Token error](/troubleshooting/recaptcha-error). # Create your workspace Source: https://user-guides.demand-genius.com/get-started/create-your-workspace Sign up, verify your email, connect your website and name your workspace. What the sitemap check does and what to do if it fails. There are two ways into Demand-Genius. Most customers receive an invitation email from Demand-Genius or from a colleague, which lands them in an existing workspace. Self-serve sign-up creates a new workspace from scratch. This page covers the sign-up flow; invitations are covered under [Users and roles](/platform-admin/users-and-roles). ## Sign up Go to [app.demand-genius.com](https://app.demand-genius.com) and choose sign up. Enter your work email and a password, or continue with Google. Enter the verification code sent to your inbox. Type the domain of the site you want analysed. The platform reads your sitemap and counts the pages it can see. You will see **Analysing your sitemap and counting pages...** while it works. **Looking good** means the sitemap was read and you can continue. **Sitemap unreadable** means the crawler could not read it. Most AI crawlers rely on the sitemap too, so this is worth fixing. Choose **Talk to us** to book a call, **Try another URL** if you entered the wrong domain, or email [hello@demand-genius.com](mailto:hello@demand-genius.com). Give the workspace a name. This is what appears in the tenant switcher if you later belong to more than one. While you finish, Demand-Genius reads your homepage and drafts a first version of your brand, competitors and categories. You review and edit these in **Settings > Brands** before anything runs. The first crawl of your site starts as soon as the workspace exists. Pages appear in the Content Intelligence Library as they are processed; a large site can take a few hours. ## What happens next 1. Review the drafted brand in **Settings > Brands** and add your competitors. See [Setting up your brand](/ai-search-intelligence/brands). 2. Create at least one segment and attach prompt clusters. See [Segments](/ai-search-intelligence/segments). 3. Watch the first runs in **Settings > Jobs**. Dashboards fill in as runs complete. # Before you start Source: https://user-guides.demand-genius.com/implementation-checklist What to have ready before configuring Demand-Genius: your site, your brand and competitor list, notes on your buyers, and the access you need for integrations. Most configuration takes between five and thirty minutes when you have this to hand. Demand-Genius usually configures the first version with you, so treat this as the list of things to bring to that call. ## Your website The live domain of the site you want analysed, for example `example.com` A readable `sitemap.xml` at the standard path. The crawler discovers pages from the sitemap, and the sign-up flow checks it can be read. The site is publicly reachable. If pages sit behind a login, a CDN bot check or a platform that throttles crawlers, see [Content Intelligence troubleshooting](/content-intelligence/troubleshooting) for custom crawler headers. Any subdomains that hold content you want included, such as `blog.example.com` ## Your brand and market Your brand name and a one-paragraph description in your own words The named people, products, trademarks, methods and terms you want AI to credit to you. See [Custom entities](/ai-search-intelligence/custom-entities). The competitors you want benchmarked against. The platform also suggests competitors it finds AI filing you alongside. Internal notes on your ideal customer profile: industries, company sizes, buyer personas, use cases and regions. One segment per distinct buyer type. For each segment, who sits on the buying committee and what each person weighs a decision on. AI can draft this; your edits make it accurate. The moments you want to show up for: the jobs your buyers are trying to get done when they ask an AI assistant. Each becomes a prompt cluster. ## Access (only if Performance is in scope) Admin access to HubSpot or Salesforce, to create the credentials the connector uses Access to your CMS, or Google Tag Manager, to add a one-line tracking script Performance is optional. AI Search Intelligence and Content Intelligence need only the domain and the brand configuration. ## Your team Who should have access, and whether anyone needs a restricted role. See [Users and roles](/platform-admin/users-and-roles). # Website and tracking script Source: https://user-guides.demand-genius.com/integrations/cms-integration Verify your live domain, add subdomains, install the one-line tracking script in any CMS or via Google Tag Manager, and what happens if you change your domain. There is no per-platform CMS connector. Any CMS works because the integration is a single JavaScript snippet added once to your site. It records page views so the [Performance columns](/content-intelligence/performance-tracking) in the Library can connect content to pipeline. Content scoring does not need it; the crawler reads your site directly. ## Settings > Website Image 11 09 2026 At 10 42 1 ### Live domain The domain entered at sign-up. **Verify domain** checks the tracking script is present and marks the domain **Verified** or **Not verified**. **Add subdomain** registers further hosts, such as `blog.example.com`, so their pages are crawled and their views recorded. ### Tracking script The snippet is a single script tag that loads `demand-genius.iife.js` from `tag.demand-genius.com`, carries your workspace ID in the `dgTenantId` query parameter, and is identified by the id `demandGeniusTag`. Click **Copy** to copy your version with the ID filled in. Add it before the closing body tag on every page. ## Install the script Image 11 09 2026 At 10 43 Most platforms have a "custom code", "footer code" or "scripts" field that applies to every page. Webflow calls it Custom Code > Footer Code; WordPress themes usually expose it in the theme settings or via a child theme's footer template. ## Verify it is working A **Verified** badge confirms the script was found. Open your site, open developer tools, and look in the Network tab for a request to `tag.demand-genius.com`. ## Changing your domain Changing the live domain is a reset, not a rename. Editing the domain field opens **Change your domain?**, which spells it out: existing AI classifications are deleted, the script stops working on the current domain, and a fresh classification starts for the new domain. It cannot be undone. Type **CONFIRM** to proceed. Before you confirm: make sure the new domain has a readable sitemap and is publicly reachable, and plan to reinstall the script on the new site immediately to avoid a gap in tracking. Use **Add subdomain** rather than a domain change if you are adding a host, not moving. ## Troubleshooting * **Not verified after installing.** Check the snippet is on the live published site, not a draft, and that no consent tool or ad blocker is blocking `tag.demand-genius.com` in your test browser. * **Traffic shows on some pages only.** The snippet is probably in a page template rather than the site-wide footer. Move it. * **Old snippet with a different parameter name.** Earlier versions of the snippet used a different query parameter. Replace it with the current one from Settings > Website. # Connect HubSpot Source: https://user-guides.demand-genius.com/integrations/hubspot Create a HubSpot private app token, connect it in Demand-Genius, then configure deal pipelines, a closed-won stage per pipeline and the funnel stages you report on. Demand-Genius reads deals and contacts from HubSpot to link content engagement to pipeline. The connection uses a private app access token you create in HubSpot and paste into Demand-Genius. After connecting, you choose which deal pipelines to sync, the deal value property and closed-won stage for each, and which funnel stages to report on. ## Prerequisites * Super admin rights in HubSpot, needed to create a private app. * The **Modify / Connect / Disconnect Integrations** permission in Demand-Genius. ## Part 1: create the private app in HubSpot In HubSpot, click the settings cog, then **Integrations** in the left menu. HubSpot has moved private apps under **Legacy Apps**; follow the prompt to go there and choose to create a private app. Something recognisable, such as "Demand-Genius integration". On the Scopes tab, grant read access to deals and contacts and to their schemas. Demand-Genius only reads; no write scope is needed. | Scope | Access | | ---------------------- | ------ | | `crm.objects.deals` | Read | | `crm.objects.contacts` | Read | | `crm.schemas.deals` | Read | | `crm.schemas.contacts` | Read | Click create. HubSpot shows the access token once. Copy it somewhere safe. ## Part 2: connect in Demand-Genius The **CRM Integration** card shows HubSpot and Salesforce tiles when nothing is connected. The **Add Integration** dialog opens. Enter it in **Hubspot API Token** and submit. The card now shows **Connected**, the pipelines configured and the number of funnel stages. Click **Configure** to continue. ## Part 3: configure pipelines and stages The configure screen opens with the connection details at the top: the API key with a pencil to update it, and **Delete Integration**. Below it sit three sections. Pipeline and closed-won choices save as soon as you make them; only the funnel stages have a Save button. ### Deals Pipelines Each row pairs one HubSpot deals pipeline with the deal property that holds its value. The first row is marked **Primary**. Its stages become your funnel stages. Pick it from the **Pipeline** dropdown; each option shows the pipeline name and how many stages it has. The HubSpot deal property Demand-Genius reads as the deal's value. It defaults to **Amount**. Change it if your team records value in a different property, for example an annual contract value field. Click **Add pipeline** for each additional pipeline you want synced, choose the pipeline, and set its own deal value property. A pipeline already in use is not offered twice. Every configured pipeline feeds the Performance columns; only the primary drives funnel stages. Use the bin icon on a secondary row. The primary row cannot be removed, only switched. Switching the primary pipeline archives your current funnel stages and stage configuration and moves deal sync to the new primary. You are asked to confirm with **Yes, switch pipeline**. You can restore the previous setup by switching back. Adding or removing a secondary pipeline never touches funnel-stage data. ### Closed Won Stages One selector per configured pipeline, each listing that pipeline's own stages. Choose the stage that counts as closed-won. A pipeline showing **Not set** contributes nothing to closed-won figures until you choose one; its deals are still synced. ### Funnel Stages The stages of the primary pipeline, as checkboxes. Untick test or redundant stages you do not want reported on. **Save** appears once something has changed; **Reset** discards unsaved changes. ## Attribute mapping The **Attribute Mapping** section maps Demand-Genius attributes to HubSpot contact properties. It belongs to the retired forms feature and can be left alone unless Demand-Genius asks you to set it. ## Update or remove the connection * **Update the token** with the pencil next to the API key. The dialog warns that existing data will be lost by updating credentials; treat it as a reconnect, not a refresh. * **Delete Integration** requires typing DELETE to confirm and removes the connection and synced data. ## How the sync runs Deals and their contacts sync once a day, with the deal stage history needed to place each deal in your funnel. Every configured pipeline is included. A pipeline added today shows up after the next sync. See [Performance tracking](/content-intelligence/performance-tracking) for how the data appears in the Library. ## Troubleshooting * **Connected but no pipelines listed.** Open Configure and choose a primary pipeline in the first row. * **Closed-won revenue is zero for one pipeline.** Its Closed Won stage is **Not set**, or its deal value property is not the one your team populates. * **Performance columns stopped updating.** HubSpot tokens can expire or be revoked. Generate a new token in HubSpot and update it with the pencil next to the API key. * **A pipeline is missing from the dropdown.** It is already used on another row, or it is archived in HubSpot. * **Funnel stages changed unexpectedly.** The primary pipeline was switched. Switch back to restore the archived setup. # Connect Salesforce Source: https://user-guides.demand-genius.com/integrations/salesforce Create client-credential OAuth access in Salesforce, connect it in Demand-Genius with the consumer key, secret and token URL, choose Lead or Contact handling and select funnel stages. Demand-Genius connects to Salesforce with OAuth 2.0 client credentials. You create an app in Salesforce that grants API access, copy its consumer key and secret, and paste them into Demand-Genius along with your Salesforce domain. Salesforce runs through the same sync path as HubSpot, but parity has not been verified end to end. Expect to check the first figures against Salesforce with Demand-Genius. ## Prerequisites * Salesforce admin rights. * The **Modify / Connect / Disconnect Integrations** permission in Demand-Genius. ## Part 1: create API access in Salesforce In Setup, go to **Platform Tools > Apps > External Client Apps** and create a new app with a recognisable name and an admin contact email. Enable OAuth, select the **Manage user data via APIs (api)** scope and enable the **Client Credentials Flow**. Set a callback URL (Salesforce requires one even though it is not used here). Under the app's policies, assign a run-as user for the client credentials flow; a dedicated integration user is recommended. From the app's OAuth settings, view and copy both values. In Setup, search **My Domain** and copy the current URL, for example `https://yourcompany.my.salesforce.com`. ## Part 2: connect in Demand-Genius The **Add Integration** dialog opens. * **Consumer Key** from Salesforce * **Consumer Secret** from Salesforce * **Token URL**: your My Domain URL. It must start with `https://`. **Lead** if new people enter Salesforce as leads and are converted later. **Contact** if you work account-based and record people directly as contacts on accounts. Demand-Genius pulls your opportunity stages. Untick any you do not want reported on and click **Save**. ## Update or remove the connection * **Update the credentials** with the pencil next to the API key on the configure screen. The dialog warns that existing data will be lost. * **Delete Integration** requires typing DELETE to confirm. ## Troubleshooting * **Connection fails.** Check the Token URL is your My Domain URL with `https://`, and that the client credentials flow has a run-as user assigned in Salesforce. * **Stages are missing.** Only stages the integration user can see are pulled. Check the user's permissions in Salesforce. * **Figures differ from Salesforce.** Report what you see to Demand-Genius; see the note at the top of this page. # What Demand-Genius does Source: https://user-guides.demand-genius.com/introduction The three questions the platform answers, the modules that answer them, and the handful of concepts every guide assumes you know. Demand-Genius shows you how AI assistants describe and recommend your brand to buyers, whether your content is good enough for AI to use, and which of it reaches pipeline. You configure the brand, the buyers you care about and the questions they ask. The platform runs those questions against the AI models on a schedule and turns the answers into scores you can track. ## Three questions, three module groups | Question | Module group | What you get | | ----------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | What does AI say about us? | **AI Search Intelligence** (Perception, Stakeholders, Visibility) | Sentiment, strengths and weaknesses, mentions, citations and the sources shaping them | | Is our content good enough for AI to use? | **Content Intelligence** (Library, Insights, Tree) | Every page on your site scored against five KPIs, tagged and searchable | | Does any of it reach pipeline? | **Performance tracking** (a column group inside the Library) | Traffic, influenced MQLs, SQLs and closed-won revenue per page | ## Concepts you will meet everywhere **Brand.** A company or product the platform reasons about. Your own brand is the default; you can add other own brands and competitors. Brands live in **Settings > Brands**. **Entities.** Named things attached to a brand that AI might mention without saying the brand name: people, trademarks, products and features, methodologies, terminology. Visibility picks them out of AI answers. **Segment.** A buyer type you want to track: an industry, a company size, a buyer persona, a use case and a region. Everything in AI Search Intelligence runs segment by segment, because AI answers change with who is asking. **Buying committee.** The people inside a segment who weigh in on a decision, and the criteria each of them cares about. Stakeholders scores you against it. **Prompt cluster.** A group of prompts covering one thing a buyer is trying to do, such as shortlisting a supplier or comparing fees. Clusters attach to segments and are what Visibility tracks. **Run.** One pass of a module's prompts across the AI models. Runs happen on a schedule set for your workspace and can be started by hand with **Run analysis**. Progress shows in **Settings > Jobs**. **Library.** The content directory: every page the crawler found on your site, with its tags and KPI scores. Additional libraries can be added for competitor sites. **KPI.** One of five content scores (Content Quality, AI Extractability, Citation Likelihood, Strategic Differentiation, Accuracy & Currency), each rolled up from underlying signals and banded Strong, Developing or At risk. **Smart Column.** A column in the Library you define with your own prompt, run across some or all pages. Smart Columns are the only thing that uses credits. **Workspace.** Your account in Demand-Genius. Users, roles, brands, segments and integrations all belong to a workspace. If you have access to more than one, you choose on login. ## Where things live * The **sidebar** holds the dashboards: Perception, Visibility and Stakeholders under AI Search Intelligence; Library, Tree and Insights under Content Intelligence. Performance tracking is a column group inside the Library rather than its own dashboard. * The **Settings** cog at the bottom of the sidebar opens configuration, grouped as Integrations (CRM, Website, Crawler & Sitemap), AI Search Intelligence (Brands, Segments, Prompt Clusters, Jobs), Data (Attribution), Team (Users, Roles) and Account (Billing). * Your **credits balance** sits at the bottom of the sidebar and links to Billing. ## What it does not do It does not write or publish content, and it is not a CRM or a CMS. It sits alongside your SEO tooling rather than replacing it. It measures and diagnoses; the work of changing the content or the sources stays with you. ## Next What to have ready before configuration. Sign up, verify your email and connect your site. The first thing every module depends on. How pages are crawled, tagged and scored. # Users and roles Source: https://user-guides.demand-genius.com/platform-admin/users-and-roles Invite colleagues, activate and deactivate users, and build roles from the permission list. What the role model can and cannot restrict. Access is managed per workspace under **Settings > Users** and **Settings > Roles**. A user has one role in a workspace; a role is a named set of permissions. You can use the roles provided or build your own. ## Roles ### System roles Every workspace has an **owner**, the person who created it. The owner is not shown in the roles list and cannot be reassigned from the app. New users are invited as **admins** and given a role you choose. Demand-Genius staff use a separate support role for onboarding and support. ### Custom roles Open **Settings > Roles**. The table lists each role with its permissions grouped by module. Image 11 09 2026 At 10 39 For example "Content Manager". Image 11 09 2026 At 10 40 The role is available in the Users tab immediately. **Edit Role** changes the name or permissions for everyone holding it. **Delete Role** is blocked while any user holds the role. ### Permissions | Module | Permission | | ------------ | ------------------------------------------ | | Directory | View Content Directory | | Directory | Tag / Edit Content Metadata | | Directory | Add / Remove Content Entries | | Directory | Add / Remove Column Entries | | Directory | Export Directory | | Performance | View Traffic | | Integrations | View Integrations | | Integrations | Modify / Connect / Disconnect Integrations | | Settings | View Attribution Settings | | Settings | Edit Attribution Models / Settings | | Settings | Add Users / Manage User Roles | A further set of Experience permissions (View Experience Sections, Edit Define, Edit Data, Edit Design, Deploy Changes to Live) belongs to the retired forms feature and can be left unticked. **View Content Directory** gates the Content Intelligence group in the sidebar, and the AI Search Intelligence dashboards sit under the same route, so a role without it sees neither. **View Traffic**, **View Conversions** and **View Revenue** gate the Performance columns in the Library. **View Integrations** gates the Integrations settings. **Add Users / Manage User Roles** gates both Team tabs. ### What roles cannot do There is no way to restrict a user to one brand, one segment or one directory. Permissions are workspace-wide and module-level. If you need a client or team to see only their own segment, give them their own workspace. ## Users Open **Settings > Users**. The table shows **Email**, **Name**, **Role**, **Invitation** status and an active **Status** switch. Image 11 09 2026 At 10 41 ### Invite a user You need the **Add Users / Manage User Roles** permission; without it the button shows "You do not have permission to add users". Image 11 09 2026 At 10 42 Any role from Settings > Roles. The person receives an email with an acceptance link. Their row shows **Pending** until they accept. If they already have a Demand-Genius account for another workspace, accepting adds this workspace to it. One invitation per email address per workspace. To re-invite someone, ask Demand-Genius to clear the earlier invitation. ### Change a user's role Open the user's row to see their details and choose a different **Role**. The change applies at their next page load. ### Deactivate or reactivate a user Use the **Status** switch. Inactive users cannot log in to the workspace but keep their history. The switch is disabled for your own account, for users who have not yet accepted their invitation, and if you lack the manage-users permission. ## Troubleshooting * **The invitation email did not arrive.** Check spam, then confirm the address in the Users table. Invitation links expire; ask Demand-Genius to resend if needed. * **A user sees an empty sidebar.** Their role lacks View Content Directory. Edit the role or assign another. * **Cannot delete a role.** Reassign the users who hold it first. # Fix the Demand Genius Missing reCAPTCHA Token error Source: https://user-guides.demand-genius.com/troubleshooting/recaptcha-error Resolve the 'Missing reCAPTCHA Token' error in Demand Genius by clearing cookies, switching networks, or adjusting browser extension settings. If you see the **"Missing reCAPTCHA Token"** message while logging into Demand-Genius, your browser was unable to generate or send a valid reCAPTCHA security token. This is usually a local issue with your browser or network, not your Demand-Genius account. This error does not indicate a problem with your Demand-Genius account or credentials. It means the reCAPTCHA verification step could not complete on your device or network. ## Why this happens * **Public WiFi networks** (airports, hotels, cafés) often use shared IPs, captive portals, or traffic filtering that can disrupt reCAPTCHA. * If your first login attempt fails on such a network, your browser may cache an **invalid token** in cookies or local storage. * Even after moving to a secure or private network, that cached data can continue to block login attempts until it's cleared. ## Quick fix Clearing your browser data forces a fresh reCAPTCHA token to be generated and resolves most cases. In your browser settings, clear cookies and cached files scoped to `app.demand-genius.com`. You can usually do this from the browser's site settings or privacy panel. Move to a trusted private network (e.g., your home or office WiFi) rather than a public hotspot. Refresh the Demand-Genius login page and attempt to sign in again. Your browser will generate a new reCAPTCHA token. ## Other things to try If clearing cookies and cache doesn't resolve the error, work through the following steps: Opening the login page in an Incognito or Private window is often the fastest way to rule out cached data or extension interference — it starts a clean browser session with no stored cookies or active extensions. * **Disable ad blockers or privacy extensions** temporarily. Some extensions intercept or block the scripts reCAPTCHA depends on. * **Ensure JavaScript and cookies are enabled** in your browser settings. reCAPTCHA requires both to function. * **If you're using a VPN or proxy**, disconnect it and try signing in again. Some VPN exit nodes are flagged by reCAPTCHA's risk scoring. ## Best practices on public WiFi Public networks introduce the most common conditions that trigger this error. Following these steps before you log in can prevent the issue from occurring. * Log in from a secure, private network whenever possible. * If you must use public WiFi, complete any **captive portal login** first (for example, the "Accept Terms" screen that appears when you connect). * If login fails on a public network, clear your cookies and cache before retrying on another network. Still having trouble? Contact Demand-Genius Support and we'll help you get back in quickly.