Best Google Ads Conversion Tracking for Solar Installers

The best Google Ads conversion tracking for solar installers separates a real, serviceable solar opportunity from a page view, a generic savings question, a financing enquiry, a job-seeker call, an existing-customer request, or a property that the installer cannot serve. It measures calls, service area, property and roof context, residential or commercial intent, system type, battery interest, site assessments, proposals, contracts, consent, stable lead IDs, and approved downstream value without treating a form submission as a qualified roof, a guaranteed system, an approved loan, a promised incentive, or realized revenue.

Solar installers often sell several different journeys. A homeowner may request a residential rooftop consultation, a business may need a commercial design, a property owner may ask about a ground-mount project, and an existing customer may need monitoring, warranty, or service support. Battery storage, electrical upgrades, financing, utility or interconnection questions, roof condition, permitting, site access, and local serviceability can change what happens after the first contact. The account should preserve those distinctions rather than optimize every interaction as though it were the same installation.

Google’s web conversion setup guidance, primary and secondary conversion guidance, and Google tag guidance provide the platform foundation. The installer defines what counts as a supported enquiry, connected call, site assessment, proposal, accepted project, completed installation, or approved later value. This article is measurement guidance, not solar-design, electrical, roofing, permitting, tax, incentive, financing, legal, or safety advice. Project claims and customer-facing promises still require the installer’s qualified review and the applicable authority or utility requirements.

Define the solar-installation outcome first

Start with the business outcome the account is supposed to find. It might be a serviceable solar enquiry, a connected call, a consultation request, a site assessment booked, a design accepted, a proposal sent, a contract signed, a deposit received, an installation scheduled, a project completed, a battery add-on accepted, a referral, or approved later value. These are different states with different evidence, timing, owners, and reporting roles.

Before creating a conversion action, write an event contract: the event’s meaning, truth condition, source system, service area, property or customer type, project category, consent condition, primary or secondary role, stable identifier, owner, test case, and rollback. A landing-page view, button click, chat start, or form submission proves an interaction. The CRM, call platform, scheduler, design tool, proposal system, contract record, project-management system, invoice, or approved offline record proves what happened in the sales and installation process.

Do not make every solar calculator, financing click, incentive article, battery comparison, phone click, or form start a primary conversion. Those signals can show demand and diagnose the funnel while remaining weak bidding signals. A job applicant, supplier, existing-customer service call, out-of-area homeowner, unsupported commercial project, duplicate contact, or request for a guaranteed savings figure may trigger a website event without being a new installation opportunity.

Separate residential, commercial, and service journeys

Map the journeys the installer actually supports: residential rooftop, residential battery, ground-mount, commercial rooftop, multi-site commercial, new construction, electrical upgrade, storage retrofit, monitoring or warranty support, referral, and any other real offering. Preserve residential or commercial context, homeowner or property-manager role, broad market, property or roof type, system category, battery interest, urgency category, project size band where approved, and serviceability when those fields affect routing or qualification.

A homeowner asking for a site assessment is not the same opportunity as a business requesting a multi-site design. A battery-only enquiry may require different technical review from a new photovoltaic installation. An existing customer requesting warranty work belongs to a service path, not necessarily a new-acquisition path. Tracking can describe the journey without claiming that the roof is suitable, the property has a particular energy profile, the utility will approve interconnection, an incentive will apply, financing will be approved, or savings will reach a stated amount.

Use project states instead of a single lead number

Give each stage a clear definition. For example, a contact can be received, serviceability checked, qualified, scheduled for a site assessment, assessed, designed, proposed, accepted, contracted, scheduled, installed, inspected, commissioned, referred, cancelled, or marked as existing-customer support. The exact names should match the installer’s systems, but the progression must be explicit.

Write down what evidence changes one state to another. A site-assessment request is not a completed assessment. A proposal sent is not a signed contract. A signed contract is not an installed or commissioned system. A financing request is not financing approval. Keeping these distinctions visible protects both campaign decisions and the sales team’s understanding of lead quality.

What the best Google Ads conversion tracking for solar installers measures

Create an event map that names the system proving each stage and the identifier that connects it to the next stage. A useful map can look like this:

