RuusterAPI Reference
Menu · Guides
Guides

Data notes

What the numbers mean and their limits: time zone, perspectives, reloads, freshness, history, attribution and email opens.

View as Markdown
  1. Days are America/Chicago. A listing viewed at 11 pm Pacific counts on the next Chicago day.
  2. Two perspectives. Listing numbers count every Ruuster site, because you own the listing. Lead and summary numbers count activity on your sites, because you own the audience. They aren't meant to add up to each other.
  3. Views count reloads. Use views.public.users (roughly distinct browsers) and views.loggedIn.uniqueLeads to estimate people. Both are distinct per day; over a week or a month they are the sum of the daily counts, so a returning visitor counts once per day they came.
  4. Freshness. Yesterday's numbers are usually complete by mid-morning Central, and today's are refreshed through the day. Use meta.coverage, not the clock, to decide what's final. Google Analytics can revise the last 48 hours, and email opens and clicks keep arriving for about two weeks, so re-pull the last few days on each sync.
  5. History. Google Analytics history goes back to coverage.ga.from in /me. Ruuster's own activity history begins about 90 days before your brokerage was enabled and grows from there. Ask your CSM if you need more.
  6. Attribution. A listing missing from /properties usually means the listing agent's MLS id isn't on their Ruuster profile. attribution in /me shows how many of your agents have one. Ask your CSM to add the missing ids; listings typically appear within a day. Listings from your MLS office are included only after Ruuster confirms the office is yours.
  7. Lead identity. A visitor becomes a lead when Ruuster can tie them to a contact. Activity from before that stays anonymous.
  8. Tour requests on a listing and tour requests in a lead's activity are measured at different points, so the two can differ slightly.
  9. Email opens. Human-open figures leave out opens that look automated. Mail scanners change often, so treat open rates as indicative.
  10. Contact details in responses carry the same obligations as your CRM data.
  11. Where data is processed. API data is stored and processed in the United States, including data about Canadian brokerages and their leads.