Reltio Connect

 View Only

An In-Depth Look at the Dun & Bradstreet Connector - Webinar

By Chris Detzel posted 11-08-2021 13:06


This video discusses how Reltio's out-of-the-box Dun & Bradstreet (D&B) connector can enrich your existing organizational data and provides you with further insight into the operations of your customers and suppliers. For more information, head to the Reltio Community and get answers to the questions that matter to you:


Chris Detzel (00:05):

All right. Well, hey everybody. So thank you everyone for coming to another Reltio community webinar. Today, we have actually two people. So my apologies, Michael, for not putting you on here, but we have Joe Snipes, senior technical consultant. We also have somebody representing D&B, Michael Gandolf here to answer questions. I think he's going to go through a couple of things as well. So it's really showing the partnerships, so appreciate those guys being here, but we will be talking about the D&B connector and we will be going in depth. So I am Chris Detzel. I'm head of the community here at Reltio. Keep yourself on mute. Please ask questions in the chat. I'll make sure that these questions get answered as usual. The webinar will be recorded and shared out on the Reltio community by next week. Again, I always hope that it's going to be Friday, but we'll see.


Chris Detzel (01:06):

So just some quick news, it's it is a big day for us, and it's a great day for our clients. So we're super excited to announce that Reltio did secure $120 million in funding round that was announced today. So it's value in our business at approximately $1.7 billion. I did add an event on the community. I'll show that here in a minute for you guys to join us, if you'd like, virtually at the NASDAQ, it will be November 9th at 6:30 Eastern Time. So we're super excited about that. Please read all about it. If you go to, I've posted it pretty much everywhere that I can, and you'll see links to the blogs and the news release.


Chris Detzel (01:58):

We do have lots of community webinars coming up by the end of the year. That's one of them today, an in-depth look at the D&B connector. Please also go to the celebration at NASDAQ with Reltio, if you want to attend, just RSVP and all that information will be filled out, or it'd be sent to your calendar directly. Then to kind of go further with the Reltio Integration Hub, next week, we have a webinar on building recipes with Reltio Integration Hub. So we go a bit deeper into that. Certainly excited about that.


Chris Detzel (02:35):

Then there's two webinars on the Salesforce connector. One's just an overview. Then one is a little bit more in depth on how to set it up. Then another one that you guys really pushed on the community, interesting enough, is around Reltio workflow, process design, and deployment. That one is exciting, because I've seen lots of questions around it and I was like, "Hey, we need to get a webinar." We have it. So I'm going to stop sharing. Lots of great stuff on the community. I think I'm going to hand this over to Joel, is that right?


Joel Snipes (03:11):

That's right. Thank you, Chris, for that great introduction. I want to thank Michael Gandolf from Dun & Bradstreet for being here today to help us with this webinar. I want to start by giving anyone who's not familiar with Dun & Bradstreet a little bit of an introduction, and I'll let Michael kind of give an overview of what Dun & Bradstreet can provide. So, Michael, do you want to tell us a little bit about the kind of data you provide, how Dun & Bradstreet brings value to our Reltio customers using the connector?


Michael Gandolf (03:50):

You bet. Thanks, Joe, and thanks Chris for the introduction as well and the opportunity. So Dun & Bradstreet, we've been around for over 180 years, so it's not about the number of years. It's really what we've amassed from a data insight perspective, over 420 million organizations across the globe, we have information on, we have a unique identifier. We call the DUNS number, and we have linkages and hierarchy and a tremendous amount of insight that can drive AI ML and a lot of different use cases, right? The use case that we're starting with today is around master data management in our prebuilt integration into Reltio.


Michael Gandolf (04:28):

When you think of Dun & Bradstreet holistically, it's the data sets that drive things like governance and quality, sites that drive AI and ML. The important part of our partnership is prebuilt connections. So you have connectivity and integrations out of the box. Towards the end, I know we'll talk about Reltio Integration Hub, which can take additional use cases and data sets of Dun & Bradstreet data throughout your ecosystem, not just Reltio, but other parts, be it ERP, CRM, marketing automation, etc. So I want this to, from a standpoint of how you view Dun & Bradstreet, be focused first on the master data management use case, creating that golden record with our third party data set, and then moving on to other use cases, which we'll talk about with the introduction of the Reltio Integration Hub.


Joel Snipes (05:17):

