RevSure Historical Web Data Ingestion & MTA Data Requirements

  • Published on Sep 11, 2026
  • 2 minute(s) read
Prev Next

Summary
RevSure can ingest historical web activity as a one-time bootstrap and combine it with new web activity captured going forward. The most important requirement is having enough identity and timestamp information to associate each historical web touch with the correct person, account, and journey.

1. Overview

Many organizations have historical web and campaign activity distributed across marketing automation platforms, CRM systems, data warehouses, data lakes, or other internal systems. RevSure can use these existing sources to bootstrap historical journey data for Multi-Touch Attribution (MTA), rather than limiting analysis to activity collected only after implementation.

Once the initial historical dataset is loaded and mapped, newly captured web activity can continue flowing into RevSure. Historical and new activity can then be analyzed together as part of the same customer journey and attribution model.

2. Historical Data Sources

Historical web and campaign activity can typically be sourced from systems where this data is already available, including:

  • Marketing automation platforms such as Marketo or HubSpot

  • CRM activity or custom objects

  • Data warehouses or data lakes

  • Existing web analytics or event repositories

  • Other internal systems that retain person-level or session-level web activity

For the initial ingestion, the most useful export includes the following categories of data:

Data Category

Recommended Fields

Purpose

Person / Contact Identifiers

Email, CRM Lead ID, Contact ID, MAP ID, or another stable person identifier

Used for identity resolution and person-level journey mapping

Web Activity

Page URL, landing page, page view, form submission, event/action type

Represents the web touch or engagement

Timestamp

Event date and time, ideally with timezone

Places each touch correctly within the customer journey

Acquisition Context

UTM source, medium, campaign, content, term, referrer/referral site

Supports campaign and channel attribution

Campaign / Ad Context

Campaign ID, ad ID, click ID, source system identifiers where available

Helps connect web activity back to paid and owned campaigns

Custom Parameters

Relevant custom dimensions or parameters captured by the source system

Provides additional context for segmentation, mapping, or analysis

4. Identity and Person Mapping

The key requirement for historical web ingestion is the ability to resolve a web activity to a known person. Ideally, each record includes one or more stable identifiers such as email address, CRM Lead/Contact ID, or a marketing automation platform ID.

When sufficient identity information is available, RevSure can associate those web interactions to the appropriate person and, through the broader RevSure data model, connect them to the relevant account and opportunity journey where applicable.

5. Historical + New Web Data

Yes. Historical web data can sit alongside new web activity captured after implementation. The intended pattern is:

1. Historical bootstrap: Export existing web activity from available systems and perform a one-time ingestion into RevSure.

2. Mapping and validation: Map identifiers, timestamps, web properties, campaign context, and custom fields into the RevSure data model.

3. Ongoing collection: Capture new web activity going forward using the RevSure First-Party SDK.

4. Unified analysis: Analyze historical and newly captured touches together in customer journeys and MTA.

6. Data Quality Considerations

The quality of historical attribution will depend on the completeness and consistency of the source data. The most important factors are:

  • Reliable person/contact identifiers

  • Accurate event timestamps and timezone handling

  • Consistent page, UTM, and referrer values

  • Sufficient campaign/ad identifiers to map activity back to marketing efforts

  • A clear distinction between anonymous activity and activity tied to a known person

The best next step is to share a sample export or schema of the historical web data. RevSure can review the available fields and confirm the recommended mapping, identity-resolution approach, and ingestion format before the full historical export is prepared.

Expected outcome: a continuous view of the customer journey that combines historical web touches with new web activity, enabling MTA analysis across the full available period.