Widget

The widget embeds the UNLOQ offer experience inside your website or app. Unlike the button — a single CTA that sends the user to a campaign page — the widget shows the reward and the ways to unlock it right in place: the user sees they can, say, generate a 50 PLN voucher, and chooses how (register with OKX, register with Superbet, or complete a registration plus a first transaction) without leaving your page.

One important boundary: verification happens in the UNLOQ app. Confirming that a user really completed an action with a brand requires the UNLOQ app, so the widget is not a fully in-page conversion — it is a structured hand-off that keeps your funnel intact.

The flow

1. Discovery in your environment. The widget shows the reward and the unlock options right where the user already is — event page, checkout, or post-purchase.
2. Hand-off to the UNLOQ app. Once the user picks an unlock option, the widget deep-links into the app on mobile, or shows a QR code on desktop. Users who already have the app land directly on their chosen unlock.
3. Verification in the app. The user completes the brand action and UNLOQ verifies it automatically — no codes, no screenshots.
4. Return to your flow. The unlock state is verified server-side, so when the user comes back, the widget reflects the unlocked reward and your page can react — for example applying the generated voucher to the order.

Why this still beats a plain redirect

• Your page never goes away. The widget opens as an overlay (or bottom sheet on mobile); the cart, the checkout, and the user's context all stay intact behind it.
• The choice happens before the hand-off. The user leaves for the app only after committing to a specific unlock, and the app opens straight into it — no re-orientation on a new page.
• Returning users skip ahead. Anyone who already has UNLOQ installed goes from your page to verification in one tap.
• Post-purchase placements are unaffected. After the order is complete, the hand-off costs you nothing — which makes post-purchase the natural first placement for the widget.

Try it

The card below is rendered by the preview build of widget.js, loaded exactly the way a partner site would load it:

Each unlock option sends the user straight to the UNLOQ app listing — the App Store on iOS/macOS, Google Play elsewhere. The campaign landing-page redirect — the redirect model — is what the button and banner use instead. The embedded app hand-off described above will replace the widget's internals without changing your integration snippet.

Integration

One script tag plus a container element:

<script
  src="https://unloq.now/widget.js"
  data-partner="your-partner-id"
  async
></script>

<div
  data-unloq-widget
  data-campaign="your-campaign"
  data-placement="checkout"
></div>

The widget renders the offer card in the container, isolated from your page styles via Shadow DOM. The reward and the unlock options are configured per campaign by UNLOQ, so you do not maintain them yourself.

Configuration

The widget emits an unloq:select event on the container when the user picks an unlock option (with the chosen option in event.detail.option), so you can hook it into your analytics.

What the full widget will add

• Overlay mode — the card expands into an in-page overlay (bottom sheet on mobile) with the unlock options and the app hand-off, instead of opening the campaign page
• Placement-aware offers — different reward framing on the event page vs. checkout
• Deeper theming — colors and typography adjustable to your design system
• Unlock-state callbacks — a JavaScript event when the user's reward is verified, so your flow can respond immediately

Interested?

We are prioritizing pilot partners whose funnels cannot tolerate redirects — ticketing, travel, and e-commerce platforms. Contact us to discuss your use case.