Awesome. Thank you, Michael. So the out of the box D&B connector really lets you get up and running with Dun & Bradstreet really, really quickly with. From day one, after you've turned on the Dun & Bradstreet connector and start matching enriching profiles, Dun & Bradstreet has a proprietary system to find the right DUNS number based on your companies that you're trying to enrich name, their address, and their phone number is what we send over. We get back that DUNS number. That gives us another avenue to match between your existing records and get to that gold record. On top of that, then we can enrich the profile. So that brings in a lot of that market data and that overview of what your customer or your supplier looks like that you're enriching in Reltio.


Joel Snipes (06:20):

On top of the enriched data, it gives you a hierarchy. So companies have complex legal structures, you have subsidiaries and corporate headquarters. You have domestic headquarters and you have global headquarters, and that relationship can be difficult to track that. Dun & Bradstreet brings in that relationship and hierarchy information for you and continues to manage it for you through their proactive monitoring. So once you have a Dun & Bradstreet DUNS number applied to your Reltio profile, you can now have Dun & Bradstreet monitor that DUNS number. When updates come through, they can automatically be pushed to Reltio, which is one of our cooler, newer features with the DUNS street connector.


Michael Gandolf (07:05):

Hey, Joel, if I can add too, that was a fantastic overview. Just for some additional insights, think of it from all types of business entities. So that would be customers, suppliers, partners, etc, that can all be mastered in the Reltio solution. For both the monitoring piece, it's important to note that we have over 30,000 data sources coming in to our data file, and we have over 5 million updates a day, which certainly sounds like it's overwhelming, but the way that monitoring is set up is we'll push the notifications that you care about when they change on specific entities or organizations that you want to monitor.


Joel Snipes (07:44):

Thanks for pointing that out, Michael, and just to curiosity, for the monitoring, I know you have good coverage of things like the S&P 500 and that sort of thing. How about smaller businesses and not publicly traded companies, is the monitoring available for that as well?


Michael Gandolf (08:00):

Yeah. Yeah. That's a great question. It's also could be a misperception about Dun & Bradstreet data. Obviously publicly traded organizations have more breadth and depth of data that's available. That's really where Dun & Bradstreet comes in. If you think about, we have 420 million plus entities across the globe, close to 30 million, just 30 million in the US and Canada. Most are private entities, right? Only a very small fraction of organizations are publicly traded in the globe. So our coverage of that 420 million plus, that's where we gather this data from those 30,000 sources, such as financial institutions, court systems, proprietary ways to gather data. So most of our data actually is on private and small businesses, right? Because it matches the marketplace. Absolutely, if we have the organization, it has a DUNS number, and data can be monitored.


Joel Snipes (08:55):

Awesome. That's that's great to know. So there's really two connectors that come with the implementation of a relative Dun & Bradstreet connector. The first one I want to show you is the on-demand connector. The on-demand connector uses three of the Dun & Bradstreet direct plus APIs, the "get matched" to find the match based on that phone number, the name of the company and the address, the "get company details" call allows from enrichment, and these map one to one with our buttons in the UI. That's what they look like. They're normally in the right panel on the top of your screen. We're going to jump into the UI in just a little bit and I'll show you how they work.


Joel Snipes (09:41):

When you make that enrichment call, what we call the "get company details", it also comes with the company hierarchy in that. In the bottom, I have a little chart explaining what kind of permissions you would need to be able to make these calls from your tenant. The main one I want to point out from a configuration perspective is you need role API, which is kind of basic API access for both your tenant and what we call the data tenant. The data tenant, for those not familiar with our DTSS architecture, is a staging area for matches that might be a potential match from Dun & Bradstreet. So they come with that, a ranking system, a match score of one to 10. You might not immediately know which match it might be versus a headquarter and maybe a domestic, or multiple offices for a particular customer. This lets a data steward view the potential matches in the UI and make an educated decision on which one they want to match with.


Joel Snipes (10:53):

So with that, I want to jump out to the user interface and take a look at what that would look like. So we have an Apple profile here. I'm just going to refresh the page. We have in the top right panel with all these other tabs, we have the Dun & Bradstreet connector tab, and our two buttons I showed you earlier, the "get matched" and "get company details". When I call all "get matched", it's going to send an API call with the name Apple and address to the direct plus API at Dun & Bradstreet. It's hopefully going to bring us back some potential matches.


Chris Detzel (11:45):

Did you say hopefully?


Joel Snipes (11:48):

