Solutions Architect, Brandon Lace, explains how to set up FullContact’s Native App in Snowflake Marketplace and discusses potential use cases.
Summary
A hands-on walkthrough covering both how to set this up and what you get once it is running.
We build the demo around a fictional retailer whose systems show one customer as three unrelated people: an online buyer with an email address and a cheerful support call on file, an in-store buyer with no email and a later unhappy call under a different phone number, and a stream of anonymous browsing from a device nobody recognizes.
The first half is setup. Installing from the marketplace, configuring the API integration, generating a key specific to your account, and preparing an input view so your column names map to what our resolution expects.
The second half runs resolution against that data and shows what the unified profile makes possible: an accurate lifetime value, a support history in the right order, and anonymous browsing attached to a customer you already know.
What We Cover
- The three-profile problem, made concrete. The same customer shows up as an online buyer, an in-store buyer under a different phone number, and an anonymous browser on another device. None of the three systems can see the other two.
- Why your PersonIDs are unique to your account. The same individual gets a different PersonID in somebody else’s account. We do that deliberately: nobody can take an identifier out of one account and use it to look that person up elsewhere.
- Your customer data never leaves Snowflake. The API integration carries the licensing key and usage tracking, nothing else. We call that out during setup rather than leaving you to ask.
- Record IDs need to be unique per row. If the same email appears on several rows, give each one its own record ID. Resolution will still assign them the same PersonID, and you merge downstream.
- Unification changes what a customer qualifies for. Split across profiles, this customer’s spend falls below the retailer’s high-value threshold. Combined under one PersonID it clears it, so she lands in the segment she should have been in all along. The same unification reorders her support history and reveals that her most recent contact was the unhappy one, not the happy one the team could see.
- Anonymous browsing becomes attributable. Our customer recognition web tag assigns the same PersonID to site traffic, so product views and cart activity that looked like a stranger join to a known customer and surface a product preference the retailer had no way to see.
Next Steps
Talk to us about unifying customer profiles across your systems.
