Pandus SDK documentation
Events without code and key events
Define events by selector, URL, form or visibility in the dashboard or by pointing in the extension. They count back in time. Mark key events as conversions.
Updated:
Events without code
Create an event in Analytics → Events → New event or pick the element in the browser extension. A rule is one of:
| Trigger | Example |
|---|---|
| A click on a selector | .checkout-button, optionally with a button text |
| A page view by URL rule | /thank-you* |
| A form is sent | the form on /contact |
| An element becomes visible | #newsletter-success |
They count back in time. The SDK stores clicks with their selectors and page views anyway, so a new event for “a click on the button” is computed from the data you already have, as Heap does. You see last month's numbers the moment you save it.
A rule cannot take the name of an event the SDK sends by itself. Names follow the same rules as in the JavaScript API.
Key events
Mark any event as a key event (a conversion) in Analytics → Events. By default purchase is a key event. Key events:
- appear in Conversions, with their rate and value;
- can be steps of Funnels and the start or end of Paths;
- get first-click and last-click attribution in Sources;
- raise the priority of a barrier that happens on the step before them in What to fix.
dataLayer import
If your site already pushes events to dataLayer for gtag or Google Tag Manager, switch on Import dataLayer in Analytics → Events. It is off by default, because many sites already send these events to GA4 and would count them twice.
The Pandus SDK and the scanner are automated checks, not a full audit, and not legal advice. The SDK changes nothing on your site and does not determine which visitors use assistive technology.