Add Email Domain Embedded field to contact in a directory when added or is updated and show in distribution funnel in dataset

You can store the email domain as an embedded data field at the contact level. Filter the Respondent Funnel by email_domain and Distribution Category to analyze bounces by domain.

Thanks for the reply ​@PeeyushBansal .  Will the new embedded data field show up automatically in the distribution data funnel dataset or is there step I need to do to make that appear?

Would you do this using an Experience iD event change (updated / added) method or would you do this in the specific distribution work flow (which already maps various embedded, transaction and contact fields to the contact when a survey is sent)?

Then, using a code task and some javascript perhaps something like :

email_str = ~{qde://common.Email}

const result = email_str.split('@')[1];

Thanks

Rod Pestell

I have a feeling that if I use the ‘update / add’ Experience iD event, am I likely to cause a continuous loop where by when it updates the contact field it will register an update and execute the code again?

if so, maybe the better way it do it in the survey distribution flow.

What do you think?

Thanks

Rod Pestell  

yes better is to do in survey flow

ok, thanks  (presume you mean the distribution flow as it’s not just survey responses I want the email domain to be populated but anyone who has been sent an email and is present in the directory).

doh! slight problem in that I can’t see the individual email addresses / contact IDs as it’s a batch process.  Can you suggest away forward?

Not too sure what to do now.  Hoping you can help

Thanks

Rod Pestell

Use a basic transform task to create your domain field, probably a split transformation.

Also, your new field won’t automatically be available, and you won’t have it for past funnel data events. See Enabling Additional Fields on the funnel data support page for the procedure.

Hi ​@vgayraud .  Thanks for the idea, i tried the basic transform but it needs a source and that is the SFTP file which doesn’t have the Email_Domain field in so I’m unable to ‘add’ the extra field and then use that as the source for the add contacts and transactions to XMD task.  Is there a way round that?

Just FYI - I did try the ‘update / add Experience iD event’ and when I update a contact (just limited it to one for testing), the flow ran twice.  Would that be a problem on mass (2K upload each day of contacts)?  If not, I could just settle with that but gut feel is making me think it might not be a good idea. 

Thanks

Rod Pestell

Hi,

Your workflow would probably look something like this:

The basic transform task would process the extract from sftp files with a transformation like this on the email field:

Resulting in this, where Email-2-1 would contain your domain.:

You can then select the result of your basic transform task in as the source in your add to XMD task.

Hope this helps!