Well I may not be leading on to that. I've pressed the button before for this record, but I deleted it and backed it back out. So Apple has a big presence in the United States and surprise, surprise, we have 25 potential matches at varying qualities. So when a data steward comes from that first certification sees that, "Hey, I have 25 potential matches." They're going to move to the potential match view over here on the left pane. They can compare their record here on the left side with three potential match records from the Dun & Bradstreet connector. On the right side, we also have 25 other potential matches, and we can change which one's currently showing by clicking these flags and moving them to the active pane to compare.


Joel Snipes (12:45):

So you can see here, the address in our record is 1 Apple Park Way, and the three samples I have up, only one of those has a matching address of 1 Apple Park Way. That is this first record with a confidence code of 10. So a confidence code of 10 coming back from D&B is the highest possible confidence code. It is very confident that this is the Apple we are looking for. So from here, I can make a decision to say not a match, which I'm going to say this San Francisco address is, which will remove it from this view. Or I can merge in the record I do believe to be a match. I can click and add it to my record. All right-


Chris Detzel (13:39):

Hey, Joel.


Joel Snipes (13:40):



Chris Detzel (13:41):

We have a couple questions already. So we know that this is an active group. If you're going to cover this later, just let me know, but would like to understand how to set up monitoring for D&B connector on a Reltio tenant. I know some steps are on the D&B side, but I'd like to know the steps on Reltio side to set this service up. Is that something you'll be covering in this or is that...


Joel Snipes (14:04):

We'll be talking about it at a high level, but if we have some time, I can dig in a little further.


Chris Detzel (14:08):

Okay. Then the other question is, they're starting to come in now, do we have control over the threshold for confidence score and the MVP score?


Joel Snipes (14:21):

We do. So by default, if you have only one matching record with a confidence code of nine or 10, it will automatically merge. So the reason our confidence code 10 record with a potential matching did not automatically merge is because there was also a confidence code nine, which was close enough for it to say, "We're going to let a data steward intervene here." But if we had only had a single record with a confidence code of nine or 10, it would have auto-matched. Then records from six and up will always show potential matches, but this is configurable by the realtime mapping API. So we have a API that will let you update how the Dun & Bradstreet data is brought into your fields, and in that, you can adjust the settings of what auto-merges, if you want anything to auto-merge, and what threshold you'd like to have potential matches show up.


Chris Detzel (15:24):

That was a great question, [Haresh 00:15:26]. The other question from [Paresh 00:15:28] is, "Does the first step of three matches come up based on the highest to lowest confidence score?"


Joel Snipes (15:37):

That's a good question. I know we have a enhancement request currently out for that. I always see the best match as the first column, but the rest of the matches seem to be displayed a bit at random. So in this particular example, when you have 25 matches, you might have to do a little digging. 25 matches is the max we bring back. Most cases bring back a fewer matches, especially for smaller companies so it's easier to identify, but that is a good chance to enhance this. I think they should be ordered in order of their confidence code, or at least have them displayed here.


Chris Detzel (16:19):

Yeah. Another good question. So, all right. Keep going. Thanks.


Joel Snipes (16:22):

All right. So we have matched our record, and what I want to do is jump over to the crosswalk resources view to kind of give you an idea of what's happening behind the scenes. So this red Dun & Bradstreet crosswalk was created when we pressed the button, even if there were no potential matches available, this record would have this crosswalk created. What it does is it populates two flags, letting us know if it has suspect matches or automatic matches available from the Dun & Bradstreet connector. So this is really a audit trail, letting you know that the button has been pressed for this record previously.


Joel Snipes (17:06):

The second crosswalk we've created after the merge is the DPT crosswalk. You see it has the DT colon deleted. That stands for data tenant. This means this record has been brought over from our Dun & Bradstreet data tenant that I alluded to earlier. When we merged, it brought that data, and you can see all the purple fields are what's populated, the most important of which is the DUNS number. We did not have the DUNS number for this record previously, and this is what's going to allow us to enrich our record, but it also brings over the matching criteria data, like the phone number, the address, and the name along with it. So it kind of gives you a baseline of your DUNS view of your record. But most importantly, you have your DUNS number.


Joel Snipes (17:58):

So I've had some customers who have migrated the Reltio who have already gone through the match process with Dun & Bradstreet, and they already have a DUNS number. If that's the case, you can skip this first step all together. You don't need to do the get matched and merge. If you have a DUNS number for your record, you can immediately go to get company details. Get company details looks up your DUNS number and brings back the company profile. So I'm going to go ahead and press that.


Joel Snipes (18:35):

