Overview
Digioh is an on-site lead capture and conversion optimization platform used by e-commerce brands and publishers. The platform enables merchants to display targeted lightboxes, page takeovers, sidebar widgets, and embedded forms based on behavioral triggers — exit intent, scroll depth, time on page, URL targeting, cart value, and referral source. Captured leads (email addresses, phone numbers for SMS) are forwarded to connected email marketing platforms (Klaviyo, Mailchimp, HubSpot, Attentive) and CRM systems.
Digioh competes with tools like Privy, Justuno, and OptiMonk in the email/SMS pop-up and lead capture space. It is widely deployed on Shopify and Magento stores.
What This Script Does
Digioh's script (www.lightboxcdn.com/vendor/digioh.js or client-specific CDN variants) deploys as a persistent behavioral layer:
Behavioral trigger evaluation: On every page load, the Digioh script evaluates configured trigger rules against the current visitor's behavior — time elapsed on page, scroll percentage reached, mouse movement toward the browser chrome (exit intent detection), number of pages visited in the session, cart contents, and URL patterns. When trigger conditions are met, the appropriate offer is displayed.
Overlay and widget injection: The script injects DOM elements for lightboxes, slide-in widgets, banner bars, full-page takeovers, and embedded forms. The injected HTML renders the offer creative, form fields, and CTA buttons. These overlays intercept the visitor's attention and promote lead capture or discount offers.
Visitor tracking and frequency management: Digioh sets cookies to track which offers a visitor has seen, whether they dismissed or converted on each offer, and how many pages they have visited. This prevents the same visitor from being shown the same pop-up repeatedly and enables sequential offer sequences. Cookie names vary by implementation but typically include digioh_ prefixed identifiers. These cookies persist beyond the session (commonly 30–90 days).
Form submission and lead capture: When a visitor submits a form (email address, phone number, name), the script captures the submitted data and triggers configured integrations — sending the contact to Klaviyo, Mailchimp, Attentive, or other connected platforms via Digioh's server-side webhooks. The collected email or phone number initiates the visitor into marketing automation sequences.
A/B testing: Digioh supports offer variant testing, randomizing which version of a pop-up or form a visitor sees. The assigned variant is stored in cookies for consistency across the visit.
Behavioral analytics: Impression counts, dismiss rates, conversion rates, and form submission data are tracked per offer variant and reported in Digioh's analytics dashboard.
Consent & Compliance
Digioh has a mixed consent profile:
- GDPR / ePrivacy: The persistent cookies Digioh sets for frequency management and visitor identification require prior opt-in consent under the ePrivacy Directive — these are not strictly necessary for the core website function. The behavioral trigger evaluation (tracking scroll depth, time on page, exit intent) constitutes behavioral profiling. Under GDPR, the legitimate interests basis is arguable for basic frequency capping but weaker for behavioral profiling tied to marketing outreach.
- Lead data collection: Email addresses and phone numbers collected through Digioh forms are personal data under GDPR. The legal basis for processing is typically consent (the visitor's form submission). The merchant must ensure Digioh's DPA terms are in place and that the integration with downstream platforms (Klaviyo, etc.) is disclosed in their privacy policy.
- CCPA: Email addresses and phone numbers collected through Digioh are personal information under CCPA. Collection for marketing purposes must be disclosed.
- Static form display vs. behavioral targeting: If Digioh is configured purely as a static embedded form with no behavioral triggers, frequency cookies, or cross-session tracking, it may qualify as a functional tool. Default Digioh deployments include behavioral targeting features that require consent.
Should You Block This Without Consent?
Conditional. Digioh's default deployment includes behavioral tracking cookies and trigger-based targeting that require consent under ePrivacy and GDPR. If configured in a static, non-tracking mode without persistent cookies or behavioral rules, it may qualify as functional. For standard deployments with exit intent, scroll triggers, and frequency management cookies, block until consent is obtained.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
lightboxcdn.comMarketingFrequently Asked Questions
Does Digioh require visitor consent before loading?
Yes for standard deployments. Digioh's default configuration sets persistent behavioral tracking cookies for frequency management, evaluates exit intent and scroll-depth triggers, and routes captured leads to email platforms — all requiring consent under ePrivacy and GDPR.
What does the Digioh script do on a website?
Digioh evaluates behavioral triggers — exit intent, scroll depth, time on page, cart value — to display targeted lightboxes and lead capture forms. Persistent cookies track which offers a visitor has seen, prevent duplicate prompts, and record A/B test variant assignments.
How does ConsentStack handle Digioh?
ConsentStack blocks Digioh until marketing consent is granted. Since Digioh sets persistent tracking cookies and performs behavioral profiling for lead capture and A/B testing, ConsentStack requires explicit opt-in consent before allowing the script to activate.
Related Vendors
Manage consent for Digioh
ConsentStack automatically detects and manages Digioh trackers so your site stays compliant with global privacy regulations.