Bramlett Partners : A realtor site and an ecommerce brand on one identification playbook

Bramlett Partners runs one site for real estate and a separate ecommerce property. Leadpipe gives one ID-rate definition and shared reporting across both, search, listings, and shop traffic included.

Start free trial → View pricing

Part 01

The setup

Their real estate site covers the residential side, neighborhood guides, listing search, mortgage and relocation content, and lead forms fed by paid and organic. Their ecommerce storefront is separate (different catalog, checkout, and lifecycle) under the same operating group.

One operator, two surfaces

Realtor

Guides + listings

Ecommerce

Separate checkout

Marketing and ops wanted a single visitor-identification layer so they could compare apples to apples: same event taxonomy, same “ID rate” definition, and separate workspaces per domain for compliance and messaging.

Part 02

Benchmark snapshot (corrected figures)

After normalizing a typo in the original real-estate-site export (13,840 unique emails, not 1,3840, and ~250K events for the quarter-million band), their blended dashboard for a recent 30-day period looked like this:

30-day benchmark (corrected)

Property	Events	Emails	Visitors	ID rate
Ecommerce	275K	5,312	~103K	32.3%
Realtor	250K	13,840	~339K	41.0%

Ecommerce property: about 275,000 tracked events, 5,312 unique work and personal emails identified, roughly 103,000 qualified visitors in scope, 32.3% identification rate against Leadpipe-eligible sessions.

Identification rate by property

32.3%

Ecom

41%

Realtor

Realtor site: about 250,000 tracked events, 13,840 unique emails identified (figure corrected from a dropped digit in reporting), roughly 339,000 qualified visitors in scope, 41.0% identification rate on the same basis.

Export correction (realtor)

Typo in file

1,3840

Corrected

13,840

Identification rate here means the share of eligible, non-bot sessions where Leadpipe returned a resolvable email or stable household key, not “emails ÷ all analytics visitors,” which would understate coverage.

Part 03

How they use it

Events stream into a shared Leadpipe account with domain-level splits. The realtor site prioritizes listing alerts, open-house reminders, and agent routing; the shop uses cart/browse paths and promo timing. Suppression and consent rules differ by property but reporting rolls up for leadership.

Reporting time / wk (hours, indexed down)

Higher match on the realtor domain seeds lookalikes for “in-market mover” audiences; the ecommerce property runs longer product nurture where match is lower but basket values reward patience.

ID rate reviews (8 wks)

Weekly reviews compare ID rate week-over-week per domain; dips trigger tag checks, new cookie banners, or traffic mix from fresh campaigns before media budgets move.

Part 04

Operational outcomes

Unifying the metric cut cross-property reporting from about six hours to under ninety minutes per week.

Weekly reporting time

Before

~6 h

After

<90 min

Remarketing CPM efficiency improved about 14% on the realtor site in the first month after switching to Leadpipe-based seed lists, holding ROAS within ±3% of plan on listing and brand campaigns.

Realtor remarketing CPM (month 1)

Baseline index

100

After ~14% efficiency gain

~86

Onboarding another domain is now mostly DNS and tag QA, no one-off “how do we count IDs here?” project per site.