> ## Documentation Index > Fetch the complete documentation index at: https://docs.unifygtm.com/llms.txt > Use this file to discover all available pages before exploring further. # Getting intent data into Unify > Connect your website or product to send visitor intent data into Unify. export const UnifyLogoLight = () => ; export const UnifyLogoDark = () => ; export const PosthogLogoLight = () => ; export const PosthogLogoDark = () => ; export const SegmentIcon = () => ; ## Quick overview Before you can build Plays on website visitors or product usage events, you need to get that data flowing into Unify. This guide walks you through the options to help you pick the right approach for your setup. Unify can collect page views, identify events, and custom events from your website or product. After events are collected, Unify links them to companies and people when possible so you can see and use that activity throughout Unify. | What you're connecting | Effort | Who does it | | :------------------------ | :----------- | :------------------------------- | | Marketing website traffic | \~15 minutes | You (or a developer) | | Product usage data | 1–2 hours | A developer, with input from you | Most teams start with **marketing website traffic** because it's the fastest path to value—you can be running Plays on website visitors within minutes. Product usage data typically comes next, once you've seen the value of intent-driven outbound and want to expand into PLG or upsell motions. Forward existing PostHog or Segment events to Unify, or install the website tag to start capturing visitor data. Forward existing PostHog or Segment events to Unify, or set up the Unify SDK to capture in-app signals. ## Connect your marketing website Getting website traffic into Unify is the fastest way to start identifying companies visiting your site and running Plays on them. In many cases, you can do this yourself without involving a developer. ### If you don't already have an analytics tool on your website Install the **Unify Intent Client**, a Unify-provided JavaScript library that will automatically capture website visits and basic form fills. } href="https://app.unifygtm.com/dashboard/settings/data/web-intent?webEventsTab=Settings" horizontal > Install the Unify website tag, React library, or JavaScript library on your website. The simplest way to install the client is using the *website tag* approach. Simply copy a snippet of code from Unify and paste it into your site's HTML (or through a tag manager). This is a one-time setup that takes about 15 minutes. If you have a more sophisticated website setup (such as single-page application), the Unify Intent Client is also available as a React library and a JavaScript library. This may require developer involvement to set up. ### If you prefer to use Segment or PostHog events You can forward events from your existing tool directly to Unify—no additional tag or script needed. This reuses your existing setup and avoids adding another piece of code to your site. } href="/reference/integrations/segment"> Send Segment events into Unify. } href="/reference/integrations/posthog" > Send PostHog events into Unify. These integrations are typically configured by a developer or someone with access to your Segment or PostHog account. The setup takes about 10–15 minutes. **Don't install both.** If you forward events from Segment or PostHog, do not also install the Unify Intent Client on the same site. Running two event sources on the same site will produce duplicate data. ### How to decide If you're unsure of which approach to use, here's our recommendation: * **Looking for the simplest setup?** Install the Unify Website Tag. * **Already have Segment or PostHog on your marketing site?** Forward events from there. * **Don't have either?** Install the Unify Intent Client. This decision is easy to change later if you want to switch approaches. ## Connecting product usage data Product usage data captures what users do inside your product—logins, feature usage, paywall hits, and more. This is what powers upsell Plays, expansion motions, and PLG-driven outbound. Setting this up often requires developer involvement. This section helps you decide on an approach and coordinate with your engineering team to get data flowing into Unify. ### Decide which user actions to track Before involving a developer, think about the product signals that would trigger outreach from your team. You don't need to track everything—start with the 3–5 actions that are most likely to indicate buying intent or expansion readiness. **Here are some common starting points:** | Signal | Why it matters | | :------------------------- | :-------------------------------------------------------------- | | User logs in | Establishes identity—links all activity to a known person | | Paywall or usage limit hit | Strongest upgrade signal—user wants more than their plan allows | | Key feature activated | Shows the user is getting value and may be ready to go deeper | | Team member invited | Team growth signals expansion readiness | | Upgrade CTA clicked | Direct purchase intent | ### If you already use Segment or PostHog in your product You can forward events from your existing tool directly to Unify—no new code needed in the product itself. This is the simplest path if you already have analytics instrumentation in place. } href="/reference/integrations/segment"> Send Segment events into Unify. } href="/reference/integrations/posthog" > Send PostHog events into Unify. Your developer may still need to add instrumentation for the specific actions you identified above if they aren't already being tracked in Segment or PostHog. ### If you don't have an existing analytics tool Install the **Unify Intent Client** JavaScript or React library directly in your product. This gives you functions in your product to send user identity and actions to Unify. } href="/developers/guides/product-usage-data/unify-intent-client" horizontal > Install the JavaScript or React SDK in your web application. This requires a developer to add code to your product. The [Product usage data guide](/developers/guides/product-usage-data/introduction) includes code examples, setup walkthroughs, and guidance on the available options. **Don't install both.** If you forward events from Segment or PostHog, do not also install the Unify Intent Client in the same app. Running two event sources in the same app will produce duplicate data. ### How to decide * **Already have Segment or PostHog in your product?** Forward events from there. Ask your developer if the actions you want to track are already instrumented—if not, they'll need to add them. * **Don't have either?** Install the Unify Intent Client. * **Use a different analytics tool (e.g., RudderStack, Amplitude)?** Check if it supports sending events to a webhook destination. If so, your developer can configure it to send events to Unify. If not, install the Unify Intent Client alongside it.