The application’s matching functions, referred to as “templates,” are customizable according to the consumer’s input data, request options, and authorized ID types. For configuration specifics for each template, please see the Configure dentsu.Composable Translate App section of the application README. The output fields, referred to as “dimensions,” can be defined when the template is invoked. To learn more about calling templates, see Match Data With Translate.
Some output fields are available only upon request. Submit a support request to enable these non-default output fields.
| Template name | Description | Input fields | Output fields | Settings table fields |
|---|---|---|---|---|
clear_email_match |
Accepts clear emails within a consumer's dataset as input and outputs corresponding matches, including associated dentsu.IDs. | clear_email |
Default: clear_email,hmid,fluid_client,druid_clientUpon request: cmid_client
|
consumer_clear_email_db, consumer_clear_email_schema,consumer_clear_email_table, consumer_clear_email_join_field
|
client_cmid_match |
Accepts client CMIDs within a consumer's dataset as input and outputs corresponding matches, including associated dentsu.IDs. | cmid |
Upon request:cmid_client, hmid, |
consumer_client_cmid_db, consumer_client_cmid_schema,consumer_client_cmid_table, consumer_client_cmid_join_field
|
device_id_match |
Accepts device IDs within a consumer's dataset as input and outputs corresponding matches, including associated dentsu.IDs. | device_id |
Default:device_id,device_type,hmid,fluid_client,druid_clientUpon request: cmid_client
|
consumer_devices_db, consumer_devices_schema,consumer_devices_table, consumer_devices_join_field
|
hashed_email_match |
Accepts hashed emails within a consumer's dataset as input and outputs corresponding matches, including associated dentsu.IDs. | hashed_email |
Default:hashed_email, hashed_email_type,hmid,fluid_client,druid_clientUpon request: cmid_client
|
consumer_hashed_emails_db, consumer_hashed_emails_schema,consumer_hashed_emails_table, consumer_hashed_emails_join_field
|
hmid_match |
Accepts HMIDs within a consumer's dataset as input and outputs corresponding matches, including associated dentsu.IDs. Can be used for transcoding across HMID spaces. | hmid |
Default:src_dentsu_client_key, tgt_dentsu_client_key, src_hmid,tgt_hmid,tgt_fluid_client,tgt_druid_clientUpon request: src_fluid_client, src_druid_client,cmid_client
|
consumer_hmid_db,consumer_hmid_schema,consumer_hmid_table,consumer_hmid_join_field
|
ip_match |
Accepts IP addresses within a consumer's dataset as input and outputs corresponding matches, including associated dentsu.IDs. | ip |
Default: ip,hmid,fluid_client,druid_clientUpon request: cmid_client
|
consumer_ip_db, consumer_ip_schema,consumer_ip_table, consumer_ip_join_field
|
phone_match |
Accepts phone numbers within a consumer's dataset as input and outputs corresponding matches, including associated dentsu.IDs. | phone |
Default:phone,hmid,fluid_client,druid_clientUpon request: cmid_client
|
consumer_phone_db, consumer_phone_schema,consumer_phone_table, consumer_phone_join_field
|
waterfall_match |
Accepts IDs of different types within a consumer's dataset as input and outputs corresponding matches, including associated dentsu.IDs. The standard waterfall order is: ["hmid", "email", "device_id", "ip", "phone"]. |
hmid,clear_email,hashed_email,device,phone,ip
|
Default:source_id,matched_id_type,hmid,fluid_client,druid_clientUpon request: cmid_client
|
|
waterfall_match_internal |
Accepts IDs of different types within a consumer's dataset as input and outputs corresponding matches, including associated dentsu.IDs. The internal waterfall order is: ["cmid_client", "hmid", "email", "device_id", "ip", "phone"]. |
cmid_client,hmid,clear_email,hashed_email,device,phone,ip
|
Upon request:source_id,matched_id_type,hmid,fluid_client,druid_client,cmid_client
|