RevSure Website Tracking Pixel - FAQs

Prev Next

1. How is the RevSure tracking script deployed, and what is its behavior?

The RevSure tracking script can be deployed through Google Tag Manager (GTM) using two independently configurable Custom HTML tags:

  • Page Tracking Tag: Loads the RevSure analytics SDK and records page-view events.

  • Form Identification Tag: Triggers when a visitor submits a marketing form (such as Marketo) and associates the session with the submitted email address.

Events are transmitted to RevSure's analytics endpoint:

https://analytics.revsure.cloud

In cookie-based implementations, the script uses first-party cookies on the customer's website domain.

Cookie

Purpose

rl_anonymous_id

Stores a pseudonymous visitor identifier.

rl_session

Maintains session information.

rl_page_init_referrer

Captures the initial referring source.

rl_user_id

Associates an identified visitor with their session after form submission.

In the described configuration, cookies have a one-year expiry and use SameSite=Lax.

Consent enforcement is managed through the customer's Consent Management Platform (CMP) and tag management configuration. RevSure also supports consent-aware and cookieless tracking with its updated SDK.

2. What is the purpose of the RevSure tracking script?

The RevSure tracking script is used for B2B marketing attribution and revenue analytics.

It helps businesses understand which marketing channels, campaigns, and website content contribute to visitor engagement, form submissions, pipeline generation, and revenue.

The script is not used for advertising delivery, retargeting, or building cross-site advertising audiences.

3. What data does the RevSure tracking script collect?

The script collects website engagement information and configured form-submission data.

Data category

Information collected

Page information

Page path, URL, title, and query string

Referral information

Referrer URL, referring domain, and initial session referrer

Marketing attribution

UTM campaign parameters

Browser information

User-agent string and browser locale

Device display information

Screen and browser window dimensions

Session information

Session ID and generated anonymous visitor ID

Event information

Page-view events and timestamps

Form submissions

Email address and submitted form field values, when enabled

Network information

Originating IP address recorded by the server

The exact information collected depends on the tracking configuration and enabled integrations.

4. What personal data does RevSure collect?

Depending on the implementation, RevSure may collect the following personal data:

Personal data

Collection behavior

IP address

Recorded by the RevSure data plane. Full IP addresses are stored in the described standard configuration.

Email address

Collected when a visitor submits a configured marketing form.

Form field values

Information submitted through the connected form, based on the integration configuration.

Pseudonymous visitor ID

Generated identifier stored in a first-party cookie.

Browser user-agent

Captured as part of website engagement information.

The tracking script does not collect precise GPS geolocation or perform device fingerprinting using canvas, WebGL, browser plugin enumeration, or battery information.

5. Who receives the data collected by the RevSure tracking script?

RevSure processes tracking information through its analytics infrastructure and supporting service providers.

Provider

Purpose

Data received

RevSure

Collection and processing of website analytics events

Website engagement events and configured form-submission data

Google Cloud

Infrastructure hosting and data warehousing

Customer data processed and stored within the hosted infrastructure

RudderStack (when applicable)

SDK delivery and configuration

Standard HTTP request metadata, including IP address and user-agent, for SDK and configuration requests; no collected analytics events or form contents

Collected analytics events are sent to the RevSure-operated endpoint:

https://analytics.revsure.cloud

RevSure also provides a RevSure-hosted version of the SDK, where both the tracking script and its configuration are served from RevSure endpoints, eliminating browser requests to RudderStack-operated infrastructure.

In the described deployment architecture, each customer's analytics data is stored in a dedicated BigQuery dataset, without routing to advertising networks or data brokers.

6. What does RevSure do with the collected data? Is it used only for the customer or for RevSure's own purposes?

RevSure processes the collected data to provide marketing attribution and revenue analytics services to the customer.

The data is used to analyze website engagement, connect marketing touchpoints to leads and opportunities, and measure marketing contribution to pipeline and revenue.

RevSure does not use the collected website tracking data to:

  • Build cross-customer visitor profiles.

  • Operate or improve an advertising network.

  • Create advertising audiences for unrelated customers.

  • Target visitors across unrelated websites.

In the described architecture, customer data sources and warehouse destinations are isolated by customer, and collected events are not routed into shared cross-customer advertising datasets.

7. Is the RevSure tracking script used for targeted advertising across other websites?

No. RevSure's website tracking script is designed for first-party marketing attribution and analytics, not cross-site targeted advertising.

  • Tracking cookies are first-party and associated with the customer's website domain.

  • These cookies are not directly accessible from unrelated domains.

  • Cross-domain linking is not enabled automatically.

  • The script does not load advertising pixels or third-party advertising integrations as part of the described tracking implementation.

  • RevSure does not operate an advertising network or use visitor data to create cross-site advertising profiles.

Any separately configured advertising conversion writeback or activation integration is managed independently of the website tracking script.

8. Is separability an option?

Yes. RevSure supports separation of tracking functionality at multiple levels.

Functional separation

The page-tracking and form-identification tags can operate independently.

Customers can disable the form-identification tag to prevent collection of submitted email addresses and form field values through that tag while continuing page-view analytics.

Page analytics may still process IP addresses, browser information, and pseudonymous identifiers.

Data separation

Customer data is maintained in dedicated data sources and warehouse destinations in the described architecture, providing isolation between customer datasets.

Deployment separation

Customers can use their tag management platform to restrict tracking to selected domains, pages, or URL paths.

SDK hosting separation

Customers can choose a RevSure-hosted SDK instead of RudderStack-hosted script delivery and configuration.

9. Does RevSure support cookieless and consent-aware tracking?

Yes. RevSure's updated first-party tracking SDK supports cookieless operation and consent-aware tracking.

  • Before consent: The SDK can operate in a cookieless mode, subject to the customer's consent configuration and applicable requirements.

  • After consent: The SDK can transition to the configured consented tracking mode.

  • Consent withdrawal: The SDK can transition back to the configured non-consented mode.

  • IP truncation: RevSure can enable IP truncation at the data plane for visitors who have not granted consent.

Customers can integrate their Consent Management Platform (CMP) with RevSure's consent functionality to control tracking behavior based on visitor preferences.

These capabilities depend on the deployed SDK version and configuration and may require an implementation update.