34.1 Overview

The WhatsApp Store Analytics feature allows the store owner to review recorded visitor activity for an individual public WhatsApp Store.

The analytics area is organized into:

Each WhatsApp Store has its own analytics destination. The WhatsApp Stores list provides an Analytics action, and the analytics submenu opens the Overview, Country, Device, Operating System, Browser, and Language reports for the selected store.

WhatsApp Store Analytics can help the business understand:

1. Whether the public store is receiving traffic
2. Which general countries produce activity
3. Whether visitors primarily use mobile or desktop devices
4. Which operating systems and browsers are common
5. Which browser languages are reported
6. Whether marketing efforts are increasing store visits
7. How store activity compares with orders and subscriptions

Analytics should be interpreted as recorded activity rather than as a verified count of individual customers.

34.2 Analytics Access Is Store-Specific

The analytics route is connected to one WhatsApp Store at a time.

The customer analytics destination follows the selected store and is protected by the application’s WhatsApp Store analytics authorization check.

Example:

Traffic from Store A should not automatically appear in Store B’s report.

Confirm the Store Name before interpreting any analytics information.

34.3 What WhatsApp Store Analytics Measures

The feature records technical visitor information associated with public WhatsApp Store activity.

The available reports focus on:

The interface labels the report as WhatsApp Store Analytics and identifies its visitor information as WhatsApp Store Visitors.

The exact information available for a visit depends on what the visitor’s browser, device, and network provide.

34.4 What Analytics Does Not Automatically Prove

A recorded store visit does not prove that the visitor:

1. Viewed every Product
2. Added an item to the cart
3. Opened WhatsApp
4. Sent a WhatsApp message
5. Submitted an order
6. Completed payment
7. Subscribed by email
8. Became a customer
9. Was a different person from every other visit

Analytics records should be compared with operational results such as:

Opening WhatsApp Store Analytics

34.5 Opening the WhatsApp Stores List

From the customer dashboard:

1. Select WhatsApp Stores.
2. Wait for the Store list to load.
3. Locate the Store you want to review.
4. Confirm the Store Name.
5. Locate its Analytics action.

Do not open the VCards Analytics area when the goal is to review a WhatsApp Store.

34.6 Selecting the Analytics Action

The WhatsApp Stores list contains an Analytics link in the Store actions and may also display a visitor-statistics link in its own column.

To open Analytics:

1. Locate the correct Store.
2. Select its chart or Analytics icon.
3. Wait for WhatsApp Store Analytics to open.
4. Confirm that the correct Store is displayed.
5. Begin with Overview.

The Store actions and statistics column both connect to the programmed WhatsApp Store Analytics route.

34.7 Confirming the Store Identity

Before recording or comparing any data, confirm:

This is especially important when the account manages:

1. Several brands
2. Several locations
3. Multiple departments
4. Seasonal Stores
5. Event Stores
6. Duplicated Stores
7. Test and production Stores

A similar Store Name can make it easy to open the wrong report.

34.8 Returning to the Store List

Use the available Back action or select WhatsApp Stores from the dashboard menu.

Returning to the list does not change or delete the analytics records.

Analytics is a reporting function and does not modify the public Store.

Understanding the Analytics Navigation

34.9 Overview

Overview is the main analytics summary.

It is used to review general WhatsApp Store visitor activity and shortened category summaries.

The Overview screen may provide summary sections for:

Use See All where displayed to open the complete report for a category.

34.10 Countries

The Countries report groups recorded visitor activity according to the country detected from available connection information.

Its route is selected through:

34.11 Devices

The Devices report groups activity according to detected device categories.

Its route is selected through:

34.12 Operating Systems

The Operating Systems report displays activity according to the operating system identified from the visitor’s browser information.

Its route is selected through:

34.13 Browsers

The Browsers report groups activity according to detected browser information.

Its route is selected through:

34.14 Languages

The Languages report groups visits according to browser or device language information.

Its route is selected through:

The programmed analytics submenu contains all six destinations: Overview, Countries, Devices, Operating Systems, Browsers, and Languages.

Understanding Store Visitors

34.15 Recorded Visits Versus Unique People

The visitor total should be understood as recorded Store activity.

It should not automatically be described as:

One person may create several recorded visits by:

