When following the steps after the registration you will be prompt to copy your Kodeless script and paste it in your website’s header, just before the </head> tag.

If you missed the instruction, please login to your Kodeless account and click the settings button on the top right of the screen.

Then click installation.

You will find your unique Kodeless script in there. From that point on it is recommended that any other tool you would like to integrate to should be added through Kodeless. More about integrations below.

Immediately after you sign-up to Kodeless you will be prompt to activate your integrations. An integration is a tool you would like to start sending customers data to.

Kodeless will automatically identify which tools are already implemented on your website. In most cases, for these tools there’s no action that you will be required to take.

If you want to add new tools you will need to enter a Tracking ID or Account ID.

Below are instructions of where to find the relevant ID in each tool:

Events, or data points, are user interactions that you would like to collect and send to different tools in order to store, analyze, or trigger certain actions within those tools.

Kodeless lets you implement different types of data points:

  • Click events
  • Pageview events
  • Forms events
  • Visibility events
  • Scroll events
  • Time-on-page events

Learn more about the different events types.

Some tools have their own specific settings for events. Click the tools to learn more:

Other relevant information:


Tracking ID – Outbrain:

This ID is found on your conversions section in your Outbrain account. To find it, click the ‘View outbrain pixel’:

Then, click ‘Copy to clipboard’:

Save the code in a note, and copy from the note that string on your OB_ADV_ID. It should look a bit like ‘00ffd632d95bda4ead3b6f8e274d1d3027‘.

Google Analytics:

Your Google Analytics ID can be found on your Admin section -> Property settings.

You can find your Google Ads tracking ID in the tracking code they asked you to implement.

Go to conversion list (you need to be logged in to Google Ads) and click any of the conversions you created.

Then open the ‘Tag setup’ section and ‘Install the tag yourself’.

Your ID is the string of numbers after ‘AW-’.

Note: The Google Ads tracking ID is different from your account ID

Facebook Pixel:

To find your Facebook pixel ID go here (you need to have an active advertiser account and be logged in), make sure you are on the right account, and the Pixel ID will be showing right there:

Bing ads:

Your Bing Ads tracking ID is found under ‘Conversion Tracking’ which is located on the sidebar in your Bing Ads account. If you haven’t done so, create your first UET tag. If you already have one, click ‘View UET tags page’:

Then click ‘View tag’ on the right side of the tags table. The ID will be there right after.


Your Snapchat tracking ID is found within the tracking code they asked you to implement:


For intercom you will need your App ID. YOu can find the App ID either in the URL of your Intercom account, or in the code the asked you to implement to:


Coming soon.


Hubspot’s tracking ID is a string of numbers that can be found in your Hubspot account’s settings page:


If this is your first time creating a LinkedIn pixel, first click conversion tracking from the top menu of your advertiser’s account:

Then follow the instructions and generate the code.

The ID you need here is your _linkedin_partner_id:

Then continue to create your first conversion. Keep its ID for later (the conversion ID), you’ll need it.


Project Management

A project enables managing different domains.

Environment Management

Environment Management enables to set and test events on staging environment first.
Important things to remember:

  • Events that are created in Staging environment will be live only once your hit Publish
  • Events that you create in Staging will also be available in ‘draft‘ mode in Production.
  • Hitting publish in Staging will not make those event live on Production

Edit Mode vs Preview Mode

By default when you start working with Kodeless, the editor will be on ‘Edit‘ mode, and more specifically ‘Click event‘ mode.

Preview Mode enables to navigate normally in the website. In this mode, it is still possible to create some types of events (pageview, scroll, and time based events).

Go To Page

You can also navigate using the ‘Go to page‘ button. Just type or paste the requested page’s URL in the appropriate place and navigate to a specific page.

Event List

Click on “Event List” icon opens the Event List table.

Event List, as the name suggests, lists all events that were implemented on the project with detailed information.

The table includes these columns:

  • Event Trigger” column – describe the event type (Click, Page View …).
  • Event Name” column – describe the event name that was set.
  • Page URL” column – describe the URL of the page that the event was set in.
  • “Across Site” column – mark the events that were set to “Across Site” implementation.
  • Status” column – show the event status. Draft (not live) or Active (live).
  • Action” column:
    • Edit icon – access event configuration. After any event changes, “Publish” has to be done.
    • Focus icon – scroll to the element position on the page and marked it.
    • Delete icon – delete the selected event.
  • Show current page events only” toggle – filter events that were set on the current URL.

