Event Queue & Consent Buffering

Conversion Bridge includes an Event Queue system that can optionally buffer analytics events before a visitor gives cookie consent. This helps improve accuracy in your conversion journeys by preserving early pageviews and actions that happen before consent is granted.

The Event Queue is designed to balance compliance with data quality. It does not process personal data before consent but may still technically use device storage.

Conversion Bridge leaves the decision up to you—enable it only if you’re comfortable with the minor legal gray area and need more complete analytics data.

What the Event Queue Does

Normally, Conversion Bridge does not record or send any analytics data until a visitor accepts cookiesA small piece of data stored in a user’s browser that helps websites remember user activity, preferences, or sessions across visits. or tracking via your consent banner.

With the Event Queue enabled, events such as pageviews or button clicks are temporarily stored in the visitor’s browser (using localStorage or in-memory storage). Once the visitor provides consent, these buffered events are processed and stored like normal—ensuring you don’t lose early parts of the session.

If consent is denied, all buffered events are deleted automatically.

This only works for Conversion Journey data, not for analytics or ad platform events

How It Works

1. Pre-consent:
   • Events are captured but not sent or saved in your site’s database.
   • Each event includes only anonymous, non-identifiable data (for example, the page URL and timestamp).
   • Data is kept only in the browser for a short time (48 hours).
2. Consent granted:
   • Conversion Bridge processes the buffered events.
   • They are then stored in the Conversion Bridge event database.
3. Consent denied or withdrawn:
   • The event buffer is immediately cleared and no data is stored or transmitted.

Why Use It

Without buffering, a user’s first few pageviews may be lost if they accept cookies later in their visit.

The Event Queue ensures that full visitor paths are recorded only after consent—resulting in more accurate attributionThe process of determining which channels, campaigns, or actions contributed to a conversion, helping you understand what influenced a visitor’s decision to take action. and conversion tracking.

This is especially useful for multi-page flows (for example, when a user browses products before consenting on the checkout page).

Privacy and Legal Consideration

The Event Queue feature introduces an element of risk and responsibility that site owners should understand:

• Under the EU ePrivacy Directive, any technology that stores or accesses information on a user’s device (including localStorage) may require consent unless it is “strictly necessary” for the service requested.
• Conversion Bridge uses this storage only to delay tracking until consent—not to track users before consent—but regulators may still view it as “device access.”
• You are responsible for ensuring that your use of the Event Queue aligns with your region’s privacy and cookie laws.
• Always disclose this behavior in your site’s Privacy Policy or Cookie Policy.

Recommended disclaimer text:

Conversion Bridge may temporarily store anonymous event data in your browser to preserve visit history until you provide tracking consent. No identifiable data is stored or transmitted before consent.

Choosing Your Risk Level

When a cookie banner integration is enabled, you’ll also see the option to enable the Event Queue.

• Unchecked (default): Strict compliance. No events are stored or tracked until consent is given.
• Checked: Early events are buffered locally for replay once consent is granted. Slightly higher privacy risk but improved analytics accuracy.

Each site owner can decide the appropriate balance between privacy strictness and data completeness.

Technical Details

• Events are stored in localStorage with a time-to-live (TTL) of 48 hours.
• The buffer clears automatically on consent denial or expiration.
• No cookies or identifiable session data are written until consent is provided.

Best Practices

• Update your privacy policy to explain how the buffer works.
• Keep the feature disabled if you serve users in regions with strict interpretations of ePrivacy or GDPR (such as France or Germany).