Skip to content

Smart Link Analytics

  1. Open Smart Links in the portal.
  2. Select the Smart Link you want to review.
  3. Select Analytics.

Analytics stays scoped to that Smart Link, including its Base URL, saved configurations, and current or historical destinations.

Use this report to compare public-link use, such as a QR code on a receipt versus a saved configuration used on a front-desk card. It counts qualifying visits and downstream results, not the number of people who saw the printed code.

The page opens with the last 30 days selected. Set From and Through to choose another range within the rolling 13-month analytics window. The page shows the earliest available retained date.

There is no All Time option or visit-export action on this page. For long-running campaigns, record your comparison totals while the period is available. Activity exports cover response records and are a separate source of information.

The summary cards divide qualifying visits into these groups:

  • All Link Traffic — Every qualifying visit to the Smart Link.
  • Base URL Only — Visits that used the Base URL without a saved-configuration suffix.
  • Configuration Traffic — Visits associated with saved configurations.
  • Unknown Suffix Fallback — Visits with an unrecognized configuration suffix that fell back to the base link.

Base URL Only, Configuration Traffic, and Unknown Suffix Fallback add up to All Link Traffic. These are summary cards, not separate filters; the tables below show the destination and configuration breakdowns for the chosen dates.

Automated preview requests and repeat visits within a short duplicate window can be excluded. Totals therefore need not match website traffic counters or every refresh during your own testing, and they are not a count of unique customers.

The destination section shows where qualifying visits were routed and what happened next. It keeps historical attribution for destinations that are no longer active, which lets you interpret older traffic after changing the link.

Depending on the destination type, results can include:

  • Review Journeys Started and Completed Review Journeys — Journeys first started through the link during the chosen period, with completions recorded through report generation. The completion percentage uses those starts as its denominator.
  • Completed Form Submissions — Form responses created through the link during the chosen period that have since completed.
  • Qualified Redirects Delivered — Recorded handoffs to My Link destinations during the period. These do not confirm a purchase, booking, or external review.
  • Qualified Page Views Delivered — Recorded deliveries to Simple Pages during the period.
  • Qualified Showcase Deliveries — Recorded handoffs to Showcase Pages during the period. These are not feedback-button clicks or completed reviews, and do not prove the visitor read the entries.

A later response through a showcase’s Leave Feedback button identifies the showcase in the Customer Journey. Keep that response activity separate from the Smart Link’s Page-delivery total. Opening a bookmarked Page directly does not itself add a Smart Link delivery.

An unfinished Review Record or Form Response remains associated with the destination it originally opened, even if the active rotation later changes.

For example, a Review Journey started near the end of August and completed in September can increase August’s completion result when you revisit that period. A visit count and a completed-response count measure different events.

Configuration traffic lets you compare reusable placements such as a front-desk card, an employee-specific handout, or a campaign QR code. Disabled and retired configurations remain available for historical reporting.

If an outcome shows partial delivery, open the saved configuration and check its preferred location, employee, sender, and destination. Partial delivery means the customer could continue, but some supplied context could not be used. For example, a selected employee may no longer be available for that location.

The outcome describes what FSRevs knew when it routed the visit. A preference waiting for the customer to choose a location is not treated as ignored at that point. Later customer choices do not rewrite the original outcome. Unknown-suffix and configuration-fallback outcomes can appear instead of a partial-delivery label.

When configuration URLs contain campaign details, the analytics page summarizes the leading values for:

  • Source
  • Medium
  • Campaign
  • Term
  • Content

Use consistent names and capitalization so related visits group together.

FSRevs may temporarily suppress analytics recording to protect public-link performance. When today’s visits are affected and today is in the selected range, a notice appears. Link routing continues, but excluded visits are missing from analytics. The notice is not a complete history of older recording interruptions.

The QR code works but the visit total did not increase

Section titled “The QR code works but the visit total did not increase”

Check that you opened this Smart Link, that the date range includes the visit, and that you are not repeatedly refreshing within the duplicate window. Automated link previews do not count as normal customer visits.

The printed code has traffic but the configuration has none

Section titled “The printed code has traffic but the configuration has none”

Confirm the code contains the saved configuration’s URL. A code generated from the Base URL contributes to Base URL Only. An unrecognized suffix is reported separately as Unknown Suffix Fallback.

Your access does not cover the destination or saved configuration context. Ask an administrator to check the relevant location access; missing detail is not proof of zero traffic.

A previous period’s completion result increased

Section titled “A previous period’s completion result increased”

Review and Form results follow the starts or response records created during the selected period. Customers can complete them later.