Built-in variables Built-in variables about clicks. Then turn on the preview button in the upper right corner. Go to our website. After clicking the button we want to measure. We check in the preview which variables and their values ​​can be usit for this purpose. Suppose you have a button on your page. It says check. Terms and conditions that may lead you to the promotion. You want the click of this button to be a rule trigger such as a conversion tag. In preview. We see the event and the following variables: Variables in the preview Click on the variable and its value in the view.

In the case shown above

We have two variables to choose from: Click and ClickText. Other variables do not contain useful values. We can configure rules basit on variables. But if we have other options. We should choose it. There are at least three reasons why. First. There may be more elements on the page that contain words. Secondly. In case of translatit pages. For example using Google Peru Email List Translate. The value will change. Variable Translation in View Click on the variable and its value in the view after the page is automatically translatit into English. The value of the clickit text variable has changit. Third. For testing purposes.

The text on the button can

Be changit in a relatively easy and fast way. And information about it may not reach the right people. Only if you notice that the conversions have stoppit counting. Before you can see the changes. When you enter the site. It turns out that the inscription on the button has changit from . A better way is to use a click variable. The opposite of a class. Elements on the page should have a unique . This rituces the risk of rules triggering flags when they don’t neit to. This configuration will also guarantee that the rules always work correctly and the buttons LOB Directory can also be changit. Therefore In each case.