Apps: Web Data Collection
- The first view of APSIS Web Data Collection is the dashboard.
- The dashboard visualizes recent user activities were you as an admin can view all changes that have been done and by which user.
- Extend recent user activities to cover all events by clicking on “See more”
What is a form interaction?
On websites, forms are all the fields where the visitor can type in or select information. For instance, search forms, newsletter subscription forms, login forms, registration forms etc.
How to define a form interaction?
Use the trigger “In-page interaction”. Click on it to access the widget.
Detect the "form" interaction by following these 3 steps:
1. When the on-site widget detects an area that is a form it will show an extra icon. Click the little icon on the far left of the grey selected area, this you will allow the widget to identify that an element is specifically a form.
2. The widget area will display “form” if this was successful.
3. Now select what type of interaction you are referring to by using the drop-down that appears in the widget. For the form, you usually want to select the "submit" interaction, for your rule to be triggered when the user submits the form.
When you want to put any restriction on your event, wire your event data to a Condition. In this case, to restrict your event to a particular page or site section, use the Event data in the "Page" category and wire it to your condition as done below.
1. Test in Dev-mode
Events are automatically deployed into your development mode when saving them. Use the “to dev” bookmarklet on your site to enter the development mode.
2. Use the Log widget
When in development mode the Log widget in the bottom right corner will give, you feedback on which events you trigger when browsing the site, to let you know if your event is working as expected.
How to test your changes before deploying them
APSIS is a powerful software that allows you to apply changes immediately on any site, regardless of code or CMS used, the only requirement being that the APSIS tag has been implemented on the website.
However, before you apply a change to your live website, you have the possibility to test it.
Testing in APSIS is very simple. You can work in the software and add a new event or edit existing ones, and test them immediately on your website. In dev mode, you are the only one seeing the changes: the changes are not yet deployed to live mode where all other visitors to the website would see them.
Working with the bookmarklets
To test your changes, you only must install 2 bookmarklets, by dragging them to the bookmarks bar in your browser:
Now you can go to your website, where APSIS Profile Cloud is installed, and click the bookmarklet Dev mode (Apsis). Your website will reload and will now display the changes that are in dev mode. You are the only one to see the changes, any other visitor to the website still see the live mode. You can click the bookmarklet Live mode (Apsis) to switch back to live mode yourself.
When you work in dev mode on your website, using the bookmarklets, a widget is placed in the bottom right corner that helps you verify if an event is effectively being triggered. The widget displays a log of all events that have recently been triggered, allowing you to see if the event you are verifying was effectively triggered when it should.
If you want to use a dynamic value in your event, use the "Value from page" building block in the Event data menu.
How to use "Value from page"?
Example: You want to identify all the visitors who search for "shoes" on your website's internal search.
1. Use the trigger "In page interaction", use the widget to select the search-button as your trigger, and choose to "click" as your interaction.
2. Use the condition "Value contains", and type in "shoes" as your value.
3. Use the event data "Value from page", and using the widget again, select the search field to define this as the element where the value is entered.
Now you have identified the segment of visitors who type "shoes" in your search field.
To create a new event, go to APSIS Web Data Collection app and click on the tab “Events”. Click on “Create new event definition”
- Name: Give the event a name
- ID: An ID is automatically generated (only for technical users). This ID is used to identify the event in the data structure.
- Category: Optional categorising of the events to maintain a good and understandable structure of the events
- Description: Optional description field to describe the event in order to keep track of all the events and their purpose.
- Add your event to your cloud profiles: Whether the event is to be stored in profile cloud or not. Some events (data) are created to be used and stored in the profiles such as product views, logins, purchases etc. Some events are created for other purposes and will not be useful to store in the profiles. Can, for example, be events that are part of a segment or used for web analytics purposes. Therefore, it is important to determine beforehand whether the created event will be stored or not in the profile.
- Click on create.
The event tab is where all the events are defined and created. All created events are listed.
- Enable and disable events: When an event is created, it is by default enabled and when a deploy is taking place the event will instantly go into production. If you want to keep an event but don’t want it to be deployed, simply disable it. It is recommended to disable events that are not ready for production as if any admin in your organization deploys, all enabled events will be deployed.
- Re-arrange order of the events: In some occasions, you need to make sure that one event is triggered before another. A normal case is an activation event triggered based on a segment that is triggered on the same page. To ensure that Innometrics understand the segment before the activation, it is preferred to trigger the segment before the activation.
A common use case is to trigger for example a newsletter sign-up promotion or a “chat with support” pop-up based on certain conditions. These pop up´s are often triggered on more than one defined page. By using more than one condition to define the pages is not sufficient as the conditions are separated by an “AND” logic and not “OR”. Hence Below event is incorrectly configured.
Create the same logic as above but with “Value matches regex” – building block.
Separate the urls by using a pipe character (|).
How to use the widget
When you are using the on-site widget to select an element, you will need to pay attention to some settings in the widget in order to get the specific data you are after.
If you select an element that requires an event, the "Select event" drop-down menu will appear. All the events are arranged in the recommended order for the selected element.
The default event is "click" and is the most common event that you will want to use.
One exception is when selecting a field element, where blur is more common. Blur specifies that the user has left the clicked field, which indicated that the field is filled out and will give you more accurate data results.
Events to choose from in the drop-down:
click - The event occurs when the user clicks on an element
dblclick - The event occurs when the user double-clicks on an element
keydown - The event occurs when the user is pressing a key
keyup - The event occurs when the user releases a key
mouseover - The event occurs when the pointer is moving while it is over an element
mouseout - The event occurs when a user moves the mouse pointer out of an element
mousedown - The event occurs when a user presses a mouse button over an element
mouseup - The event occurs when a user releases a mouse button over an element
mousewheel (scroll) - The event occurs when a document view is scrolled.
blur - The event occurs when a form element loses focus
change - The event occurs when the content of a form element, the selection, or the checked state have changed (for <input>, <select>, and <textarea>)
focus - The event occurs when an element gets focus (for <label>, <input>, <select>, textarea>, and <button>)
select - The event occurs when a user selects some text (for <input> and <textarea>)
All mentioned events are HTML DOM Events.