1. Opening the Store repeatedly
2. Refreshing the page
3. Returning on another day
4. Using more than one device
5. Using several browsers
6. Opening the Store from several shared links
7. Testing Products and policies
8. Returning after a WhatsApp conversation

A count of 500 should therefore be described as:

rather than:

34.16 Internal Testing Can Affect Analytics

Store-owner and staff testing may contribute to the report.

Examples include:

1. Opening Preview
2. Testing the public Store URL
3. Testing a QR code
4. Reviewing template changes
5. Testing Products
6. Checking the cart
7. Testing Store policies
8. Testing on several phones
9. Opening private browser sessions
10. Refreshing after design changes

Maintain a simple record of major testing periods when Analytics is being used for campaign reporting.

34.17 Automated and Nonhuman Activity

Some recorded activity may come from:

1. Search-engine crawlers
2. Social-media preview systems
3. Email security scanners
4. Automated link checkers
5. Messaging-app previews
6. Monitoring services
7. Other automated requests

Do not assume every recorded Store visit represents a potential buyer.

34.18 Visitor Count Does Not Equal Order Count

Example:

The Store did not receive 1,000 orders.

The visit count measures public activity, while WhatsApp Product Orders record submitted purchases.

34.19 Visitor Count Does Not Equal WhatsApp Conversations

A visitor can open the Store without selecting WhatsApp.

A customer can also save the WhatsApp number and return later without reopening the Store.

The Analytics report should not be treated as a complete WhatsApp-message report.

Reviewing the Overview

34.20 Purpose of Overview

Use Overview to obtain a high-level understanding before opening the detailed category reports.

Review:

Look for patterns rather than focusing only on one number.

34.21 Reviewing the Visitor Total

Record the visitor total together with:

1. Date reviewed
2. Store Name
3. Store Alias
4. Major marketing activity
5. Major internal testing
6. Current number of orders
7. Current number of subscribers

Example:

This provides more useful context than retaining the visitor number by itself.

34.22 Using See All

Where the Overview displays only a limited number of results:

1. Locate the category.
2. Select See All.
3. Review the complete report.
4. Return to Overview when finished.

The analytics interface contains a programmed See All label for expanding category summaries.

34.23 Reviewing Patterns Over Time

When reviewing Analytics regularly, compare the current total with a previously recorded baseline.

Example:

This does not establish that all 175 visits came from the campaign unless the Store was used exclusively for that campaign.

34.24 Establishing a Baseline

Before distributing a Store link:

1. Open its Analytics.
2. Record the current visitor total.
3. Record the date and time.
4. Record the current number of orders.
5. Record the current subscriber count.
6. Begin the campaign.
7. Review the same information afterward.

Without a baseline, earlier activity can be confused with campaign results.

Countries Analytics

34.25 Opening Countries

To review country information:

1. Open WhatsApp Store Analytics.
2. Select Countries.
3. Review the displayed countries.
4. Review each country’s recorded activity.
5. Compare the result with the intended Store audience.

34.26 What a Country Result Means

The country result is based on technical location information associated with the visitor’s connection.

It may provide a useful approximation of where activity originated.

It does not prove:

1. Citizenship
2. Nationality
3. Billing address
4. Shipping address
5. Permanent residence
6. Exact physical location
7. Customer identity

34.27 Factors That Can Affect Country Detection

Country information can be influenced by:

A customer in Michigan might appear under another region when using a company network or VPN.

34.28 Using Country Information

Country patterns may help the business review:

1. International shipping availability
2. Currency clarity
3. Telephone country codes
4. Store language
5. Product descriptions
6. Delivery restrictions
7. WhatsApp communication hours
8. Regional legal requirements
9. International payment methods

Use consistent patterns rather than isolated visits when making operational changes.

34.29 International Traffic

When meaningful international traffic appears, review whether the Store clearly explains:

Do not allow international visitors to assume worldwide delivery when the Store serves only one country.

34.30 Unexpected Countries

When unexpected country activity appears:

1. Review recent staff testing.
2. Check whether a VPN was used.
3. Review public social-media sharing.
4. Check whether the Store link was placed on a public website.
5. Review whether search engines can reach the Store.
6. Continue monitoring for a pattern.

One unexpected country is not necessarily a security incident.

34.31 Country Data and Shipping Addresses