All right, enrichment successful. Notice how the hierarchy will likely update. This is the top hierarchy. So we're not actually going to get that, but I'll jump to another record with a hierarchy in a little bit. So the API we use is get upward family tree. If you enrich the highest record, there is no upward family tree, because you're already at the top of the tree. But if you started with, for example, a parent record, or one of the children records, you'll get the parents, grandparents, etc. So I have a example of that I can show you.


Joel Snipes (19:39):

So I enriched a Accenture Office at the lowest level, and we got its parent, grandparent, and great grandparent all the way up to its global headquarters in Dublin. It actually went ahead and created three more organizations and the relationships in between them. So for our Apple example, we can see a whole lot of data that didn't exist previously has been brought in. Conveniently, it's all located in this Dun & Bradstreet facet. We have information about his trade style name, the hierarchy, and the DUNS number of the other records in the hierarchy, financial figures in terms of revenue and growth, all sorts of industry codes and that sort of thing. We have the web URL, which we didn't have previously. This has all been brought in by the company details call.


Joel Snipes (20:43):

So this is an overview of that real-time connector. This is meant for ad hoc data stewards to come in and enrich records individually. A lot of the times, if you have a big data set, you don't have the time or manpower to go through and enrich each record in your system manually. So next, I want to talk about the batch connector. So this lets us enrich our records at scale, which is really cool. It's an asynchronous API call you make from Postman or any other kind of rest API tool or ETL tool. What happens is you supply a filter, so some search criteria, of records you want to enrich in Reltio. My go-to is any organization without a DUNS number.


Joel Snipes (21:39):

Reltio will extract all of those records and drop them in an S3 bucket, which Dun & Bradstreet is monitoring. Dun & Bradstreet will then pick up the records, match them, enrich them, and drop them back in the S3 bucket, and Reltio loads, it enriching your records. By default, any match, the best match available over a match score of seven is matched to your data. So unlike the real time connector, you don't have a potential match or a data steward managing what gets enriched and what doesn't. So that saves you a lot of man time, but it also is a bit of a double-edged sword. So depending on your use case, I've had customers use different match score settings. This is completely configurable. So for like a marketing use case, I have a customer maybe dropping the match score to a five or a six, because if it's not quite right, not a huge impact, maybe just a few marketing dollar wasted, but the potential of having the information outweighs that.


Joel Snipes (22:55):

Whereas if you have a use case that requires a high degree of accuracy, you might set the threshold to an eight. It also has a setting to automatically match records with the same DUNS. So if two records that are currently in your Reltio tenant resolved to the same DUNS number, you can have Reltio automatically merge them. So you're getting some value on your match and merge side on top of just the enriched data. But there's not much of a demo here, because the service level agreement is up to 48 hours. It very rarely takes that unless you have absolutely massive data sets, but it wouldn't be conducive to a one-hour webinar.


Michael Gandolf (23:45):

Joel, is there a max amount of records that can be put through that batch process within that 48 hours? Do we cap it for clients just to set the right expectations of turnaround?


Joel Snipes (23:58):

That is a good question. I am not aware of a max, and I've put some 10 million plus data sets through that were in well under a day, but I'd have to get back to you for that to know the max.


Michael Gandolf (24:12):

Yeah, that'd just be one of the typical questions. I got it actually offline from a client asking that same. So we certainly can take that and verify, because that's a great volume that we see come through there. So that tends to meet a lot of needs of our clients, so appreciate that.


Joel Snipes (24:31):

Yeah. Thank you for that question. I'll have to get back to that.


Chris Detzel (24:35):

Hey Joel, I have a question. So in the batch use case, what happens if more than one record has match score of greater than seven?


Joel Snipes (24:45):

Good question. So Dun & Bradstreet returns their records in order of match score. So if you have two records of match score seven, there is still a waiting within the seven and the best record is returned first. So if there's two match score sevens, your record will still be enriched. The order they returned in affects which one wins, but that order is meaningful.


Chris Detzel (25:19):

Thank you.


Joel Snipes (25:23):

All right. If there's no further questions, I'll jump to monitoring, which I know was asked about earlier.


Chris Detzel (25:30):

There is one more question.


Joel Snipes (25:33):



Chris Detzel (25:35):

If you give me a space, then I'll ask it. Does the D&B enriched data get stored in Cassandra/GBQ?


Joel Snipes (25:45):

Yes. It's brought over like any other Reltio data that you load to your tenant. So it's stored in a crosswalk. It is stored in Cassandra in the back end and indexed by elastic search, just like any other data.


Chris Detzel (26:01):

