You are running an STR operation across multiple properties. Last month your inquiry count jumped 40%. Your Airbnb, Vrbo, and Booking.com channels all show more activity. Your team is busier. Bookings are up—maybe. But your owner statements show something was off about the distribution. You cannot tell which channel produced the margin. This is the gap between leads and measurable revenue. It is the reason many operators optimize for the wrong thing and why growth that looks good on a dashboard often feels hollow on a spreadsheet. ## The Inquiry Trap Most STR operations measure success in inquiries, not outcomes. An inquiry is a signal, not a conversion. It is cheap to count—every OTA platform hands you the number—but it tells you almost nothing about whether that inquiry is worth your team's time or whether it will pencil. When you optimize for inquiry volume, you are optimizing for traffic to a leaky funnel. A property that gets 50 inquiries per month but converts 6 of them at an average $180 night is generating roughly $2,160 in revenue from those inquiries. A property that gets 20 inquiries per month but converts 8 of them at $220 per night is generating $3,520. The second operation looks worse on the inquiry dashboard. It is actually more profitable. Most operators have no way to see this difference because they do not connect inquiry source to booking outcome to owner payout. The systems sit in parallel—Airbnb data here, Vrbo data there, GHL or HubSpot holding some workflow notes, the accounting spreadsheet living in isolation. When you run the Scorecard, this is often the first system break we find. ## Attribution Without Source Tagging Is Guesswork You cannot measure revenue by source if you do not tag the source at the moment the inquiry arrives. Most operators do not. A lead comes in from Airbnb, lands in an email inbox or a CRM, and by the time it becomes a booking, no one has kept a clean record of where it came from. Many teams rely on memory or loose notes. "I think that was a Vrbo guest." "Pretty sure I texted them back last week." When the month ends and you try to reconcile which channel drove which dollars, you are reconstructing history from fragments. Clean source attribution means the inquiry carries a tag—Airbnb, Vrbo, Booking.com, or direct—from the moment it arrives through to booking, arrival, and finally owner settlement. That tag sits in a queryable record alongside response time, booking rate, nightly rate, stay length, and final revenue. Without it, you have activity. With it, you have data. ## The Channel Parody Problem Multi-channel STR operations often suffer from a specific distortion: one channel sends high-volume, low-intent inquiries while another sends fewer but higher-quality prospects. Operators optimize for the noisy channel because it feels productive. They add listings to it, adjust pricing to appease its algorithm, spend operational time managing its quirks. Meanwhile, the quieter channel is actually converting higher and driving more margin, and it gets no attention. This happens most often when an operator is measured on activity instead of outcome. A manager tasked with "increase Booking.com inquiries" will adjust that lever. A manager tasked with "increase owner revenue per available night" will ignore Booking.com entirely if another channel is more efficient. The fix is not complex, but it is structural: stop measuring channel success by inquiry count. Measure it by conversion rate to booking, by average nightly rate on that channel, by stay length, and by repeat guest rate. These four numbers tell you which channel is actually working. Most operators have never calculated them. ## Response Time Inflation Hiding in Channel Mix When you measure inquiries instead of revenue, you also hide response time problems. A channel that generates high-volume but low-intent inquiries will slow your team's average response time. If 40% of your inquiries are low-intent window-shoppers from one platform, your median time to first response looks bad even if you are answering the convertible inquiries fast. The operator story usually goes like this: "Our response time went from 8 minutes to 22 minutes. Our conversion rate dropped 15%." But the raw inquiry volume is up. So they blame capacity or staffing. The real culprit is often a shift in channel mix—a platform algorithm change pushed more marginal inquiries into the pipeline, and now the signal-to-noise ratio has degraded. Hiring another team member or upgrading the CRM does not solve it. Adjusting the channel strategy does. ## Building an Attribution System Attribution at scale requires three elements working in tandem. First, the source tag must travel with the inquiry from the moment it arrives—whether it lands via API, Zapier, email, or manual entry. Second, that tag must map forward to the booking record in your PMS. Third, the booking record must carry the final revenue number so you can answer: "Which channels generated revenue, at what rate, with what guest quality, at what price point?" This is not a marketing question. It is an operations question. Your PMS, your inquiry intake, and your financial records need to speak the same language. For operators running a single property, this can be a spreadsheet with discipline. For multi-unit or multi-market operations, it requires a queryable database or a reporting layer that sits above your fragmented tools. Many operators assume their PMS or their CRM does this natively. It often does not. You have to wire it. ## The Scorecard Catches This Fast When we run the free STR Leak Scorecard with an operator, one of the first things we audit is whether they can answer this question: "Of your bookings last month, how many came from Airbnb versus Vrbo, and what was the average revenue per booking from each?" If they cannot answer it cleanly—if the answer requires digging through three systems or reconstructing history—that is a system leak. It costs them strategic blindness and optimization drag every single month. Inquiry volume feels like progress. Measurable revenue is actual progress. The operator who builds the attribution layer to see the difference between them will stop hiring for the wrong channels, stop optimizing for the wrong metrics, and start scaling the operations that actually work.