Creating events (data points)

Event types — an explanation:

Click event:

This event will be sent every time a user clicks the element you selected

Page view event:

This event will be sent every time a user views this page

Scroll event:

This event will be sent every time a user scrolls this page to a certain depth.

Visibility event:

This event will be sent every time a user sees the element you selected. If the element is below the fold, it will not be considered an event.

Time on page event:

This event will be sent every time a user spends X time on this page

Form interaction started:

This event will be sent when a user started interacting with one of the form’s elements

Form submission:

This event will be sent every time a user tries to submit the form you selected.

When creating an event, a sidebar menu will show up on your screen. Let’s go over the different elements you will see there:

  • Custom Properties
    Used for defining names and values for non “standard” \ “reserved property name” integrations fields.
    Currently supported integrations by Kodeless: FB Pixel, intercom, Alooma.
  • Google Analytics
    Google Analytics” is a freemium web analytics service offered by Google that tracks and reports website traffic.
    If enabled, “Google Analytics” menu will appear in the event sidebar menu. Events data will be sent to to the account using the provided “Tracking ID”.
    • “Google Analytics” can be turned on and off using the toggle 
    • Additional available fields: “Category”, “Label” and “Value”. Those fields also support “Dynamic Value” setting.
    • by default, events affect the bounce rate. That is if a user lands on a page and an event is triggered, they are not a bounce (even if they don’t view any subsequent pages).
      In case that event should not be counted as interaction (like scroll event for example), non-interaction parameter so can be set by turning it on and off using the toggle 


  • Google Ads
    With Google Ads conversion tracking, you can see how effectively your ad clicks lead to valuable customer activity, such as website purchases, phone calls, app downloads, newsletter sign-ups, and more.
    If enabled, “Google Ads” menu will appear in the event sidebar menu. Events data will be sent to to the account using the provided “account’s conversion ID” (example: AW-123456789).


  • “Google Ads” can be turned on and off using the toggle 
  • Additional available fields:
    • Event ID – use the string provided in the tag setup step in Google ads conversion tool. Example:
    • Transaction ID – used for sending a “Transaction ID” value to Google Ads. It can be implemented with “Dynamic Value”.
    • Currency – used for sending a “Currency” value to Google Ads. It can be implemented with “Dynamic Value”.
    • Value – used for sending a “Value” to Google Ads. It can be implemented with “Dynamic Value”.
      In case “Don’t use a value” option was selected in Google Ads – Conversion action settings, the value will not be sent.


  • Facebook Pixel
    Helps you track conversions from Facebook ads, optimize ads based on collected data, build targeted audiences for future ads, and retarget qualified leads—people who have already taken some kind of action on your website.
    If enabled, “Facebook Pixel” menu will appear in the event sidebar menu. Events data will be sent to to the account using the provided Facebook Pixel ID”.


  • “Facebook Pixel” can be turned on and off using the toggle 
  • If “Standard FB event name” is selected”, “event name/action” will be set to “Facebook Pixel”,
    Else other predefined options can be selected “event name”.


  • Outbrain – event ID:

    If enabled, Outbrain will appear as an option on your ‘Create event’ sidebar.
    Use the event name you created in your Outbrain account. We recommend to use the same event name across all platforms/tools. It will dramatically simplify your analysis.

  • LinkedIn
    If enabled, LinkedIn will appear as an option on your ‘Create event’ sidebar.


Enter here the conversion ID as found in the code LinkedIn showed you when you created this conversion on your LinkedIn Advertiser’s account.


  • Implement across all site:

    We will recognize identical elements across the site and will attach this event on them. This is helpful when setting up events on cross-site menus for example.


White editor screen with endless loading

This is common for sites that are not secure and not using SSL certificates (load with HTTP, instead of HTTPS).
This is a browser default to not load un-secured sites in secured sites. There is a workaround though.
You will need to locate a black and white shield on the right side of your browser’s address bar (see on the left side of the image below).

Click it and then click ‘Load unsafe scripts’. Don’t worry though, the unsafe script is actually your website.

Assuming your code is installed properly, and you clicked ‘Code has been installed’ (see below), this should fix it.

We strongly recommend to purchase an SSL certificate and load your site in HTTPS for the safety and privacy of your users. Once you do that, don’t forget to update the URL of your site in your Kodeless project settings.