Know each customer, whatever identifier they use. One persistent ID per person, built for Saudi data.

EleeNID resolves the emails, phone numbers and device IDs in your data into one pseudonymous ID per person, read in place in your cloud. Every clean room, audience and activation in EleeN runs on it.

Book a call

Connections/Sources/CUSTOMERS – DatabricksR

CUSTOMERS – DatabricksLiveDatabricks·analytics.customers·Last synced 4h ago

Build an audience

OverviewSchema and mappingConnectionActivityDependents7

Records resolved

86%

2.4M records

Activatable reach

2.0M

≈ 2.1M of 2.4M records

Resolution strength

5/5

6% excluded from resolution

Identity and resolutionRecords resolved using the identifiers you mapped.FieldCoverageMatchedDevice ID98%2.3MAndroid ID99%2.3MEmail96%2.2MClient ID73%1.7MPhone number73%1.7M

Last sync, 02:00DoneIngesting sourceFrom the hashed table, in batches.Matching to the EleeN graphHashed IDs looked up.Building the identity graphLinks stitched, EleeNIDs assigned.Indexing for audiencesReady for the audience builder.

EleeN reads only customers__eleen_hashed

[ 01 / 04 ] Mapping

Map your columns once. EleeN reads the columns you map, and nothing else.

Your tableanalytics.customersEleeN field
Identity fields (5)Required. The fixed slots EleeN resolves people with.
cust_idstringClient IDRequired
email_addrstringEmailRequired
mobile_nostringPhone numberRequired
device_maidstringDevice IDRequired
android_maidstringAndroid IDRequired
No column in this tableNational ID (Iqama)
Attributes (3)Optional, for building audiences. Switch one off to stop reading it.
city_locationstringLocation
birth_datedateAge band
segment_tierstringCustomer tier
Not mapped (3)Left out, so they stay in your environment.
first_namestringStays in your environment
last_namestringStays in your environment
notestextStays in your environment
Unmapped columns stay in your environment.Columns EleeN reads8 of 11

[ 02 / 04 ] Hashing

Hashed in your database, before anything moves. EleeN reads only the hashed table.

Trust center

[01]Your tableThe columns you mapped, as they are. The table stays where it is.

analytics.customers

cust_idemail_addrmobile_nodevice_maidfirst_name

C-10482sara.a@example.com+966 55 555 010138400000-8cf0-11bd…Not read

C-10483omar.k@example.com+966 55 555 01026f1c2a4e-5b7d-4c11…Not read

C-10484lina.h@example.com+966 55 555 0103a91e7c30-2f4b-4d8e…Not read

[02]A script you runIt hashes each identifier with SHA-256 and a salt issued to your organisation, inside your own database.

eleen_hashing.sql

1sha256(salt ‖ email_addr)
2sha256(salt ‖ mobile_no)
3sha256(salt ‖ device_maid)

[03]A parallel tableHashes and EleeNIDs only. The one table EleeN reads.

analytics.customers__eleen_hashed

eleenidemail_sha256phone_sha256device_sha256

EID-7F3A-92C1ee0fb60941aeb7e2…2424cf0a094b2067…9751c4b36614549f…

EID-2B8D-41E0e150c77130f668ca…71a21e3adf29f7c7…872b84f2208241af…

EID-C05E-7A19c2bbfc7380cec1a3…fb38d2fce4385ae0…afb3c2de1a6a1b26…

[ 03 / 04 ] EleeNID

Three records, one person. One EleeNID, the same after every sync.

CUSTOMERS – Databricksanalytics.customersClient IDEmail

LOYALTY – Snowflakecrm.loyalty_membersEmailPhone number

APP_EVENTS – BigQueryevents.app_usersDevice IDAndroid ID

EID-7F3A-92C1Resolved from 3 sourcesClient ID4f9a1c22e07b51d8…Emailee0fb60941aeb7e2…Phone number2424cf0a094b2067…Device ID9751c4b36614549f…Android ID0c3d8e5a71f2b946…Hashes only. No name, no contact details.Same ID since 12 Jun 2026

CUSTOMERS – Databricksanalytics.customersClient IDEmail

LOYALTY – Snowflakecrm.loyalty_membersEmailPhone number

APP_EVENTS – BigQueryevents.app_usersDevice IDAndroid ID

Point at a source to see what it adds.

Used across EleeN

[ 04 / 04 ] FAQ

What EleeNID reads, and where. Identifiers, hashing and working without a partner.

Emails, phone numbers, device IDs (Android IDs included) and your own client ID. Your team maps the columns into these fixed slots once.

No. Identifiers are hashed before they're compared, and resolution runs where your data lives. Nothing is copied out to EleeN.

Yes. Resolve your customers, build audiences and activate them on your own; partners are optional.

It's designed around Saudi data from the start, and resolution runs where your data lives.

Something else?

Ask the team directly.

Book a call

Build your callPick the green words to make it yours.

Resolve the in my into one ID per .

0 of 3 picked

0.0%matched into one ID · Example

Pick a word above, and your example builds here.

Example figures only. Your real ones come on the call.

Your callDraft

About EleeNID

On the call

Resolve the identifiers in my data into one ID per person.

With the EleeN teamRiyadh--:--Book a call

What is identity resolution?

Know each customer, whatever identifier they use. One persistent ID per person, built for Saudi data.

Map your columns once. EleeN reads the columns you map, and nothing else.

Hashed in your database, before anything moves. EleeN reads only the hashed table.

Three records, one person. One EleeNID, the same after every sync.

What EleeNID reads, and where. Identifiers, hashing and working without a partner.

Which identifiers does EleeNID use?

Does EleeN see our raw identifiers?

Can we use EleeNID without a partner?

How is EleeNID different from a global identity graph?

Resolve the identifiers▼ in my data▼ into one ID per person▼.

Map your columns once. EleeN reads the columns you map, and nothing else.

Hashed in your database, before anything moves. EleeN reads only the hashed table.

Three records, one person. One EleeNID, the same after every sync.

What EleeNID reads, and where. Identifiers, hashing and working without a partner.

Which identifiers does EleeNID use?

Does EleeN see our raw identifiers?

Can we use EleeNID without a partner?

How is EleeNID different from a global identity graph?

Resolve the identifiers▼ in my data▼ into one ID per person▼.

Resolve the in my into one ID per .

Resolve the in my into one ID per .