Do not use analytics country information to override the customer’s submitted delivery address.

For order fulfillment, use the address confirmed through the WhatsApp Product Order and approved customer communication.

Analytics country information is only a general reporting signal.

Devices Analytics

34.32 Opening Devices

To review device activity:

1. Open WhatsApp Store Analytics.
2. Select Devices.
3. Review the available device categories.
4. Identify the most common device type.
5. Test the Store on that device type.

34.33 Common Device Categories

Depending on the detected information, results may include broad categories such as:

The exact labels depend on the visitor information received by the system.

34.34 Mobile-Dominant Store Traffic

WhatsApp Stores are commonly used on mobile devices because visitors may:

1. Scan a QR code
2. Open a social-media link
3. Open a shared WhatsApp message
4. Select the Store from a VCard
5. Move directly into WhatsApp

When mobile traffic is dominant, prioritize:

34.35 Mobile Cart Testing

Test the complete mobile order process:

1. Open the Store.
2. Browse a category.
3. Open Product Details.
4. Add a Product to the cart.
5. Change its quantity.
6. Add another Product.
7. Review the Order Summary.
8. Select Place Order.
9. Confirm the correct WhatsApp destination.
10. Confirm that the dashboard order is created.

High mobile traffic makes this test especially important.

34.36 Desktop-Dominant Store Traffic

Desktop traffic may occur when the Store is shared through:

1. Email
2. Company websites
3. Online advertisements
4. Professional directories
5. Customer portals
6. Desktop messaging applications
7. Business proposals

Review desktop presentation for:

1. Product grids
2. Image quality
3. Long descriptions
4. Cart layout
5. Policy pages
6. Search and filtering
7. WhatsApp Web behavior

34.37 Tablet Traffic

Tablet visitors may see a layout between mobile and desktop sizes.

Test:

1. Product-grid wrapping
2. Menu navigation
3. Cart controls
4. Popup placement
5. Image cropping
6. Landscape orientation
7. Touch selection

Do not assume that a layout working on a phone will automatically work well on a tablet.

34.38 Device Detection Limitations

A device can be categorized incorrectly when:

1. A phone uses desktop mode
2. A browser changes its identifying information
3. The Store opens inside another application
4. The visitor uses a privacy browser
5. The device is not recognized
6. Automated traffic imitates a device

Use device information as a broad guide.

Operating Systems Analytics

34.39 Opening Operating Systems

To review operating systems:

1. Open WhatsApp Store Analytics.
2. Select Operating Systems.
3. Review the listed systems.
4. Identify the systems with the most activity.
5. Prioritize testing in those environments.

34.40 Possible Operating-System Results

Depending on detected information, the report may contain categories representing:

The actual names displayed depend on the visitor’s browser information and the system’s detection process.

34.41 Android Testing Priorities

When Android activity is significant, test:

1. Public Store loading
2. Category navigation
3. Product images
4. Add to Cart
5. Quantity updates
6. Place Order
7. WhatsApp application opening
8. WhatsApp Web fallback
9. Policy pages
10. Newsletter signup
11. Invoice downloads where applicable

Test more than one Android browser when possible.

34.42 iOS Testing Priorities

When iOS activity is significant, test:

1. Safari Store loading
2. Product navigation
3. Cart behavior
4. Popup behavior
5. WhatsApp opening
6. External links
7. Image display
8. Policy scrolling
9. Email subscription
10. Browser Back behavior after leaving for WhatsApp

34.43 Windows and macOS Testing

For desktop operating systems, test:

1. Product-grid layout
2. Image resolution
3. Cart presentation
4. WhatsApp Web
5. Downloaded invoice files
6. Store sharing controls
7. Search and filters
8. Popup positioning
9. Long policy pages

34.44 Operating System Does Not Identify a Customer

An operating-system result does not tell the business who visited.

One customer may use:

and appear in several operating-system categories.

Do not combine these records to make unsupported identity assumptions.

Browsers Analytics

34.45 Opening Browsers

To review browsers:

1. Open WhatsApp Store Analytics.
2. Select Browsers.
3. Review the detected browser categories.
4. Identify the most common browsers.
5. Test critical Store functions in those browsers.

34.46 Browser Testing Priorities

Test the following functions in the leading browsers:

