Apptics SDK playground

Drives the build in this install against a test app. Local build
SDK
not started
Storage
none yet
API host
—
App
not registered
Device
not registered
Session
none
Queued
0 events, 0 errors
Tracking
—
Transport
0 keepalive · 0 xhr

App

Paste the config from the Apptics console as JSON. It needs base_url, auth_key, app_domain and appversion (the earlier serviceUrl, zak, identifier, base_domain and token work too); any other init() key is passed through. It stays in this browser.

The SDK calls app/addversion with these values first; its answer supplies aaid and the portal and project ids.

Event

Events are stored first. Nothing leaves the browser until you send.

Screen

The SDK records a screen for each navigation by itself, unless the config has "track_screen": false. These navigate the way a router does, on #/ routes so a reload still works:

API call

With this on, the SDK records the page's own requests without AppticsApi.startTrackApi() being called. Its own calls are never recorded. Set it before Start SDK; the checkbox also switches it at runtime. The two rules go to AppticsApi.configure(new AppticsApi.ApiTrackingBuilder().allowRegex(…).ignoreRegex(…)) on Start, each tried on the request's URL without its query; an ignore always wins.

Sends an actual fetch to the url above so the wrappers can catch it. Cross-origin calls usually fail, which is still a recorded item — response code 0, the browser's reason as the message.

Error

Heatmap

Records where you click and how far you scroll. Clicks are stored as they happen; scrolling is coalesced into one record per gesture. Click the dead zone a few times fast to see a rage click. Records go out with the rest of the stored data.

Dead zone (does nothing)

User

Registers the user and sends it straight away.

Remote config

Parameters the console publishes, resolved against this device. The SDK stores the rule set, so values are readable with no network on the next visit; a fetch only brings anything when the console has published since.

Last fetch never · — parameters

No parameters yet.

fetchValues([names]) answers with those names, null for one the console doesn't have; with no names, every parameter. Conditions are tried in the console's all_condition order: the first that matches gives the value, else the parameter's default. A custom condition matches when one of the values set for its name is listed. Resolved here, in the browser.

Push notification

The SDK registers this browser on its own when the console has push on (getsdkconfig module 16 and its wms block), then connects to WMS. Messages arrive while the page is open, and each shows as a browser notification once you allow them. Unregister holds across visits until Register. For action buttons and the image carousel, the SDK uses this site's /apptics-pn-sw.js by itself (a one-line worker importing the Apptics CDN copy).

Registered — · notifications — · 0 clicks

No notification clicks yet.

Remote logger

The SDK's own diagnostics: when it drops something, it reports that to log/add tagged with the module. These buttons make it drop something on purpose.

Lines are sent about a second after they happen, and on tab close. A refused line is retried up to five times.

Feedback log and diagnostics

Recorded now, sent with the next feedback submission as feedbacklog.txt and dyninfo.txt.

Send and control

Sends engagement, errors and heatmap records. Stored data is also sent every 30 seconds, when the network comes back, and when the page is hidden.

Open feedback works before Start — the form is markup. Sending one needs a running SDK, since the submission carries the device ids.

Debug mode sends engagement, exception and log to their debug/ twins, whose answers carry a request id and a link to the server's logs. Those show up on the request lines below. It switches itself off after an hour with nothing tracked.

Click tracking

Elements carrying apeventaction are tracked with no code of your own.

Activity

0