Event	Truth condition	Evidence to retain	Typical role
Solar service page view	The page renders for the requested topic	Topic and broad market context	Secondary
Calculator or battery tool use	An approved interaction completes	Tool version and non-sensitive selection context	Secondary
Phone click	A visitor activates a phone link	Number, page, timestamp, and source context	Secondary
Connected sales call	The phone provider records a real connection	Call and routing IDs	Secondary or candidate
Solar enquiry accepted	CRM accepts a request the installer can review	Lead ID, serviceability, and disposition	Primary candidate
Site assessment booked	Scheduler confirms an appointment	Appointment and lead IDs	Primary candidate
Proposal accepted	Approved sales record changes state	Proposal, project, and lead IDs	Downstream
Installation completed	Project system records the completed state	Project, completion, and lead IDs	Analysis or value

The installer may need every stage for internal reporting while sending only selected events to Google Ads. Decide which action may influence bidding, which action diagnoses demand, and which later state is reconciled from the CRM, call system, scheduler, design or proposal system, project-management system, invoice, or approved offline process. The best Google Ads conversion tracking settings article provides a broader account framework.

Define a qualified solar opportunity

Write the installer’s real qualification rule before choosing a primary conversion. It may require a supported market, a genuine request, a reachable contact, an eligible property or customer type, an offered system category, a project the team can review, consent where applicable, and no spam, duplicate, job-seeker, supplier, existing-customer, out-of-area, or unsupported-project classification. Use the company’s actual sales definition rather than inventing an exact roof pitch, system size, annual usage, property value, electricity bill, distance, or call-duration threshold.

Document residential and commercial requests, battery-only enquiries, new construction, ground-mount, multi-site projects, electrical upgrades, financing questions, incentive questions, monitoring requests, warranty calls, referrals, landlord or tenant roles, property-manager requests, utility or interconnection questions, out-of-area contacts, abandoned forms, missed calls, cancellations, and projects that never reach design or proposal. Pending, referred, rejected, cancelled, existing-customer, and not-yet-reviewed states should remain visible instead of being silently counted as qualified projects.

Track the question behind the contact

A solar lead’s first stated goal can matter to routing: reduce a bill, add battery backup, support a commercial facility, replace an existing system, evaluate a new building, understand a utility process, or request service after installation. Keep broad intent and approved project categories separate from the personal details or technical claims that do not belong in an advertising event. A battery interest field does not prove that storage is appropriate. A request for savings does not prove a savings amount. A financing click does not prove an approval.

Track enough context for the installer to decide what happened next: source, campaign or landing-page context, broad market, residential or commercial route, property or customer type, system or service category, battery interest, serviceability, disposition, lead ID, and consent state. Avoid turning every answer in a long qualification form into a separate conversion. The event should remain understandable to the person who reconciles it against the sales record months later.

Choose primary and secondary conversion roles

Use Google’s primary and secondary conversion guidance to separate actions that may support bidding from actions that mainly explain user behavior. A qualified solar enquiry, a genuine connected sales call, or a booked site assessment can be a primary candidate when the installer can define, identify, and reconcile it. Page views, calculator use, battery content engagement, financing-page clicks, phone clicks without a connection, and generic form starts can remain secondary.

The strongest primary state depends on the installer’s sales cycle. A local residential installer may be able to validate a serviceable enquiry quickly. A commercial installer may need a reviewed project brief or a scheduled assessment. An installer with many missed calls may need a connected, correctly routed call before it trusts a phone conversion. A business that sells through partners may need an accepted referral rather than a raw web form. The point is not to choose the latest possible event by instinct; it is to choose the earliest reliable state that represents genuine business value and can be measured consistently.

Match bidding signals to sales capacity

If the sales team can review and contact most accepted enquiries, a qualified-enquiry event may provide enough volume for reporting and optimization. If many enquiries are out of area, unsupported, duplicate, or service requests, a later reviewed state may better describe the traffic. If the later state is too sparse or delayed, keep it as a downstream reconciliation signal while using a clearly defined earlier state and watching quality separately.

Do not solve low conversion volume by promoting every weak interaction to primary. That can make campaigns appear busy while steering toward calculator curiosity, incentive searches, financing questions, job applications, existing-customer service, or unserviceable properties. Instead, inspect routing, landing-page promise, service-area clarity, form quality, call handling, sales response, and the relationship between the selected primary event and site assessments, proposals, contracts, and completed projects.

Keep the solar funnel visible

