(function () {
try {
// AQ-r2 (2026-06-09): respect the explicit-denial sentinel
// written by cookie-consent-harden.js writeATR() on any
// marketing-axis denial (payload.marketing === false; cycle-3 F1).
// Without this gate, the next page navigation re-creates
// gmx_first_touch from the current URL+referrer+utm_*+click_ids,
// silently undoing the reject-all deletion (sweep finding #1).
// The sentinel is cleared the moment the visitor grants
// marketing in the banner (analytics-only grant does NOT
// clear), restoring the writer path on the very next
// page load. Page-cache-safe: the sentinel is a
// browser-resident cookie checked in the inline script, so
// varnish/breeze-served HTML still hits this gate.
if (/(?:^|;\s*)gmx_consent_denied=1(?:;|$)/.test(document.cookie || '')) return;
var CLICK_IDS = ['gclid','fbclid','msclkid','ttclid','wbraid','gbraid','li_fat_id'];
var qs = new URLSearchParams(window.location.search);
var urlClickIdKey = null;
for (var i = 0; i < CLICK_IDS.length; i++) {
if (qs.get(CLICK_IDS[i])) { urlClickIdKey = CLICK_IDS[i]; break; }
}// Parse existing cookie.
var existing = null;
var match = document.cookie.match(/(?:^|;\s*)gmx_first_touch=([^;]+)/);
if (match) {
try { existing = JSON.parse(decodeURIComponent(match[1])); } catch (e) { existing = null; }
}// GWP-273 — referrer-enrichment branch.
// Keep existing unless either (a) URL carries a new click id
// the stored payload lacks (paid click is a higher-value
// signal and upgrades direct/organic), OR (b) the stored
// payload has empty referrer AND the current document.referrer
// is non-empty + external (Safari/ITP/policy-quirk catch:
// first-hit may have missed the referrer; later same-session
// page-loads can recover it).
var existingHasRef = !!(existing && existing.referrer && existing.referrer !== '');
var docRef = document.referrer || '';
var refHost = '';
if (docRef) {
try {
refHost = new URL(docRef).hostname.replace(/^www\./, '').toLowerCase();
} catch (e) { refHost = ''; }
}
var ownHost = (location.host || '').replace(/^www\./, '').toLowerCase();
var currentExternalRef = !!(refHost && refHost !== ownHost);
var canEnrichRef = !!existing && !existingHasRef && currentExternalRef;if (existing) {
if (!urlClickIdKey && !canEnrichRef) return;
if (urlClickIdKey && existing[urlClickIdKey] && !canEnrichRef) return;
}var utm_keys = [
'utm_source','utm_medium','utm_campaign','utm_content','utm_term',
'utm_adgroup','utm_matchtype','utm_network','utm_device','utm_placement'
];
// GWP-273 — merge-preserving base. When enriching an existing
// payload, retain its landing_url + ts + prior click ids /
// utms; only overlay referrer (and any click id appended below
// via the forEach). Branches with/without urlClickIdKey were
// collapsed — both produced the identical Object.assign — the
// click id is added uniformly later.
//
// GWP-273 design choice: "latest external referrer wins" —
// accepted edge case where a user opens a new external tab
// post-empty-first-touch and returns; low-volume, simple, no
// sentinel flag needed.
var data;
if (existing && canEnrichRef) {
data = Object.assign({}, existing, { referrer: docRef });
} else {
data = { landing_url: window.location.href, referrer: docRef, ts: Date.now() };
}
utm_keys.concat(CLICK_IDS).forEach(function (k) {
var v = qs.get(k);
if (v) data[k] = v;
});
// GWP-208 — carry Meta's first-party click-linker cookies (_fbc
// = fb.1.<ts>.<fbclid>, _fbp) into the captured payload so they
// ride the persistent gmx_first_touch cookie cross-page (LP X →
// LP Y) the same way the URL click-ids do. The CF7 hidden-field
// populator copies the whole payload verbatim, so fbc/fbp reach
// the lead even when the form lives on a page without ?fbclid.
var fbcMatch = document.cookie.match(/(?:^|;\s*)_fbc=([^;]+)/);
if (fbcMatch && fbcMatch[1]) data.fbc = decodeURIComponent(fbcMatch[1]);
var fbpMatch = document.cookie.match(/(?:^|;\s*)_fbp=([^;]+)/);
if (fbpMatch && fbpMatch[1]) data.fbp = decodeURIComponent(fbpMatch[1]);
var encoded = encodeURIComponent(JSON.stringify(data));
if (encoded.length > 3800) return;
var expires = new Date(Date.now() + 90 * 864e5).toUTCString(); // GWP-143 C1: match Google Ads 90-day attribution window
var secure = window.location.protocol === 'https:' ? '; Secure' : '';
document.cookie = 'gmx_first_touch=' + encoded + '; Path=/; Expires=' + expires + '; SameSite=Lax' + secure;
} catch (e) {}
})();
/* Meta Pixel base — inline in wp_head so Breeze Delay-All-JS does not defer it; fbevents.js is async-injected (optimizer-invisible). */
!function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};if(!f._fbq)f._fbq=n;
n.push=n;n.loaded=!0;n.version='2.0';n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window,document,'script',
'https://connect.facebook.net/en_US/fbevents.js');/* Symmetric with server GMX_Consent: revoke BEFORE init; cookies/sends held until grant. */
fbq('consent', 'revoke');
fbq('init', '1857131551802431');
fbq('track', 'PageView'); /* queued; flushed to Meta only after consent grant *//* Grant bridge — reads the SAME ATR marketing signal as GMX_Consent.applyConsent(). */
(function () {
function read(name){var m=document.cookie.match('(?:^|; )'+name.replace(/([.*+?^${}()|[\]\\])/g,'\\$1')+'=([^;]*)');return m?decodeURIComponent(m[1]):'';}
function marketingGranted(){
try {
var given = read('atr_cookie_notice_consent_given');
if (!given) return false; // undecided -> stay revoked
var c = JSON.parse(read('atr_cookie_notice_consent') || '{}');
return !!(c.marketing || c.ad_storage === 'granted');
} catch (e) { return false; } // NO-SILENT-OK: parse/read failure degrades gracefully to revoked (consent stays held; no marketing send) — not an error to report.
}
function apply(){ if (marketingGranted()) fbq('consent', 'grant'); }
apply();
document.addEventListener('click', function(ev){
if (ev.target && ev.target.closest && ev.target.closest('[class*="atr-cookie"], #atr-cookie-notice')) setTimeout(apply, 50);
}, true);
window.addEventListener('storage', apply);
})();
var breeze_prefetch = {"local_url":"https://gomixapp.com","ignore_remote_prefetch":"1","ignore_list":["/cart/","/checkout/","/my-account/","https://gomixapp.co.il/(.)/u05d4u05d8u05d5u05e4u05e1-u05e0u05e9u05dcu05d7-u05d1u05d4u05e6u05dcu05d7u05d4/","wp-admin","wp-login.php"]};
//# sourceURL=breeze-prefetch-js-extra
LED screen installation succeeds or fails long before the screen arrives on site. L.I.P – short for LED Installation Protocol – is the structured checklist we use to prepare a site for a safe, stable and precise installation: the exact power and data infrastructure, the right mounting or foundation, and the municipal permits. This guide is organized so you only read the installation track that applies to you.
What is L.I.P? LED Installation Protocol – a site-preparation protocol for LED screen installation that consolidates power, communication, structural and licensing requirements into one clear process, before the installation team is booked.
In short: what does LED screen installation preparation include?
Preparing a site for an LED screen covers four pillars: power (one single-phase 16A line per 4 m² of screen), communication (CAT7 cables sized to the screen pixel count, plus one spare), mounting or structural work matched to the screen weight (about 55 kg/m² outdoor, 26 kg/m² indoor), and municipal licensing. Each installation type – pole, roof, concrete wall or drywall – has its own preparation track.
Part A – Mandatory infrastructure for every installation
The first two pillars of the LED screen installation protocol apply to every screen, regardless of whether it ends up on a pole, a roof or a wall. When this infrastructure is ready in advance, installation day becomes fast, clean and free of surprises.
Power: how many lines do you need?
An LED screen draws power in proportion to its area and brightness. A safe planning rule of thumb: provide one single-phase 16A power line per 4 m² of screen. A screen of about 4 m² needs one line, about 8 m² needs two, and so on. This is a conservative planning figure – the exact draw depends on the model and brightness, so always confirm against the manufacturer spec sheet.
Leave the power conductors coiled in the wall, at a length of roughly half the screen width, and route them together with the data cables to a central point behind the screen, from which they are pulled into the communications cabinet.
Data: how many CAT7 cables to prepare?
An LED screen is made of hundreds of thousands of pixels, and a single network cable can only carry a limited number of them. The logic is simple: the bigger or denser the screen (smaller pixel pitch), the more cables you need. In practice you calculate the total pixel count, divide by a single cable capacity, and round up. On common control systems (for example NovaStar), one network cable carries up to about 650,000 pixels.
Power and data cables converge at the communications cabinet (controller, player and router)
Example: a 3×4 m screen at pixel pitch 3. Convert the dimensions to millimetres and divide by the pitch: width 3,000 mm ÷ 3 = 1,000 pixels; height 4,000 mm ÷ 3 ≈ 1,333 pixels. Total ≈ 1,333,000 pixels. Divide by a cable capacity (650,000) and you get about 2.05 – rounded up to 3 active cables. Add one spare cable from the control point, and you prepare 4 CAT7 cables in total.
The spare cable is not a luxury – it is a safety net. If a primary cable is damaged, the backup feeds the picture from the opposite side and the screen keeps running. Like the power lines, all data cables converge into a communications cabinet housing the controller and the media player. For remote content management you also need a router with a stable internet connection; content itself is managed through a cloud-based digital signage platform.
Recessing the screen in a drywall niche
If you want the screen flush-mounted inside a drywall niche for a clean architectural finish, plan the niche 2 cm larger than the screen in both width and height. That leaves a gap of about 1 cm around the entire perimeter – enough for ventilation, service access and small construction tolerances, without the frame looking cramped.
Part B – Installation tracks: choose yours
This is the practical heart of the LED screen installation protocol. You do not need to read every track – jump straight to the one that matches your screen. Two points first that apply to everyone:
Screen weight: for structural planning assume roughly 55 kg/m² for outdoor screens and 26 kg/m² for indoor screens. These are conservative planning weights including frame and mounting; the exact figure is in the model spec sheet.
Structural engineer approval: required whenever the screen is not anchored directly to a concrete wall or to properly reinforced drywall – which means always for pole and roof installations, and for any non-standard support structure.
Track 1: Pole installation (foundation and excavation)
A freestanding pole suits outdoor screens at a business entrance, in a parking lot or along a road. It is the most demanding track to prepare, because all the stability rests on the foundation in the ground.
A pole-mounted outdoor LED screen – stability starts at the foundation
Excavation permit: before breaking ground, obtain an excavation permit and verify there are no underground utilities (power, water, communications) at the spot.
Foundation casting: excavate and cast a concrete foundation with anchor bolts per the engineer design. The foundation is engineered for wind loads on the screen full area – the critical parameter for outdoor screens.
Erecting the pole: after the concrete cures, the pole and support frame are erected, and the power and data conduits are routed through them.
Engineer sign-off: mandatory. The engineer signs the foundation and pole design and takes responsibility for stability.
Track 2: Roof installation (structural frame)
A roof-mounted screen gives high exposure, but demands double care: stability against wind, and the integrity of the roof waterproofing.
Support frame: a steel structure distributes the screen weight and wind loads to the building load-bearing elements – not to the roof deck itself.
Protecting the waterproofing: anchor points are detailed so the roof waterproofing layer is not compromised – preventing future water damage.
Engineer sign-off: mandatory. The engineer designs the frame and its connection to the existing structure.
Track 3: Concrete wall (direct anchoring)
A concrete wall is the ideal surface for an LED screen: strong, stable and suitable for direct anchoring. It is also the simplest track to prepare.
Direct anchoring to concrete, or to drywall reinforced every 40 cm
Wall check: verify the wall is flat, plumb and strong enough to carry the screen weight. A crooked wall must be leveled before installation.
Anchoring: the screen is anchored directly to the concrete with appropriate anchors – no additional support structure needed.
Engineer: for direct anchoring into sound concrete an engineer approval is usually not required, unless the building or screen size is unusual.
Track 4: Drywall (reinforcement)
A standard drywall partition is not designed to carry an LED screen. Installation is possible – but only if the wall was built as reinforced drywall in advance.
Reinforcement: add metal reinforcement profiles every 40 cm, so anchors grip metal rather than plasterboard.
Plan ahead: reinforcement is integrated when the wall or frame is built – retrofitting it later is difficult and expensive.
Engineer sign-off: required, to confirm the reinforcement matches the planned screen weight.
Part C – Municipal licensing and permits
Licensing is an integral part of the LED screen installation protocol. In Israel, a screen facing the public space is considered signage and normally requires a municipal sign license before it goes live. Requirements vary by municipality, but these documents are almost always required for the initial permit:
Certified electrician certificate confirming a sound installation, including a residual-current device (relevant to any illuminated or electronic sign).
Property owner consent for the screen placement.
Excavation permit – where digging is needed for a pole foundation.
Structural engineer approval – for pole, roof or reinforced-drywall installations.
A rendering/drawing of the sign and its location, as required by the local bylaw.
Note that a sign license is usually annual and must be renewed. For the full legal picture, see our guide to digital signage licensing and fees in Israel. GoMixApp customers get guidance through the process – we make sure all the engineering and electrical paperwork is ready to submit.
Preparing for installation day
Crane/lift access: for high installations (pole, roof, tall facade) confirm a clear access route for a crane or lift in advance, including parking coordination or sidewalk closure with the municipality if needed.
Third-party insurance: make sure the installation team carries liability coverage for work at height and in public space.
Infrastructure ready: on installation day the power lines, data cables and communications cabinet must already be in place – that is the whole point of the LED screen installation protocol.
Frequently asked questions
How many power lines does an LED screen need?
As a safe planning rule, provide one single-phase 16A line per 4 square metres of screen. An 8 square-metre screen, for example, needs two lines. Final consumption depends on the model and brightness, so confirm against the manufacturer spec.
How many network cables does an LED screen need?
Calculate the screen total pixels (dimensions in mm divided by the pixel pitch), divide by a single cable capacity (about 650,000 pixels) and round up, then add one spare CAT7 cable. A 3×4 m screen at pitch 3 needs 4 cables in total.
When is a structural engineer required for LED screen installation?
Whenever the screen is not anchored directly to a concrete wall or properly reinforced drywall – that is, for every pole or roof installation and any non-standard support structure.
Do you need a municipal license for an LED screen?
Yes. In Israel, a screen facing the public space is considered signage and normally requires an annual municipal sign license, together with an electrician certificate, the property owner consent, and in some cases an excavation permit and an engineer approval.
How much does an LED screen weigh?
For structural planning assume about 55 kg per square metre for outdoor screens and about 26 kg per square metre for indoor screens. These are conservative planning weights; the exact figure is in the specific model spec sheet.
Summary: proper preparation = a perfect installation
The LED screen installation protocol exists so that the installation itself is the easiest step of the project. When the power (16A per 4 m²), the data cables (including a spare), the mounting or structure matched to the screen weight, and the municipal permits are all prepared in advance – you get a stable, safe screen ready for years of continuous operation. Every installation starts with planning, and every good plan starts with a protocol.
var atrCookieNoticeSettings = {"cookieName":"atr_cookie_notice_consent","decisionCookieName":"atr_cookie_notice_consent_given","expiryDays":"365","autoHideDelay":"0","enableDebug":"","siteName":"GoMixApp","isPrivacyPage":"","privacyPolicyUrl":"https://gomixapp.com/privacy-policy/","privacyNoteText":"\ud83d\udca1 You can read this page while deciding about cookies","mode":"simple"};
//# sourceURL=atr-cookie-notice-simple-js-extra
