Your site. A script. Some answers.

Create an account, verify your email, and add a domain in your dashboard. Copy that site’s script into your website. Each site has its own public key.

1. Add the tracker

Place your installation snippet before the closing </head> tag, or add it as a custom HTML tag in your tag manager. The example below waits for your consent manager before collecting anything.

<script async src="https://bleap.it/b.js"
  data-site="YOUR_SITE_KEY"></script>

After the script has loaded and collection is allowed:

window.bleap?.consent(true);

// If the visitor withdraws consent:
window.bleap?.consent(false);

If your consent manager controls when the script is loaded, add data-consent="granted" to the tag after consent. The tracker respects Global Privacy Control and Do Not Track even when this attribute is present. Check your site’s applicable requirements before collecting analytics.

2. Visit the website

Use the exact domain you registered. The www version is also accepted. Other subdomains need their own site entry. Allow collection, browse a few pages, and wait about 10 seconds. Your dashboard updates every 15 seconds.

An accepted event changes the installation status. A short visit may appear as uncertain until there is enough interaction evidence. The first visitor gets the same assessment rules as everyone else.

3. Track meaningful outcomes

Pageviews, clicks, scrolls, and basic input interactions are collected automatically. For outcomes such as an add-to-cart, search, or completed order, send a named conversion event.

window.bleap?.track('add_to_cart');
window.bleap?.track('purchase', {
  value: 49.00,
  currency: 'USD'
});

Use stable event names such as purchase. Never put names, emails, order IDs, search text, or other personal information into event names. Values are optional. Do not send payment details.

Single-page apps and content security policy

The tracker observes changes to the browser path, including history navigation in single-page apps. Query-only and fragment-only changes are ignored. It removes queries and fragments before sending paths. Add https://bleap.it to your website’s script-src and connect-src directives if you use a content security policy.

What you will see

Observed sessions, behavior segments, interactions, conversion events, and a timeline for each session. AI and automation estimates are separate and experimental. The methodology page explains how to interpret them.

Why no events are appearing

• Confirm the tag uses the right site key and the page hostname matches the configured domain.
• Check that the script loaded, collection was allowed, and the site is not paused.
• A browser privacy signal, blocker, or your content security policy can prevent collection.
• Check the browser’s network panel for requests to /api/collect/init and /api/collect/events. A 403 means the origin or site is not allowed. A 429 means a collection limit was reached.

Evaluation limits

Each workspace can add five sites. Each site accepts up to 100,000 new sessions and 1,000,000 events per calendar month, with short-term rate limits. Session details expire after your chosen 7, 14, or 30 days. CSV exports include at most 10,000 recent sessions.

Evaluate for free. If you want to use Bleap commercially, talk to us about your traffic, workflows, and requirements.