Do not hide job seekers, suppliers, electricians seeking work, existing customers, warranty or monitoring requests, renters without an appropriate project path, out-of-area properties, unsupported commercial scopes, duplicate forms, financing-only questions, generic incentive questions, or utility-process questions inside one new-installation count. Record disposition, service category, customer or property type, and the reason for rejection, referral, merge, or service routing.

A campaign can produce many contacts and few site assessments for several different reasons: the traffic may be broad, the service area may be unclear, the call queue may fail, the contact form may not capture enough routing context, the team may reject projects for valid reasons, or the site-assessment process may be slow. A conversion map that preserves those states gives the installer a path to investigate. A single “lead” number conceals the difference.

Use stable lead, call, and project identities

Retain a stable lead, call, appointment, site-assessment, design, proposal, contract, project, installation, service, referral, cancellation, and value ID in the authoritative systems. A visitor can submit a form twice, call after submitting, request both solar and battery information, reschedule an assessment, or return as an existing customer. The relationship among records matters more than creating a new conversion for every interaction.

The identity should survive handoffs between the website, phone provider, CRM, calendar or scheduler, design and proposal tools, project-management system, finance or invoice system, and any approved offline import. It does not need to expose the customer’s full project file to Google Ads. It needs to let the installer answer a narrower question: which measured interaction led to which business record, and what did that record become?

Deduplicate without losing project context

Test a phone click without a connected call, a missed call followed by a callback, a transferred call, a repeat caller, a duplicate form, a form retry, a battery enquiry that becomes a solar enquiry, a residential-to-commercial correction, an appointment reschedule, an existing-customer request, a partner referral, and a cancellation. Keep the record that represents the real qualified opportunity and document whether other events are merged, related, rejected, or retained as service interactions.

Do not use an exact timestamp, page view, browser session, roof photo, utility bill, telephone number, or email address as the only identity. Those values can be missing, repeated, corrected, or inappropriate for an advertising event. A stable source ID lets the installer reconcile the acquisition record with the sales and project systems while preserving the distinction between a new contact, a follow-up, a design, an assessment, an installation, and a service request.

Do not overwrite a lead when the project category changes. If a homeowner starts with rooftop solar and later adds a battery, the measurement should show the relationship between the original opportunity and the add-on. If an existing customer calls about monitoring or warranty, keep the service record separate from acquisition. If a landlord, tenant, property manager, general contractor, or partner submits a request, preserve the role and routing outcome rather than forcing it into a homeowner installation bucket.

Make the source of truth explicit

For each event, name the system that can prove it. The website can prove that a form was accepted. The phone provider can prove a connection according to its own call record. The CRM can prove that the request was reviewed and classified. The scheduler can prove that an assessment was booked. The proposal or contract system can prove a sales state. The project system can prove a scheduled, installed, inspected, or commissioned state when its own record says so.

If two systems disagree, do not silently choose the larger number. Record the matching key, source owner, timestamp convention, time zone, status mapping, consent state, and reconciliation decision. A discrepancy may come from retries, routing, delayed entry, a reschedule, a duplicate merge, a partner handoff, a cancellation, an offline sale, or a project that was entered under a different customer record.

Assign value without overstating the project

Choose what a reported value means before assigning one. It might represent a modeled qualified-enquiry value, a booked-assessment value, a proposal value, an accepted-contract value, a deposit, a scheduled installation, a completed project, a battery add-on, a service job, an invoice, a referral, realized revenue, or contribution after approved costs. Document the source and assumptions, and keep modeled values distinct from business records.

An estimated system price, expected savings, potential incentive, financing amount, roof area, energy production estimate, contract value, or lifetime customer value is not automatically realized revenue. If a modeled value is used for measurement, label it and preserve the calculation inputs and owner. Do not report a quote as a completed installation, a financing request as approval, an interconnection request as approval, or an installation appointment as a commissioned system.

Match value to a decision the installer can make

Value is useful when it answers an operational question. A qualified-enquiry model may help compare campaign sources before later outcomes are available. A booked-assessment value may reflect the team’s capacity and attendance history. A signed-contract value may support sales analysis. A completed-project or invoice value may be the appropriate downstream evidence for revenue reporting. Each has a different delay and a different owner.

