Your Anewgo floor plans collect registrations. Your ads can't see them.
Buyers register inside Anewgo to save a plan, build a brochure or favorite a homesite, and Google Ads and Meta often never hear about it, because the registration happens in the Anewgo app, on myhome.anewgo.com or in a frame, not on the page your tags watch. So bidding treats your best communities as dead weight. We route Anewgo's own webhooks through a first-party server container so each new registration reaches your ad platforms once, with plan and community attached, and contracts from your CRM follow.
Free30 minutesNo obligation
Anewgo · what breaks
What goes wrong with Anewgo and your ads
- 01
"Our floor plan leads never show up in Google Ads"
The registration happens inside the Anewgo app, out of your Google tag's sight. Smart Bidding sets bids from the conversions it records, so it pulls back on the communities that actually fill your lead list.
- 02
"Meta reports more leads than we have buyers"
Anewgo fires webhooks on register, sign in, brochure and favorite. Send them all as leads and one shopper counts four times, and Meta learns to find heart-clickers, not touring buyers.
- 03
"Walk-ins at the model home might be counted as ad leads"
Anewgo runs a Sales Center App with email sign-in alongside your website. If those sign-ins feed the same webhooks as online registrations, walk-in traffic gets credited to campaigns and you overpay for leads you already had. We confirm how your account separates them.
- 04
"We can't tell which campaign sold a home"
Anewgo's documented registration payload has name, email, phone, registration date and favorites, but no ad click. The contract is signed weeks or months later in your CRM, so bidding never learns which registrations bought.
Anewgo · the fix
What changes after we fix it — Anewgo
Every new registration counted once
First registration only, sent from Anewgo's webhook through your server container with a shared event ID, so Google Ads, GA4 and Meta agree.
The ad click travels with the buyer
The click ID captured at registration lands on the lead in Lasso, HubSpot or whichever CRM your Anewgo webhooks feed.
Bidding learns from buyers, not browsers
Kept appointments and contracts flow back from your CRM, so spend shifts toward the communities and plans that close.
Anewgo · architecture
What Anewgo actually lets you hook into
Everything below comes from Anewgo's own help docs. Where the docs stop, we list a check rather than a promise.
- 1
Webhooks on buyer actions
Set up under Admin, Integrations, Webhooks. Documented for register, sign in, brochure, favorite and interest in a home or community, with email, phone, community, plan, inventory and Contact Us message.
- 2
Extra Cookies on each webhook
Documented for passing HubSpot's tracking cookie. We test whether it can carry Google and Meta click cookies on your setup before relying on it.
- 3
Lead registration notifications
Insights posts a JSON record for each new registration to a URL you set; Pro and Enterprise add the buyer's favorite plan, elevation and homesite.
- 4
Custom scripts in the website head
Anewgo websites take head scripts under Website, Customize, SEO. Anewgo documents it for Lasso's tracking script; it's also where we test placing your Google tag or Tag Manager container on an Anewgo-built site.
- 5
Lasso integration
A documented endpoint to Lasso CRM plus a tracking script, so Lasso's UTM report shows where registrants came from.
- 6
No native ad platform connection found
We found no Google Ads, GA4 or Meta Pixel connection in Anewgo's help docs, so we confirm what your account has turned on.
Anewgo · diagnose
Where Anewgo tracking breaks, in diagnostic order
Start with where the app runs, because that decides whether your site tags can see a registration at all.
- 01
Find where buyers register
Your Anewgo-built site, a frame, or myhome.anewgo.com. Each needs a different capture path.
- 02
Register once from an ad-tagged URL
Then check Google Ads, GA4 and Meta Events Manager for anything that fired.
- 03
Open the webhook record for that test registration
If nothing identifies the ad click, attribution stops at the registration.
- 04
Count the lead events per shopper
Register, sign in, favorite and build a brochure, then see how many leads reached Meta.
- 05
Separate the sales center
Confirm whether Sales Center App sign-ins reach your webhooks, and that they can be told apart before they reach any ad platform.
- 06
Check the CRM loop
See whether a contract marked in Lasso or HubSpot ever reaches Google Ads or Meta.
Anewgo · prove
The QA evidence — Anewgo
Run on your live builder site with real test registrations, not the Anewgo console preview.
Source of truth
Anewgo's lead list (registration date, community and favorites per buyer), plus appointment and contract records in your CRM
- An ad-tagged registration with the click ID confirmed on the CRM lead.
- One Meta lead and one Google Ads conversion per new registration, sharing an event ID.
- A repeat sign-in, a favorite and a Sales Center App sign-in all confirmed absent from the lead conversion.
- A test contract reaching Google Ads and Meta with the right community.
- Every registration in a closed month matched by email against what Google Ads and Meta recorded.
- Rerun at 30 days, and again whenever someone edits an Anewgo webhook or republishes the site.
Anewgo · free audit
What we check in the free audit
- Find where buyers register
- Register once from an ad-tagged URL
- Open the webhook record for that test registration
- Count the lead events per shopper
- Separate the sales center
- Check the CRM loop
Checked against
Anewgo's lead list (registration date, community and favorites per buyer), plus appointment and contract records in your CRM
Free30 minutesNo obligation
Anewgo · when not to buy
When you don't need this on Anewgo
Some builders are better off with a quick settings review than a project.
- If your registrations come from listing feeds, signage and walk-ins rather than paid ads, ad attribution won't change a decision.
- If you just want campaign-level registration counts, don't use conversion-based bidding, and Lasso's UTM report already shows them, that may be enough.
- If you sell a handful of custom homes a year, there are too few contracts for bidding to learn from; track registrations and stop there.
- If the only fault is the Zap behind one Anewgo webhook mapping the wrong field, your team can fix that in an afternoon.
Anewgo · what we deliver
The event map on Anewgo
Community or plan viewed
A browsing signal for audiences, read from the Anewgo community and plan path. Never a conversion.
Buyer registered
The primary lead conversion, fired on a buyer's first registration only, with community and plan attached.
Favorite saved or brochure created
A secondary engagement signal with plan, elevation and homesite where your subscription sends them. Kept out of the bidding goal.
Contact Us message sent
The qualified lead, carrying the buyer's message and the community, plan or quick move-in home they were viewing.
Model home visit kept
Sent from the appointment status in your CRM once your sales team marks it.
Contract signed
The money conversion, from your CRM. Excluded everywhere: repeat sign-ins, Sales Center App sign-ins at the model home, agent and staff test accounts.
Written guarantee
95%+ tracking accuracy
Measured against Anewgo's lead list (registration date, community and favorites per buyer), plus appointment and contract records in your CRM. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Anewgo questions, answered
We didn't find a native Google Ads, GA4 or Meta Pixel connection in Anewgo's help docs. What Anewgo documents is webhooks, a Lasso integration and custom head scripts on its websites, and that's what we build on.
The buyer registers inside the Anewgo app, often on myhome.anewgo.com or in a frame, so the tags on your page never see it. Sending the registration from Anewgo's webhook through a server container fixes that.
Not on their own; a webhook just posts to a URL. Anewgo documents Zapier as a receiver, and we point it at your first-party container instead, which sends to Meta and Google Ads with one event ID.
As secondary signals, yes. As the bidding goal, no, because shoppers favorite plans they'll never tour and the algorithm would chase that behavior.
Yes, if the ad click is stored at registration and your CRM marks the contract; Google Ads can import offline conversions against its click ID. Contracts trail the click by weeks or months, so we also send kept appointments so bidding learns sooner.
They shouldn't. Buyers who sign in at the model home on Anewgo's Sales Center App didn't come from an ad click, so once we confirm how they reach your webhooks, we keep them out of ad conversions and report them on their own.
More on Anewgo
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Anewgo, and what their bookings feed
- ProSitesYour ProSites site sends appointment requests. Which ads actually put patients in the chair?
- HandL UTM GrabberHandL UTM Grabber shows which ad each lead clicked. Google Ads still only learns "form submitted."
- FindLawFindLaw reports contacts. Which ones became signed cases?
- IPSTUDIOYour IPSTUDIO site sells intro offers. Your ads can't see them.
- KicksiteYour Kicksite trial form fills the Prospects list. Your ads say they booked nobody.
- Owner.comYour Owner.com site takes the orders. Your ads never hear about them.
- HotplateYour Hotplate drop sold out. Meta says the ad sold nothing.
- ThanxYour Thanx app is busy. Your ad accounts say nothing sold.
Free · 30 min
Find out what your Anewgo registrations are telling your ads
Free30 minutesNo obligation
