Step 1. Decide what you want to add to your audiences.


Step 2. Create triggers on GTM

Step 3. Create tags
Facebook:
<script>
fbq(‘trackCustom’, ‘remarketing-ecommerce’);
</script>
‘remarketing-ecommerce’ <- this part of the script will be the name of the audience on your Ads Manager

Google Ads:

How Company Identification works:
Leadoo collects information about visiting companies based on the public IP address of the company. So, the visiting person’s IP address is identified -> checked if it belongs to a company. If it does, the company is shown in the company listing. If it doesn’t, the information isn’t displayed – in either case, the IP address isn’t stored anywhere.
We have a partner company called Clearbit. So, the IP address information goes there and company information comes back from their database. Visitor profiles (if in use) are then linked to these companies either via IP or according to company information given in the bot (i.e., manually filled in the company name into the bot). If there are additional questions / need for clarification, I am happy to answer.
Where Clearbit gets its data:
In short, from public sources. Clearbit probably won’t tell where they get their data but almost all such actors (for example, Leadfeeder in Finland, Lead Forensics in UK) make use of several different sources; they have people who browse the web, they use public data sources, etc. However, it’s important to note that these are not personal data, but Clearbit, Leadfeeder etc. link the company’s IP space to the company’s name and its public information. For example, if Nokia Oy owns the IP space 109.68.1.1-109.68.1.45, then whenever a visitor comes from those addresses, it is recognized that the visitor works at Nokia.
Another important thing is, from Clearbit’s point of view they never know whose sites the visitor has even visited and from your site there never goes a call to Clearbit. All traffic to them goes through Leadoo. So, they don’t know whether the person working at Nokia has visited hs.fi, leadoo.com, or etuovi.fi. They don’t even know about the existence of any of these or any information about the person.
How Visitor Tracking works:
Personal data comes from the information people leave in the bot. Before that, we can “identify” the devices that have been used to visit the sites. These people are “unknown visitors” until they leave their contact details through the bot. Identification is done based on the etag left by the device and browser (works the same way as a cookie, but different technology). So how it works: A person comes to the site -> tracking is on if cookies are accepted -> x device is identified. -> person leaves the site -> an “unknown visitor” profile is created -> The person returns to the site the next day with the same device -> the same etag is recognized, meaning the person visiting with the same device is recognized -> the information from the previous day and new information are combined under the same profile -> person leaves their own information in the bot -> “Unknown visitor” becomes an identified person based on lead information.
Tracking Options:
There is 4 different tracking options you can set up on Leadoo’s control panel.
There is also on options to override user tracking options if you want to only track companies. In that case you would choose “Never track” and in Company tracking you’d choose “Always track”.
If you want to add Leadoo tracking to your cookie acceptance but your CMP isn’t TCFv2 compliant you have to use Custom Consent Handling
How Custom Consent Handling works:
So how this should work is that Leadoo loads two types of scripts in different ways depending on whether the user accepts statistical cookies or not. So if the user does not accept statistics, the bots will load, but the analytics script will not load. As a result of this loading, cookies etc load correctly automatically. Below is how to make this work like this:
Leadoo’s bots can be loaded directly onto the website. However, Leadoo’s tracking can be put behind cookie acceptance. This happens in the following way:
From Leadoo’s tracking settings, the option “never” is activated <- tracking doesn’t automatically start. By default, Leadoo’s settings are ‘always track’, but it can be changed from Leadoo’s control panel. At the same time, the following script is added to your CMP that overrides the “never” rule after cookie acceptance and Leadoo’s tracking starts to work:
if (!window.ldanalytics) window.ldanalytics = [];
window.ldanalytics.push(function(a) {
a.toggleTracking(true, false);
});
More information here: http://docs.leadoo.io/docs/analytics-tracking#custom-consent-handling
And here’s which category each cookie falls into: https://leadoo.com/help/does-leadoo-use-cookies/. But as mentioned, with the way above, they load correctly depending on cookie acceptance.
If you are currently using our livechat application and have noticed that the sound notifications are not working properly, we would like to clarify that this is not an issue with our application. Instead, it appears to be a browser-related problem.
To resolve this issue, we recommend following the instructions provided on thetroubleshooting sound issues in Chrome for Chromebook, Mac, Windows, and Ubuntu users. By following the steps outlined in the article, you can attempt to resolve the sound issue on your browser and ensure that you receive sound notifications for our livechat application.
1. Launch Chrome
2. Click on the three dots (or three horizontal lines) in the upper right-hand corner of the browser.
3. Go to the Settings
4. Now, under the Privacy and security tab, click on Site settings.
5. Find app.leadoo.com
6. Find “Notifications”, “Sound” and “Background sync”. Then set all of them to “Allow”
1. Open Firefox
2. Select settings -> Privacy & Security
3. Search for App.leadoo.com and allow notifications

If you are currently using our livechat application and have noticed that the sound notifications are not working properly, we would like to clarify that this is not an issue with our application. Instead, it appears to be a browser-related problem.
To resolve this issue, we recommend following the instructions provided on thetroubleshooting sound issues in Chrome for Chromebook, Mac, Windows, and Ubuntu users. By following the steps outlined in the article, you can attempt to resolve the sound issue on your browser and ensure that you receive sound notifications for our livechat application.







1. Open Firefox

2. Select settings -> Privacy & Security

3. Search for App.leadoo.com and allow notifications

You can change your Bot Icon and Bot nickname from individual bots settings.
Navigate to the bot you want to change the icon.
When you’re in the Conversion Kit and have found the bot you want to edit click Actions and select Settings
*You can use the search field to find specific bot by searching either the bot name or the bot id found on the embedding code

On the General tab you can see Bot Icon and Bot nickname next to each other.


You can use predefined bot icons or upload a photo from your files to use as your bot icon. Make sure that the photo you upload is a square (ie. 200px x 200px) and that the photo is .png .jpg. or .jpeg
You can also give the bot a nickname that will be visible on chatbots header. This name will be shown to anyone who starts a discussion with the bot.
Make sure to save any changes you make.
If you have any issues or need help you can contact [email protected]
On Lead settings you can define what information you want to include on your lead emails by selecting different sections.*
*Note, that all the information is not always available, in which case the field will not be included in the email even if selected.
You can also define Email subject and intro text. That way you can make the email subject more clearer to the lead recipients. Ie. You can add the email subject to contain name and company of the person that contacted you. You can use following macros:

If you use outlook we recommend you to use Outlook optimized email templates.
And if you have issues copying the message from lead emails select ”Include a plain .txt to lead info with the lead email”