So many of our customers have more than a thousand family members. Are they all loaded into Reltio?


Joel Snipes (26:10):

Yes. So it gets the upward tree. So it's not going to get your sibling members. For example, if you were a CVS, right. CVS has a lot of locations. If you were to find the DUNS for a particular store, it would not go sideways to all the sibling stores across the United States and the world. It would only give you its regional headquarters, its domestic headquarters, and global headquarter.


Michael Gandolf (26:42):

So Joel, yeah, that would be defined as that upward linkage from where you started in the tree, which would be the direct parent, the domestic ultimate, the global ultimate, for example. If a client does have a use case to bring in that full family tree, which would be downward sideways, right? All entities, branches, divisions, etc. Is there ability to bring in that full family tree and map that within the Reltio solution?


Joel Snipes (27:08):

Not within the Dun & Bradstreet connector, but the Reltio Integration Hub, which we're going to touch on later is going to give you that kind of opportunity to use some of the Dun & Bradstreet APIs that aren't immediately available in the connector.


Michael Gandolf (27:23):

Great. That was kind of a leading question on purpose. Perfect.


Joel Snipes (27:28):

Yeah, really good one. All right. So whether you use the on-demand Reltio D&B connector or you use the batch connector, you are now at a point where you have the DUNS numbers for your data in Reltio. The next step is to configure monitoring. So monitoring is what brings in the updates after you've already been enriched once. As things change over time, Dun & Bradstreet can push fresh data to your tenant. The first step is to register with Dun & Bradstreet for a monitoring solution. You set up a place for your data to be stored, what products you're using, that sort of thing. After you have that initial registration done, everything else can be done within the Reltio APIs.


Joel Snipes (28:28):

On registration, you set up a seed file of which initial records you want to have handled by monitoring The best practice for us is just to set a seed file with one customer, because the monitoring APIs are going to populate the rest of your monitoring list with the data in your tenant. So there's no need for you to go and try and do an extract of all your DUNS numbers from Reltio to set up your seed update. Just pick one and go ahead and set it up, because you have to have one to start. After that, you can subscribe the rest with the monitoring APIs


Joel Snipes (29:12):

You set cadence. So you could have your monitoring updates push weekly, daily, monthly, quarterly, yearly, that sort of thing, intraday even. You can set a Cron schedule to pick how often the Reltio connector goes and scans for updates to be pulled in. So once you schedule that Cron job to run every so often, it's just a wait and see. As Dun & Bradstreet gets updates, they will flow into your tenant. For decent sized data sets of over, I don't know, maybe a couple thousand, you normally start seeing updates within a day or two if you're doing daily. You'll also get email notifications every time you have a monitoring update come through as well. So that'll help you keep track on what's going on.


Joel Snipes (30:11):

If anyone's familiar with the batch connector already, this is our newer product at... The monitoring is our newer product. The monitoring API is very, very similar to the batch API, just a different endpoint, but the way you schedule jobs and handle filters and everything like that, absolutely the same. If we didn't have to wait a couple days for an update to come through, I would demo monitoring for you, but I don't think anyone wants a 48-hour webinar.


Chris Detzel (30:39):



Joel Snipes (30:44):

So one of our recent updates at Reltio is the introduction of our Integration Hub. This is a really cool low code, no code solution for bringing in data sets to Reltio and from all over places. There's an out-of-the-box connector that's very easy to use, and Dun & Bradstreet also has a connector. So it's really easy to integrate data sets that aren't currently available throughout the connector. Michael kind of alluded to that earlier. So Michael, can you tell me a little bit about what other use cases and opportunities are out there to bring in Dun & Bradstreet data outside of what we have in the connector?


Michael Gandolf (31:27):

Yeah, sure, Joel. So think about it as outside that MDM golden records use case, which you just demoed. So one is the full family tree, which you mentioned. So if you want to bring in that entire family tree, all the members, that can be brought in through the Reltio Integration Hub by a specific API call that's licensed with D&B and leveraging the hub to map those fields. Additionally, I think a big use case that would be important to cover would be around the financial and credit risk perspective. So whether that data will be mapped into Reltio or SAP or other downstream systems, you can leverage the Reltio Integration Hub to bring in very specific use case data sets. So credit risk being one. If you think about supply chain, it could be around minority women-owned businesses. It could be around compliance, [inaudible 00:32:21] lists, etc. Compliance, which I just alluded to, also with beneficial ownerships, who was the actual owner of an organization in doing a conflict of interest.


Michael Gandolf (32:36):