Segment the model by residential or commercial route, solar or battery category, broad market, serviceability, property or customer type, project stage, partner or direct source, cancellation, referral, warranty, and approved cost assumptions. An installer that treats a small residential battery enquiry and a multi-site commercial project as one value class may conceal useful differences, even when both originate from the same campaign.

Keep incentives, financing, and savings claims separate

Solar customers may ask about incentives, utility programs, financing, bill reduction, resilience, or energy production. Those topics can affect the content journey and the sales conversation, but the tracking record should not convert a question into a promise. Availability and eligibility can depend on location, project facts, provider rules, timing, and review. Use a broad intent or topic field, route the question to the appropriate owner, and record the actual project state only when an authoritative system supports it.

The same caution applies to savings calculators and design tools. A calculator completion can be a secondary research signal. It is not evidence that a roof is suitable, that the assumptions are correct, that a utility will approve the project, that the customer will sign, or that a particular savings outcome will occur. Make the distinction visible in dashboards and in the names of conversion actions.

Review consent and project-data boundaries

Review consent choices, the privacy notice, retention, access controls, approved integrations, customer-data terms, and applicable advertising requirements before sending lead fields to Google Ads or another measurement system. Google’s conversion measurement and data-use guidance and consent-management guidance are platform resources; they do not decide which fields an installer may collect, share, or retain in a particular jurisdiction. The installer should obtain the professional privacy or legal review appropriate to its operations.

Document which fields are necessary, what event is permitted under each consent state, how a consent change affects the measurement path, and where data may appear in forms, calls, CRM records, schedulers, design tools, proposal systems, project files, debugging tools, exports, or vendors. Keep the advertising event as a measurement signal, not a copy of a roof, utility, financing, contract, or customer file.

If the installer uses enhanced conversions or another customer-data feature, follow the current Google requirements and the organization’s approved data policy. Google’s enhanced conversions for web documentation explains the platform feature, but the decision to collect or share a particular first-party field still belongs to the installer and its privacy process. Do not add an integration simply because it could increase matching; establish the purpose, permitted fields, consent path, retention, access, and deletion process first.

Keep property and financial details purposeful

Broad market, residential or commercial route, property or customer type, service category, battery interest, serviceability, stable lead ID, source, value category, channel, and consent state may be enough for acquisition analysis. Do not send roof photos, utility bills, electrical diagrams, access codes, identity documents, payment data, financing applications, contract files, exact property plans, or unnecessary household or business details to an advertising platform. A conversion does not establish a design, an energy-production forecast, interconnection approval, financing approval, an incentive, or a completed installation.

Use fictional or controlled records for testing. Test consent granted, declined, changed, and unavailable; residential, commercial, battery, ground-mount, new-construction, multi-site, service, warranty, referral, and partner paths; homeowner, tenant, landlord, property-manager, and existing-customer roles; emergency or time-sensitive requests; out-of-area, unsupported, duplicate, rejected, cancelled, and rescheduled states; and site-assessment, proposal, contract, installation, inspection, commissioning, and invoice outcomes. Record the consent-management, phone, CRM, scheduler, design, proposal, project, tag, and release versions so a discrepancy can be tied to a real change.

Reconcile enquiries with assessments and installations

Compare Google Ads actions with phone, form, CRM, scheduler, site-assessment, design, proposal, contract, project, installation, inspection, commissioning, battery add-on, service, invoice, referral, cancellation, and approved-value records over a defined reporting period. Explain differences caused by attribution or reporting delay, call routing, duplicate merging, consent, browser behavior, time zones, seasonal demand, partner handoffs, rescheduling, no-shows, cancellations, financing review, utility review, or offline work.

Segment by residential or commercial route, system category, battery interest, service area, property or customer type, broad market, call versus form, landing page, campaign, device, enquiry disposition, assessment state, proposal state, contract state, installation state, partner source, cancellation, referral, warranty, service request, and approved value. A mismatch limited to commercial proposals needs a different investigation from a missing event across every residential form and phone route.

Preserve the lead-to-project relationship

Connect the original lead or call ID to the assessment, design, proposal, contract, installation, inspection, commissioning, battery add-on, service, invoice, referral, cancellation, and approved value states. Do not count an assessment, design revision, proposal, signed contract, scheduled installation, completed project, or invoice as a new lead. Do not overwrite a rejected, cancelled, existing-customer, or partner-routed record merely because a phone number, address, or company name matches.

If an approved offline process is used, document its matching key, source owner, status mapping, timestamp, consent state, project category, customer or property type, service area, value category, and data owner. A later import should improve evidence about lead quality or project value; it should not expose a project file or make an estimate look like realized revenue. Keep the original source and current business state available so a campaign review can distinguish “generated the enquiry” from “produced the completed project.”

Investigate mismatches by stage

When website events exceed CRM records, inspect form validation, retries, consent handling, duplicate logic, response failures, and whether the website reported success before the CRM accepted the request. When CRM records exceed website events, inspect phone routing, manual entry, partner referrals, offline sources, call tracking, and imports. When assessments exceed qualified enquiries, inspect direct traffic, repeat customers, partner work, or a status mapping that counts a later state twice.

When proposals or installations are missing, do not immediately change the Google Ads tag. Check the lead ID, stage transition, sales owner, project-system import, cancellation, time zone, and reporting window. A real delay can be normal for a long solar cycle, while a missing identifier or inconsistent status mapping can make a genuine project impossible to reconcile. Document the finding and the smallest correction that restores the relationship.

Test the complete solar-installation path

Use an approved test environment and controlled contacts. Google Tag Assistant can help inspect tag behavior, but a browser event is not proof of a qualified solar enquiry, connected call, site assessment, proposal, contract, installation, inspection, commissioning, battery add-on, or invoice. Compare the event with the form handler, phone provider, CRM, scheduler, design or proposal system, project-management system, invoice system, and approved offline record that establishes the business state.

Cover project, customer, and consent cases

Test a solar service page, battery page, savings or design tool, phone click, connected call, missed call and callback, residential form, commercial form, ground-mount or new-construction route if supported, multi-site route if supported, service or warranty request, partner referral, homeowner, tenant, landlord, property manager, existing customer, financing question, incentive question, utility or interconnection question, out-of-area contact, unsupported project, duplicate form, rejected enquiry, booked assessment, reschedule, no-show, proposal, contract, cancellation, installation, inspection, commissioning, and invoice state. If the installer serves multiple markets, languages, property types, or project categories, test each materially different route.

For every test, record:

the truth condition, event name, conversion role, expected trigger, and source record;
stable lead, call, appointment, assessment, design, proposal, contract, project, installation, service, referral, cancellation, and value IDs as applicable;
broad market, residential or commercial route, property or customer type, system or service category, battery interest, serviceability, source, value category, and channel;
consent state and whether the approved data path allowed the event; and
expected deduplication, partner handoff, assessment reschedule, cancellation, downstream match, and rollback result.

Diagnose a missing, extra, duplicate, or wrongly valued event by inspecting the trigger, validation, consent state, phone routing, CRM creation, service-area rule, project-category rule, customer classification, scheduler state, design state, proposal state, contract state, project state, invoice state, tag version, and import timing. Test mobile as well as desktop, calls as well as forms, and declined or changed consent as well as the successful path. Do not add tags or change campaign definitions to conceal poor lead quality or a source-system mismatch.

Avoid common solar-installation tracking mistakes

Making every solar page, calculator completion, battery comparison, financing click, incentive question, phone click, chat start, or form start a primary conversion.
Counting job seekers, suppliers, electricians seeking work, existing customers, monitoring or warranty requests, partner contacts, out-of-area properties, unsupported projects, duplicates, and utility-process questions as new installations.
Treating a site-assessment request, design, proposal, contract, deposit, scheduled installation, inspection, commissioning, or invoice as a guaranteed project result.
Combining residential rooftop, battery, ground-mount, commercial, multi-site, new-construction, electrical-upgrade, storage-retrofit, and service paths without meaningful project context.
Inventing an exact roof pitch, system size, annual usage, electricity bill, property value, distance, call-duration, savings, or project-stage threshold that the installer does not use.
Creating a new lead or project ID for a form retry, callback, transfer, battery add-on, assessment reschedule, design revision, follow-up, referral, service request, or cancellation.
Sending roof photos, utility bills, electrical diagrams, access codes, identity records, payment data, financing applications, contract files, exact property plans, or unnecessary household or business details to an advertising platform.
Presenting an estimated system price, expected savings, incentive, financing amount, energy-production estimate, contract value, or lifetime value as realized revenue.
Ignoring service area, customer or property role, consent, retention, access, data-use terms, approved integrations, project ownership, partner handoffs, no-shows, cancellations, utility review, or long sales-cycle delays.
Testing only a successful desktop residential form and never checking mobile, calls, battery, commercial, service, partner, duplicate, out-of-area, assessment, proposal, cancellation, installation, or declined-consent paths.
Changing conversion definitions or campaigns to hide a source-system mismatch instead of tracing the event, identifier, stage transition, and authoritative record.

The most damaging mistake is usually not a missing optional field. It is a conversion name that implies more truth than the evidence supports. “Solar lead submitted” and “completed installation” should not be interchangeable labels. Clear names help the sales team, analyst, and campaign owner make different decisions from the same data.

Solar-installer conversion-tracking checklist

Before relying on the account, confirm that:

Page, calculator, phone, form, enquiry, assessment, design, proposal, contract, installation, inspection, commissioning, battery add-on, service, referral, cancellation, invoice, and value boundaries are written down.
Each action has a meaning, truth condition, trigger, source, serviceability rule, project category, conversion role, owner, test case, consent condition, and rollback.
Stable IDs connect lead, call, appointment, assessment, design, proposal, contract, project, installation, service, referral, cancellation, and value records.
Residential or commercial route, broad market, property or customer type, system or service category, battery interest, serviceability, consent, and disposition are explicit where they affect qualification.
Modeled enquiry, booked assessment, proposal, accepted contract, scheduled installation, completed project, invoice, realized revenue, and contribution values remain distinct.
Financing, incentive, utility, interconnection, savings, design, and energy-production questions are tracked as intent or approved business states, not as unsupported promises.
Privacy, consent, retention, access, customer-data terms, approved integrations, data owners, and professional review responsibilities are documented.
Desktop, mobile, residential, commercial, battery, ground-mount, new-construction, multi-site, service, warranty, partner, call, form, duplicate, out-of-area, assessment, proposal, contract, installation, cancellation, invoice, and declined-consent tests pass.
Google Ads, phone, form, CRM, scheduler, design, proposal, contract, project, installation, invoice, referral, cancellation, and approved-value evidence can be reconciled by stable ID and reporting window.

Review the account after meaningful changes

Recheck the event map when the installer changes its form, phone provider, CRM, scheduler, design tool, proposal workflow, project system, consent platform, landing-page promise, service area, product mix, partner process, or status definitions. A tag can continue to fire while the business meaning behind the event has changed. A conversion review should therefore compare both the technical event and the source record that proves the business state.

Watch for changes in the mix, not just the total count. A sudden increase in calculator completions, financing questions, battery interest, missed calls, duplicate forms, out-of-area requests, partner referrals, or existing-customer service may be a routing or traffic change rather than a growth in qualified installation demand. Segmenting before changing campaign settings makes that distinction visible.

Keep an evidence trail

Record the event definition, source owner, identifier, consent path, conversion role, value model, test result, release or configuration version, and date of review. When a number later looks wrong, this record lets the installer trace whether the issue began in the ad destination, tag, form, call route, CRM, scheduler, proposal process, project system, import, or reporting window. It also prevents the team from re-arguing the meaning of a conversion every time a campaign changes.

Practical next steps for solar installers

Begin with the shortest useful measurement path: define a serviceable enquiry or connected call, identify the authoritative record, and make its primary or secondary role explicit. Then add site assessment, proposal, contract, installation, battery add-on, service, and value states as the sales and project systems can prove them. This sequence gives the installer useful visibility without pretending that a long downstream cycle is already available at the first click.

If the account already has tracking, inventory the existing conversion actions before adding more. For each one, ask what event triggers it, what record proves it, whether it is included in bidding, how duplicates are handled, which consent states permit it, what value it carries, and whether it can be connected to an assessment or project. Retire or reclassify ambiguous actions only after their reporting impact and ownership are documented.

For the broader account framework, see best Google Ads conversion tracking settings, best Google Ads bid strategy for solar installers, best Google Ads location targeting for solar installers, and best Google Ads conversion tracking for home services. adz.so can help organize measurement evidence and review steps around the installer’s definitions. It does not design solar systems, assess roofs, approve financing or incentives, guarantee savings, perform electrical or roofing work, replace the CRM or project systems, or provide legal, tax, utility, or safety advice.