33.1 Overview

The VCard Analytics feature allows the card owner to review how often a public digital card is being opened and learn general information about the devices and environments used by its visitors.

The analytics area organizes visitor activity into:

The VCards management screen includes a line-chart icon that opens the analytics page for the selected card. It also contains a view-count column based on the analytics records associated with that VCard.

33.2 What VCard Analytics Helps You Understand

VCard Analytics can help answer questions such as:

1. Is the digital card receiving visits?
2. Did traffic increase after an event or campaign?
3. Which countries produce the most activity?
4. Are most visitors using phones or computers?
5. Which operating systems and browsers are common?
6. Which browser languages are reported?
7. Is one VCard receiving more traffic than another?

Analytics should be used to identify patterns rather than to make unsupported conclusions about individual visitors.

33.3 What VCard Analytics Does Not Replace

The built-in analytics area should not be treated as a complete website analytics, customer relationship management, or advertising-attribution system.

Do not assume that it provides:

Use the built-in data for VCard-level visitor monitoring and general audience insights.

Opening VCard Analytics

33.4 Opening Analytics from the VCards List

To open analytics:

1. Sign in to the customer dashboard.
2. Select VCards.
3. Locate the desired digital card.
4. Find the line-chart icon in the card’s Actions area.
5. Select the icon.
6. Wait for the VCard Analytic page to open.

The application uses a dedicated analytics destination for each VCard rather than one combined report for every card. The customer analytics route is connected to the selected VCard and opens through the chart-line action.

33.5 Confirm the Correct VCard

Before interpreting the report, confirm that the analytics page belongs to the intended card.

This is particularly important when an account manages:

Analytics from one VCard should not automatically be treated as activity for another.

33.6 Returning to the VCards List

Use the page’s Back action or return to VCards through the dashboard navigation.

Do not use the browser Back button repeatedly when an analytics chart is still loading because it may cause unnecessary page reloads.

Understanding the VCard View Count

33.7 View-Count Badge

Depending on the selected VCards table layout, a numeric badge may appear for each card.

The badge is generated by counting the analytics records associated with that VCard:

The programmed view-count column uses the VCard’s related analytics-record count.

33.8 View Count Is Not Guaranteed Unique Visitors

Do not interpret the count as a verified number of different people.

One person may open the card:

1. More than once
2. On several days
3. On a phone and computer
4. Through multiple browsers
5. After scanning the QR code repeatedly
6. During testing

Each recorded visit can contribute to the analytics total.

A count of 100 should therefore be understood as approximately:

rather than:

33.9 Your Own Visits May Affect the Count

Opening the public VCard while testing may contribute to its visitor activity.

Testing can include:

1. Opening Preview
2. Scanning the QR code
3. Testing a custom domain
4. Opening the card on several phones
5. Refreshing the public page
6. Checking template changes
7. Testing from a private browser window

Keep a record of major internal tests when precise campaign comparisons are important.

33.10 Repeated Refreshes

Repeatedly refreshing the public card can potentially create additional analytics records.

Avoid repeatedly refreshing a live VCard merely to increase or test its count.

For controlled testing:

1. Record the current count.
2. Open the public VCard once.
3. Wait for the page to load fully.
4. Return to Analytics.
5. Refresh the report.
6. Compare the count.

The exact recording behavior can depend on the public page request and analytics-processing logic.

Analytics Navigation

33.11 Analytics Sections

The analytics interface is organized into separate sections for:

The default section is Overview when no specific analytics category has been selected. Separate analytics destinations use the country, device, operating-system, browser, and language categories. The source also contains a dedicated VCard analytics view and VCard analytics submenu.

33.12 Selecting a Section

To review a category:

1. Open the VCard’s Analytics page.
2. Select the desired tab.
3. Wait for the category information to load.
4. Review the displayed totals or chart.
5. Return to Overview when finished.

Changing tabs does not change the public VCard.

It only changes the analytics information being reviewed.

Analytics Overview

33.13 Overview Purpose