Additionally, in sales and marketing, deeper-level insights, activity triggers, information on an organization that you might bring into market automation, downstream systems, Salesforce, for example, additional levels of detail. Again, going back to that financial and credit risk into finance systems. So that breadth and depth of D&B data outside the traditional MDM use case can all be brought in with very easy mappings through the Reltio Integration Hub. I would just start with saying from the MDM use case, leverage the out-of-the-box connector that's built, Then as we build out from additional use cases data sets, collaborate with both Reltio from the hub, as well as Dun & Bradstreet and your sales rep to license the specific content. We call them data blocks that are specific to that use case. So there'll be some good collaboration between Reltio and D&B with the end client to get the best result.


Joel Snipes (33:35):

That's going to be a great opportunity, because I, just a few months ago, had a customer who wanted to bring in that diversity and women-led business data. It just wasn't available in the current connector, but it could probably be configured really quickly with this Integration Hub. I've already done a few sample recipes, and it's amazing how quickly you can get up and running.


Chris Detzel (33:58):

That sounds really cool. You have a few questions here. So this I think came before this particular slide, but [Harish 00:34:07] asked, "Are there any custom monitoring alerts that we can set, for example, when bankruptcy indicator changes?"


Joel Snipes (34:18):

That's a good question. So inside the monitoring tool, it's specifically looking for updates from Dun & Bradstreet, but within Reltio, it would not be difficult to configure a alert around bankruptcy, for example. The way you would do that, and I think you would actually probably use the Integration Hub to do it, is Reltio, every time there's an update to one of your records, it publishes a message to an SQSQ, and that allows for real-time downstream integration.


Joel Snipes (34:55):

So if you put that bankruptcy attribute attached to that SQS message, and that's pretty easily configurable, you can now listen for bankruptcy alerts. All you would do is have the Integration Hub, you'd have that SQSQ listener as the trigger. When a message comes in, you would read it, say, "Does this equal bankruptcy? If so, send out an email or, or publish a report to a Google Drive," or something along those lines. So while that's not out of the box with a Dun & Bradstreet connector, that's one of those opportunities the integration Hub's going to enable.


Michael Gandolf (35:38):

Exactly. I think the other one that comes up quite a bit is merger acquisition from a corporate family tree structure, because there's a lot with sales operations that gets impacted if there's a change in the family tree, be it from a merger or a divestiture. So same thing there, you want to bubble up the monitoring events that are most important, rather than be inundated, it's hard to sift through. As we talked about those additional use cases, both in supply chain, merger and acquisition, and hierarchy is so important. In [inaudible 00:36:08] of the finance or credit risk use case, changes in risk type, predictive scoring is very important as well for how you manage both suppliers as well as customers throughout the organization from collection as well as supply chain disruptions.


Chris Detzel (36:26):

Thanks, Michael. Really good, and I thought for a minute, Joel was going to be stumped, but I guess not. We have another question. "Like the D&B connector, do we have any more of these kind of tools in our Reltio platform?" I think that's a loaded question, but...


Joel Snipes (36:44):

We do. So we also have the Salesforce connector, which allows for a bidirectional sync and search before create kind of use cases for integrating with your Salesforce CRM. There is a Snowflake connector and there is also a Google BigQuery connector. So a lot of opportunities out there in the connectors. If your connector doesn't exist, it's probably just one recipe away in the Integration Hub. Something I wanted to mention, I know Dun & Bradstreet has a library of recipes available. So most of the work would be done for you. The only piece you really have to do is that connect the Reltio at the front of the recipe to build out a lot of these things.


Michael Gandolf (37:36):

Yeah. Just to build on that, Joel, as well is when you think about the Reltio Integration Hub, the data contained within Reltio to get a master record as you move that master record, DUNS number, the global ultimate DUNS number throughout your ecosystem into things like SAP, CRM, market automation, that is where traditionally we'll see additional data sets being integrated or leveraged for AI or ML. If it's to prioritize prospects by most likely to purchase or by financial risk, that's where the data can be enhanced through the Integration Hub and pushed out to your entire ecosystem to be leveraged. But starting within the hub of Reltio is your golden record. That can be enhanced further using the Integration Hub with all those additional D&B data insights.


Chris Detzel (38:32):

Yeah. Thanks guys. I think we have some more questions coming in. By the way, we've covered most of the connectors on one webinar or another. We do have a Salesforce connector community webinar over the next few weeks. So we have two of those coming up. So make sure you listen in, or you can go to the community to see all the past webinars. So it looks like Jay answered one of Gino's questions. I'm not going to go into that. Then there's another question that says, "Search before create use case is supported with the native D&B connector or is it through the Integration Hub?"


