Privacy

This website, jacknat.com, is operated by JackNat Consulting, LLC, the business named in the site footer. This page describes the consultation and meeting forms, the visit fields stored with them, and Google Ads measurement. It matches the pages and scripts currently published here.

Contact page

The form on the Contact page opens an email draft in your mail app. It is not submitted to this website and is not stored by the site host. Enterprise ERP inquiries are addressed to erp@jacknat.com. Residential Smart Living messages, including homeowner consultations and builder partnerships, are addressed to smart.living@jacknat.com.

Forms on this site

Two forms are submitted to the site host, Netlify, which stores the entry so we can reply:

• Smart Living consultation (homeowner-consultation) on Smart Living.
• Builder meeting request (builder-meeting) on Builder Partners.

We use what you submit to respond to that request. Both forms are meant to notify smart.living@jacknat.com only, and follow-up with you comes from that address. Enterprise ERP mail stays on erp@jacknat.com and is not a recipient of these two forms. A hidden subject line is included so the notification can be recognized. The form fields themselves are listed below.

Smart Living consultation

The consultation form asks for:

• Name, email, phone, and address or town
• What you are interested in (any of: home theater / media room, whole-home audio, outdoor TV and audio, lighting control, climate control, Wi-Fi and networking, cameras and security readiness, support for an existing system, or not sure yet)
• Timeline
• Notes
• How did you hear about us? (Google search, online ad, social media, friend or family referral, builder / designer / realtor referral, Homearama, or other)

Builder meeting

The builder meeting form asks for:

• Name, company, role, email, and phone
• Homes per year
• Typical price range or home size
• Notes (upcoming projects, timing, or questions)
• How did you hear about us? (Google search, online ad, LinkedIn, referral from another builder or trade partner, Homearama, industry event or association, JackNat reached out, or other)

Visit fields stored with each submission

On the first page of a visit, the site reads these values from the page address when they are present, and leaves them blank when they are not:

• utm_source
• utm_medium
• utm_campaign
• utm_term
• utm_content
• gclid (the Google Ads click identifier, when the ad click added one)
• landing_page (the first page entered, including its full query string, without the form contents)
• form_page (the page that submitted the form, such as /smart-living/ or /builder-partners/)

landing_page is the first page address, including the query string, and is not replaced. utm_source, utm_medium, utm_campaign, utm_term, utm_content, and gclid are taken from that original tagged arrival and are not replaced by a later ad click. form_page is the address of the page where the form was submitted. These values are kept in sessionStorage and localStorage under the key jacknat_lead_attribution for 90 days, written into the form when the page loads and again just before it is sent, and submitted with your "How did you hear about us?" answer. landing_page is saved even when the address has no campaign parameters.

After the site host accepts a form, the browser stores a pending token for that submission. The thank-you page can send one advertising conversion for that token. The token is marked completed, and removed from the pending entry, only after the advertising tag reports that it fired. If the tag does not report back, the token stays pending and a later visit can try again. The same token is sent with the event so a repeat is not counted as a second conversion. Once it is completed, a reload or a return to the thank-you page does not send it again. If advertising measurement is not configured, the token stays pending and no advertising tag is requested.

Spam checks

Each form includes a field that is not shown on the page. Submissions that fill it in are rejected. Netlify also runs its own spam filter on submissions. Entries it flags are kept out of the verified submissions list.

Google Ads

Every page loads a small script that looks for a Google Ads ID in the site configuration. When a real ID is set, that script loads Google's tag (gtag.js) once on the page. While the ID is still unset, the tag is not requested and no data is sent to Google.

When the tag is active, Google may set its own cookies to measure ad clicks. The consultation thank-you page (/smart-living/thank-you/) can send one conversion event to Google Ads after the consultation form is accepted. That event says a consultation form was submitted. It does not include your name, email, phone, address, notes, or the other form fields. Opening that page directly does not send the event. After the tag has reported the event, reloading the page or coming back to it does not send it again.

The builder thank-you page does not send the consultation conversion. It can send its own conversion event after a builder meeting request, and only when a separate builder conversion label is configured. No conversion value or currency is sent. Hashed-email enhanced conversions are not enabled.

The gclid stored with the form is there so a later follow-up can be matched back to the ad click. That matching is not done automatically by this website beyond storing the value on the form submission.

Questions

Questions about a Smart Living consultation or a builder meeting: smart.living@jacknat.com. Questions about enterprise ERP consulting: erp@jacknat.com. Phone, address, and hours are on the Contact page.