Retrieve city, county and country for your visitors?
Visitor current City, Country and IP Address are only available if you set this to true. You can use them in segmentation conditions for onsite campaigns (interactions, polls, content).
Also you can display those values as dynamic variables for your onsite campaigns template (content).
Note, those values are only available to onsite campaigns and are not available for segmenting email recipients, because they might change according to device used by the visitor.
Listen to input fields and identify email addresses.
This option works like a stalker who waits for user to enter an email address into any input fields on the website, and generated a login event, so we can identify users.
You have the option to limit listening on some input fields only, based on css selectors.
Also if you want you can set a source attribute for all these email, so you can trigger some specific emails or use them later in segmentation. For example in the image below:
- we only listen for inputs fields with the class .newsletterinput or #email ID
- site gets added as source for these emails
Generate referer events?
Your visitors come to your website from other sources. When such sources are identified (either using UTM params), or through the referrer available by the browser, we can generate an event for the user in order to be available in segmentation.
Include our CSS (used for animations)
All our interactions use our own CSS file for animations.
Stop event tracking for the following IP’s. (Needs Visitor info enabled)
Event tracking will be disabled for IP addresses you input here. Visitor Info needs to be enabled in order to identify IP address
For ecommerce platforms we have built integrations modules.
Sometimes the selectors that trigger addtocart, addtowishlist events use other HTML classes and ID’s, so you can change them to match the ones from your website. Read more here.
Custom JS for each page load
A few considerations:
- document.write is not permitted and will be replaced from the code
- code evaluation will happen at the end of our loader init method, very late in the process but before:
- request for visitor info (IP, city and so on)
- reading DataLayer variables
- managing time difference between client & server;