Joel Snipes (39:09):

The search before create was in relation to the Salesforce connector. So it lets you search to see if a record exists in your Salesforce instance before you create it in Reltio. For Dun & Bradstreet, that use case doesn't really make as much sense, because you're normally taking existing data and trying to enrich it with what's available in Dun & Bradstreet.


Michael Gandolf (39:36):

Joel, just to dig into that just a little bit, just from a workflow perspective. So couldn't the use case B a, whether it's a sales rep working in Salesforce and they want to create a new opportunity or a new record, that that's where it would do the search within Reltio MDM before creating that record in Salesforce to drive data stewardship, de-duplication, things like that? Is that along the lines of maybe that same question?


Joel Snipes (40:02):

That's exactly it. Yep.


Michael Gandolf (40:04):

That's where we see a lot of advantages around having that search before you create within the application of Salesforce to always check the MDM from a data stewardship and governance perspective. Then it can obviously point to that golden record or that DUNS number if it does already exist. But typically from a sales rep perspective, reps have traditionally not been very good at providing correct data, the onset of setting up maybe an opportunity or a record. So it's a good way to standardize that and catch mistakes and duplication before they get created in the CRM workflow.


Speaker 4 (40:42):

Yeah. The question basically was in our use case, search before create is first do the search in the Salesforce. If doesn't find, go to the Reltio, if it doesn't find, is there a scope we can go into D&B universe. So we want them to everything pre-populate for them. They don't have to pick the right account. So that's why the question is through the D&B connector, if you get that visibility of search before create or not. I know through the Salesforce connector you have, which we are planning to use, but from a D&B connector standpoint, do you provide that, or it has to be through the Integration Hub?


Joel Snipes (41:24):

That doesn't exist through the out-of-the-box connector. So that would be an Integration Hub kind of thing.


Speaker 4 (41:31):

Use case. Okay. Got it.


Joel Snipes (41:32):



Speaker 4 (41:34):

Thank you.


Chris Detzel (41:37):

So I love the teamwork here. This is great. We have Jay in here answering some of these questions and going into detail. Love it, Jay. Thank you. We have Michael here teaming with Joel here to really help out. It's so awesome. One more question, and then we can get going here. Can you please give a ballpark figure on the cost to D&B for the company you connect for? So I think that's probably going to be a question for either your customer success manager and/or sales rep, but I don't know, Joel, if you can touch on that or...


Michael Gandolf (42:11):

I'll get Joel off the spot I'll take that one. So yeah, there's a lot of factors, right? So it will be the number of records. There's obviously volume discounts when you leverage D&B agreements directly with Dun & Bradstreet. So again, just to clarify, the connector and Reltio's licensed by Reltio, the D&B data set, and API's licensed directly through Dun & Bradstreet and your sales team. So without trying to avoid the question, it really depends on volume of records that you look to match and enrich, as well as the ability to update or monitor those records. Then additionally, with the Reltio Integration Hub, the D&B sales team member would be able to quote accurately based on volumes, those specific what I call data blocks, specific data sets that could be integrated into those recipes for the use cases.


Michael Gandolf (43:07):

I could say it's anywhere from a couple cents to a couple dollars a record. That probably doesn't help you. So feel free to reach out to me directly and I can connect you to your D&B sales rep. If you don't have one, I'll ensure we connect directly and get you in touch to get some accurate pricing. So not to avoid the question, there's just a lot of factors in determining the investment of a D&B data record.


Chris Detzel (43:30):

Yeah. Just maybe shoot your email in the chat. That'd be helpful so that they can person personally send a note. All right. So let's keep going, Joel. Thank you.


Joel Snipes (43:42):

All right. That's actually where I wanted to leave off, because I think the Reltio Integration Hub leaves basically limitless possibilities on what you can do between not only Reltio and Dun & Bradstreet, but like we were talking about, Salesforce, Snowflake, or any new or existing system, ERP, etc. So that more or less covers and wraps up the Dun & Bradstreet connector from my side. So unless we have any more questions, I think we can finish.


Chris Detzel (44:15):

Well, so far, there are no other questions, but again, I want to thank you both for coming, Michael and Joel, lots of really great conversation here. I love these kind of webinars where people are asking questions and we get direct answers. So thank you everyone so much. We are-


Speaker 4 (44:38):