A Store that loads correctly in one browser may behave differently in another.

34.47 Embedded Browsers

Visitors may open a Store inside browsers built into:

1. WhatsApp
2. Facebook
3. Instagram
4. LinkedIn
5. Gmail
6. QR-scanning applications
7. Other mobile applications

Embedded browsers may handle:

1. Popups
2. Cookies
3. New windows
4. WhatsApp links
5. File downloads
6. Payment links

differently from Safari, Chrome, or another full browser.

34.48 Opening in a Standard Browser

When a visitor experiences a problem inside an embedded browser, an appropriate troubleshooting step is:

1. Open the browser menu.
2. Choose Open in Browser, where available.
3. Continue through the normal device browser.
4. Retry the Store action.

The exact wording depends on the application.

34.49 Unknown Browser

An Unknown or unusual browser result can occur because:

1. Browser identification was withheld
2. Privacy settings changed the information
3. An embedded application opened the Store
4. A new browser is not recognized
5. Automated traffic accessed the page
6. The identification data was incomplete

Do not redesign the Store based on one unknown browser record.

Languages Analytics

34.50 Opening Languages

To review language information:

1. Open WhatsApp Store Analytics.
2. Select Languages.
3. Review the listed language values.
4. Compare them with the intended Store audience.
5. Review whether additional language support is necessary.

34.51 What Language Analytics Represents

Language Analytics generally reflects language information supplied by the visitor’s browser or device.

It does not prove:

1. Native language
2. Spoken language
3. Reading ability
4. Nationality
5. Preferred customer-service language

Use it as a general audience-accessibility signal.

34.52 Examples of Language Differences

A person may:

1. Speak Spanish but use an English-language phone
2. Speak English but use a French office computer
3. Use a shared device
4. Configure several browser languages
5. Open the Store from a translated browser
6. Travel while keeping the device’s normal language

Do not make strong conclusions from one language record.

34.53 Using Language Information

When a consistent language pattern appears, review:

1. Store description
2. Product names
3. Product descriptions
4. Category names
5. Order instructions
6. WhatsApp message wording
7. Shipping Policy
8. Refund Policy
9. Privacy Policy
10. Terms and Conditions

All public legal and operational text should be reviewed accurately before translation.

34.54 Unknown Language

Unknown Language can occur when:

1. No language value was supplied
2. The browser restricted technical information
3. The language code was not recognized
4. An embedded browser was used
5. Automated traffic opened the Store
6. The information was incomplete

Unknown Language does not mean that the visitor cannot read the Store.

Comparing Analytics with Business Outcomes

34.55 Compare Visitors with Orders

A basic estimated order conversion can be calculated as:

Example:

Because recorded visits are not guaranteed unique visitors, treat this as an operational estimate.

34.56 Compare Visitors with Subscribers

A basic estimated subscription conversion can be calculated as:

Example:

This can help determine whether the Store’s newsletter invitation is useful and visible.

34.57 Compare Orders with Delivered Orders

Visitor traffic alone does not measure successful fulfillment.

Review:

Example:

High order activity with a large number of cancellations may indicate:

1. Stock problems
2. Payment problems
3. Delivery limitations
4. Incorrect pricing
5. Customer confusion
6. Duplicate orders
7. Incomplete checkout information

34.58 Compare Analytics with WhatsApp Activity

The built-in Analytics report does not provide a complete WhatsApp conversation report.

The business can maintain an internal summary such as:

This helps identify where customers leave the process.

34.59 No Built-In Product-Level View Report

The available WhatsApp Store Analytics categories are organized around Store visitors and technical audience information.

The report does not provide a standard per-Product analytics tab for:

Use Product Orders, inventory records, external analytics, or a separately developed reporting function when Product-level reporting is required.

34.60 No Built-In Cart Abandonment Report

Analytics does not establish how many visitors:

1. Added an item
2. Removed an item
3. Abandoned the cart
4. Opened WhatsApp but did not send
5. Stopped at Order Summary
6. Failed during payment

Review customer feedback and external tracking when this information is operationally important.

Measuring Marketing Campaigns

34.61 Sharing the Store URL

The Store may be distributed through:

1. VCards
2. QR codes
3. Social media
4. Email
5. WhatsApp messages
6. Websites
7. Printed materials
8. Advertising
9. Events
10. Business directories