The Overview section provides the main summary of the VCard’s visitor activity.

It may contain:

1. Total visitor activity
2. A visitor chart
3. Time-based traffic information
4. Summary information for visitor categories
5. Links to see additional category details

Use Overview as the starting point before reviewing individual countries, devices, browsers, operating systems, or languages.

33.14 Visitor Activity Chart

The analytics controller prepares data for the selected VCard and uses a separate chart-data operation to supply chart information.

The chart is intended to show how recorded visits changed over time rather than displaying only one lifetime total.

Use it to identify:

33.15 Reading the Chart

A typical visitor chart contains:

A higher point indicates more activity during that period.

A lower point indicates less activity.

Do not assume that every increase represents new customers. A spike can also result from:

1. Internal testing
2. A link being shared repeatedly
3. Automated traffic
4. One person reopening the card
5. A public event
6. A social-media post
7. A QR code campaign
8. An email distribution

33.16 Date or Period Selection

Where a date or period control is displayed:

1. Select the desired starting and ending period.
2. Apply the selection.
3. Wait for the chart to reload.
4. Confirm the date labels.
5. Compare the new result with the previous period.

Use the same period when comparing two VCards.

Example:

Comparing one card’s monthly total with another card’s yearly total would be misleading.

33.17 No Data in a Period

A blank or zero-value chart can mean:

1. The card received no recorded visits.
2. The selected dates are before the card was created.
3. The selected period is too narrow.
4. The wrong VCard is open.
5. The card was inactive.
6. The public link was not distributed.
7. The chart did not load properly.

Expand the selected period and refresh the analytics page before concluding that the card has never been visited.

33.18 Using See All

The interface language includes a See All action for analytics summaries.

Where displayed, select See All to open the complete category report rather than relying only on the limited Overview preview.

For example:

Countries Analytics

33.19 Countries Section

The Countries section groups recorded visitor activity by country.

This can help determine whether the VCard is reaching:

1. Local visitors
2. National visitors
3. International visitors
4. Intended campaign regions
5. Unexpected locations

Country information should be treated as an estimate rather than a verified mailing or physical address.

33.20 Opening Countries

To review country information:

1. Open the VCard’s Analytics page.
2. Select Countries.
3. Review the listed countries.
4. Review the number or proportion connected to each country.
5. Compare the results with the intended audience.

33.21 Interpreting Country Information

A country result is generally derived from technical information associated with the visitor’s connection.

It does not prove:

1. Citizenship
2. Nationality
3. Home address
4. Business location
5. Current street location
6. Permanent residence

A visitor can appear under another country because of:

33.22 Using Country Information Operationally

Country patterns can help with decisions such as:

1. Which language versions may be useful
2. Whether international telephone codes are needed
3. Which appointment time zones should be considered
4. Whether shipping policies need international coverage
5. Whether prices need clearer currency labels
6. Whether international visitors need separate contact instructions

Do not change business policies based on one or two uncertain records.

33.23 Unexpected Country Activity

When an unexpected country appears:

1. Confirm whether staff tested from a VPN.
2. Confirm whether an employee was traveling.
3. Review recent public distributions.
4. Review social-media sharing.
5. Check whether the VCard link was publicly indexed.
6. Continue monitoring the pattern.

One unexpected visit does not necessarily indicate unauthorized access.

Devices Analytics

33.24 Devices Section

The Devices section groups visitor activity according to the type of device reported by the visitor’s browser or user agent.

Typical distinctions can include mobile devices, computers, tablets, or other detected categories.

The exact labels depend on the technical information received from each visit.

33.25 Opening Devices

To review device activity:

1. Open VCard Analytics.
2. Select Devices.
3. Review the displayed device categories.
4. Identify the categories with the highest activity.
5. Test the VCard on the most commonly used devices.

33.26 Mobile-Dominant Traffic

When most visits appear to come from mobile devices, prioritize:

A digital business card is frequently opened through QR code scans, which commonly occur on phones.

33.27 Desktop-Dominant Traffic

Desktop activity may be common when the VCard is distributed through:

1. Email signatures
2. Business proposals
3. Online directories
4. Desktop messaging platforms
5. Company websites
6. Professional portals

Confirm that long descriptions, Galleries, Blogs, and Iframes display properly on larger screens.

33.28 Device Data Is an Estimate

Device detection depends on the technical information sent by the visitor’s browser.

It may be affected by:

1. Browser privacy controls
2. Desktop mode on a phone
3. Tablet browser behavior
4. Modified user-agent information
5. Embedded browsers
6. Automated traffic
7. New or unsupported devices

Do not assume every device classification is exact.

Operating Systems Analytics

33.29 Operating Systems Section

The Operating Systems section groups visits according to the operating system reported by the visitor’s device or browser.

Possible results may represent environments such as:

The exact names shown depend on the detected data.

33.30 Opening Operating Systems

To review operating systems:

1. Open VCard Analytics.
2. Select Operating Systems.
3. Review the listed systems.
4. Identify the most common environments.
5. Test important VCard actions on those environments.

33.31 Using Operating-System Information

Operating-system patterns can guide testing priorities.

For example:

Strong iOS Activity

Test:

1. Add to Contact on iPhone
2. Telephone links
3. Email links
4. Apple browser behavior
5. QR scanning
6. Calendar and appointment functions

Strong Android Activity

Test:

1. VCF downloading and import
2. WhatsApp links
3. Product forms
4. Payment redirects
5. Browser compatibility

Strong Windows or macOS Activity

Test:

1. Desktop layout
2. Downloaded files
3. Contact imports
4. Iframes
5. External links
6. PDF documents

33.32 Operating System Is Not Device Ownership

An operating-system result does not identify the person who owns the device.

It also does not prove that the same visitor uses only that operating system.

One person may appear through several devices and systems.

Browser Analytics

33.33 Browsers Section

The Browsers section groups recorded visits according to the browser reported during the public VCard request.

Browser information can help identify where compatibility testing should be concentrated.

33.34 Opening Browsers

To review browser activity:

1. Open VCard Analytics.
2. Select Browsers.
3. Review the browser categories.
4. Identify the most frequently reported browsers.
5. Test the VCard using those browsers.

33.35 Browser Testing Priorities

Review important functions in the leading browsers shown by the report:

A card that works in one browser may behave differently in another.

33.36 Embedded Browsers

A visitor may open the VCard inside an embedded browser from:

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

An embedded browser may be classified differently from the device’s normal browser.

When a function fails inside an embedded browser, instruct the visitor to open the page in their standard browser when appropriate.

33.37 Unknown or Unusual Browser Names

Unknown browser information can occur when:

1. The browser withholds identifying information.
2. A privacy tool modifies the user agent.
3. The VCard is opened through an application.
4. Automated traffic accesses the page.
5. A new browser is not recognized.
6. The analytics parser cannot classify the value.

Do not alter the VCard solely because one unusual browser entry appears.

Languages Analytics

33.38 Languages Section

The Languages section groups visits according to language information reported by the visitor’s browser or device.

The system’s interface includes both Languages and Unknown Language analytics labels.

33.39 Opening Languages

To review language information:

1. Open VCard Analytics.
2. Select Languages.
3. Review the listed languages.
4. Identify the most frequently reported values.
5. Compare them with the VCard’s intended audience.

33.40 Browser Language Versus Spoken Language

The analytics language should not automatically be treated as the visitor’s preferred or spoken language.

It generally reflects technical browser or device settings.

For example, a visitor may:

1. Speak Spanish but use an English browser.
2. Speak English but use a French company computer.
3. Use a shared device.
4. Have several browser languages configured.
5. Travel while keeping their normal device language.

Use language analytics as a general accessibility signal.

33.41 Unknown Language

Unknown Language can appear when the application cannot determine a usable language value.

Possible reasons include:

1. Missing browser-language information
2. Privacy controls
3. Automated traffic
4. Unsupported language codes
5. Embedded browser behavior
6. Incomplete technical data

