Bedrock Data Customer Blog

Bedrock Data beta launches Conditional Mapping to help power users control multi-system data integrations

Posted by Zak Pines on Jul 26, 2016 4:04:01 PM

Bedrock Data has announced the beta launch of its Conditional Mapping tool to help its power users control business rules around multi-system data integrations.

This addition to the Bedrock Data integration hub creates greater capabilities for users to directly manage and control their workflows. For existing Bedrock Data customers, this will replace the functionality previously labeled as “Workflows”. Note that for existing customers, existing workflows are still supported and will continue to operate without issue or interruption.

We are currently running a beta program with customers and the functionality will be generally released in September. This help article provides more details on the setup and tips for implementing.

If you are an existing customer interested in taking advantage of these features, let our Support team know. If you are not yet a Bedrock Data customer and these use cases are applicable to you, let us know and one of our specialists will follow up with you.

These are some examples of use cases that can be accomplished with Conditional Mapping:

Systems Integration Pairings

  • You're using different marketing automation instances for different geographies rolling up to a single CRM
  • A specific example of this is a customer using multiple HubSpot instances across different geographies
  • Another example is a company using different marketing automation systems (Marketo, HubSpot, Pardot, Act-on) across different divisions, rolling up to a single CRM

 Multi-System Workflows

  • You're using Bedrock Data to manage rules around business process for a lead lifecycle touching multiple systems
  • For example a lead comes into marketing automation system, is pushed to an outbound calling system (e.g. Quota Factor, Phone Burner) until qualified, and once qualified pushed to CRM system
  • Then, when it becomes a customer it’s pushed to a support system and a billing system

 Tightly Control Initial Data Syncs Between Systems

  • Conditional mapping is also very useful for setting the initial rules on which data synchronizes when systems are initially integrated
  • For example only sync to the marketing automation system data which has been updated in the CRM in the past year, or vice versa
  • Other examples include only syncing data based on a lead score

Once again, if you are an existing customer interested in taking advantage of these features, let our Support team know. If you are not yet a Bedrock Data customer and these use cases are applicable to you, let us know and one of our specialists will follow up with you.

Topics: Product, HubSpot, Updates, New Features, Conditional Mapping, Marketo, Workflows

Subscribe to Email Updates

Bedrock Help Center

The help center is our library of help documentation where customers can find answers to their data integration questions.  

Visit the Help Center

Bedrock Support Team

Can't find the answers to your questions in our Help Center? Reach out to our support team by either filing a ticket at our dedicated support page or give us a call at 877-588-2671 extension 3. 

Recent Posts