When the same Store URL is used everywhere, Analytics combines the resulting Store activity.

It does not provide a standard source-attribution report showing which channel created each visit.

34.62 Store Connected to Multiple VCards

One WhatsApp Store can be connected to more than one VCard.

When visitors open the same Store through several VCards, the Store Analytics report combines the Store activity.

It does not automatically separate visits by the referring VCard.

To measure VCard-specific Store traffic, use:

1. Separate campaign Stores, or
2. Approved external tracking methods

where appropriate.

34.63 QR Code Campaign

A controlled QR campaign can be reviewed using this process:

1. Record the current Store visitor total.
2. Record current orders and subscribers.
3. Publish the QR code.
4. Record the campaign date and location.
5. Review Analytics after the campaign.
6. Review Orders and Subscribers.
7. Compare results with the baseline.
8. Account for internal setup scans.

34.64 Social-Media Campaign

Before publishing a Store link on social media:

1. Record the current Analytics total.
2. Record the publication date.
3. Record the platform and account.
4. Publish the Store link.
5. Review traffic after an appropriate period.
6. Review new orders.
7. Review new subscribers.
8. Review WhatsApp conversations.

Do not assume all new traffic came from the post when the Store was also promoted elsewhere.

34.65 Event Store

For an event-specific Store:

Staff testing before the event should be documented.

34.66 Separate Stores for Separate Campaigns

When accurate campaign separation is important, create a different Store for each major campaign.

Example:

Each Store then receives its own future analytics.

Review all duplicated products, stock, prices, WhatsApp numbers, policies, and branding before distribution.

34.67 One Store Used for All Campaigns

Using one Store everywhere is easier to maintain but limits source analysis.

The built-in report can show combined visitor activity but may not identify whether the visit came from:

Choose the campaign structure before distribution.

Store Changes and Analytics

34.68 Changing the Store Template

Changing the Store template normally changes the visual presentation rather than creating an entirely new Store record.

Analytics associated with the same Store can continue to represent activity before and after the design change.

Record the change date.

Example:

34.69 Changing Products

Adding, editing, or deleting Products does not automatically create a new Analytics history.

Record major Product changes when evaluating Store activity.

Example:

34.70 Changing Store Prices

A traffic increase after a price change does not prove that the price caused the change.

Compare:

1. Visit activity
2. Orders
3. Cancelled orders
4. Customer messages
5. Delivered orders

before reaching a conclusion.

34.71 Changing the Store Alias

The Store Alias forms part of its public URL.

Changing it can make old links and QR codes ineffective.

After an alias change:

1. Open the new Store URL.
2. Test the complete Store.
3. Replace VCard connections where necessary.
4. Replace QR codes.
5. Replace social links.
6. Replace website links.
7. Replace printed materials where possible.
8. Review Analytics for a traffic drop.

A decrease may result from old links rather than reduced customer interest.

34.72 Changing the WhatsApp Number

Changing the WhatsApp Number should not by itself be treated as a new Analytics campaign.

However, it can affect business outcomes if:

1. The new number is not monitored
2. The country code is incorrect
3. Customers cannot open WhatsApp
4. Conversations reach the wrong team
5. Existing customers continue using the old number

Review visits, conversations, and orders after the change.

34.73 Deactivating a Store

When a Store is inactive, ordinary public access may stop or become restricted.

Before deactivation:

1. Record important Analytics totals.
2. Review active orders.
3. Review subscribers.
4. Replace distributed links.
5. Inform customers where appropriate.
6. Preserve required reports.

Deactivation should not be used as a method for clearing Analytics.

34.74 Reactivating a Store

Before reactivating:

1. Review Products.
2. Review Selling Prices.
3. Review Available Stock.
4. Review Store policies.
5. Review the WhatsApp Number.
6. Review Store Alias.
7. Test the public Store.
8. Record the reactivation date.
9. Resume Analytics comparisons from that date.

34.75 Duplicating a Store

A duplicated Store is a separate Store record.

Its future visitor activity should be reviewed through its own Analytics action.

Do not assume the original Store’s previous Analytics automatically belongs to the duplicate.

After duplication:

