Considerations for Custom Connections

Because a custom connection does not rely on a replication schedule or API to import data into the CDP, the connection setting options are different than those of the native integrations. 

The custom connection page will not have the option to schedule a sync on a regular cadence. Nor will it have the ability to set a modified date. Below are what you should consider when working with a custom connection. 

Considerations for configuring a custom connection

• How much of your data should you import to the CDP? 
  • Because custom connections leverage AWS S3 or a file form your desktop, the amount of data you load to the CDP is completely up to you. You should consider your contracted Records Under Management (RUM) amount and priority use cases within the CDP to determine what and how much data you should load. 
  • We recommend importing records that have been modified within the last year. 

• How often will your data be imported into the CDP? 
  • This is dependent on how often you choose to send data to AWS S3 or manually upload using the one time import. We recommend using a third party tool to automate sending your data to the CDP. Data dropped into AWS S3 will automatically be picked up by Rev.Up and imported into your next Process and Analyze (P&A) job.

• Set priority for the connection: It is common for the same data to exist in multiple systems and contain the same fields and information. You may have one system that is the source of truth among all of your systems. You can use priority to determine which information is kept when a record exists in multiple systems. For additional information, check out our article on priority.