Page History
...
- CardioLog Client-Side API
- The SendEvent JavaScript Function
- The SetReferer JavaScript Function
- The SendGoal JavaScript Function
- Monitoring Internal E-Mail Campaigns Using the __referrer Parameter
- CardioLog Server-Side API
- Event Types
- Non-Browser (Mobile) Apps
- Data Export API
| Anchor | ||||
|---|---|---|---|---|
|
...
How many visitors arrived on my page through my email campaign? To see how many visitors arrived on your page through your email campaign, use the The CardioLog API report, and select the relevant page in the Website Item URL field.
| Anchor | ||||
|---|---|---|---|---|
|
By using the CardioLog Server-Side API, CardioLogAPI/Events.asmx web service, and the SendEvent method, you can send view, duration and search events, custom events, and track the URL of the referrer page.
...
1. Add the custom event type to the CardioLog database by executing the following query against the CardioLog database:
INSERT INTO tab_event_type(id,description)
...
VALUES(100, 'Item-Sold')
...
GO
ID - must be 100 or higher
Description - event type title
...
4. Create a custom report to display the number of items sold using the CardioLog SDK.
| Anchor | ||||
|---|---|---|---|---|
|
Mobile apps and other non-browser apps don't contain HTML pages, therefore, developers must determine when their apps should trigger page view requests. CardioLog Analytics can then aggregate this data in reports to display page views, unique visitors, session length, bounce rates, etc. This data gives insight into how users interact with the client app.
Developers can also track visitor actions that don't correspond directly to page views using other Event types. These user actions can include views of embedded videos, button clicks, downloads and more. This data can then be used to understand which features are most popular, and make informed decisions about the features that should be prioritized for further development.
| Anchor | ||||
|---|---|---|---|---|
|
In order to track visitor actions for non-browser apps, developers must send usage event objects to the CardioLogAgent web application through HTTP POST requests in JSON format. The JSON string must be embedded in the request body. The POST response is provided in JSON format as well.
...
- Replace [SharePoint WFE] with your SharePoint URL address
- The random param is used as a cache buster
| Anchor | ||||
|---|---|---|---|---|
|
With the Data Export API you can develop client applications to retreive data from the CardioLog reporting engine, and refine the results of the request using query parameters. It allows for more flexibility and customization than the CardioLog UI, giving you a great deal of freedom over how to display your reports, in terms of their design, filters and data content, and where the reports are displayed. It's also possible to brand your data with your organization's colors and logos to really take ownership of it.
...
- Select a Report.
- Select the report parameters - Date Range, Time Interval, Website Item, Users and Groups
- Check Generate Chart Image to create an image and set its Width and Height (pixels).
- Click Get URL to generate the report URL
- Click Generate Report to generate the report.
- Click Show Advanced Options and Get Report Preferences to modify report preferences.
| Anchor | ||||
|---|---|---|---|---|
|
The CardioLog report XML contains a preferences section (prefs node), and a data section (data node).
...