Getting started onboarding data

Integrations

Pros:

Cons:

• Easy-to-follow steps to set up your integration. 
• Can be accomplished by anyone regardless of technical expertise. 
• Initial set-up is quick. 
• Data requirements will be handled by Lexer. 

• The Support team will need to approve your integration. 
• The Product team will then need to transform your data which can take time. 
• Transforms require our team to have access to your data. 
• If your company has the capability to handle the data transformation, this could be an expensive option.
  
  

APIs using our schemas

Pros:

Cons:

• Not limited to the integration list. 
• Potential cost reduction. 
• More control over the speed of implementation. 
• Less back and forth required to transform the data as you can validate as you go.
• API reference docs are updated frequently to ensure you have accurate schemas. 
• Imports or changes can be carried out independently. 
• Certain rate limits are applied to API keys to manage traffic efficiently. For more detail read our Rate Limits article.

• Your team will take on some of the responsibility of the data transforms. 
• You may not have the capability within your business to utilize this feature. 
• The data limits may mean this solution has limitations for your intended purpose. 

Structured data uploads using our File Upload API, SFTP, or S3

Pros:

Cons:

• Clear documentation about standard schema use via SFTP or S3 to transform your data, ready for the hub.
• A significant reduction in back and forth communications during the transform process. 
• Issues with the transform can be easily identified and resolved. 
• Schemas will be updated regularly. 

• Your data has to be transformed into the standard schema format using JSON. This requires someone in your company having the technical skill to complete this work. 

CSV Uploads

Pros:

Cons:

• Can be a good solution for small volumes of basic customer data.
• You may be able to get CSV data easily generated by products in your MarTech suit. 

• It is far more difficult and time consuming to identify and resolve issues using a CSV file than it would be using a JSON file. 
• Will only allow simple customer data uploads such as purchased lists, form/competition exports, or modeled data against a profile.

Custom

Pros:

Cons:

• If you want to break the mold, who are we to stop you! Reach out to your Success Manager to discuss custom work. 

• It can be expensive to create custom integrations. 
• It can take some time.