Identifying Users Twice

In the event that you may not be identifying users with hashed emails and are instead using a different cuid and cuidType, you might encounter difficulty with setting up Triggered Emails since we need to identify users via hashed emails for this module.

As the login and signup events are designed to be used with either hashedEmail OR cuid and cuidType, it is not possible to simply use both in one event. That would cause the API to fail and affect the identification of your users.

What you may do instead is choose to identify each user twice:

• First with their CUID through the login/signup event:

DY.API("event", {
  name: "Login",
  properties: {
    dyType: "login-v1",
    cuid: "...", // Pass the customer ID 
    cuidType: "..." // Pass the customer ID type
  }
});

•  Second with their hashed email, through the identify API that you can trigger once the login/signup event is sent - to connect it to that user:

DY.API("identify", {
  uid: "c0e93cee791b35af528a825f6476e8108e5f03e481ee39800a31a75559cdba2e", //SHA 256 hashed email of the plain text email in lower case
  type: "he"
});

Following that, you can focus on the next steps required for triggered email enablement.

This kind of request can be passed to your Technical Account Manager in the event that you need further guidance and they should be able to facilitate this.