Here we are using the data-analytics-interaction-description custom HTML5 attribute, a single inline attribute to describe the whole interaction.
| Link | Link |
| Button tag | |
| Input button tag | |
| Input checkbox tag |
Here we are using the data-analytics-interaction-attribute-* custom HTML5 attribute, multiple inline attributes to describe various characteristics of the interaction.
| Link | Link |
| Button tag | |
| Input button tag | |
| Input checkbox tag |
Here we are using the data-analytics-interaction-key custom HTML5 attribute, a single inline attribute which acts as a lookup key. The data associated with that lookup key describes the interaction characteristics. This lookup data is stored in the kermit.js file.
| Link | Link |
| Button tag | |
| Input button tag | |
| Input checkbox tag |
Here we are using the data-analytics-interaction-key custom HTML5 attribute, a single inline attribute which acts as a lookup key. The data associated with that lookup key describes the interaction characteristics. This lookup data is stored in a single external file. You could use multiple external lookup files. The path to these files is listed inside the kermit.js file and Kermit loads these files for you.
| Link | Link |
| Button tag | |
| Input button tag | |
| Input checkbox tag |
Here let's have a look at what happens when we combine the data-analytics-interaction-description, data-analytics-interaction-attribute-* and the data-analytics-interaction-key custom HTML5 attribute. Each HTML5 element here only uses one the three HTML5 attributues at a time.
| Link | Link |
| Button tag | |
| Input button tag | |
| Input checkbox tag |
Let's see what happens when each element we want to track an interaction combines the first 4 methods.
Can the same
| Link | Link |
| Button tag | |
| Input button tag | |
| Input checkbox tag |
Here we are using the data-analytics-interaction-description custom HTML5 attribute, a single inline attribute to describe the whole interaction.
| Drop-down (single selection) | |
| Drop-down (multiple selection) | |
| Radio buttons |
Here we are using the data-analytics-interaction-attribute-* custom HTML5 attribute, multiple inline attributes to describe various characteristics of the interaction.
| Drop-down (single selection) | |
| Drop-down (multiple selection) | |
| Radio buttons |
Here we are using the data-analytics-interaction-key custom HTML5 attribute, a single inline attribute which acts as a lookup key. The data associated with that lookup key describes the interaction characteristics. This lookup data is stored in the kermit.js file.
| Drop-down (single selection) | |
| Drop-down (multiple selection) | |
| Radio buttons |
Here we are using the data-analytics-interaction-key custom HTML5 attribute, a single inline attribute which acts as a lookup key. The data associated with that lookup key describes the interaction characteristics. This lookup data is stored in a single external file. You could use multiple external lookup files. The path to these files is listed inside the kermit.js file and Kermit loads these files for you.
| Drop-down (single selection) | |
| Drop-down (multiple selection) | |
| Radio buttons |
Here let's have a look at what happens when we combine the data-analytics-interaction-description, data-analytics-interaction-attribute-* and the data-analytics-interaction-key custom HTML5 attribute. Each HTML5 element here only uses one the three HTML5 attributues at a time.
| Drop-down (single selection) | |
| Drop-down (multiple selection) | |
| Radio buttons |
Let's see what happens when each element we want to track an interaction combines the first 4 methods.
Can the same
| Drop-down (single selection) | |
| Drop-down (multiple selection) | |
| Radio buttons |
Here we are using the data-analytics-interaction-description custom HTML5 attribute, a single inline attribute to describe the whole interaction.
| Input text tag | |
| Textarea tag |
Here we are using the data-analytics-interaction-attribute-* custom HTML5 attribute, multiple inline attributes to describe various characteristics of the interaction.
| Input text tag | |
| Textarea tag |
Here we are using the data-analytics-interaction-key custom HTML5 attribute, a single inline attribute which acts as a lookup key. The data associated with that lookup key describes the interaction characteristics. This lookup data is stored in the kermit.js file.
| Input text tag | |
| Textarea tag |
Here we are using the data-analytics-interaction-key custom HTML5 attribute, a single inline attribute which acts as a lookup key. The data associated with that lookup key describes the interaction characteristics. This lookup data is stored in a single external file. You could use multiple external lookup files. The path to these files is listed inside the kermit.js file and Kermit loads these files for you.
| Input text tag | |
| Textarea tag |
Here let's have a look at what happens when we combine the data-analytics-interaction-description, data-analytics-interaction-attribute-* and the data-analytics-interaction-key custom HTML5 attribute. Each HTML5 element here only uses one the three HTML5 attributues at a time.
| Input text tag | |
| Textarea tag |
Let's see what happens when each element we want to track an interaction combines the first 4 methods.
data-analytics-interaction-description custom HTML5 attributedata-analytics-interaction-attribute-* attributesdata-analytics-interaction-key which will attach additional datadata-analytics-interaction-key which will load an external file and also attach additional data
Can the same data-analytics-interaction-key lookup key perform an internal lookup and fetch additional data from an external file? What happens if the same data point is declared in in the internal lookup data and the external data?
| Input text tag | |
| Textarea tag |