ISOBUS solutions

ISOBUS operational concepts

After long years of experience in the crop care sector the intuitive handling concept of the HORSCH Leeb technology has been optimised, extended and is now successively introduced in the seed drill sector.
The innovative handling concept facilitates the adjustment, handling and monitoring of the machine for the farmer. To meet the individual requirements of the machine operators on handling, the terminal interface can be configured freely.
By means of the software a fully diagnoseable platform was created that can control an almost unlimited number of sections and components.

VariableRate

ISOBUS VariableRate allows for a site-specific application of seed and fertiliser. Thus, with an appropriate application card for every section within a field the optimum quantity of fertiliser and seed can be applied.

Advantages of VariableRate

Saving of seed and fertiliser as only the necessary quantity is applied
Homogeneous emergence with an optimum number of grains/m²
Simple and quick documentation – The different application rates are documented automatically. – Uncomplicated transmission to the acreage index
Reduced stress for the driver – Fields are drilled or fertilised automatically with the optimum application rate
Protection of the environment – Only the necessary amount of fertiliser is applied

Name	Purpose	Lifetime	Type	Provider
CookieConsent	Saves your consent to using cookies.	1 year	HTML	Website
PHPSessID	Retains the user's states for all page requests.	3 months	HTTP	php
fe_typo_user	This cookie is set by TYPO3 for the unmistakable identification of a user. It offers the user better user guidance	1 session	HTTP	TYPO3
be_typo_user	Used to identify a backend session when a backend user logs into the TYPO3 backend or frontend.	1 session	HTTP	TYPO3
mtm_cookie_consent	Saves your consent to use matomo tracking.	1 session	HTTP	TYPO3

Name	Purpose	Lifetime	Type	Provider
personalization_id	Marketing Used to determine the number of visitors accessing the website via Twitter advertising content and can be used for targeted advertising.	2 years	HTTP	Google Tag Manager / Twitter
ANID	Marketing Used to play out advertisements.	10 years		Google
_fbc	Marketing / Tracking Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.	3 months		Google Tag Manager / Facebook
datr	Marketing / Tracking Identify the web browser used to connect to Facebook, regardless of the logged-in user. This cookie plays a key role in Facebook's security and integrity features.	2 years		Google Tag Manager / Facebook
fr	Marketing / Tracking Provides information to Facebook to associate functionality of Social Plugin. Send information to Facebook regardless if you are a member or you have logged on the social network.	3 months	HTML	Google Tag Manager / Facebook
sb	Marketing / Tracking Provides information to Facebook to associate functionality of Social Plugin. Send information to Facebook regardless if you are a member or you have logged on the social network.	3 months	HTML	Google Tag Manager / Facebook
_fbp	Marketing / Tracking Used by Facebook to display a range of advertising products, for example real-time bids from third party advertisers.	7 days	Pixel	Google Tag Manager / Facebook
_gcl_au	Marketing / Tracking Used by Google AdSense to experience the efficiency of advertising on websites that use their services.	1 day	HTML	Google Tag Manager / Google Ad
RUL	Marketing / Tracking Used by DoubleClick to determine whether website advertisement has been properly displayed	1 year		Google DoubleClick
IDE	Marketing / Tracking Contains a randomly generated user ID. Using this ID, Google can recognise the user across different websites and display personalised advertising.	1 year		Google DoubleClick
__adroll_fpc	Marketing / Tracking Used to identify the visitor across visits and devices. This allows the website to present the visitor with relevant advertisement	1 session	HTTP	Adroll
NID	Marketing / Tracking Google cookies store information about user settings and information for Google Services.	6 months		Google Ads Optimazation
__Secure-3PAPISID	Marketing / Functional Used by for targeting purposes to profile the interests of the website visitor and display relevant and personalised Google advertising.	2 years		Google
__Secure-3PSID	Marketing / Functional Used by Google for targeting purposes to profile the interests of the website visitor and display relevant and personalised Google advertising.	2 years		Google
__Secure-3PSIDCC	Marketing / Functional Used by YouTube / Google for targeting purposes to profile the interests of the website visitor and display relevant and personalised Google advertising.	1 year		YouTube / Google
CONSENT	Functional Store cookie settings.	10 years		Google / YouTube
_ar_v4	Optimises ad display based on the user's movement combined and various advertiser bids for displaying user ads.	1 year	HTTP	Google DoubleClick
MYSAPSSO2	Used by for targeting purposes to profile the interests of the website visitor and display relevant and personalised Google advertising.	1 session		SAP

Name	Purpose	Lifetime	Type	Provider
_ga	Statistics This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier.	2 years	HTML	Google Analytics
_ga_XXXXXXXXXX	Statistics Contains a unique identifier used by Google Analytics 4 to determine that two distinct hits belong to the same user across browsing sessions.	2 years	HTML	Google Analytics
_gid	Statistics Functionality to count and track pageviews.	1 day	HTML	Google Analytics
1P_JAR	Statistics Used by Google to display personalised advertising on Google websites based on current search queries and previous interactions.	1 month		Google
_hjAbsoluteSessionInProgress	Statistics This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.	30 minutes		Hotjar
_hjFirstSeen	Statistics This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.	1 session		Hotjar
_hjTLDTest	Statistics When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.	1 session		Hotjar
_hjid	Statistics Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.	365 days		Hotjar
_hjIncludedInPageviewSample	Statistics This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.	30 minutes		Hotjar
_hjIncludedInSessionSample	Statistics This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.	30 minutes		Hotjar
_pk_id	Statistics Used to store a few details about the user such as the unique visitor ID.	13 months		Matomo
_pk_ses	Statistics Short lived cookie used to temporarily store data for the visit.	90 minutes		Matomo

Innovative and digital solutions

ISOBUS operational concepts

VariableRate