--- title: "Data Handling FAQs" slug: "data-handling-faqs-2" description: "RevSure unifies leads and contacts, deduplicates records, maps accounts and opportunities, and enables funnel, campaign, visitor, and attribution analytics." tags: ["Website Tracking", "Lead Attribution", "Entity Resolution"] updated: 2026-11-11T06:36:28Z published: 2026-11-11T06:36:28Z canonical: "documents.revsure.ai/data-handling-faqs-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revsure.ai/llms.txt > Use this file to discover all available pages before exploring further. # Data Handling FAQs This document answers frequently asked questions about how RevSure ingests, processes, matches, deduplicates, and analyzes data across CRM, marketing automation, advertising, website tracking, and other connected systems. ## Lead, Contact, and Account Management ### How does RevSure differentiate between Leads and Contacts? RevSure treats Leads and Contacts as a unified **Lead entity** for reporting and analysis. Each record is associated with a RevSure Lead ID, allowing the platform to track lifecycle changes and status history across both Salesforce Leads and Contacts. When a Salesforce Lead is converted into a Contact, RevSure uses the `ConvertedContactId` field to establish the relationship. Lead and Contact status values can be configured within RevSure's funnel to support your organization's lifecycle definitions and reporting requirements. ### How does RevSure identify duplicate Leads and Contacts? RevSure supports configurable entity resolution to identify and deduplicate Leads and Contacts across connected systems. Matching can use identifiers such as email address, name, account, company domain, and other available attributes. RevSure supports both exact matching and probabilistic matching techniques to identify records that may represent the same individual. Deduplication configurations help reduce duplicate records and improve the accuracy of funnel reporting, attribution, and pipeline predictions. ### How does RevSure merge Leads from Salesforce and marketing automation platforms? RevSure unifies Leads from Salesforce and connected marketing automation platforms, including HubSpot and Marketo, under a single Lead entity. Where available, RevSure uses source-system identifiers to establish deterministic relationships. Examples include: - **HubSpot:** `salesforceleadid` on HubSpot Contact records. - **Marketo:** `sfdcleadid` on Marketo Lead records. - **Salesforce:** Lead and Contact identifiers, including converted Lead relationships. When these identifiers are unavailable, RevSure can use entity resolution based on email, name, account, company domain, and other attributes. ### Can Leads be double-counted when the same person exists in multiple systems? Duplicate counting can occur when the same individual exists in multiple source systems without a reliable linking identifier. RevSure helps mitigate this through its configurable entity resolution framework. The platform prioritizes deterministic matching using source-system IDs and can use probabilistic matching when direct identifiers are unavailable. Correctly configured entity resolution improves the accuracy of lead volumes, funnel conversions, projections, and attribution reporting. ### How does RevSure map Leads to Accounts? RevSure uses multiple methods to associate Leads with Accounts, depending on the available source data. - **Direct account association:** Uses the Account ID available on a source record, such as a Salesforce Contact. - **Converted Leads:** Uses the Account associated with the converted Contact. - **Company-name matching:** Uses the company field to identify an existing Account or create an Account entity within RevSure. - **Domain matching:** Uses email and company domains to associate Leads with Accounts. - **Entity resolution:** Uses additional matching attributes when direct relationships are unavailable. Multiple Leads associated with the same identified company can be mapped to a unified Account in RevSure. ### How does RevSure identify duplicate Accounts across different systems? RevSure first looks for shared source-system identifiers that establish a direct relationship between Account records. When these identifiers are unavailable, RevSure uses its entity resolution framework to compare attributes such as company name, domain, industry, and other available company information. This helps consolidate Account records across connected systems, even when names or labels differ. ### Can RevSure support an account-based marketing (ABM) funnel instead of a Lead-based funnel? Yes. RevSure supports configurable funnels based on Leads, Accounts, and Opportunities. For an account-based marketing motion, you can configure Account as the primary funnel entity. RevSure then uses account-level metrics and lifecycle definitions to support funnel analysis, conversion reporting, and attribution. ## Opportunity Association and Data Mapping ### How does RevSure associate Leads and Contacts with Opportunities? RevSure uses relationships available in the source CRM to associate Leads and Contacts with Opportunities. For Salesforce, RevSure uses the `OpportunityContactRole` object. For HubSpot, it uses Contact-to-Deal associations. When a primary Contact is identified in Salesforce, RevSure uses the `Primary` indicator from Opportunity Contact Roles. For HubSpot configurations without a primary Contact indicator, RevSure can use the oldest associated Contact. When direct associations are missing, additional configurable matching methods can be applied. ### What happens when an Opportunity has no associated Contacts? RevSure supports multiple configurable methods for associating Contacts with Opportunities when direct CRM relationships are unavailable. These include: - Assigning the oldest Contact associated with the Opportunity's Account. - Identifying Contacts with activities around Opportunity creation, using a configured time window. - Identifying Contacts with activities during the Opportunity lifecycle. - Using email participants and email activities associated with the Opportunity. These methods help improve Opportunity engagement coverage when CRM associations are incomplete. ### What Opportunity attribution scopes does RevSure support? RevSure supports different scopes for determining which engagements should be considered in Opportunity attribution. | Attribution scope | Description | | --- | --- | | Primary Contact | Considers engagements associated with the Opportunity's primary Contact | | First Contact | Considers engagements associated with the first Contact | | All Contacts | Considers engagements from Contacts associated with the Opportunity | | Account Engagements | Considers account-level engagements and interactions associated with Leads and Contacts belonging to the Account | The attribution scope can be selected based on your organization's CRM data and reporting requirements. ### How does RevSure determine Funnel Lead Source for Opportunities? RevSure first uses the Lead Source attribute available directly on the Opportunity record in the source CRM. If the Opportunity does not contain a Lead Source value, RevSure can use the Lead Source associated with the Opportunity's primary Contact. For Lead records, Funnel Lead Source is derived from the corresponding Lead source field. ### How does RevSure calculate Campaign Touches and Activities for Opportunities? RevSure supports Campaign Touch and Activity calculations across multiple association scopes. These include: - All Leads and Contacts directly associated with an Opportunity. - The primary Contact associated with an Opportunity. - All Leads and Contacts associated with the Opportunity's Account. The selected association scope determines which campaigns and activities are included in the calculated metrics. ## Campaign Data and Attribution ### How does RevSure associate Leads with Campaigns? RevSure uses campaign membership records, marketing automation data, and captured tracking identifiers to associate Leads with Campaigns. Examples include: - Salesforce Campaign Members - Marketo Program Members - Salesloft Cadence Memberships - UTM parameters stored on Lead or Contact records - Advertising identifiers captured through website activities - Marketing automation website-visit records For HubSpot Campaigns, campaign membership extraction may require a manual export of influenced Contact lists. ### How does RevSure associate Activities with Campaigns? RevSure uses available campaign identifiers and tracking parameters to connect Activities with relevant Campaigns. For example, Marketo Programs, Outreach Sequences, and Salesloft Cadences can provide campaign-related identifiers. Website activities can be associated with paid campaigns using UTM parameters, GCLIDs, and other advertising identifiers. For Salesforce and HubSpot Activities without native campaign associations, custom source-system attributes may be required. ### How does RevSure determine Campaign Engagement Dates? RevSure derives Campaign Engagement Dates from timestamped engagement records in connected systems. These can include: - Salesforce Campaign Member records - Marketo Program Member activities - Advertising clicks - Website visits recorded by RevSure's first-party tracking script - Website activities from marketing automation platforms For campaign matching based on UTM fields, historical field tracking may need to be enabled to preserve engagement timestamps. ### How does RevSure prevent duplicate Campaigns when advertising platforms sync data into CRMs? RevSure supports configurable campaign deduplication to identify overlapping Campaigns across connected systems. When consistent naming conventions or shared identifiers exist, RevSure can use them to match Campaign records. When direct identifiers are unavailable, RevSure can evaluate campaign names, engagement information, and other available attributes using probabilistic matching. This reduces the risk of duplicate Campaign records affecting attribution and reporting. ### How does RevSure handle duplicate Campaigns with different names across systems? RevSure uses the available source identifiers, naming conventions, and engagement associations to identify potentially equivalent Campaigns. When direct matching is not possible, its entity resolution framework can compare campaign names and other characteristics to identify likely matches. The resulting associations depend on the configured matching rules and available source data. ### Can RevSure attribute Campaign performance using custom source-system fields? Yes. RevSure supports custom attribution based on Campaign information captured in CRM or marketing automation fields. For example, when a Salesforce Lead, Contact, or Opportunity contains a custom Campaign attribution field, RevSure can ingest and use that information in reporting. Custom dimensions and campaign classifications can also be configured through business mappings. ### Can RevSure perform attribution by marketing asset type? Yes. RevSure can support attribution by asset types such as whitepapers, e-books, webinars, videos, banners, and other campaign assets. Assets can be associated with Campaigns, Ads, or Ad Groups when relevant source data is available. RevSure can also derive campaign attributes using UTM parameters and configurable business mapping rules. These attributes can then be used as reporting dimensions for campaign and attribution analysis. ### Can RevSure attribute marketing and sales activities to different teams? Yes. RevSure supports team-level analysis using campaign ownership and other configured GTM dimensions. Campaign owners can be mapped to teams and used as dimensions in Demand Generation Effectiveness reporting. RevSure also supports configurable rules that classify Activities into synthetic Campaigns, allowing sales and marketing activities to participate in attribution analysis. ### How does RevSure support Account-level attribution? RevSure ingests account-level engagements from connected platforms such as LinkedIn, 6sense, and Demandbase. These engagements can be combined with interactions from Leads and Contacts associated with the same Account. This enables account-level analysis of campaign influence and funnel progression. ### How does LinkedIn View-Through Attribution work? LinkedIn View-Through Attribution allows RevSure to consider advertising exposure even when an individual does not click an ad. LinkedIn provides impression information at the company or Account level. RevSure uses this account-level exposure information as an engagement signal in supported attribution analyses. Because the impression data is account-level, it does not necessarily identify the specific individual who viewed an advertisement. ## Website Visitor Tracking and Identity Resolution ### How does RevSure capture website visitor activity? RevSure uses a first-party JavaScript tracking script installed on your website to capture visitor interactions. Depending on the implementation, these interactions can include page visits, form submissions, and other website activities. RevSure also integrates with marketing automation platforms such as Marketo, HubSpot, and Pardot to retrieve website activities associated with known Leads and Contacts. The collected data supports visitor analytics, buyer journey analysis, and marketing attribution. ### How does RevSure connect anonymous website visitors to known Leads and Contacts? RevSure uses identifiers captured through website interactions and connected source systems to associate anonymous visitors with known records. For example, when a visitor submits a form containing an email address, RevSure can match that identifier with an existing Lead or Contact in the CRM. This enables RevSure to connect earlier website interactions with the identified Lead or Contact when matching information is available. ### How does RevSure identify anonymous visitors across devices or browsers? RevSure supports configurable visitor fingerprinting based on available network, device, and browser attributes. The supported matching levels include: | Level | Attributes | | --- | --- | | Level 0 | IP address, location, time zone, and ISP | | Level 1 | Level 0 attributes plus device and operating system information | | Level 2 | Level 1 attributes plus browser information | These methods can help associate visitor interactions when direct identifiers are unavailable. The available tracking and matching methods depend on the selected configuration and applicable consent requirements. ### Can RevSure enrich anonymous visitor information? Yes. RevSure supports enrichment through connected data providers such as 6sense, Apollo, People Data Labs, and 5x5Coop. Depending on provider availability and coverage, enrichment can add company-level attributes such as company name, industry, revenue, region, country, and city. RevSure can also support person-level identification through applicable enrichment providers, including RB2B and 5x5Coop, where supported. The information available depends on the provider, subscription, integration configuration, and matching coverage. ### How does RevSure identify the source of anonymous website traffic? RevSure evaluates multiple data points captured during website visits to classify traffic sources. These include: - Referrer URLs and domains - UTM source and medium values - GCLIDs and other advertising identifiers - Campaign tracking parameters - Additional available URL attributes RevSure uses configurable classification rules to identify channels such as Paid Search, Paid Social, Organic Search, Direct Traffic, Referral, and other sources. ### How does RevSure derive Referrer Campaigns? RevSure uses referring domain information captured through its first-party tracking script and marketing automation website activities. These domains can be modeled as Campaigns within RevSure. Referrer Campaigns can then be analyzed in Demand Generation Effectiveness reporting to understand their contribution to Lead and Opportunity generation. ### Does RevSure support webpage-level analytics? Yes. RevSure can track selected webpages and evaluate their effectiveness in generating traffic and contributing to funnel progression. Relevant webpages can also be modeled as Campaigns, enabling them to participate in attribution analysis within Demand Generation Effectiveness. ### How is RevSure website analytics different from Google Analytics? RevSure connects website engagement with broader revenue lifecycle information from CRM, advertising, marketing automation, and sales engagement systems. This allows teams to trace interactions beyond website activity to downstream business outcomes such as Opportunity creation, pipeline progression, and bookings. RevSure also combines advertising performance, attribution, and available enrichment information in a unified reporting environment. ### Why might visitor counts differ between RevSure and GA4? Visitor counts may differ because RevSure and GA4 can use different tracking configurations, identity definitions, bot filtering rules, consent handling, and reporting methodologies. GA4 metrics such as Active Users are not necessarily equivalent to raw visitor or interaction counts in RevSure. When comparing the platforms, ensure that the reporting period, visitor metric, filtering rules, and consent configurations are aligned. ### How does RevSure track website visitors when cookies or JavaScript are blocked? RevSure supports first-party tracking, which can reduce reliance on third-party cookies. The tracking script can also be configured to load through a customer-controlled domain using a CNAME configuration. For environments where client-side JavaScript cannot execute, RevSure supports server-side event tracking through customer-implemented backend integrations. RevSure also provides configurable identity resolution mechanisms using available identifiers and attributes. Tracking coverage depends on the implementation, available data, browser restrictions, and applicable privacy requirements. ### How does RevSure handle website tracking consent? RevSure supports consent-aware website tracking configurations. Customer consent preferences can be passed to the tracking SDK, allowing tracking behavior to align with the organization's consent policies. The tracking implementation can also be configured to activate tracking after the required consent has been granted. Customers should configure consent behavior in accordance with their applicable legal requirements and privacy policies. ### Can RevSure work with Google Tag Manager Consent Mode? Yes. RevSure tracking can be configured alongside Google Tag Manager consent management. The `analytics_storage` category is commonly used for analytics-related tracking, although the appropriate configuration depends on your organization's consent policies. Consent gating should be configured and validated through the website's consent management implementation. ### Does RevSure use RudderStack for event collection? Yes. RevSure incorporates RudderStack as part of its event collection architecture. The RudderStack data plane is deployed within RevSure-managed private Google Cloud infrastructure. Event processing and storage are managed within the RevSure environment. ## Marketing Automation and Advertising Integrations ### How does RevSure import HubSpot Campaigns? HubSpot Campaign data ingestion can require a manual extraction process because the integration described does not support direct Campaign retrieval through the applicable public APIs. The process involves exporting Campaign information and associated influenced Contact lists from HubSpot. RevSure's Customer Success team can assist with Campaign identifier validation, data preparation, and mapping during onboarding. ### Can RevSure map HubSpot Campaign Types and Channels? Yes. RevSure can use available HubSpot fields and custom mappings to classify Campaigns. Campaign Type is not automatically mapped for HubSpot Campaigns in the described integration. Where appropriate custom attributes are available, they can be mapped to RevSure's Campaign Type dimension. HubSpot channel information from Contact records can also be ingested and used in reporting filters and breakdowns. ### How does RevSure attribute HubSpot engagements to advertising Campaigns? RevSure uses available HubSpot attribution fields, influenced Contact lists, website activities, and URL tracking parameters. These can include first-touch and last-touch converting Campaign fields, UTMs, and advertising identifiers. Where reliable advertising identifiers are available, RevSure can match website interactions with Campaigns from platforms such as Google Ads and LinkedIn Ads. ### How does RevSure associate online and offline event engagements? RevSure supports multiple methods for capturing event engagement: - Online registration and form submission activities. - Salesforce Campaign and Campaign Member records. - Other configured CRM objects and attributes. - Uploaded CSV or spreadsheet data. - Integrations with event management platforms through supported APIs or webhooks. These interactions can be combined with digital engagements to build more complete buyer journeys. ### How does RevSure track third-party advertising and engagement activity? RevSure integrates with advertising, ABM, CRM, and sales engagement platforms to ingest relevant interactions. Depending on the connected source, these can include Campaign data, impressions, clicks, account engagements, sales activities, and other interactions. RevSure uses shared identifiers, source-system relationships, and configured matching rules to associate these engagements with Leads, Contacts, Accounts, and Opportunities. ### How does RevSure classify Organic Search and Direct Traffic? RevSure uses configurable channel classification rules based on information such as referring domains, UTM values, and available advertising identifiers. Organic Search can be identified through recognized search engine referrers and related signals. Direct Traffic can be classified when applicable traffic signals meet configured direct-visit rules. Users can review relevant source attributes and buyer journey interactions to understand how traffic was classified. ### How does RevSure handle missing or incorrectly tagged UTM parameters? RevSure prioritizes reliable campaign identifiers when available. For example, advertising IDs captured through marketing automation website activities can be used to associate engagements with Campaigns. When direct identifiers are unavailable, RevSure can use UTM parameters and configurable matching rules. Custom mapping logic can help account for naming inconsistencies or incorrectly formatted campaign parameters. Attribution accuracy depends on the quality and completeness of the available tracking data. ## Attribution Models and Measurement ### How does First-Touch Attribution work? First-Touch Attribution assigns credit to the earliest qualifying Campaign engagement before the relevant conversion. For Leads and Contacts, the model evaluates engagement timestamps to identify the first touchpoint. For Opportunities, the first touchpoint depends on the configured association scope, such as Primary Contact, All Contacts, or Account Engagements. ### How does Last-Touch Attribution work? Last-Touch Attribution assigns credit to the most recent qualifying Campaign engagement before the relevant conversion. For Opportunities, the selected Contact or Account association methodology determines which touchpoints are considered. ### What is Last-Touch Converting Campaign Attribution? Last-Touch Converting Campaign Attribution identifies the final qualifying Campaign engagement before a Lead or Opportunity advances to a particular funnel stage. For example, a Lead may have different last-touch Campaigns for its transitions from Lead to MQL, MQL to SAL, and SAL to Pipeline. This differs from evaluating a single last-touch Campaign across the entire lifecycle. ### How does Any-Touch Attribution work? Any-Touch Attribution identifies all qualifying Campaign engagements associated with a Lead, Contact, Account, or Opportunity. Unlike fractional attribution models, influence-oriented Any-Touch views can credit multiple qualifying Campaigns with influence over the same conversion. As a result, attributed influence totals can overlap and should not automatically be interpreted as unique pipeline value. ### Which attribution models does RevSure support? RevSure supports multiple attribution methodologies, including: - First Touch and Last Touch - Any Touch and Influenced Attribution - Linear Attribution - U-Shaped and W-Shaped Attribution - J-Shaped and Inverse J-Shaped Attribution - AI / Markov Chain-based Attribution - Custom Attribution using available source-system data RevSure also supports Marketing Mix Modeling for broader marketing investment analysis. ### How does RevSure attribute engagement after Opportunity creation? RevSure supports stage-to-stage attribution and conversion analysis through Demand Generation Effectiveness and related attribution capabilities. These analyses help evaluate which Campaigns and channels influenced Opportunity progression, including movement toward Closed Won or Closed Lost outcomes. RevSure's AI-based models can also estimate the relative contribution of marketing engagements to funnel and pipeline stage conversions. ### How does RevSure measure LinkedIn Campaign impressions and influenced Accounts? RevSure ingests available impression and account engagement data directly from LinkedIn. Account information from LinkedIn is matched against Accounts in the connected CRM. Matched Accounts contribute to the associated influenced Account metrics. When an identifiable Account does not match an existing CRM Account, RevSure can create an Account entity internally for reporting and analysis. ### How does RevSure calculate projected pipeline value for Leads? RevSure estimates projected pipeline value using AI-generated Opportunity Amount Estimates and conversion probabilities. The platform analyzes historical Lead-to-Opportunity conversions and associated Opportunity values to estimate the potential value of new Leads. This estimated amount is multiplied by the Lead's predicted conversion probability. **Projected Lead Value = Estimated Opportunity Amount × Conversion Probability** The model uses historical patterns and available Lead attributes to produce these predictions. ## Reporting and Funnel Analytics ### Why might metrics differ between a standard table and a Trend view? Differences can occur because Trend views and standard tables apply time-period filters differently. Trend views automatically apply the selected time period across the relevant period-based calculations. In standard tables, applicable Period Filters may need to be aligned manually. To compare results accurately: - Verify that all relevant Period Filters use the same reporting period. - Confirm that cloned views preserve the underlying filter configuration. - Check that the same attribution model and reporting dimensions are selected. ### What is the difference between Cohort Intelligence and Attribution? Cohort Intelligence and Attribution answer different analytical questions. | Cohort Intelligence | Attribution | | --- | --- | | Measures how defined groups progress through funnel stages | Measures the contribution of engagements to conversion and revenue | | Tracks conversion, velocity, leakage, and regression | Evaluates Campaign influence and credit distribution | | Focuses on cohort progression over time | Focuses on touchpoint influence and attribution | Use Cohort Intelligence to understand how groups move through the funnel. Use Attribution to understand which marketing and sales interactions contributed to pipeline or revenue outcomes. ### Why might an engaged Contact not appear in Cohort Intelligence? Cohort Intelligence supports cohort analysis based on the Opportunity's Primary Contact or all Contacts associated with that Opportunity. An individual who engaged with the Account may not appear in the cohort if they are not associated with the Opportunity under the selected configuration. ### Does Cohort Intelligence support multi-touch pipeline attribution? No. Cohort Intelligence is designed for analyzing progression, conversion, velocity, and leakage. It does not distribute pipeline credit across multiple touchpoints. For multi-touch influence and revenue attribution, use the appropriate attribution capabilities in RevSure. ### Can RevSure analyze campaign impact on deal velocity? Yes. RevSure supports funnel and pipeline analytics that help compare conversion performance and stage velocity across Campaigns, channels, and engagement types. For example, teams can compare the sales cycles of Opportunities associated with a particular event against those without that engagement. These analyses help identify relationships between marketing activities and deal progression. ### Can RevSure analyze conversion journeys across channels and content types? Yes. RevSure's Journey and Attribution capabilities support analysis across marketing channels, Campaigns, offers, and assets. Users can evaluate engagement sequences, common conversion paths, campaign combinations, and time spent progressing through funnel stages. This helps identify successful journeys and potential conversion bottlenecks. ## Data Synchronization and Permissions ### Can RevSure write data back to Salesforce and data warehouses? Yes. RevSure supports configured write-back to Salesforce and supported data warehouses. Supported outputs can include attribution results, reporting metrics, and other calculated RevSure attributes. RevSure also supports precomputed reporting and attribution tables that can be made available through supported warehouse destinations, including BigQuery and Snowflake. These tables can be used by downstream BI tools without requiring the attribution calculations to be recreated. Synchronization schedules can be configured according to integration requirements. ### Can I change the Marketo API role to read-only without affecting RevSure? Yes. When Marketo write-back is not enabled, a read-only API role is sufficient for data ingestion into RevSure. You can remove the **Read-Write Person** permission while retaining the required read permissions, including Read-Only Person and access to Activities, Programs, Campaigns, and Program Members. If write-back is enabled, additional permissions may be required. ### Can I restrict Salesforce permissions to read-only except for fields used by RevSure write-back? Yes. RevSure can continue reading Salesforce data as long as the integration retains read access to the required objects and fields. For write-back, the necessary permissions depend on the configured mappings. - **Lead and Contact:** Require object-level Edit and field-level Edit permissions for mapped write-back fields. - **Account and Opportunity:** Can remain read-only when write-back is not enabled for those objects. - **Campaign Member:** Requires appropriate Create and Edit permissions if RevSure is configured to add or update Campaign Member records. Missing Edit permissions can cause the corresponding write-back operations to fail without affecting read synchronization. ### Can the LinkedIn Audience Upload permission be removed? Yes. The LinkedIn `rw_dmp_segments` permission is specifically used for Audience Upload functionality. It is not required for standard reporting or conversion uploads. If Audience Upload is not required, RevSure can update the requested integration scopes and arrange for the connection to be reauthorized. After successful reauthorization, reporting and conversion functionality can continue without requesting Audience Upload access. ### What happens to historical data when an integration is disconnected? Disconnecting an integration stops RevSure from ingesting new data from that source. Previously ingested data is not automatically deleted when the connection is revoked. For the Facebook Ads and Outreach integrations described, historical data is retained for up to five years under the applicable data retention policy. Customers can submit a data deletion request if historical data must be removed before the standard retention period. ## Data Enrichment Integrations ### What use cases are supported through the 6sense integration? RevSure supports three primary 6sense enrichment use cases: - IP enrichment - Account and Account scoring enrichment - Lead enrichment The available capabilities depend on the customer's 6sense subscription and enabled packages. ### What 6sense subscription is required? The documented package requirements are: | Use case | Required subscription | | --- | --- | | IP Enrichment | 6sense Platform or Sales Intelligence package | | Account Enrichment | 6sense Platform | | Account Scoring | 6sense Platform with the Advanced scoring package | | Lead Enrichment | Applicable enrichment add-on | Customers should confirm their package entitlements with 6sense. ### What is required to connect 6sense to RevSure? RevSure requires an appropriate 6sense API token to configure the connection. For IP enrichment, the API token can be obtained through the applicable 6sense configuration interface. Other use cases may require assistance from the customer's 6sense representative. IP enrichment also requires the RevSure first-party website tracking script to be configured. Campaign extraction may require additional access to the 6sense user interface. ### How does RevSure ingest 6sense Campaign data? The documented 6sense Campaign extraction workflow uses a manual export process. RevSure can coordinate periodic Campaign extraction and ingestion based on the customer's Campaign volume and reporting requirements. The extraction frequency and operational process are agreed during implementation. ## Historical Data and Change Tracking ### How does RevSure track historical changes to CRM attributes? RevSure supports three approaches for historical attribute tracking. **Source-system history:** RevSure ingests available historical field changes from source-system history objects, such as Salesforce Lead History, Contact History, Account History, and Opportunity Field History. **RevSure-generated history:** When source-system history is unavailable, RevSure can build change history by comparing attribute values across successive synchronizations. The synchronization timestamp is used as the detected change time. **Salesforce Change Data Capture (CDC):** RevSure can ingest configured Salesforce CDC events to capture changes to supported objects and attributes. History tracking is enabled for selected attributes based on reporting requirements and available configuration. ### Can RevSure retrieve field history from before onboarding? Yes, when the source system retains the relevant historical data and provides access to it. For example, Salesforce field history records may be ingested for periods preceding RevSure onboarding, provided that history tracking was enabled and the records remain available. When RevSure builds history from periodic synchronization instead, historical changes become available from the point that tracking is configured. ### Does historical attribute tracking require additional configuration? Yes. History tracking must be enabled for the required attributes in RevSure Data Hub. For source-system history ingestion, history tracking must also be enabled in the source platform where applicable. Because storing additional history can increase data volume and processing costs, tracking is typically configured for attributes relevant to lifecycle reporting, attribution, and analytics. ## Data Security and Privacy ### Does RevSure support consent-aware tracking for GDPR and EEA visitors? Yes. RevSure supports tracking configurations that use the consent preferences supplied by your website's consent management implementation. Tracking can be configured to begin only after the required consent has been granted. Customers are responsible for defining their consent policies and ensuring the website implementation complies with applicable privacy requirements. ### Does the RevSure website tracking script need to load before consent? The script can be configured to load before or after consent, depending on the selected implementation. For consent-gated tracking, events are configured to be collected only after the required consent is granted. The configuration should be tested with the website's consent management platform to ensure tracking behaves as intended. ### Where is website event collection data processed? RevSure uses a RudderStack-based event collection architecture deployed within RevSure-managed private Google Cloud infrastructure. The event collection data plane, processing, and storage are managed within the RevSure environment. ### Can customers request deletion of previously ingested data? Yes. Customers can submit a data deletion request to RevSure. Disconnecting a data source does not automatically delete previously ingested information. Deletion requests are handled according to the applicable data retention and deletion policies. --- *Note: Integration availability, historical data coverage, matching accuracy, permissions, and supported configurations depend on connected source systems and the customer's implementation. RevSure works with customers during onboarding to validate the required data mappings and configurations.* ## Related - [Derived Dimensions Descriptions](/derived-dimensions-descriptions.md) - [How RevSure connects leads and contacts to accounts and opportunities that are not in the CRM/MAP or not mapped properly?](/how-revsure-connects-leads-and-contacts-to-accounts-and-opportunities-that-are-not-in-the-crmmap-or-not-mapped-properly.md) - [Lead Entity - Dimensions](/lead-entity-dimensions.md)