[GTM glossary](/glossary.txt) Technology install signals Signals & Intent # Technology install signals In short Technology install signals are detected events showing that a company has added a specific technology product to its stack, usually found through traces on its website or other public sources. A new analytics tag or chat widget is a typical example. They are a narrow, event-based type of technographic data. The signal is the fresh install, which matters because the weeks after a purchase are when related needs, such as integrations, add-ons, and services, are most active. ## How installs are detected Most detection tools scan public websites for scripts, cookies, tags, and other fingerprints that identify a product. Some also use DNS records and job postings. By comparing scans over time, they flag when a product appears. * **Strengths:** Covers many companies without asking them. * **Limits:** Cannot see internal systems, back-office tools, or products with no web footprint. * **Lag:** A detection may come days or weeks after the real install. --- ## Ways to use install signals ### Complementary products Reach accounts that just installed a platform you integrate with, with a message about connecting the two. ### Competitive plays When a competitor’s product appears, share comparison content or switching help, where relevant. ### Services and consulting A new install often means an implementation or training need. ### Customer expansion Spot when an existing customer adds a tool that your product should connect to. --- ## Example Say a company sells email deliverability monitoring. It tracks accounts that newly install a particular marketing automation platform. When a target account appears, the rep writes about the deliverability issues teams often hit during setup and offers a checklist, a more relevant note than a cold pitch. --- ## Technology install signals vs. tech adoption signals Install signals capture a single event, the detected installation. Tech adoption signals also include expansion, hiring, and removal, so they cover a wider picture of change. --- ## Common mistakes * **Reaching out on old installs:** Value drops as time passes. Filter by recency. * **Overclaiming:** Do not state they use a tool unless you have verified it. Say you noticed signs of it. * **No fit check:** An install at a poor-fit company is still not a lead. * **Single-signal reliance:** Combine with hiring, leadership change, or engagement for stronger timing. --- ## Technology install signals FAQs **What are technology install signals?** Technology install signals are detected events showing a company has recently added a specific technology product to its stack, usually spotted through scripts and tags on its website. Vendors use them as timely triggers for relevant outreach. **How are technology installs detected?** Detection tools scan public websites for scripts, cookies, tags, and other fingerprints that identify products, and compare scans over time to find new ones. Some also use job postings and DNS records. They miss internal systems with no public footprint. **How fresh does a technology install signal need to be?** Fresher is better, since needs around a new install, such as integrations and training, are most active soon after it. Set a recency window that fits your sales cycle, and treat older installs as background context rather than triggers. **How do you use technology install signals in outreach?** Tie the message to the problem a new install usually creates, such as integration or setup issues, and offer something useful. Avoid claiming certainty about their stack; say you noticed signs of the tool and keep the focus on their likely needs. Share term --- ## More related phrases * [Job postings data](/glossary/job-postings-data.txt) * [Job change signals](/glossary/job-change-signals.txt) * [Intent data](/glossary/intent-data.txt) ## Similar phrases * [Tech adoption signals](/glossary/tech-adoption-signals.txt) Tech adoption signals show that a company is starting to use, expand, or drop a technology, and give sales and marketing a timely reason to reach out with a relevant offer. * [Tech stack data](/glossary/tech-stack-data.txt) Tech stack data lists which software, platforms, and tools a company uses, so teams can segment accounts, qualify fit, and tailor outreach around the tools already in place. * [Technographics](/glossary/technographics.txt) Technographics is the practice of profiling companies by the technologies they use, the way demographics profile people, so B2B teams can segment and target accounts. * [Technographic data](/glossary/technographic-data.txt) Technographic data describes the technologies a company uses and how it uses them, helping B2B teams segment accounts, judge product fit, and time relevant outreach. * [Trigger events](/glossary/trigger-events.txt) Trigger events are changes at a company or in a role, such as funding, a new executive, or an expansion, that create a timely reason to start a sales conversation.