1. Open the duplicate.
2. Confirm its Store Name.
3. Confirm its Alias.
4. Confirm Products and prices.
5. Confirm stock.
6. Confirm WhatsApp Number.
7. Open the duplicate’s public Store.
8. Open its Analytics.
9. Confirm that testing is recorded under the correct Store.

Analytics and Store Pages

34.76 Store Homepage

The Store homepage can display:

1. Branding
2. Categories
3. Featured Products
4. Store Announcement
5. Offers
6. Business Hours
7. Policies
8. Newsletter signup
9. WhatsApp action

Store Analytics is reported at the Store level rather than as a separate homepage-only report.

34.77 Product Listing Pages

A visitor may browse:

1. All Products
2. One category
3. Search results
4. Filtered Products
5. Sorted Products

The built-in Analytics tabs do not provide a separate Product-listing-page report.

34.78 Product Details Pages

Opening Product Details may contribute to the visitor’s overall Store activity, depending on the application’s recording process.

Do not describe the visitor total as Product Detail views unless that behavior has been specifically tested.

The built-in report does not contain a dedicated Product Details analytics tab.

34.79 Policy Pages

Visitors may open:

The Analytics report does not separately identify how many visitors read each policy page.

Do not treat a Store visit as proof that a customer read every policy.

Require appropriate policy agreement in the order workflow where applicable.

Responsible Analytics Interpretation

34.80 Use Analytics as Directional Information

Analytics can indicate general patterns such as:

It should not be used to make unsupported claims about individual people.

34.81 Small Sample Sizes

Example:

This is not enough information to redesign the Store’s entire international strategy.

Wait for a more meaningful amount of activity and compare several periods.

34.82 Do Not Identify Visitors from Technical Categories

An inappropriate conclusion would be:

The one iPhone visitor from Canada must be a specific customer.

Country, device, browser, operating system, and language information do not establish identity.

Use submitted Orders, Subscribers, and approved WhatsApp conversations for customer information.

34.83 Analytics Data and Customer Data

Analytics data is different from information intentionally submitted through an order.

Analytics

May include:

WhatsApp Product Order

May include:

Do not substitute one type of information for the other.

Privacy

34.84 Store Privacy Policy

The WhatsApp Store Privacy Policy should accurately explain Analytics use where applicable.

It may need to address:

1. Recording public Store visits
2. General device information
3. Browser information
4. Operating-system information
5. Approximate country information
6. Language information
7. Cookies or similar technologies
8. External analytics providers where used
9. Purpose of analytics
10. Retention

The policy should reflect the actual configuration and business practices.

34.85 External Analytics

Custom Analytics or tracking code may be added through other Store configuration methods where supported.

External analytics can produce reports different from the built-in WhatsApp Store Analytics.

Differences may result from:

1. Cookie consent
2. Tracking prevention
3. Script blocking
4. Bot filtering
5. Date boundaries
6. Time zones
7. Recording methods
8. Custom code errors

Do not expect two analytics systems to show identical totals.

34.86 Protect Analytics Access

Only authorized account users should review Store Analytics.

Analytics can reveal confidential business patterns such as:

1. Campaign performance
2. Customer regions
3. Store growth
4. Device trends
5. Product-launch activity

Remove dashboard access when an employee or contractor no longer requires it.

Analytics Limitations

34.87 No Individual Visitor List

The Analytics area does not provide a directory of individual visitors.

Use:

for information intentionally supplied by customers.

34.88 No Standard Click Report

The built-in categories do not provide a standard report showing how many visitors selected:

1. Add to Cart
2. Remove from Cart
3. Place Order
4. WhatsApp
5. Newsletter Subscribe
6. Product category
7. Product Detail
8. Social-share button
9. Policy link

Additional tracking would be required for those specific actions.

34.89 No Standard Referrer Report

The Analytics navigation does not include a standard report for:

Use separate Store campaigns or approved external tracking when source attribution is necessary.

34.90 No Automatic Revenue Report

The visitor report does not calculate:

1. Revenue
2. Average order value
3. Profit
4. Cost per visitor
5. Cost per order
6. Refund total
7. Sales by country
8. Sales by browser
9. Sales by device

Use WhatsApp Product Orders and the approved accounting process for financial reporting.

34.91 No Standard Analytics Export

The inspected customer analytics interface does not present a standard PDF, XLS, or CSV export action.

