"the main problem you’re trying to solve (who needs to chat with whom, and what’s missing with the current DirectChat)"...No, not really. "chat-impression" has a measurement id of: G-VP60ZZDDDM

G-VP60ZZDDDM is our GA4 measurement id for fergusonbuickgmc.com

however; our measurement id for fergusondeal.com is:

G-L1JPK80XLF....Because fergusondeal.com and fergusonbuickgmc.com use the same ID (4588bced...), the Ignitify script treats them as the same entity.

The Trigger: When a user lands on fergusondeal.com, the Ignitify script loads.

The Action: It fires a chat-impression event to track that the chat bubble appeared.

The Destination: Because the ignitifyId is linked to your Buick GMC account in DriveCentric’s backend, it sends that event to Measurement ID G-VP60ZZDDDM (the Buick GMC GA4 property).....We have three OEM's (GM, Kia, Subaru)...we have three DriveCentric Stores (GM, Kia, Subaru)...we want the chat tool on our GROUP SITE (fergusondeal.com); but we don't have a fergusondeal store in Drive....An enterprise level would solver for this; yes. But, so would changing the API to read the domain header on the http request; and changing the handler to switch the measurement ID based off that domain.

Thanks for the suggestion, Cody Teegerstrom — this is helpful context. To make sure we’re thinking about the right enterprise-level DirectChat experience on the enterprise page, could you share a bit more on: (1) the main problem you’re trying to solve (who needs to chat with whom, and what’s missing with the current DirectChat), (2) who should be able to access/see the enterprise chat (all stores under the enterprise vs specific roles/teams, and internal-only vs customer-facing), and (3) how you’d expect conversations to be structured at that level (one shared thread across all stores vs separate threads per store/customer, and whether messages should be visible across stores)?