Three identifiers. One identity. Every screen.
Dymos links real-world mobility across MAID, IP and HEM — resolving fragmented signals into one person you can reach on any screen. This is the connective layer: it turns the foundational mobility signal into addressable, activatable identity.
How it works
- Density & exclusivity: how many devices share an IP, and how uniquely it ties to one.
- Geographic consistency: whether a device's real-world observations hold together in one place.
- Recurrence & stability: repeated connections over time are what make a link trustworthy.
- Observed, not fixed: associations are day-level and refreshed, never a permanent mapping.

One mechanic. Two ways to use it.
An IP, a hashed email, a device ID — on its own, each is just a key. Our edge is the same in every case: we enrich the identifier with mobility-linked behavioral evidence, so it stops being a key and becomes a customer you can read. That single mechanic shows up three ways — and almost no one else holds all the pieces to do it.

The IP & Location Loop: behavior, beyond geography
Standard data leaves you with a static dot on a map. We bridge IP ⇔ Location both ways, enriching residential IPs with observed device behavior. We go beyond geography to turn a simple connection into a readable audience.
Residential IP segmentation
POIs matched to IP addresses
Reach where device IDs have gone dark
Reach the screens device IDs can't and make the ones you already have mean something.

Unifying HEM, IP & MAID: volume at the identity layer, enriched
A hashed email (HEM) is just a string without context. We connect HEMs directly to IPs and devices (MAID), linking first-party identity to real-world behavior. We bridge the gap between scale and relevance, adding meaning on top of volume at the identity layer.
Coverage at scale, honestly qualified
Enriched, not just matched
The same person, wherever you find them
Reach the customers behind your hashed emails and understand them, not just match them.
What teams do with it
When the same customer shows up as a different ID on every channel, and you need to tie those identifiers back to one person.
When reach breaks between screens, you need recognition that follows the audience, not the device.
When your first-party profiles are rich but flat and you need real-world geographic and behavioral context to deepen them.
When your inventory can't see device IDs, and you need household-level reach to activate at all.
When you already hold hashed-email or IP inventory and you need a mobility-based behavioral layer to make it addressable.
Trusted by teams at







Three layers, one foundation.
Each works on its own, and they are strongest together.




