Visioix Pro Documents
Version 1.1
Understand your visitors, build thoughtful feedback forms, and turn website evidence into practical decisions.
Start with installation →Meet Visioix Pro
Visioix combines visitor feedback, behavior analysis, website intelligence, and follow-up workflows inside WordPress.
Start with one clear question and one form. Collect enough real evidence before drawing conclusions or creating automated actions.
Detailed event history starts when Visitor Intelligence tracking is enabled. Earlier stored responses can still be available, but missing historical events cannot be reconstructed.
Install and open Visioix
Prepare the site
Back up your WordPress files and database. Obtain the Visioix Pro ZIP from your ARN account. If you are moving from Free, keep existing data and use the Pro transition rather than deleting the plugin with a data-removal option enabled.
Upload the package
Open Plugins → Add New Plugin → Upload Plugin. Choose the Pro ZIP, select Install Now, and then Activate Plugin. On multisite, plugin upload normally belongs to the network administrator.
Find the workspace
Open ARN Visioix in the WordPress menu. Use its submenu to reach Forms, Visitor Analytics, the intelligence workspaces, Integrations, and Settings. The plugin appears as ARN Smart Visioix in the Plugins list.
Activate your Pro license
Open ARN Visioix → Settings → License. A locked installation opens the license screen directly.
Enter your ARNA
Copy the complete one-time ARNA activation code from your ARN account or activation email into the activation field. Keep it private. Confirm that the license is for Visioix and that its domain allocation matches this installation.
Activate and check the result
Select Activate. Confirm that the screen reports an active license and inspect the domain, expiry date, and online verification information before starting Pro workflows.
An offline fallback is a temporary validity window shown by the product. It does not renew a subscription. If activation fails, check the full ARNA value, domain allocation, server clock, and the server’s ability to make outbound HTTPS requests. The connection or diagnostic area identifies the latest problem.
Use Change license when replacing a key. Disconnecting a license affects Pro availability; it is not a data-cleanup action.
Create your first form
Give the form a purpose
Open ARN Visioix → Forms. Enter a short name, such as Visitor feedback, then select Create Form. Use separate forms for different products, departments, or research goals.
Open its builder
Select Open Builder on the form’s row. The list also provides Display Rules, Design Studio when enabled, Duplicate, Activate or Pause, and Archive.
Keep a safe working draft
Use Save Draft while developing. Publish structural changes when the form is ready, then make sure its status is active. Published versions and form-specific response history help you interpret which questions a visitor answered.
Build questions and multiple steps
The left library supplies blocks and fields. The center shows the structure. The right inspector edits the selected item.
Add a Form Block
Expand Structure Blocks. Place a Form Block in the step, add a section, and then place fields inside that section. Text, header, and other structure blocks provide context around the questions.
Set each field
Choose Text, Textarea, Email, Phone, Number, Radio, Checkbox, or Dropdown from Form Fields. Select the field in the center to edit its label, placeholder, column span, and required state. Choice fields also need meaningful options.
Organize the flow
Use arrows to reorder items. Select Add Step for a multi-step form and edit its step titles. The Progress Bar setting controls the visitor’s progress indicator. Check the Desktop and Mobile previews.
Review and publish
Use concise labels and ask only for necessary information. Check the submit label and success message, save a draft, and use Publish Changes when ready. Submit one real test on your staging site and confirm that a response is recorded.
Use conditional logic
Conditional logic changes the form according to earlier answers. For example, show a contact section only when a visitor requests a reply.
- Open the form builder and find Conditional Logic.
- Select Add Rule, choose the answer source and comparison, then choose the target field or section and the available action.
- Review diagnostics for missing targets or conflicting rules.
- Test every branch, including an unanswered optional field, on desktop and mobile before publishing.
Keep rules simple at first. Duplicate a working form before making a large structural change.
Choose pages, audience, and triggers
Each form has its own Display Rules. Global Settings also contain display and trigger controls for the visitor experience.
Choose where it appears
Select Sitewide, Homepage only, or Selected pages only. Use include and exclude pages deliberately. If several forms match, the higher priority wins; give important forms distinct priorities.
Choose who sees it
Set user state, device, and first or returning visitor audiences. Start broadly while testing, then narrow the rules after the form works.
Choose when to invite a response
In Settings → Triggers, enable the trigger system and the specific timing, scroll, exit, page-view, or time-on-site conditions you want to use. Avoid immediately interrupting every visitor with several competing prompts.
General settings can hide the bar for a number of days after submission or dismissal. An administrator testing repeatedly may therefore stop seeing the invitation even when the form is active. Use a fresh browser session, or intentionally reset the display cache while testing.
Style the form
Enable Settings → Appearance → Use a separate Design Studio for each form to expose form-specific design controls. Then open Forms → Design Studio.
- Set the background, text, accent, border, and button colors.
- Choose typography, content width, spacing, border radius, and mobile width.
- Review the preview at the available device sizes. Check label readability, contrast, and long answer options.
- Save the design and verify it on an actual frontend page.
Design changes control presentation; they do not change the questions or reset the form’s response history. Theme fonts and frontend cache can affect how the result appears.
Consent and response handling
Open Settings → Privacy & Consent to enable a configurable consent checkbox and connect it to the site’s actual privacy explanation.
Ask for contact details only when you need a reply path. Verify the visitor-facing wording and the destination of privacy links on your site.
Use Visitor Responses to inspect stored submissions. Review the form/version, answers, intent, and contact information before following up. Treat the records and CSV exports as private site data.
In Settings → Data & Cache, choose response retention and automatic cleanup deliberately. Export anything you need before deleting responses. Manual Reset Display Cache changes whether visitors can see the invitation again; it is separate from deleting response data.
Notifications and direct contact
Choose the notification destination
In Settings → Notifications, enable email notifications, set the recipient address, and decide whether messages should be sent only when contact information is provided.
Verify delivery
Choose WordPress Mail, an external SMTP plugin, or Internal SMTP. Configure only the method you actually use. Save the settings and send a test email where the interface provides it. Confirm delivery in the recipient inbox and check spam filtering.
Offer direct contact paths
In Settings → Contact Widget, enable the widget, select its position and device visibility, then add contact buttons for calls, email, or WhatsApp. Check every destination on a real device.
A clicked call or WhatsApp button records an action signal. It does not prove that a conversation or sale completed.
Read Visitor Analytics
Open ARN Visioix → Visitor Analytics. Compare the same date range and audience when assessing changes.
| Measure | How to use it |
|---|---|
| Impressions / Panel Opens | Check whether the invitation is visible and whether visitors choose to open it. |
| Responses / Contact Leads | Review participation and submitted contact details. A lead is not a verified purchase. |
| Dismissals / Contact Clicks | Look for intrusive timing or useful direct contact routes. |
| Trends / Segments / Funnel | Compare periods and groups, then find where visitors stop progressing. |
| Behavior Pro / Lead Intelligence | Read the evidence and confidence behind recommendations before choosing a follow-up. |
The full workspace includes Overview, Summary, Trends, Segments, Intent, Contact, Triggers, Time, and Funnel views. Use 7, 30, or 90-day periods where offered. Low volume can produce unstable percentages; wait for sufficient observations.
Website intelligence and AI workspaces
Visitor Intelligence focuses on visitor evidence. Website Intelligence focuses on the site. Cross Intelligence combines available signals, and Action Plan turns them into reviewable priorities.
- Confirm that tracking and the required data sources are enabled and actually collecting.
- Read source availability and confidence notices before interpreting any score.
- Use Advanced AI, SWOT, Forecasts, or Reports for their specific analysis tasks when the required inputs are ready.
- Choose one actionable improvement, record your baseline, and compare a later period after the change.
For optional AI processing, review Settings → AI Insights and the shared ARN Smart AI connection workspace. Choose the configured engine, provider and model there, then test the connection. Growth requests use the existing background queue and shared usage records.
Responses are saved before background AI processing. A provider error does not by itself mean the original response is lost. Check queue and error information before retrying. Scores and forecasts are decision aids, not guaranteed outcomes.
Integrations, automation, and experiments
Use Integrations to configure available delivery destinations, then test them with non-sensitive example data. Inspect the delivery result before relying on the connection.
Use Automations to connect an available trigger to an action and add the relevant conditions. Begin with one narrow rule and monitor its execution history. Review the recipient and payload before enabling any external delivery.
Experiments and Website Experiments help compare controlled changes. Define the goal and variants, avoid changing several unrelated settings during the same comparison, and review sample size before declaring a winner.
Do not interpret an unavailable integration or an empty experiment panel as a completed action. Some workflows depend on configuration, tracking history, or external provider availability.
A practical first-run checklist
- Confirm the Pro license and that the visitor intent bar is enabled.
- Create one feedback form with a short question and an optional message.
- Publish its structure, activate it, and target one staging page.
- Test its desktop/mobile layout, display conditions, and every logic branch.
- Submit one response and confirm both the stored record and any email notification.
- Review analytics after real traffic arrives, then expand targeting.
For an update, back up the site, install the verified new Pro package through the normal WordPress update path, and repeat a short frontend submission and notification check.
Troubleshooting
The form or invitation does not appear
Check the plugin enabled state, form active status, published structure, matching pages, audience, trigger conditions, and competing form priorities. Submission/dismissal hiding periods and cached frontend HTML can also explain the result. Test in a new browser session.
The form cannot be submitted
Inspect required fields, consent, and hidden conditional fields. Reproduce on a staging page with the simplest form. Check browser errors and server logs if the submission request fails.
There is no analytics history
Check tracking configuration and whether visitors have produced events. Detailed event history begins when tracking is enabled. Check the selected date range; older responses do not recreate missing event history.
Emails or integrations do not arrive
Confirm the recipient/destination, chosen delivery method, and transport credentials. Run a test and inspect the result, spam folder, and delivery history. Avoid repeatedly resubmitting real visitor data.
AI fails or remains pending
Check provider access, key, model, endpoint, quota, and background processing. Review the recorded error before retrying. Original stored responses should be inspected separately from AI status.
License or file-integrity warning
Read the license connection diagnostic. For missing or altered protected files, reinstall a complete verified package; do not edit sealed product files to bypass the warning.
When requesting support, include the plugin version, WordPress/PHP versions, screen name, steps to reproduce, and a screenshot without licenses, API keys, or private responses.
Growth Intelligence: evidence and actions
Open ARN Visioix → Growth Intelligence. Select a completed 7, 30 or 90-day period. The overview compares equal, non-overlapping windows and keeps each source separate.
- Open Data connections. Google Site Kit must be installed, active and configured with Analytics and Search Console access.
- Read Evidence health before interpreting a chart. Missing observations remain missing; they are not replaced with zero.
- Review supported traffic changes and their source, dates and sample. A change does not prove its cause.
- Review AI explanations or title drafts where available. Open the actual WordPress editor or add an action to the existing Action Plan.
- After completing a task, select a later completed window of the same length to record an observational follow-up.
Smart internal links: suggest, preview, apply and undo
Open Smart internal links, choose a source article and select Find candidates. Context and language come before performance. Targets with fewer incoming links from this catalogue are prioritized before matched page views.
- Choose a relevant published target. No matched analytics means the recommendation uses content context, not measured performance.
- Choose an unlinked text segment and enter the exact existing words to use as the anchor. Optional AI drafting uses the configured background queue.
- Select Preview change and review the before/after text and target.
- Select Apply this link. The plugin rechecks content, permissions and the target, and records a revision. If the document changed, create a fresh preview.
- To reverse the change, select Undo this link only. This removes the inserted link while preserving later unrelated edits.
Supported sources are static Gutenberg/classic text and active Elementor text-editor fields. Dynamic Elementor fields, other widgets and unsupported builders are excluded.
The default catalogue contains the 200 most recently modified published posts/pages. Incoming link counts exclude menus and content outside the sample. Zero catalogue links does not prove a site-wide orphan.
Applied links show consenting anonymous visitor exposures and clicks. Signed-in users are excluded. A link click does not prove a lead, sale or SEO gain.
Authors, content groups and executive summaries
Use Authors & content to inspect matched author, category, word-count, age and content-type groups. Check coverage and group membership before comparing periods. Engagement seconds per view are weighted by views.
A relationship between length and engagement is an observation. It does not establish an ideal length for every article. WordPress comment counts are lifetime counts, not automatically comments received during the analytics period.
Executive summary adds an optional AI explanation to the saved reporting evidence. Weekly/monthly scheduled reports use the existing email workflow and an immutable snapshot. Review the saved report and recipient configuration before scheduling.
AI has a bounded waiting window. If it fails or times out, the numerical report can still be delivered. An uncertain dispatch is not automatically resent; check delivery history before sending again.
Ask supported analytics questions
Open Ask your analytics and ask about a supported report, metric, filter and period. For example, ask which country received the most visitors during a supported completed window.
The query is constrained to supported reports. The application calculates the numbers; optional AI explains the returned evidence. Answers retain source, dates and a report link. Unsupported questions or missing inputs are disclosed.
Money values require a specific currency and sufficient coverage. A question about why traffic fell cannot prove a cause from a percentage alone.
Commerce evidence and product mapping
Open Commerce analyst. GA4 product/event aggregates and WooCommerce orders are separate sources. Do not add their revenue totals together.
- Check Analytics ecommerce instrumentation for view_item, add_to_cart, begin_checkout and purchase.
- Inspect WooCommerce cohorts grouped by order creation date in the site timezone. Currencies remain separate. Refunds are lifetime refunds against those selected orders.
- Verify GA4 item-to-WooCommerce product mappings explicitly. Item IDs are not automatically treated as WordPress product IDs.
- For sequential journeys, import the documented closed Google runFunnelReport export and its request contract. It requires ordered steps and at most 24 hours between successive steps.
Independent event counts do not form a checkout funnel. Imported provenance is administrator-supplied, not independently verified. Shipping prices or technical issues remain hypotheses without additional evidence.
The order report caps each period at 5,000 orders. Product reports collect up to 1,000 product/currency pairs and display the first 50. GA item reports return at most 100 rows per period. Review incomplete-coverage notices.
Controlled title experiments
Use Controlled automation for title experiments with one specific on-site click goal. Set the target element, variants, fixed 7–90-day horizon and publication policy before beginning.
Exclude experiment pages from full-page and CDN caching. Verify assignment and the visible click goal with consenting anonymous visitors. Exposure requires the target to be visible; visits alone are not goal clicks.
Winner publication requires the ended horizon, minimum sample/outcomes, significance and current-content guards. Automatic publication is opt-in. Insufficient evidence or a tie does not produce a forced winner.
Restore affects the experiment field and protects other edits. This tests an on-site click goal; organic Search Console CTR is not attributed to title variants.
Recommendations and visitor permission
Add the Recommendations block or [arnvisiox_recommendations count="4"] shortcode. The general list remains available without a profile.
After visitor permission, category interests stay locally in the browser for up to 30 days and rank prepared content suggestions. Withdrawal restores the general list and removes the local profile. Global Privacy Control overrides profiling.
This feature personalizes the recommendations block. It does not fetch an individual's GA4 history or rearrange the entire homepage. No paid AI request runs during page display.
External trends and reviewed comment samples
In Trends & community, import a dated 0–100 topic-index CSV with its HTTPS source and geography context. Review the import period and provenance before comparing it with Search Console context.
Imported indices are not search volume, competitor rankings or guaranteed traffic forecasts. Their source is supplied by the administrator. Site and external values are not added together.
- Select an eligible approved-comment sample and inspect its coverage.
- Review the redacted text preview. Author names, emails and IP metadata are not sent as comment metadata.
- Edit the sample if necessary, then explicitly approve the exact preview for AI processing.
- Review sentiment results as interpretations of the selected sample. Moderation changes can invalidate eligibility.
Shared AI connection settings, privacy choices and the existing queue apply. Failed requests require fresh review where instructed; do not assume a retry reuses the previous approved context.
What changed in Pro 1.1.4–1.1.5
This guide references Visioix Pro 1.1.5. Growth Intelligence was introduced in 1.1.0; the current release improves supported analytics questions and optional visitor-field configuration.
Ask a supported question
- Open ARN Visioix → Growth Intelligence and review the connected sources and completed period.
- Ask an observed-data question, such as comparing supported country traffic in the selected period.
- Check the supported/unsupported response before queuing a report.
- Read the result with its source, period and report references.
Requests for future-year revenue predictions or other unsupported answers are rejected. An unsupported question should not become an unrelated report. The separate Forecast module is a different workflow.
Keep optional visitor fields optional
- Open component settings and review the intent, message, name, email, phone and company switches.
- Leave fields you do not need off, even when AI Insights is on.
- Complete a redirect/contact target only for a channel you enable.
- Save, reopen settings and verify the intended switches and the actual visitor form.
For title experiments choose a fixed 7–90 day horizon and one on-site click goal. Review the winner policy, sample and current-content checks; insufficient evidence remains inconclusive.