Unknown Language does not mean the visitor has no language preference.

33.42 Using Language Information

Consistent language patterns may indicate a need to review:

1. VCard localization
2. Alternate-language descriptions
3. Appointment instructions
4. Product descriptions
5. Terms and policies
6. Telephone support
7. External linked pages

Do not publish automatically translated legal policies without appropriate review.

Comparing VCards

33.43 Compare Similar Time Periods

When comparing two VCards:

1. Open the first card’s Analytics.
2. Select the desired period.
3. Record the visit total and major categories.
4. Open the second card’s Analytics.
5. Use the same period.
6. Compare the results.

A fair comparison uses consistent dates and similar distribution conditions.

33.44 Consider Distribution Differences

A VCard may receive more visits because it was:

1. Shared more frequently
2. Placed in an email signature
3. Printed on marketing materials
4. Used at an event
5. Connected to an NFC card
6. Included in social-media posts
7. Used by a larger department
8. Promoted through a QR code

Higher traffic does not automatically mean the card design is better.

33.45 Compare Outcomes, Not Only Visits

Traffic should be reviewed with operational outcomes such as:

Example:

VCard B may be producing stronger engagement even though it has fewer visits.

The built-in analytics screen does not automatically calculate every conversion rate, so these comparisons may need to be recorded manually.

33.46 Basic Conversion Calculation

A simple manual inquiry conversion estimate can be calculated as:

Example:

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

Measuring QR Code and Campaign Activity

33.47 QR Code Distribution

Analytics can help determine whether a distributed VCard QR code is being used.

A controlled process is:

1. Record the VCard’s current visitor count.
2. Distribute the QR code.
3. Record the distribution date.
4. Review Analytics after the event or campaign.
5. Compare the activity before and after.
6. Review resulting Contacts, Inquiries, and Appointments.

33.48 Event Campaigns

For an event:

Remember that staff testing and event setup scans can also contribute to the count.

33.49 Separate VCards for Separate Campaigns

When precise campaign separation is important, create a distinct VCard for each major campaign.

Example:

Each card then has its own analytics records.

Duplicating one card and assigning a unique alias can make campaign reporting easier, provided all duplicated information is reviewed before distribution.

33.50 One VCard Shared Everywhere

When the same public VCard URL is used in email, social media, print, NFC, and QR codes, the built-in analytics report combines those visits.

It does not necessarily identify which individual distribution source created each visit.

Use separate VCards or appropriately configured external campaign tracking when source attribution is required.

Analytics and VCard Changes

33.51 Template Changes

Changing the VCard template does not normally create a separate analytics history.

The card remains the same VCard record when its template is changed.

Traffic before and after the design change may therefore appear in the same analytics report.

Record the date of the change when evaluating its effect.

33.52 Content Changes

The same principle applies when changing:

1. Headline
2. Profile image
3. Services
4. Products
5. Banner
6. Call-to-action wording
7. Appointment settings
8. Inquiry form
9. Social links

Create an internal change log.

Example:

Then compare traffic and operational outcomes around those dates.

33.53 Changing the VCard Alias

Changing the public URL alias can affect traffic because previously distributed links may stop leading visitors to the intended destination.

After an alias change:

1. Test the new URL.
2. Update QR codes.
3. Update email signatures.
4. Update NFC destinations where applicable.
5. Update social links.
6. Monitor Analytics for unexpected traffic changes.

A traffic decrease after an alias change may result from old links rather than reduced interest.

33.54 Deactivating the VCard

When a VCard is inactive, normal public traffic may stop because visitors cannot access the card as intended.

Existing analytics records should still be treated as historical data for that VCard.

Before deactivation:

1. Record important totals.
2. Review recent activity.
3. Preserve any necessary operational report.
4. Confirm that distributed links will be replaced.

33.55 Duplicating a VCard

A duplicated VCard is a separate card with its own identity and future analytics.

Do not combine the original card’s previous analytics with the duplicate’s new analytics unless doing so manually for a broader business report.

After duplication:

1. Confirm the duplicate’s alias.
2. Confirm the public information.
3. distribute only the duplicate’s URL or QR code.
4. Open its Analytics page.
5. Confirm that testing appears under the correct card.

Custom Domains and Analytics

33.56 Custom-Domain Traffic

A VCard may be displayed through its standard public URL or an approved custom domain.

The VCards list can produce a public preview URL based on the active custom-domain configuration.

When using a custom domain:

1. Record the current analytics count.
2. Open the custom-domain VCard once.
3. Allow the page to load fully.
4. Return to Analytics.
5. Confirm whether the visit is recorded.
6. Repeat the test with the standard URL only when necessary.

This verifies the behavior of the actual configured installation rather than assuming both access paths behave identically.

33.57 Redirects and Old Links

Redirects, custom domains, and old aliases may affect:

1. Whether the card loads
2. Which card receives the visit
3. Whether the analytics request completes
4. Whether visitors reach an error page

Test every public address used in marketing.

Built-In Analytics Versus Google Analytics

33.58 Two Separate Analytics Functions

The system has two analytics-related functions:

Built-In VCard Analytics

Opened from the line-chart icon in the VCards list.

It presents VCard visitor information such as Countries, Devices, Operating Systems, Browsers, and Languages.

Google Analytics Field

Configured inside the VCard’s SEO section.

The SEO editor contains a dedicated Google Analytics text area where approved tracking code can be entered.

These functions should not be treated as the same report.

33.59 Built-In Analytics

Use built-in analytics for:

The information is reviewed directly through the Book dashboard.

33.60 Google Analytics

Google Analytics can provide additional external reporting when configured correctly.

Its information is reviewed through the applicable Google Analytics property rather than through the Book VCard Analytics tabs.

The Google Analytics field should contain only approved tracking code or configuration intended for that VCard.

33.61 Totals May Differ

Built-in analytics and Google Analytics may show different totals because they can use different:

1. Recording methods
2. Privacy controls
3. Cookie behavior
4. Filtering rules
5. Bot filtering
6. Time zones
7. Date boundaries
8. Script-loading requirements
9. Consent settings

Do not expect the totals to match exactly.

33.62 Avoid Duplicate Google Tracking

Do not place the same tracking configuration repeatedly in several locations without understanding the result.

Duplicate tracking can produce repeated page events or inaccurate external reports.

Review:

1. VCard SEO Google Analytics field
2. Global analytics settings
3. Custom JavaScript
4. Tag manager configuration
5. Iframe tracking
6. Custom-domain tracking

Privacy and Responsible Use

33.63 Analytics and the Privacy Policy

The VCard Privacy Policy should accurately explain visitor analytics when the organization uses it.

It may need to describe:

1. That public visits are recorded
2. General device and browser information
3. Approximate country information
4. Language information
5. External analytics services
6. Cookies or similar technologies where applicable
7. Purpose of analytics
8. Retention practices

The policy should reflect actual system use.

33.64 Do Not Attempt to Identify Individuals

Country, device, browser, operating system, and language information should not be combined to make unsupported claims about a specific person.

Example of an inappropriate conclusion:

One iPhone visit from Canada must have been a particular customer.

The data does not establish that identity.

33.65 Analytics Are Directional

Use the information to identify general direction:

Do not treat small samples as statistically conclusive.

33.66 Small Sample Sizes

Example:

It would be premature to redesign the entire VCard for Country A based only on four recorded visits.

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

33.67 Retention and Access

Analytics information should be accessible only to authorized account users.

Do not publish internal analytics screenshots containing sensitive business information without approval.

When an employee leaves:

1. Review their dashboard access.
2. Remove unnecessary organization access.
3. Preserve required business reports.
4. Protect all customer and visitor information.

Analytics Limitations

33.68 No Individual Visitor Directory

The built-in analytics page is not a visitor-contact directory.

Use:

for visitor information that was intentionally submitted through those workflows.

33.69 No Built-In Click Report

The category tabs do not establish that a visitor selected:

