Stop Creating contact as user completes registration using Event Portal

(0) Share

Report

Posted on by LeoFernandas

Hi All,

Could you please help me with my following questions,

Can contact creation be stopped whenever user completes registration using Event Portal in D365 Marketing App.
Would it be possible to track details of those who have registered for the event if contact creation is stopped.
Is there a way to distinguish contact created from CRM portal and Event Portal?

Thanks alot for your answers in advance!

Regards,

Leo

All responses (7)

Answers (1)

cloflyMao 25,198 on at

Like (0)

Report

RE: Stop Creating contact as user completes registration using Event Portal

Hi Leo,

-> Workflow could only send activity email to recipients, if you would like to send Welcome email to contacts who are originated from event reigstration,

you should create a segment and filter out contacts with the field, then add it to customer journey to send them marketing welcome email, workflow is not required for the process.

-> In your current scenario, I thought logic would be If Contact:Originating event contains data:

please check whether there was anything which made the workflow stuck:

My test contact could receive email successfully from my workflow configuration:

Regards,

Clofly
LeoFernandas on at

Like (0)

Report

RE: Stop Creating contact as user completes registration using Event Portal

Hi Roma,

Thanks a lot for taking time to answer my questions!

Regards,

Leo
LeoFernandas on at

Like (0)

Report

RE: Stop Creating contact as user completes registration using Event Portal

Hi Clofly,

Thanks much for your pretty quick and detailed answers which was helpful to me. I found the Originating Event filed was helpful to distinguish contact records created from CRM portal and Event Portal. With this field, I have updated Send Invitation workflow which actually triggers welcome email to redeem invitation and complete sign up as the contact gets created from CRM portal. Now that, there is no email sent out for contact which are created from Event portal.

Logic used to update Send Invitation Workflow:

**************************************************

If "Originating Event doesn't contain value", then send email out.

Regards,

Leo
Suggested answer

Roma Gupta 725 on at

Like (1)

Report

RE: Stop Creating contact as user completes registration using Event Portal

Hi Leo

1. You can't stop contact creation, its OOB functionality & couldn't be customize. Please read more details in link - [View:https://docs.microsoft.com/en-us/dynamics365/marketing/market-to-leads:750:50]

2. Contact creation can't be stopped. Is there anything specific you looking for.

3. Use marketingonly flag for such differrentiation (you can ready it in same URL mentioned above) or if you are using workflow you can also add your own custom field
cloflyMao 25,198 on at

Like (1)

Report

RE: Stop Creating contact as user completes registration using Event Portal

Hi Leo,

I would like to add supplement to my anwser for situation that if a event form submitter is an existing record in CRM:

You should enable matching strategy for event registration, otherwise it'll still create a new record.(By default, it's not enabled)

https://docs.microsoft.com/en-us/dynamics365/marketing/events-settings#event-administration

After enabled it, then it'll just associate an event registration record to the existing contact, but its Originating event wouldn't be populated,

in other word, the field will only be populated when a contact is completely created from event registration form.

So it would be hard to catch submitted information by existing contacts because there is not creation behavior,

and it could prevent multiple registration if we enable the option.

Please let me know whether you still have any other doubt,

and please kindly mark as verified if you had found any anwser helped, it would be greatly appreciated.

Regards,

Clofly
LeoFernandas on at

Like (0)

Report

RE: Stop Creating contact as user completes registration using Event Portal

Hi Clofly,

Thanks a lot for explaining event management portal flow in creating contact and answering my questions.

Regards,

Leo
Verified answer

cloflyMao 25,198 on at

Like (1)

Report
RE: Stop Creating contact as user completes registration using Event Portal

Hi Leo,

---------------------------------------------------------------------------------------------------------------------------

Can contact creation be stopped whenever user completes registration using Event Portal in D365 Marketing App.

When event portal visitor submits event registration form in event portal,

if the person not exists in crm, then a new contact or lead record will be created for it, and a field called Originating event will be populated with the event name.

if the person exists, then its data will be updated with submited information;

at same time, an event registration entity record will be created and assoicated to the contact whatever creation or update.

The whole process couldn't be prevented, but you could delete the associated event registration record with workflow/flow.

Workflow: There is no delete record function in OOB workflow, you need to download third party solution to delete record when a record is created.

https://github.com/demianrasko/Dynamics-365-Workflow-Tools/blob/master/docs/Delete%20Record.md

---------------------------------------------------------------------------------------------------------------------------

Would it be possible to track details of those who have registered for the event if contact creation is stopped.

Yes, as we did in your first question, the new created contact/lead record will be kept even if we had deleted their reigstration.

---------------------------------------------------------------------------------------------------------------------------

Is there a way to distinguish contact created from CRM portal and Event Portal?

Could you let me know what CRM portal refers to?

Acutally there are two type portal to host event page: CRM Portal and Powerapps portal, the previous one will be migrated to the last gradually,

however, whatever Portal type we use, Originating event field would be the only field/flag for us to identify/distinguish whether the contact record is from event registration.

Regards,

Clofly