To preserve a report:

1. Record the Store Name.
2. Record the date.
3. Record the visitor total.
4. Record leading category results.
5. Record Orders and Subscribers.
6. Save an approved screenshot where permitted.
7. Enter the information into an authorized business report.

34.92 No Standard Reset Control

The customer Analytics area does not provide an ordinary Reset or Clear History action.

Do not delete or alter data directly to start a new campaign.

Use a new campaign Store when a separate Analytics history is required.

Recommended Reporting Process

34.93 Weekly Review

A practical weekly review is:

1. Open the Store’s Analytics.
2. Confirm the Store identity.
3. Record the visitor total.
4. Review Countries.
5. Review Devices.
6. Review Operating Systems.
7. Review Browsers.
8. Review Languages.
9. Review new Orders.
10. Review Store Subscribers.
11. Review delivered and cancelled orders.
12. Record major Store changes.

34.94 Monthly Store Report

A simple report can contain:

34.95 Example Monthly Report

34.96 Reviewing Store Performance

Use several indicators together.

Example:

Month 2 has more traffic but weaker order and delivery outcomes.

Possible areas to review include:

1. Product availability
2. Pricing
3. Shipping restrictions
4. Cart usability
5. WhatsApp response time
6. Payment process
7. Customer qualification
8. Duplicate orders

34.97 Comparing Two Stores

Use the same reporting period.

Example:

Also consider differences in:

1. Number of Products
2. Product prices
3. Marketing distribution
4. Store age
5. Intended audience
6. Shipping area
7. Brand recognition
8. Available Stock

Higher traffic does not automatically mean better performance.

Troubleshooting Analytics

34.98 Analytics Action Is Missing

Confirm that:

1. The correct account is signed in.
2. WhatsApp Stores loaded completely.
3. The selected Store belongs to the account.
4. The Actions area is visible.
5. The table is not too narrow.
6. The Analytics icon is not inside an overflow menu.
7. The page was refreshed.
8. The user has appropriate Store access.

On a smaller screen, scroll horizontally or open the Store’s action menu.

34.99 Analytics Page Will Not Open

Confirm that:

1. The Store still exists.
2. The account session is active.
3. The correct Store was selected.
4. The Store belongs to the current account.
5. The internet connection is working.
6. The Analytics action was selected only once.
7. Browser extensions are not blocking the page.
8. The account is authorized to view that Store’s Analytics.

The route uses a Store-specific analytics authorization check, so a user should not expect to open reports for an unrelated Store.

34.100 Analytics Shows No Visitors

Confirm that:

1. The public Store is active.
2. The public URL works.
3. The correct Store Analytics page is open.
4. The Store was opened publicly.
5. The page loaded completely.
6. Internal testing was performed while signed out.
7. The Analytics page was refreshed.
8. The correct Store Alias was used.

Perform one controlled test before creating repeated visits.

34.101 Controlled Visitor Test

Use this process:

1. Record the current visitor total.
2. Open a new private browser window.
3. Open the public Store URL once.
4. Wait for the Store to load completely.
5. Browse normally.
6. Close the private window.
7. Return to Store Analytics.
8. Refresh the report.
9. Compare the total.

The recording may not always appear instantly, so avoid repeated refreshing until the first test has been reviewed.

34.102 Visitor Count Is Higher Than Expected

Possible causes include:

1. Staff testing
2. Repeated customer openings
3. QR-code setup scans
4. Social-media previews
5. Email security scanners
6. Search-engine crawlers
7. Automated traffic
8. Several devices used by one person
9. Customers returning to review Products

Interpret the total as recorded activity.

34.103 Country Looks Incorrect

Country detection can be affected by:

Do not change an order’s shipping country based on Analytics.

34.104 Device Looks Incorrect

A device may be classified unexpectedly when:

1. Desktop mode is active
2. The Store is opened in an embedded browser
3. The browser hides its information
4. A new device is not recognized
5. Automated traffic imitates a device

Use the result as an estimate.

34.105 Operating System Is Unknown

Unknown operating systems can result from:

1. Privacy restrictions
2. Embedded applications
3. Modified browser information
4. Specialized devices
5. Automated requests
6. New operating-system releases

Confirm that the Store itself still works correctly.

34.106 Browser Is Unknown

