|
This article covers the following: |
Overview
The Wingify QA Assistant is a powerful debugging tool designed to help you preview and validate your testing campaigns directly on your website before launching them. It allows you to simulate how variations will appear and behave in a live environment, so you can confirm that targeting rules, audience segments, and tracking metrics are working as expected.
Unlike standard preview modes, the QA Assistant gives you a complete view of the current campaign that you are previewing, along with visibility into other campaigns running across your account. You can:
- Switch between variations
- Force-run campaigns that you may not normally qualify for
- Monitor events and metrics in real time
This is especially useful when testing campaigns with specific targeting conditions. For example, if a campaign is set to run only for visitors from the US, you can still use the QA Assistant to force-apply it while browsing from another location. This helps you verify both the user experience and conversion tracking without needing to meet all targeting criteria manually.
Prerequisites
- The campaign must be in the Draft, Running or In QA state.
- The Wingify SmartCode must be installed on the website where you are performing the QA.
Access the QA Assistant
You can launch the QA Assistant from within the Wingify application during the campaign setup or review process. To launch the QA assistant, follow these steps:
- Navigate to the Review tab of your campaign.
- Select Live Preview.
- Click Preview in a new tab. Your website opens in a new tab with the QA Assistant overlay visible at the bottom of the page.
Navigate the QA Assistant Interface
The QA Assistant offers three different view modes to suit your workspace needs: Expanded (detailed table view), Minimized (floating window), and Icon (small chatbot-style bubble). You can drag and drop the assistant to any position on your screen.
The expanded interface is divided into three primary tabs:
Current Campaign
This tab focuses on the campaign you are currently previewing on the page. It provides a quick snapshot of how the campaign is behaving for your session, including:
- Status: Indicates whether the campaign is running, paused, or not eligible.
- Variation: Shows which variation (for example, Control or a specific variant) is currently applied. You can also switch between variations to verify different experiences.
- Acceptance: Displays whether the campaign has been applied to your session (accepted) or skipped due to targeting or traffic allocation rules.
You can also use this tab to force show or hide a campaign, regardless of its actual targeting or eligibility conditions. This is useful when you want to:
- Test a variation without meeting all targeting criteria
- Debug why a campaign is not appearing
- Validate UI changes in isolation
Use this tab to validate whether the campaign is being applied as expected and to quickly debug issues related to targeting, variation delivery, or traffic allocation.
All Campaigns
This tab gives you a broader view of all campaigns running across your account, helping you understand how multiple campaigns may interact with each other.
It is divided into two sections:
- On this page: Lists campaigns whose targeting conditions match the URL of the page you are currently viewing. These are the campaigns that can potentially run on this page and may impact the user experience.
- On other pages: Lists campaigns that are active in your account but are targeted to different URLs. While these do not affect the current page, they are useful for gaining visibility into overall campaign activity.
This tab is especially useful for identifying conflicts, overlaps, or dependencies between campaigns, and for ensuring that the correct campaigns are triggered on the intended pages.
Events
This tab provides a real-time stream of all Wingify events triggered during your session. This includes:
- Page view events
- Custom events
- Conversion events linked to goals and metrics
Each event is logged as it occurs, allowing you to verify whether tracking is working correctly. Select an event to view its details in the panel on the right.
Use this tab to:
- Confirm that metrics are being triggered as expected
- Debug issues with event tracking or missing conversions
- Validate integrations and custom event implementations in real time
Force and Hide Variations
The QA Assistant lets you override Wingify’s default targeting and eligibility logic, enabling you to test specific scenarios without needing to meet all campaign conditions. This is particularly useful for validating experiences, debugging delivery issues, and testing edge cases during the QA process.
From the Current Campaign tab, you can perform the following actions:
- Switch Variations: Use the variation dropdown to toggle between the Control and different variations. This lets you instantly preview UI changes and verify that each variation is rendering correctly on the page.
- Hide Campaign: Use the Hide option to temporarily disable the campaign’s changes on your current page view. This helps you compare the original (control) experience with the modified version or isolate the impact of a specific campaign. This action only affects your current session and does not impact how the campaign is delivered to other visitors.
- Force Apply: If a campaign is not applied due to unmet conditions (such as segment rules or trigger criteria), you can use the Force option to manually apply it. This allows you to preview and validate the campaign even when you do not qualify for it.
Validate Campaign Configuration
Within the Current Campaign and All Campaigns tabs, you can drill down into the conditions that determine whether a campaign is eligible to run for your session. To do this, select a campaign from the list to open its Validations tab on the right. This view breaks down each rule applied to the campaign and shows whether it has been successfully met.
The QA Assistant evaluates the following parameters:
Info: A green checkmark indicates the condition is met, while a red "X" indicates it has been rejected. If any mandatory condition is rejected, the campaign will not execute naturally on the page. This detailed breakdown allows you to quickly identify which rule is preventing the campaign from running and take corrective action.
| Page URL | Verifies whether the current page URL matches the campaign’s targeting rules (such as included or excluded URLs). If this condition fails, the campaign will not trigger on the page. |
| Segment | Indicates whether your current session satisfies the defined audience conditions (for example, location, device type, or custom segments). This helps you confirm if you qualify as an eligible visitor. |
| Trigger | Checks whether the campaign’s trigger conditions have been met. These could include behaviors such as time spent on the page, scroll percentage, or exit intent. Even if all other conditions are satisfied, the campaign will not run until the trigger condition is fulfilled. |
| Display Frequency | Confirms whether the campaign is eligible to be shown based on its frequency settings (for example, once per session or after a defined interval). This helps prevent overexposure to the same visitor. |
Track Logs and Metrics
To ensure that campaign data is being captured and tracked correctly, you can use the Logs and Metrics sub-tabs available within a selected campaign in the QA Assistant. These tabs help you validate both campaign execution and conversion tracking during your session.
Logs
The Logs tab provides a chronological view of your session activity. It tracks how the campaign behaves as you navigate through your website.
This includes:
- Pages visited during the session
- Whether the campaign was accepted or rejected on each page
- Changes in campaign eligibility as you move across different URLs
Use this tab to:
- Verify if the campaign is triggering on the correct pages
- Identify inconsistencies in campaign behavior across navigation
- Debug issues where a campaign is applied on one page but not on another
Metrics
The Metrics tab lets you validate whether conversion goals associated with the campaign are being tracked correctly.
To test this:
- Perform the action required to trigger a metric (for example, clicking a button or submitting a form).
- Observe the metric status in the QA Assistant.
Once a metric is successfully triggered:
- A checkmark appears next to the corresponding metric, confirming that the conversion has been recorded.
You can also:
- Click the Link icon next to a converted metric to jump directly to the corresponding event in the Events tab.
- Review detailed metadata for that event to ensure accurate tracking and correct parameter capture.
Use the Metrics tab to confirm that all goals are firing as expected and that conversion data is being recorded accurately before launching your campaign.
Share the QA Preview
The QA Assistant lets you share your current testing setup with team members or stakeholders, so they can view the exact campaign experience you are validating, without needing to meet the campaign’s targeting conditions.
This is especially useful for collaboration, approvals, and cross-device or cross-browser testing.
To share your QA setup:
- Click the Share link icon located at the top-right of the QA Assistant window.
- Choose one of the following options:
- Copy Preview Link: Share the link with others to open the same preview in their browser.
- Scan QR Code: Use a mobile device to scan and open the preview directly on that device.
The shared preview preserves your current QA configuration, including:
- The selected campaign and variation
- Any forced or overridden campaign states
- The exact experience being tested on the page
This ensures that anyone accessing the link sees the same setup, making it easier to validate behavior, gather feedback, and test across different environments.
Note: The shared link reflects the specific QA state at the time of sharing. Any changes made afterward will require generating a new link.
FAQs
-
Can I use the QA Assistant to test campaigns on mobile devices?
Yes. Use the Share feature to generate a QR code, which you can scan with your mobile device to open the preview in a mobile browser.
-
Does hiding or forcing a campaign in QA Assistant affect live visitors?
No. All actions performed within the QA Assistant are session-based and only affect your local browser view. It has no impact on the experience of actual visitors or the campaign's global data.
Need more help?
For more information or further assistance, contact Wingify Support.