DASENTER Connections
All connectors

JavaScript SDK

Adds a small script tag to your website that quietly watches for real problems (a broken page, a JavaScript error, a failed checkout call) and reports them to Dasenter — no backend, no secret key, nothing to install.

What you need

  • A Dasenter account with at least one store already created
  • Access to your website's HTML (anywhere you can paste a <script> tag)
  • Five minutes — this one has no .env file and no server restart at all

Steps

  1. 1Log in to your Dasenter dashboard and pick the right store with the store switcher, if you have more than one.
  2. 2Click Integrations in the left-hand menu.
  3. 3Find the card labeled "Dasenter JavaScript SDK" and click Set Up JavaScript SDK.
  4. 4Dasenter shows you a real script tag, plus your store ID, a public key, and the API address to use — all four are already filled in with your real values, ready to copy.
  5. 5Copy that whole block and paste it into your website's HTML, just before the closing </body> tag, on every page you want watched.
  6. 6That's it for the basic setup — reload your website once in a real browser tab. Just loading the page with the script on it is what moves the integration from Pending to Connected.
  7. 7Everything from here is optional extra detail you can add if you want more than automatic monitoring — see the three examples below.

Real examples

Step 1 — the basic setup (paste this once; automatic monitoring starts immediately)

HTML

<script src="https://your-dasenter-host/sdk/nexora.js"></script>
<script>
  Dasenter.init({ storeId: "your_store_id", publicKey: "nx_public_xxxxx", apiBase: "http://localhost:3001" });
  // From this line on, JavaScript errors, failed fetch() calls, and
  // console.error() calls on this page are already being watched —
  // you don't have to write anything else for that part.
</script>

Optional — tell Dasenter who a real visitor is, once they log in or check out

JavaScript

Dasenter.identify({ email: "shopper@example.com" });
// Call this any time you already know who the visitor is — right after
// login or at checkout is usually the natural place.

Optional — report a problem yourself, in your own words, instead of waiting for a crash

JavaScript

Dasenter.captureMessage("Checkout button did nothing", "warning");
// Use this for a real problem your own code notices that isn't a
// JavaScript crash — for example, a button click that silently failed.

What success looks like

The integration card moves from Pending to Connected the moment a real page with the script on it actually loads in a browser and runs init().

Common mistake

The public key shown here is meant to be visible in your page's source — that's fine, it can only ever send one-way telemetry and can never create an order, write a product, or read anything back. Never confuse it with the separate, secret key from the Dasenter API tutorial, and never put that other key in a browser page.

Making Product Push/Pull supported

Push/Pull are never "supported" for this connector, by design — its public key can only ever send read-scope telemetry, so Dasenter refuses any write it's asked to make regardless of what the request claims. There is no setting that changes this. If your website needs its product catalog, the Frontend SDK is the connector built for that instead.

What data actually comes through

No currency, product, or order status data moves through this connector at all — it only ever reports monitoring signals (errors, performance, page views, an optional visitor identity), never business data of any kind.