Open the Store in a standard browser and repeat the controlled test.

When a standard browser is recognized but an embedded application is not, the unusual result may be caused by the embedded browser.

34.107 Language Is Unknown

Unknown language information can occur when the visitor’s browser does not provide a usable language value.

Confirm that:

1. Store text appears correctly.
2. Product descriptions are readable.
3. The intended Store language is configured.
4. Legal policies appear in the intended language.

34.108 Analytics Appears Under the Wrong Store

Confirm:

1. The public Store URL
2. Store Alias
3. QR code
4. Shared social link
5. VCard Store connection
6. Duplicated Store identity
7. Store selected in the dashboard

Replace incorrect distributed links.

34.109 Traffic Dropped After an Alias Change

Review every location where the old URL may still exist:

Open the old URL and determine whether visitors receive an error.

34.110 Analytics Did Not Separate VCard Sources

This is expected when several VCards connect to the same WhatsApp Store.

The Store Analytics report is associated with the Store, not with a separate source report for every VCard.

Use different Stores or external campaign tracking where source separation is essential.

34.111 Orders Increased but Visitors Did Not

Possible explanations include:

1. Returning visitors placed orders without creating the expected additional records
2. Customers continued through WhatsApp later
3. Orders were created manually or through another flow
4. Analytics was delayed
5. The wrong reporting periods were compared
6. The wrong Store Analytics report was open

Review Store URLs, Order IDs, and dates.

34.112 Visitors Increased but Orders Did Not

Review:

1. Product availability
2. Selling Prices
3. Product descriptions
4. Product images
5. Store speed
6. Cart usability
7. Place Order action
8. WhatsApp Number
9. Shipping restrictions
10. Payment instructions
11. Mobile presentation
12. Customer confidence
13. Store policies

Traffic alone does not guarantee purchases.

34.113 Visitors Increased but Subscribers Did Not

Review:

1. Email subscription visibility
2. Popup timing
3. Signup wording
4. Privacy explanation
5. Mobile popup design
6. Subscribe button
7. Success response
8. Whether the Store offers a useful reason to subscribe

34.114 Analytics Does Not Show Product Views

This is expected because the available Analytics categories do not include a Product-level view report.

Use controlled external tracking or a separately implemented report where Product view measurement is required.

34.115 Analytics Cannot Be Exported

When no export action appears:

1. Record the report manually.
2. Save authorized screenshots where appropriate.
3. Preserve the Store Name and reporting date.
4. Store the report securely.
5. Do not change database data directly.

34.116 Analytics Checklist

Before relying on WhatsApp Store Analytics, confirm that:

1. The correct Store is open.
2. The Store is active.
3. The public Store URL works.
4. The Analytics action opens.
5. Overview is reviewed first.
6. Countries is reviewed as an estimate.
7. Devices is reviewed.
8. Operating Systems is reviewed.
9. Browsers is reviewed.
10. Languages is reviewed.
11. Unknown values are interpreted cautiously.
12. Visitor totals are not described as guaranteed unique people.
13. Internal testing activity is considered.
14. Automated traffic is considered.
15. Analytics is compared with Product Orders.
16. Analytics is compared with Subscribers.
17. Analytics is compared with delivered and cancelled orders.
18. Mobile Store behavior is tested.
19. Desktop Store behavior is tested.
20. Embedded-browser behavior is considered.
21. Campaign baselines are recorded.
22. Separate Stores are used where campaign separation is needed.
23. Alias changes are documented.
24. Duplicated Stores use their own Analytics.
25. Store Analytics is distinguished from VCard Analytics.
26. Store Analytics is not treated as a product-view report.
27. Store Analytics is not treated as a revenue report.
28. Store Analytics is not treated as a WhatsApp-message report.
29. Privacy policies explain Analytics use accurately.
30. Analytics access is restricted to authorized users.
31. Reports are preserved through an approved process when needed.
32. Historical Analytics is not expected to have a standard reset control.

Chapter Completion

At the end of this chapter, the user should understand how to open WhatsApp Store Analytics, review Overview, Countries, Devices, Operating Systems, Browsers, and Languages, interpret recorded Store visitors responsibly, compare traffic with orders and subscribers, measure campaign activity, and troubleshoot missing or unexpected analytics information.