BigMarker Integrations: Microsoft Dynamics

Synchronize webinar registrants and attendees with your entities in Microsoft Dynamics.

Prior to setting up this integration in the BigMarker platform, you'll need to grant BigMarker permissions in Microsoft Azure so that we can access your API. 

To set up your Microsoft Dynamics integration in the BigMarker platform, navigate to the Integrations tab in your Series dashboard. Scroll down to find Microsoft Dynamics

The screen will look like the above image. To begin, you'll need to fill out the Tenant ID, Client ID, Client Secret and Resource. We will need these client provided details in order to connect Microsoft and BigMarker. Once input, select Link Account

Following this, you'll select your export settings in the fields below. Make sure you are checking off Enable Entity Export in order for us to export any data to your Microsoft Dynamics account. 

Next, you'll fill in your Dynamics Entity. The data that will be exported gets delivered to Dynamics Entities. The Entity is essentially a table in a database. The Entity can be anything: an account, a contact, a campaign. If the Entity is a contact, that contact has attributes to then consider. For example, a contact has a person's email address, first name, last name, phone number, etc. The users can map the data we provide to the attributes on the entity, which is then exported directly to them.

Mapping data is in the next section down, which is shown in the image below:

To start, you'll need to input a Unique ID, which is the first line item under the data mapping section. A Unique ID is an identifier to uniquely identify a row within an entity. For a contact entity, an email address can be used as the Unique ID, keeping with our example above. If this data is going to be more widely shared, you can use a combination of email addresses and another field - for instance, DOB. Ensure the Unique ID field is mapped as an alternate key in the Dynamics Entity. To create an alternate key, refer to this document. If not mapped, duplicate records will be created for each export.

From there, the integration exports all the line item data to Microsoft Dynamics. As soon as a person registers to a webinar, we export that data to Microsoft Dynamics. Then the data is exported again at the end of the webinar with additional attendee data. Lastly, the data is exported once the user takes an assessment or once someone watches a recording of the webinar. Just ensure those coordinating fields are filled out and mapped correctly.