1. Telephone
2. Email
3. WhatsApp
4. Service
5. Product
6. Banner
7. Payment Link
8. Appointment
9. Custom Link

A recorded visit only confirms applicable public-card activity, not every subsequent action.

33.70 No Automatic Sales Attribution

An order or appointment received after a VCard visit may have resulted from that card, but the built-in analytics screen does not automatically prove the full customer journey.

Use source questions, CRM records, separate campaign cards, or external analytics when detailed attribution is needed.

33.71 No Standard Analytics Export

The inspected customer analytics workflow does not provide a standard PDF, Excel, or CSV export action like the VCard Contacts feature.

To retain an operational snapshot:

1. Record the date range.
2. Record the total.
3. Record the leading categories.
4. Save an authorized screenshot where appropriate.
5. Enter the information into an approved report.

Do not modify database records directly to create an unsupported export.

33.72 No Standard Reset Button

The customer analytics interface does not provide an ordinary reset or clear-history action.

Historical data should not be deleted merely to begin a new campaign.

Use a separate campaign VCard when a clean reporting history is required.

Recommended Analytics Review Process

33.73 Weekly Review

A practical weekly process is:

1. Open the VCard’s Overview.
2. Record the current activity.
3. Review Countries.
4. Review Devices.
5. Review Operating Systems.
6. Review Browsers.
7. Review Languages.
8. Compare Contacts and Inquiries.
9. Compare Appointments and Orders.
10. Record any major campaign or VCard changes.

33.74 Monthly Report

A simple monthly report may contain:

33.75 Example Analytics Review

This type of report connects traffic with business outcomes.

33.76 Establish a Baseline

Before beginning a campaign:

1. Record the current visit count.
2. Record the current date.
3. Record existing Contacts, Inquiries, and Appointments.
4. Begin the campaign.
5. Review the same information afterward.
6. Calculate the change.

Without a baseline, it may be difficult to separate new campaign activity from previous traffic.

Troubleshooting Analytics

33.77 Analytics Icon Is Missing

Confirm that:

1. The correct customer account is open.
2. The VCards page loaded completely.
3. The card belongs to the current account.
4. The user has appropriate access.
5. The browser is not hiding Actions.
6. The table is not too narrow.
7. The chart icon is not inside an overflow area.
8. The page was refreshed.

On a small screen, scroll horizontally or open the card’s action area.

33.78 Analytics Page Will Not Open

Confirm that:

1. The VCard still exists.
2. The account is signed in.
3. The session has not expired.
4. The selected card belongs to the account.
5. The internet connection is active.
6. The chart icon was selected only once.
7. Browser extensions are not blocking scripts.

Sign out and sign back in when the session appears invalid.

33.79 Analytics Shows Zero

Confirm that:

1. The public VCard is active.
2. The correct URL was distributed.
3. The correct VCard Analytics page is open.
4. The selected period includes the present date.
5. The card was opened publicly.
6. The page loaded fully during testing.
7. The report was refreshed after the test.

Do not create repeated public visits until one controlled test has been evaluated.

33.80 Count Does Not Change Immediately

Possible reasons include:

1. The report needs to be refreshed.
2. The public page did not load completely.
3. The analytics request was interrupted.
4. Browser privacy controls affected processing.
5. Cached report data is still displayed.
6. The wrong card was tested.
7. The selected period excludes the test.

Wait briefly, reload Analytics, and confirm the correct VCard.

33.81 Count Is Higher Than Expected

Possible causes include:

1. Repeated internal testing
2. Repeated visitor openings
3. QR code setup scans
4. Social sharing
5. Email security scanners
6. Automated traffic
7. Several devices used by one person
8. Public search-engine access
9. Custom-domain testing

Treat the count as recorded activity, not a verified head count.

33.82 Country Is Incorrect

Country detection may be affected by:

1. VPN
2. Proxy
3. Mobile carrier
4. Corporate gateway
5. Travel
6. Privacy services
7. Network-routing location

Do not manually alter the result merely because it differs from the visitor’s known address.

33.83 Device Is Incorrect

A phone may appear differently when:

1. Desktop mode is enabled.
2. An embedded browser is used.
3. User-agent data is modified.
4. The device is newly released.
5. A privacy browser reduces identification.
6. Automated traffic imitates a device.

Use the data as a broad category.

33.84 Operating System Is Unknown

Confirm whether the visitor used:

1. An embedded application
2. A privacy browser
3. A specialized device
4. A new operating-system version
5. Automated software

Unknown operating-system records do not necessarily indicate an error in the VCard.

33.85 Browser Is Unknown

Test the card through a standard browser such as the device’s normal web browser.

When the standard browser appears correctly but an embedded browser does not, the issue may be the embedded application’s reported information.

33.86 Language Is Unknown

Unknown Language can result from missing or unsupported browser-language information.

Confirm that the VCard itself still displays the intended language correctly.

Visitor analytics language and VCard display language are separate concepts.

33.87 Chart Does Not Load

Confirm that:

1. The page finished loading.
2. JavaScript is enabled.
3. Browser extensions are not blocking charts.
4. The selected period is valid.
5. The internet connection is stable.
6. The browser console is not required for ordinary user operation.
7. Another browser can display the report.
8. The card has analytics records.

Refresh the page once before escalating the issue.

33.88 Category Tabs Do Not Respond

Try:

1. Refreshing the analytics page.
2. Opening Overview first.
3. Selecting one category at a time.
4. Using another browser.
5. Signing out and back in.
6. Confirming that the URL changes to the selected analytics category.
7. Disabling an interfering browser extension.

33.89 Built-In and Google Analytics Do Not Match

Review:

1. Same VCard
2. Same dates
3. Same time zone
4. Google tracking-code installation
5. Cookie consent
6. Browser blocking
7. Bot filtering
8. Custom domain
9. Duplicate external tracking
10. Internal test traffic

Some difference is expected because the systems do not necessarily record visits in the same manner.

33.90 Traffic Dropped After a URL Change

Confirm that all distributed materials were updated:

Open the old links and determine whether they still lead visitors correctly.

33.91 Traffic Appears Under the Wrong VCard

Confirm that:

1. The correct URL alias was shared.
2. The correct QR code was used.
3. The correct NFC card was programmed.
4. A duplicated VCard was not confused with the original.
5. The custom domain opens the intended card.
6. The analytics chart belongs to the intended VCard.

Replace incorrect links immediately.

33.92 Analytics Review Checklist

Before relying on VCard Analytics, confirm that:

1. The correct VCard is open.
2. The public VCard is active.
3. The line-chart action opens successfully.
4. The view count is understood as analytics records rather than guaranteed unique people.
5. Internal testing activity has been considered.
6. Overview loads correctly.
7. The visitor chart is readable.
8. The reporting period is appropriate.
9. Countries information was reviewed as an estimate.
10. Device information was reviewed.
11. Operating-system information was reviewed.
12. Browser information was reviewed.
13. Language information was reviewed.
14. Unknown values are interpreted cautiously.
15. Mobile and desktop experiences were tested.
16. Traffic is compared with Contacts and Inquiries.
17. Traffic is compared with Appointments and Orders.
18. Campaign baselines are recorded.
19. Separate campaign VCards are used where useful.
20. Alias and custom-domain changes are documented.
21. Built-in analytics is distinguished from Google Analytics.
22. Google tracking is not duplicated.
23. The Privacy Policy accurately describes analytics use.
24. Reports do not attempt to identify individual visitors.
25. Analytics information is accessible only to authorized users.
26. The system is not treated as a complete conversion-attribution platform.
27. Historical analytics is not expected to have a standard reset or export control.

Chapter Completion

At the end of this chapter, the user should understand how to open a VCard’s Analytics page, interpret its recorded view count, review Overview, Countries, Devices, Operating Systems, Browsers, and Languages, compare activity across campaigns, distinguish built-in analytics from Google Analytics, and troubleshoot missing or unexpected visitor information.