No one can be in two places at the same time and, for the most part, people are fine with that. After all, if you could be in two places at the same time, you might have to sit through a meeting in Portland at the same time you have to sit through a meeting in Brussels. You might have to drive south on the freeway at rush hour at the same time that have to drive north on the freeway at rush hour. You might – well, you get the idea. Like we said, no one can be in two places at the same time and, for the most part, people are fine with that.
When it comes to data, however, it's a different story: in that case, people want their data to be in two (or even more) places at the same time. For example, through our user profiles, Janrain collects, and securely stores, a wealth of information about your registered users. Furthermore, we provide tools (most notably Customer Insights version 2.0) that help you analyze and make use of that data.
Needless to say, that's great. And yet …. Suppose you have a CRM (customer relationship management) application; wouldn't it be nice to have that same user profile information replicated in your CRM? Suppose you have a DMP (data management program) application; wouldn't that DMP be far more valuable if it contained data from the Janrain user profile? There's nothing better than having your data stored in a Janrain user profile database, but, still, it would be even better if that data could be stored in more than one place at the same time.
And guess what? Thanks to Janrain data integrations, and thanks to Janrain, your data can be in more than one place at a time. Best of all, this can happen with minimal effort on your part. What does all that mean? We're just about to tell you.
Note. If you aren't familiar with the term, a "data integration" involves taking data from multiple sources and presenting users with a unified view of all the retrieved data. For example, an Oracle Responsys user might use the application to look at data; some of that data might have been directly entered into Responsys, and some might have been copied over from a Janrain user profile. The user doesn't know, or care, where the data came from; he or she is just happy to have a wealth of information at their disposal.