Troubleshoot event management in outbound marketing

Note

Azure Active Directory is now Microsoft Entra ID. Learn more

Important

This article only applies to outbound marketing, which is gradually being removed from Customer Insights - Journeys. To avoid interruptions, stop using outbound marketing and transition to real-time journeys. Learn more: Transition overview.

How are contacts created in event management?

• Contacts in event management are created when:
  • A website visitor (1) registers through a portal or (2) logs in through Microsoft Entra ID using the events API.
  • An attendee (not necessarily the same as a website visitor) (1) is registered or (2) a pass is paid for the attendee (a contact isn't created before this action).
• Contacts are merged when an attendee matches an existing contact by email, name, or surname. The merging functionality is configurable.

My portal is blank, what can I do?

Make sure that:

• The portal language is the same as the Dynamics language.
• You don’t have duplicate webpage records (same partial URLs twice, which results in a 404 error).
• You didn’t upload the script files manually. They need to be deployed through a script.
• Localized content exists for your webpages.
• The event portal has all 44 languages.
• Script files are attached to web files in the Notes section.
• The viewing user has permission to view the webpages.

Before any portal changes, you should make a backup of the current website.

After changing the sample website, changes don’t reflect or it’s showing errors

• When deploying the changes:
  • Change the website code in the /src folder, not in /dist folder. The /dist folder will be rebuilt when deploying from /src files.
  • Run the script for deployment.
• Depending on where you want to deploy, make sure the changes are reflected in the appropriate environment configuration files:
  • The portals deployment script uses the environment.d365.ts configuration
  • For self-hosting, you should use environment.selfhosted.ts, but you also need to build with ng build --configuration self-hosted.
  • Local testing: use the environment.ts configuration and build without any parameters (ng build).
• As best practice:
  • Before deploying to your production environment, test the code changes locally using the self-hosted approach.
  • Make sure that your website builds and runs without errors locally.

I hosted the sample website on my IIS server but I cannot get it work, what can I do?

Even though hosting the website anywhere is possible, Dynamics 365 Customer Insights - Journeys can't configure or debug the custom hosting environment.