Chris, I have one question.


Chris Detzel (44:40):

Yeah. Yeah.


Speaker 4 (44:41):

Just wanted to just follow up. On the monitoring service, Joel, you mentioned the APIs are there, which is very similar batch APIs, but is there a place I can look at the monitoring service APIs?


Joel Snipes (44:59):

Yes. So if you go to, you can see I've been searching for them recently. So if you search for monitoring APIs, it'll bring you to this header and there are kind of six children. So there's one for registering or removing a particular entity. The one I use most often is the one for registering multiple entities.


Speaker 4 (45:39):

So before we trigger this one, we have to set it out with D&B for the registration. Once the registration is done, then I can go and add this one out, right? Or this is the first one?


Joel Snipes (45:53):

That's right. So once you've have your D&B registration, they're going to give you a registration identifier, which is one of our required fields here. That is what enables you to start monitoring within Reltio.


Speaker 4 (46:06):

Yeah. That's the information I was looking. So the registration identifier needs to put in over here. Okay.


Joel Snipes (46:13):



Speaker 4 (46:14):

Makes sense. Got it. Thank you.


Joel Snipes (46:17):

You're welcome.


Chris Detzel (46:18):

Thank you. Then if you're interested and you don't use the D&B connector, Michael has put his email there. So make sure you get to touch with him. As of now, that concludes our webinar for today. Thank you so much to D&B and also Joel for the webinar. Thank you all for coming. Please quickly put in a note on if you enjoyed the webinar and that kind of stuff. I love giving feedback to my boss and whoever else is interested in the feedback, but I know I'm interested in the feedback on how we're doing. But great job as always, Joel, as [Harseh 00:47:00] mentioned. So thank you everyone for coming. Really appreciate it. I'm going to stay on for another minute or two, if there are other additional questions I might come in.


Michael Gandolf (47:10):

Hey Chris, thanks again for the opportunity. There's a way to post questions also in the community chat-


Chris Detzel (47:17):

That's correct.


Michael Gandolf (47:19):

... once this webinar ends. Is that correct?


Chris Detzel (47:20):

That is correct. So if you go to, post your questions, and then I'll make sure to touch base with the D&B team. Michael, I'll let you know.


Michael Gandolf (47:31):



Chris Detzel (47:32):

And you can find the right people or look, some of you guys are already members of the community. You can see it for yourself just by adding like a.. Go in and just go and subscribe to the content. All right, well, thanks everyone. Take care.


Michael Gandolf (47:53):

Thanks again.


Chris Detzel (47:56):

This is so interesting. I loved it.


Michael Gandolf (48:00):

Yeah. Joel. Great job. Great demo. I'll connect with the team. You saw Jay Dailey answer some questions as well from the D&B side. So we'll follow up on a few of the questions as well, as well as some of that functionality that maybe we can look to build in directly within the connector, right? That we can meet some of those needs right out of the box. So I'll take that back to our teams and we'll work through that as well.


Joel Snipes (48:25):

Absolutely. Thank you for co-hosting with me, Michael. It was fun.


Michael Gandolf (48:28):

You bet.


Joel Snipes (48:28):

This is my first time having a co-host on here.


Michael Gandolf (48:31):

You bet. I appreciate it.


Chris Detzel (48:32):

Hey, let's do it more often. If you guys have topics you want to go deep into that is about Reltio type stuff, but also your connector and those things, happy to host those kind of webinars. Joel's done several of them. It doesn't have to be just employees. I'm happy to let some of our partners to do some of these too.


Michael Gandolf (49:01):

No, I appreciate that. I do think we're going to get some interest around the Reltio Integration Hub and those additional use cases. It's so top of mind with connecting to solutions like Snowflake, Salesforce, or SAP, for example. So it's a huge need in the marketplace. If we can avoid our clients, our mutual clients having to build connectors on their own, time to value is huge with the Reltio Integration Hub. So it's a great technology to use. It's easy to build the recipes and get the data flowing in weeks versus what typically could be months, right? From some-


Chris Detzel (49:36):

Well, Michael, you're speaking our language. My boss always talks about time to value.


Michael Gandolf (49:43):

Yep. Absolutely, and ROI, so I agree.


Chris Detzel (49:45):

It's huge. All right. Well, thanks everyone. Really appreciate it.


Michael Gandolf (49:49):

Thanks, all.


Chris Detzel (49:49):

Take care. Thanks.


Michael Gandolf (49:50):

Have a great day. Cheers. Bye bye.