Our Products

· Product Update

Consent in the lead form — per channel, and separately for advertising

Marketing consent is now split by channel — email, SMS, WhatsApp — and passing identifiers to ad platforms has a consent of its own. Every tick is written to the consent log with the wording version.

Until now marketing consent was a single tick: “agrees to receive mailings”. The real question is more precise — which channel exactly the person agreed to, and in which wording. Consent in the “new lead” form is now itemised, and each item stands on its own.

Marketing consent is split by channel — email, SMS, WhatsApp. The form shows only the channels the office actually uses: that is an office setting, and a channel that is not in use simply does not appear. An office that only writes by email does not ask for SMS consent “just in case”, and a person does not tick a channel that will never reach them anyway.

Passing data to ad platforms has a separate consent of its own. The wording says plainly what is passed — technical identifiers only, that is a click or form identifier, or hash values of the phone and email — what for: to measure how the advertising performs, and what is not passed: the name and the text of the inquiry. The tick appears only in an office whose quality loop is running, and events go to the Meta and Google ad accounts only for the people who gave it.

No tick is pre-selected, and none of them blocks the form from being sent. There is no “select all” button, deliberately: consent collected without looking is not worth the record it leaves behind. Someone who ticked nothing is handled exactly like someone who ticked everything — the only difference is what may be sent to them afterwards.

Every tick that is set goes into the consent log as a separate record, together with the version of the wording that was shown at that moment. Months later the question “what exactly did this person agree to” is answered by a wording and a date, not by the memory of whoever spoke to them.

The form also gained an expandable block — “what data we collect”: which details are collected, what for, and what happens if they are not provided. This is the notice required by the privacy protection law; there is nothing to tick in it — it opens for whoever wants to read it and does not make the form longer for everyone else.

We set the channels when the office is connected, as we do with the logo and the colour. A screen where the office changes them itself does not exist yet; it comes later.

← Back to all updates

Release Details

Published
26.08.2026
Status
Live in all offices

Want to see this on your office or enterprise inquiry flow?

Leave your details and we will get back to you by the next business day to schedule a live office demo or an enterprise architecture review (30–500+ seats, SLA & CISO).

Prefer to reach out directly?

050-577-0731 · WhatsApp · support@lidin.co.il

Request type
Please enter your name so we know how to address you.
To schedule your live demo or engineering callPlease enter a valid phone number, e.g. 050-5770731.
Please enter an email address with @, e.g. name@company.co.il.
Please enter the name of your company, organisation, or office.

In this form you provide your name, phone number, email address, and company or office name. Providing these details is voluntary and not required by law (Amendment 13, § 11). The details are used solely to contact you regarding your request. They are held by IsraSky and never sold or shared with third parties. You may write to privacy@lidin.co.il at any time to review, correct, or delete your data.

We respond to every website request by the next business day.