Datasets
Sense360 collects proprietary data from several different consumer panels, totaling over 10 million consumers across the United States. These data sources are organized in the datasets used among the different dashboards:
Transaction
Transaction insights are collected from consumers' debit cards, credit cards, and banks accounts. The data is collected in real-time from financial institutions and personal finance services that allow consumers to track and monitor their financial status. Subsequently, Sense360 undergoes the processing and cleaning of the raw transaction data and converts it into the brand/retailer-level spend, assigning transactions to the different purchase geographies and channels. The proprietary weighting models ensure a complete view of all transactions; the weighting methodology controls for income and geographical representativeness to be as close as possible to the overall US population.
When the underlying data is processed, Sense360 converts those transactions into usage metrics such as Panel sales, Wallet share, Check size, and Penetration. These metrics are used together with longitudinal analyses such as Guest frequency and Migration over time.
Used in Competitive performance, Market performance, Customer profile, Customer migration, and KPI tracking.
Metrics
These metrics apply to Transaction dataset:
| Metric | Description | Usage |
|---|---|---|
| Panel sales | Total sales for a brand or market among the panel of 6 million U.S. consumers. |
|
| Spend per capita | Average amount of spend per panelist on the specified brand or market. | |
| Transactions per capita | Average number of transactions per panelist on the specified brand or market. | |
| Penetration | Percent of total panelists that have one or more transactions with the specified brand or market in the period. |
|
| Wallet share | Percent of spend that a brand or category receives out of all the spend in the market |
|
| Frequency | Average number of transactions per customer on the specified brand or market. A customer must have at least one transaction with the specified brand or market within the time period to be included in the metric. |
|
| Spend per customer | Average amount that a customer spends on the specified brand or market. | |
| Average check size | Average amount of dollars spent per transaction of all transactions made for a brand. |
|
| Median check size | Midpoint check size among all transactions, that is, the equal number of transactions above and below amount. |
Collection and methodology
Collecting Transaction data consists of three steps:
Collection — Consumer spend data is collected from a panel of around 10 million consumers across their debit, credit, and banks cards. However, Sense360 filters the panel down to only the highest quality and most consistent users (around 5 million consumers).
The data is collected directly from financial institutions (banks) and from personal finance services that allow consumers to track and monitor their financial state.
Processing — Processing and cleaning of the raw transaction data. Sense360 receives the data five days after the transaction and requires a 10-day lag to ensure the bulk of the data has been received and to stable metrics.
Processing includes: mapping charge line items into the brands spent at, assigning transactions to the geographies of purchase, and applying a variety of models to the data to select only the highest quality panelists, correct for bias, and ensure stability.Reporting and insights — Sense360 converts transaction data into usage metrics like Spend, Share of wallet, Check size, and Migration and stealing to report on those metrics.
Biases
These biases affect the Transaction data set:
| Bias | Description | Impact |
|---|---|---|
Demographic | Under-representation in the low income (< USD 30,000) and extremely high income (> USD 300,000) ranges. Ultimately, banked consumers who use debit and/or credit represents a slightly more high-spending, urban, and affluent portion of the population. |
|
| Credit/debit transactions only | Cash, check, wire transfer, B2B invoicing, and other transaction types are not included. |
|
| Returns | Negative transactions (returns) are ignored in Sense360 KPI metrics as it is impossible to know in which period the original transaction occurred and/or whether the transaction location remains consistent. |
|
| Larger Check sizes for restaurants | Includes catering and native digital payments (such as order ahead, delivery, and pick up) which have larger check. While it includes 1st-party digital payments, 3rd-party payments are tracked separately (for example, DoorDash). |
|
| 1st-party digital transactions | Transaction data set provides billions of transaction data points similar to a credit card statement. The way the information comes through may allow, in some but not all cases, to separate digital versus physical transactions. |
|
| Fees, taxes, and tips | All consumer spending is included in Sense360 metrics. |
|
3rd-party delivery | Sense360 exposes data on what specific businesses customers are ordering on 3rd-party platforms, such as DoorDash. However, the raw data does not have full coverage of all platforms (for example, UberEats does not expose this information) and not all businesses are mappable within the mappable platforms due to POS integrations. |
|
| Buy now, Pay later | These transactions are assigned to the Buy now, Pay later provider (such as Klarna, AfterPay) and Sense360 unable to discern which retailer the purchase is for. |
|
| DMA assignment and fixed geo- weights | Transaction locations are assigned to the panelist home zip code since transaction location is often unavailable (such as in digital purchases). Additionally, geographical representation in our models is locked to the most recent census. |
|
| Check size and Frequency for hospitality | All transactions are included, such as room service and spa treatments at hotels, as well as baggage fees and in-flight WiFi for airlines. |
|
| Aggregator data for hospitality | Sense360 to identify which hospitality brand a consumer is transacting with when purchasing through an aggregator (for example, Travelocity, Kayak, etc.) |
|
Foot traffic
Foot traffic data is collected from a panel of approximately 400 thousand opted-in consumers using SDKs placed within apps stored on their mobile devices. The data is collected in real-time by mobile applications that send location-based surveys or other types of location-based services to consumers.
Subsequently, Sense360 undergoes the processing and cleaning of the raw visit data and converts it into the visited brands, as well as assigns a geography, daypart, and duration to visits.
Advanced machine learning models and phone sensors are then used to accurately identify visits to a brick and mortar location. The proprietary weighting models ensure a complete view of all all visits and account for natural smartphone adoption biases and natural panel churn; the weighting methodology also controls for demographics and geographical representativeness to be as close as possible to the overall US population.
Used in Customer profile.
Metrics
These metrics apply to Foot traffic dataset:
| Metric | Description | Usage |
|---|---|---|
| Visit share | Percent of visits the brand or retailer receives out of all the visits in the market. It similar to Market share, but it measures visits instead of revenue. |
|
| Brand draw | Percent of visits that a brand or retailer receives out of all of the visits in the market. As opposed to Visit share, it only looks at visits within 1 mile of a brand's locations. | Understand how often a person chooses a brand or retailer versus a competitor in the same market when they are within striking distance of a brand or retailer location. |
| Head-to-head brand draw | Percent of visits that the brand or retailer receives when its stores are within 1 mile of a competitor's stores. | Understand how often a person chooses the brand or retailer versus the competitor when the two are within striking distance of each other. |
Collection and methodology
Collecting Foot traffic data consists of three steps:
Collection — Foot traffic data is collected from a panel of around 5 million opted in consumers using SDKs placed within apps stored on their mobile devices. Advanced machine learning models and phone sensors are used to accurately identify visits.
Processing — Processing and cleaning of the raw transaction data. Sense360's proprietary weighting models ensure a more complete view of all visits and account for natural smartphone adoption biases and natural panel churn. The weighting methodology also controls for demographics and geographical representativeness to be as close as possible to the overall US population.
Reporting and insights — Sense360 converts visits into usage metrics like Visit share and Brand draw that are available through a variety of lenses including Daypart, Weekpart, 1-mile Visit share, and Visit share head-to-head against nearby competitors.
Biases
These methodology-driven biases affect the Foot traffic data set:
| Difference | Description | Example impact | Takeaway |
|---|---|---|---|
| Check size | Foot traffic data does not account for check size | Check size has been the biggest driver of growth and drive a 5 - 7% divergence from foot traffic in recent years (NRN and MillerPulse, March 2019). | Check size is crucial to monitor and can be analyzed through Transaction data. |
| Market and competitor changes | Visit share is relative and factors in market/competitor changes in Foot traffic. | Visit share can increase even when internal transactions decrease, in the case where competitors transactionsdecrease even further. | While Visit share moves differently than internal transactions, it provides valuable competitive and market context. |
| Party size | Foot traffic is influenced by party size, but transactions do not account for Party size. | In 2x1 promotions, transactions may remain flat but could drive a significant increase in Visit share. | Visit experience survey can be used to understand party size changes. |
| Digital and delivery | Foot traffic data does not capture delivery purchases. | Delivery has become a significant portion of revenues, though this is not be captured and Visit share understates their total growth (for example, Dominos, Chipotle). | Delivery is crucial to monitor and can be analyzed through Sense360 Delivery IQ solution. |
| Short and close visits | Short (2.5 minutes or less) and close (less than 100 meters from previous destination) visits are not captured. | Short visits are often mobile pick-up orders; brand performance that relies heavily on this is understated. | Short visits are often mobile pick-up orders; brand performance that relies heavily on this is understated. |
Surveys
Survey data is collected by delivering surveys directly to customers' mobile phones and desktops, and are tied to consumers' real-world behavior through Sense360's integrated foot traffic and digital survey panels.
For visit-based surveys, a proprietary SDK sits inside mobile applications that reward panelists for completing surveys. When a visit is detected to a location of interest, Sense360 uses a targeting system to select users based on certain behaviors, such as a visit to specific locations or some demographic criteria. If the panelist fulfills the survey requirements, an alert is triggered on a mobile phone to display an in-app survey when opening the alert notification.
For digital surveys, consumers are targeted based on their digital behavior, collected through a browser plugin that monitors all the URLs that a panelist visits on their browser. The plugin tracks the page domain, time spent on the website, and the pages they were at before and after. Subsequently, Sense360 targets consumers that have visited specific sites or have specific demographic criteria. If the panelist fulfill the survey requirements, an alert is triggered to display the survey in the browser when opened.
Used in Brand perception, Restaurant customer experience, and Retail customer experience.
Collection and methodology
Collecting Survey data consists of three steps:
Collection — Sense360 directly integrates its proprietary SDK technology into survey partner mobile applications. Through this integration, it observes foot traffic behavior of respondents and directly target surveys to respondents based on their real world behavior.
In certain situations, Sense360 augments sample from other sources.
Processing — Processing and cleaning of the raw transaction data. Typical steps can include removing poor quality responses, weighting the data to be representative of the U.S. population, and calculating a variety of metrics and cross-tabs.
Reporting and insights — Sense360 exposes the data in a variety of self-service dashboards as well as custom reports prepared by client service teams.
Biases
These biases affect the Surveys data set:
| Bias | Description | Impact |
|---|---|---|
| Mobile panelists | Sense360 visit-based panel primarily consists of mobile panelists — respondents who are taking surveys on their mobile phones through survey apps. | Mobile panelists tend to skew younger than desktop panelists. |
| Demographic skews | Survey panels almost universally skew towards lower-income respondents (the population that is most motivated by survey incentives). Additionally, Sense360 panel skews younger as a result of being primarily mobile. | While representative sampling and weighting may correct for this bias to an extent, it is unavoidable and results in an over-representation of this demographic's opinions, thus brands that resonate with this group getting more favorable responses. |
| Self-perception and recall error | Regardless of source, all survey data is subject to a variety of well-documented human biases. |
|
