Event management

Completed

Important

This unit only applies to outbound marketing.

With the Event management settings, you can set up the connections to your webinar providers and manage default settings for events.

To find these settings, open the Settings work area and go to Event management. This section has several pages that are related to event management settings such as webinar applications, webinar providers and configurations, and more. Each of these areas and pages will be discussed in greater detail.

Web applications

The Web applications settings help you register web applications, which is required if you develop custom features that use the Events API to interact programmatically with event features. This feature is of particular interest to developers rather than administrators or end users.

For more information, see Using the Events API and Register your web application to use Events API.

Webinar providers

webinar provider is an external company that hosts webinars. The provider accepts registrations and provides URLs where the presenter and participants can join each webinar. A server to run the webinar is provided also.

Providers usually deliver attendance statistics and other webinar features. Microsoft doesn't provide this service. To run a webinar, you must sign up with another provider and then configure Dynamics 365 Customer Insights - Journeys with the necessary details to connect to that provider.

Each webinar provider that you use must have a record listed on the Webinar providers page. For each account that you have with your webinar provider, you also must set up a Webinar configuration record, as described in the next topic.

To set up a webinar provider, follow the steps in Webinar providers.

Note

If you are choosing to use the Microsoft Teams integration, you won't need to set up a webinar provider or webinar configuration record.

Webinar configurations

After you set up an account with your webinar provider and set up the provider as described in the previous section, you must enter your account details to enable Dynamics 365 Customer Insights - Journeys to authenticate and interact with it. Even if you use just one webinar provider, you might have several accounts with the provider, and you can set up each as needed.

Note

Each time you set up an event or session as a webinar or a hybrid, you must choose a webinar configuration. This approach will help you control which account you'll use for the event or session.

To configure a webinar account, follow the steps in Webinar configurations.

Event administration

In the Event administration settings area, you can set up standard options for your events. These settings are optional, and you can have only one active record at a time.

  • Match contact based on - Choose the strategy to use when you are matching a new event registration to an existing contact record. If a contact record is found that has matching values for all fields that you choose in this section, then the registration will be linked to that contact record. If no match is found, then a new contact will be created and linked to the new registration record. You can choose to match by email alone, by first name and last name, or by email, first name, and last name.

  • Enable demo payment confirmation - This feature lets you simulate payment on the event website for demo purposes. Set this option to Yes to enable demo payment; set it to No to disable demo payment. To enable online payment on a production site, you must partner with an external payment provider and then customize your event site to work with their system. Never enable demo payment on a production system because it can introduce a security vulnerability.

For more information, see Event administration.

Website table configuration

With the Website table configurations settings, you can expose custom fields through the Events API. This feature can be useful if you develop custom features that use the Events API to interact programmatically with event features. This feature is of particular interest to developers rather than administrators.