Know which search sent the tour request, and which tour became a signed lease.

How does a renter pick the community they tour?

A renter picks from a short list, and fast. A new job across town, a first year of graduate school, or a lease that ends in sixty days starts the search. The renter types apartments near the office, near campus or in the neighborhood they want, and opens a few communities side by side. They compare the photos, the floor plans and the rent range. They read the star rating and the most recent resident reviews, including how management answered the unhappy ones. Then they request a tour from the community whose site and listing answered their questions in the first minute.

That request is where your leasing office starts working. Someone calls or texts back and books the tour, and a prospect who walks the model and likes the unit applies. An approved application becomes a signed lease and a filled unit ahead of a move-out, or one more unit off the lease-up count. The office wants the answer the ad platforms do not give it: which source sent the tour that became the lease. The Google Ads campaign on the community name, the neighborhood campaign, the Business Profile listing and the organic search visit each claim some of the credit.

TruLata is built for the community that wants that answer on one screen. The marketing may sit with the community manager between renewals and resident issues, with a leasing consultant between tours, or with a regional marketing lead covering several properties, and each of them reads the same screen. Search, ads and content run on a schedule whether or not anyone had time this week, every tour request is counted from your own site, and the screen shows what happened and what it cost. A property management company chasing owner leads has its own page. This one is about renters.

What runs while the office is out giving tours?

The ads account is watched every morning. At 7:05 Eastern the ads change watch reads your Google Ads change history and the account's user list. It sets our own writes and Google's routine churn aside, and raises a material change made by anyone else to the team the same day, including a recommendation Google applied on its own. The user list is read directly, because a change to who can see the account does not log as a change event. Where we manage search on all tiers, a budget or bid change is made within the limits set for your engagement and lands in your account's own change history. Shifting spend from the community name campaign to the neighborhood campaign before a heavy move-out month leaves a record.

Every day at 7:20 Eastern, where your forms feed the lead sheet, the lead watch runs five checks across the sheet, GA4 and Ads. It checks the tour requests that landed against the conversions Google counted. A dead tag, a blind ad account or a tour form that stopped submitting is flagged the next day, not after the busy leasing season is over. Every night at 12:01am Central a fallback snapshot is baked, and a failed pull leaves the previous page up. When you open the screen it loads that snapshot first and pulls live numbers behind it when the snapshot is older than five minutes.

On Launch, Growth and Command, the content engine researches and drafts, on your cadence, the pages a renter reads before touring. Examples are a guide to the neighborhood, what a commute from the community looks like, and what to bring to an application. Each topic passes a demand gate on real search volume, the research cites current sources, and the dedupe reads the titles already published on your site. Each piece is filed as a Google Doc in your Drive with a featured image, and auto-publish is a per-client setting. On Growth and Command, Meta ads are managed alongside search. On Command, prospects are sourced weekly to a target profile set with you, such as employer relocation and HR contacts near the community. Prospect emails leave from a review-first queue. A person releases them, or the queue releases on the schedule set for the engagement, and every send is logged.

The judgement stays with your people. Your reviews are read onto the screen, and answering a resident's review stays with your office, where the next renter will read the reply. From the screen you can set what a tour request became and request a website, content, keyword or targeting change. Each request reaches the team as a logged ticket, and every change made through the screen is written to an audit log with the address, the request and the result.

Can I see it before I sign anything?

Yes. The demo is the same engine code every client runs, on a fictional company called Meridian, and every number in it is illustrative. It opens with your name and email. Open the Leads view for submissions newest first, then the ads view for spend by campaign, and you are looking at the screen your community gets, with your accounts behind it.

Ranking is not earning. The search view puts the tour requests your own forms took beside the queries and positions, and a position is Search Console's average for the query, not a rank tracker's guess. A page that climbed for a studio search and a page that sent a renter who signed are told apart on the same screen. The attribution use case follows one lead from source to outcome.

A tour request from your own form is yours alone. It came to your community's site, it was written to your sheet, and your office marked what it became. If you would rather have the work done as a service, the services side of TruLata is the other door.