![]() ![]() You can use the form ID to specify which form to target Change on: form#new_user #user_email which will limit the event to just the new user sign up form and Change on: form#newsletter #user_email, which would limit the event to the newsletter form. For example, let’s say you have more than one email form on a page: one to sign up, another to subscribe to a newsletter, and both email fields are defined the same way. To combine selectors in a hierarchy, add a space between the tags, classes, and IDs. For example, Change on: input#user_email.email. You can combine tags, classes, and IDs in the same element by stringing them together. A form submission as Submit on: #new_user. ![]() A change in the password field as Change on: #user_password.email or Click on: which uses the attribute instead of the class. A click into the email field as Click on.Quotes are only required if the attribute contains a space. Attributes are contained in square brackets, as in or. IDs are prepended by a hash, as in #user_password.Īn attribute is the part of the markup that is not an id or class, such as placeholder or name. email.Īn id comes after the attribute id=. Classes are prepended by a period, for example. ![]() In line with standard CSS practices, in Heap, this is written as input.Ī class name comes after the attribute class=. To better understand what modifiers to apply to these events, we’ll walkthrough how common CSS elements should be written in Heap event definitions. Defining these pageviews as events allows you to dig into engagement with those pages to better understand user behavior. We provide a list of recommended pageview events to define based on the popularity of those pages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |