Help4 Product Insights, Download Starts and Adoption Stats
Before changing settings
Confirm the site, user state, current version, and recovery path.
Open the exact site and feature named in the request, record its current behavior, and keep a bounded recovery option. Change one setting group at a time so the verification can identify what actually changed.
Target
Record the domain, URL or admin screen, user role, viewport, and specific outcome before changing configuration.
Current state
Capture the relevant version, enabled module, existing value, and a fresh public or runtime check.
Recovery
Keep the previous immutable package, WordPress revision, export, or narrow data snapshot needed for this feature.
Privacy
Keep credentials, private customer data, payment secrets, nonces, and protected files out of screenshots and support reports.
Visual orientation
Match the screen before following the steps.
Open each image at full size. The numbered notes explain what the screen controls and what to confirm before changing customer content.
Screen 1
Page Settings and recovery
Confirm page-level layout, history, preview, and recovery controls before a larger edit.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 2
Settings and launch center
Choose a launch plan, confirm modules, download Help4 Blank, review readiness, and keep the site configuration in one place.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 3
Searchable Quick Help in Builder Studio
Search the task guides without leaving the page-editing context, then open the matching workflow in a separate tab.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Watch the real workflow
Watch the clicks before making the change.
Use the narrated walkthrough first, then follow the written steps and verification checks on this page.
Lesson 12
Commerce Products, Quantity, and Checkout
Create a native product, configure purchase and quantity rules, and verify the checkout and order path.
Read the complete transcript
- Open Native Products
Open Commerce, then Products. Native Catalog mode lets you create simple, service, digital, booking, variable, and subscription products without adding a separate store plugin.
- Describe the Product
Set the name, SKU, status, price, stock, description, image, tax behavior, fulfillment, and customer requirements. Use variants when options need their own price, stock, image, or SKU.
- Set Quantity Rules
Turn off customer quantity when a configured package must stay one unit per cart line. Customers can still add another separately. Use the order-limit option only when the whole order may contain one.
- Test the Full Order
Run a test from product display through cart, payment routing, confirmation, inventory, customer record, and order status. Verify both normal quantity products and fixed one-per-line products.
Two different measurements
Do not confuse a clicked ZIP route with an active installation.
Download-start aggregates help measure which product, source, campaign, and referrer host initiated a first-party redirect. Installation records exist only after consent and report public site/version facts, never customer content or visitor behavior.
Download definition
Treat the count as a non-bot GET request that started the redirect to a ZIP, not proof that the file completed, activated, or remained installed.
Consent state
Installed-domain reporting is off by default and requires a managing administrator to review the payload and enable it.
Payload boundary
The weekly status includes site address, version/build, WordPress/PHP, theme, enabled module names, channel, environment, multisite state, and an installation identity.
Deletion path
Stopping sharing disables the local heartbeat immediately and requests deletion of the matching remote installation record.
Guided walkthrough
Make one verified change at a time.
Each step includes the action, why it belongs in this order, and the checkpoint to verify before moving forward.
-
Open Product Insights
In Help4 Builder Suite, open Product Insights and confirm sharing is Off before making a consent decision.
Why nowStarting from a confirmed target prevents a correct edit from being applied to the wrong page, template, product, or responsive view.
Done whenThe open product insights result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Review every field
Read the exact payload preview and verify that it contains no page content, users, customers, forms, emails, cookies, secrets, or raw logs.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe review every field result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Choose deliberately
Leave sharing off or check the consent box and send the first status. There is no dashboard takeover or implied consent.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe choose deliberately result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Read the result
Check the last attempt, last successful send, response status, and release environment instead of assuming delivery.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe read the result result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Interpret Help4 reports
Use active consented domains for adoption and download-start aggregates for campaign interest; never combine them into a fabricated install count.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe interpret help4 reports result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Stop and delete
Use Stop sharing and delete record. Local sharing stops immediately; if the collector is unavailable, remote deletion stays queued for retry.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe stop and delete result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Update the privacy notice
Use the WordPress privacy-policy suggestion when the site enables sharing and keep the public notice aligned with the actual choice.
Why nowThe final verification separates an editor preview from a result that is actually saved, responsive, interactive, and ready for visitors.
Done whenThe update the privacy notice result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
Release check
Test the real public or member outcome, not only the settings screen.
Reopen the saved setting, run the intended workflow in the correct visitor state, test desktop and phone behavior where a frontend surface exists, and inspect fresh browser or PHP errors from the same attempt.
Persistence
The saved values remain correct after reload and do not overwrite newer settings from another session.
Public behavior
The intended visitor can complete the workflow and an unintended visitor cannot access protected output.
Responsive behavior
Controls, text, tables, media, dialogs, and focus stay visible and usable at 768px, 390px, and 360px.
Fresh evidence
The final request has the expected status, output, cache state, and no new related console or PHP error.
Common questions
Answers for the decisions that block this setup most often.
Does Help4 track every site automatically?
No. Installed-domain reporting is disabled by default and starts only after explicit administrator consent.
Are download starts the same as installations?
No. A start means a qualifying request reached the tracked first-party download redirect; it cannot prove download completion, activation, or continued use.
What happens when sharing is disabled?
The weekly heartbeat stops locally and Help4 requests deletion of the installation record identified by that site token, retrying if the collector is temporarily unavailable.
Continue learning
Use the next guide that matches the work in front of you.
The full tutorial hub remains available without repeating dozens of unrelated cards on this page.
Start here
Install and setup
Download the ZIP, activate Builder Suite, understand the blank-theme path, and run the first clean check.
First page
Build a page safely
Open Builder Pages, launch Studio, build structure first, check mobile, then publish or hand it to Help4.
Editor controls
Know which tab changes what
Use Content for information, Design for appearance and responsive values, and Advanced for identity, attributes, visibility, and motion.
Recovery
Edit without losing work
Replace media safely, recognize stale drafts, and restore a known-good page snapshot from Page Settings History.
Responsive
Control every viewport
Set spacing, widths, columns, alignment, and typography independently for desktop, tablet, and mobile.
Templates
Choose a starter
Pick a starter spec by page job: service, product, support, recent work, local SEO, launch, or checkout recovery.
Need a second set of eyes?
Send one complete, privacy-safe support record.
Include the affected URL or admin screen, current Builder version, user state, exact steps, expected result, actual result, and one screenshot or fresh error when available.