Subscribe to our newsletter
Get the latest insights on identity, data, and audience activation.
Most businesses already know a lot about their customers. Sales and service history lives in a CRM or DMS, the website records sessions, and the email platform tracks clicks. Each system identifies people its own way, so the same household can appear as a customer record, a string of anonymous sessions, and an email address, with nothing connecting them.
An identity graph is what connects them. It's also where every identity resolution platform starts, which makes it worth understanding before evaluating one.
An identity graph is the infrastructure that links the identifiers a business sees for the same household or person, along with the relationships between them. Those identifiers include email addresses, phone numbers, devices, browsers, IP addresses, and customer records.
Identity resolution is the process of applying the graph to decide which activity belongs together. When you're evaluating vendors, the useful questions are what the graph connects, how those connections are made, and what level the platform resolves to.
Take one household shopping for its next vehicle over a few weeks. Across the dealership’s website, email platform, and DMS, its activity looks like this:
An identity graph stores each of these identifiers: the email address, the phone, the laptop, the home network, and the customer record. It also stores the links between them. The email click connects the email address to the phone. The shared network connects the phone to the laptop. The customer record connects the email address to a known customer.
Read together, those links describe a past service customer who's shopping again. Read separately, they're a service record, two anonymous visitors, and an email click.
An identity graph is built from observations. Each time two identifiers show up together, the graph records the connection. The signals that feed it typically include:
Some connections are direct. A login, a form submission, or a tracked email click ties a device to a known identifier with high confidence, which is why click-based and visit-based resolution produce different levels of certainty. Most website visits come without a direct identifier, so much of an identity graph's value comes from indirect signals: devices, networks, and browsing patterns that keep appearing together.
An identity graph is one of three layers, and each answers a different question.
Identity resolution uses deterministic matching when a direct identifier is available and probabilistic matching when it isn't, evaluating multiple signals and relationships to decide whether activity belongs together. Resolution is also where quality gets decided, because it sets how much confidence a connection needs before it counts. That's the balance between accuracy and reach.
An identity graph lets marketing systems treat scattered activity as one household or customer. That makes a few things possible:
All Launch Labs products are built on the Launch Labs identity graph. The products use its connections to resolve anonymous website activity, build and activate first-party audiences, and tie verified households to confirmed sales and service.
Resolution settings are validated against known identities, so reach and accuracy can be balanced to the goal, whether that's broad audience insight or precise retargeting. The resulting audiences can be activated through the advertising platforms marketers and their agencies already use, including Google, Meta, and TikTok.
Book a demo to see how much more of your website traffic you could identify and reach.
Get the latest insights on identity, data, and audience activation.

A CDP and an identity graph do different jobs. A customer data platform manages customer data: it collects records from sources like a CRM, email platform, and website, organizes them into profiles, and sends that data to tools like ad platforms and email systems. An identity graph is a connection layer that records how identifiers relate to one another.
Many CDPs match people on their own when someone fills out a form, logs in, or clicks a tracked email, which works well for known customers. Most website visitors never take those actions. An identity graph that connects devices, networks, and browsing patterns can recognize more of them before their activity reaches the CDP. The CDP remains where customer data is managed and activated, and the identity graph extends how many of the people behind that data it can recognize.
An identity graph connects identifiers. Whether that leads to an individual or a household depends on how a platform applies it during identity resolution. Some platforms resolve to individuals, others to households.
In many consumer categories, vehicles included, the household is the more practical unit, because purchase decisions often involve several people and devices. Launch Labs works at the household or individual level depending on the product and use case.
It depends on how connections are made and how much confidence a platform requires before treating activity as related. Direct identifiers like logins and tracked email clicks produce high-confidence matches, while connections based on devices, networks, and browsing patterns involve more judgment. Platforms that require more confidence reach fewer people more precisely, and those that require less reach more people with more uncertainty. That's the balance between accuracy and reach every platform has to strike. The best way to judge accuracy is to test results against identities you already know.
They can be, but it depends on how the data is collected, stored, and used. Questions worth asking a vendor include where identifiers come from, whether personal data is hashed or encrypted, how consumer opt-outs are handled, and which privacy regulations the platform is built to meet.