> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inflection.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Common Connections & Use Cases

> How data from Sales, Product, and Marketing come together to power personalization at scale.

Inflection brings together data from Product, Marketing, and Sales to create a fully-contexed, 360-degree view of a prospect or customer. This enables marketers to target and personalize across their product and account-based data. (Learn about setting up and configuring integrations at our help center.)

<AccordionGroup>
  <Accordion title="Sales data (CRM)">
    Inflection natively integrates with Salesforce.

    ### Objects & fields

    Inflection integrates with Salesforce Leads, Contacts, Campaign Members, Campaigns, and Accounts.

    | Summary              | **Read** | **Write** | **Create** |
    | -------------------- | -------- | --------- | ---------- |
    | **Leads**            | ✅        | ✅         | ✅          |
    | **Contacts**         | ✅        | ✅         | ✅          |
    | **Campaign Members** | ✅        | ✅         | ✅          |
    | **Campaigns**        | ✅        |           |            |
    | **Accounts**         | ✅        |           |            |
    | **Opportunities**    | ✅        |           |            |

    Inflection does not interact with Activities or Custom Objects at this time.

    ### Common Use Cases

    #### Leads and contacts

    * When a marketing contact is created in Inflection, nurture and score the contact until it is ready for Sales follow-up; then, create a lead in Salesforce.
    * Update score, status, lifecycle (etc.) fields in either system and see updates reflected in the other in near real-time.
    * When an Inflection contact is identified as a key contact on a target account (through Inflection Contact-to-Account matching), create as a contact in Salesforce.

    #### Campaigns and campaign members

    * When an Inflection contact submits a Sales or campaign form, add them to the appropriate Salesforce campaign for reporting and attribution.
    * Use Salesforce campaigns and statuses to track event registration, attendance, and other statuses.
    * Target Inflection contacts based on campaign membership and status.

    #### Accounts

    * Trigger and/or dynamically populate emails based on account attributes like rep and renewal date.
    * With Inflection Contact-to-Account matching, apply account-based segmentation *before* the Inflection contact has been created in Salesforce.
    * Target Inflection contacts based on activity or attributes of other members of the account. e.g., Target executives at an account where at least one member has an active free trial.

    #### Opportunities

    * Suppress contacts at accounts with active deals to keep marketing aligned with sales during negotiations (e.g., exclude renewal nurtures while Stage is Discovery, Negotiation, or Proposal Sent).
    * Run executive nurtures keyed to deal size: target CFOs at accounts with Opportunities above a threshold amount.
    * Segment audiences by deal stage: education sequences for Discovery-stage contacts, deal-acceleration content for Negotiation, expansion offers for Closed Won.
    * Surface deal context on every contact and account profile so marketers know which accounts are mid-deal before reaching out.

    ### Sync & monitoring

    Inflection is built for enterprise PLG companies that have high-volume, high-velocity data feeds. At this time, there is no limit to the volume of data Inflection can house or sync.

    Salesforce API limits can be configured and sync health can be monitored from Inflection.

    The scope of leads/contacts that sync between Inflection and Salesforce can be configured via the integration user’s permission set in Salesforce, and/or in Inflection. Learn more about configuring the [Inflection\<>Salesforce integration](/connections/salesforce).
  </Accordion>

  <Accordion title="Product data (CDP/DWH)">
    Inflection natively integrates with Big Query, Databricks, Redshift, Segment.io, and Snowflake, with more on the way. We are constantly expanding the providers we support.

    Inflection natively supports the following tables/views.

    | Tables             | **Read** | **Write** |
    | ------------------ | -------- | --------- |
    | Product Activities | ✅        |           |
    | Product Users      | ✅        |           |
    | Product Workspaces | ✅        |           |
    | Journey Activities |          | ✅         |

    ### Common Use Cases

    #### Product Activities

    Think of the product activity table as a receipt of every tracked action (commonly called events) each user takes in your product. Inflection ingests an unabridged feed of the events you choose, complete with event properties.

    * Understand which onboarding milestones a new user has reached, and which they have left to complete. Personalize an onboarding nurture to only message around the next-best action (milestone) for each user.
    * Detect when a free plan user shows signs that they are ready to upgrade (i.e., they are trying to use a paid-only feature). Send a timely nudge to the user to upgrade.
    * Send abandoned-cart messaging to users who view the pricing page but do not upgrade.

    [Read how Formstack jacked up their expansion revenue with product-informed campaigns.](https://www.inflection.io/post/how-formstack-ditched-legacy-marketing-automation-for-inflection-io)

    #### Product Users

    For many product-led companies, it is common that their customers participate in multiple product workspaces; therefore one customer can have many users. Inflection supports the many-to-many relationship between users and workspaces.

    Inflection can distinguish between, segment, and personalize to a person who is an admin in a free trial workspace **and** a member in a paid workspace.

    * Send a personalized message to admins regarding their account, with deep links to features within their workspace, and workspace details like plan or billing details.
    * Identify users who have downgraded from a paid workspace but are still active in a free workspace; offer targeted win-back campaigns.
    * Identify users in free workspaces who belong to accounts where a paid workspace is already available; nudge the free user to join the paid workspace (growing upsell potential for the existing customer).

    #### Product Workspaces

    Workspaces, also called orgs, typically include attributes like plan. This is information about the workspace that multiple users can share.

    * Trigger account-wide upgrade or renewal campaigns based on workspace plan type, billing cycle, or trial expiration.
    * Identify workspaces with high user activity but limited seat usage and promote expansion offers.
    * Deliver account-specific messages (like onboarding guides, feature highlights, or renewal tips from the AE or CSM) to members of enterprise workspaces.

    #### Journey Activities

    Inflection writes journey activities back to CDP/Data Warehouses in order to power reporting, insights, and attribution in our customers’ analytics environment. These activities include email events (open, click, bounce, unsubscribe), form and webhook submissions, and journey lifecycle events (journey entered, journey completed, journey exited) (read more in the set-up doc).

    * Correlate email engagement with in-product activity to understand which messages drive feature adoption.
    * Attribute upgrades and expansion revenue to specific campaigns or nurture sequences by joining journey events with conversion data.
    * Create dashboards in your BI tool to visualize the full funnel from email send to product milestone completion to paid conversion.
    * Report on journey-level performance: entries, completions, and early exits alongside email engagement to see where contacts drop out of a nurture.

    Learn more about configuring [data warehouse](/connections/import-from-data-warehouse) or [CDP](/connections/segment) integrations with Inflection.
  </Accordion>

  <Accordion title="Web data">
    Inflection's web tracking captures anonymous and identified visitor behavior across your marketing website, documentation, pricing pages, and other digital properties. This behavioral data enriches your customer profiles and enables precise targeting based on demonstrated interest and intent signals.

    ### Web tracking data

    Inflection natively supports web tracking through a lightweight JavaScript snippet that captures page views, form submissions, and link clicks.

    | Event Type           | **Track** | **Properties**                       | **Identity Resolution** |
    | -------------------- | --------- | ------------------------------------ | ----------------------- |
    | **Page Views**       | ✅         | URL, title, referrer, timestamp      | ✅                       |
    | **Form Submissions** | ✅         | Form ID, field values, page context  | ✅                       |
    | **Link Clicks**      | ✅         | Link URL, text, destination, context | ✅                       |

    Inflection automatically captures UTM parameters, device type, browser, and geographic information with every event.

    ### Common Use Cases

    #### Page views

    Page view tracking reveals what content prospects engage with before and after they convert, providing critical context for personalization and lead scoring.

    * Identify prospects who visit high-intent pages like pricing, security, or enterprise features multiple times; score them and trigger sales alerts.
    * Segment contacts based on content theme engagement (e.g., "visited 3+ integration-related pages") to deliver targeted campaign messaging about your integration capabilities.
    * Detect when a prospect returns to your website after going dark; automatically re-engage them with content related to pages they previously viewed.

    #### Form submissions

    Form submissions are high-value conversion events that signal explicit interest. Inflection captures both the fact that a form was submitted and the data entered.

    * When a prospect submits a demo request form, immediately route to sales and trigger a personalized nurture sequence that references their specific use case or pain point mentioned in the form.
    * Track which content downloads (whitepapers, case studies, templates) each contact has requested; use this to understand their role, priorities, and stage in the buying journey.
    * Identify contacts who submit multiple forms across different topic areas; flag them as high-intent and enable multi-threading sales outreach.

    #### Link clicks

    Link click tracking reveals micro-commitments and specific areas of interest, especially valuable for content embedded in your website.

    * Track clicks on "Book a Demo" or "Contact Sales" CTAs even when they don't result in form submissions; these are strong intent signals worth scoring or alerting on.
    * Monitor clicks on integration or feature pages to understand technology stack and feature priorities; personalize follow-up content accordingly.
    * Track social proof interactions like clicks on customer logos, awards, or analyst reports; use this to gauge trust-building progress.

    ### Identity resolution & enrichment

    Inflection automatically resolves anonymous web visitors to known contacts when they identify themselves through form submissions or email link clicks. This creates a complete behavioral timeline from first anonymous visit through customer journey.

    This means new contact records will enrich with historical web behavior data automatically upon identification.

    Learn more about setting up web tracking with Inflection: [Web Tracking](/connections/web-tracking).
  </Accordion>
</AccordionGroup>
