Understanding Meritto Developer Portal vs Proper Integration

Understanding Meritto Developer Portal vs Proper Integration

Purpose 

This article helps internal Meritto teams clearly understand the difference between: 
  1. Meritto Developer Portal, and 
  2. A Proper Meritto Integration 
It is intended for: 
  1. Support Engineers 
  2. Delivery & Implementation Teams 
  3. Onboarding Teams 
  4. Pre-Sales & Solutioning Teams 
  5. New Joiners 
Correct understanding of this topic helps prevent: 
  1. Incorrect issue diagnosis 
  2. Wrong client expectations
  3. Repeated escalations 
  4. Over-customized implementations

What Is the Meritto Developer Portal? 

Simple Explanation 
The Meritto Developer Portal is a technical reference platform that explains: “How an external system can technically communicate with Meritto.” 
It is meant primarily for developers and technical teams.

What the Developer Portal Provides 

The Developer Portal includes: 
  1. API documentation 
  2. Authentication details 
  3. Sample API requests and responses 
  4. Webhook references 
  5. Test / sandbox usage guidance 
It answers questions like: 
  1. How do I send a lead to Meritto? 
  2. What fields are required? 
  3. What response will the API return? 

What the Developer Portal Is Typically Used For

The Developer Portal is suitable for: 
  1. Proof of Concepts (POCs) 
  2. Initial API validation 
  3. Technical exploration 
  4. Small or isolated use cases 
It allows teams to test connectivity, not business correctness. 

What the Developer Portal Does NOT Do

This is critical for internal understanding. 

The Developer Portal does not: 
  1. Define lead allocation logic 
  2. Handle duplicate management rules 
  3. Control stage movement logic 
  4. Ensure follow-up workflows 
  5. Guarantee reporting accuracy 
  6. Validate production readiness
Internal support rule: 
API success only confirms connectivity, not correctness. 

What Is a Proper Meritto Integration? 

Simple Explanation 
A proper integration ensures that: Meritto works exactly as per the client’s real business process. 
This means Meritto is not just receiving data, but: 
  1. Applying business rules 
  2. Driving workflows 
  3. Supporting operations and reporting reliably 

Key Components of a Proper Integration 

A setup can be considered a proper integration only when it includes:
1. Requirement Understanding 
  1. Lead source behavior 
  2. Ownership rules 
  3. Duplicate scenarios 
  4. Expected reporting outcomes
2. Data Mapping 
  1. Correct mapping of external fields to Meritto fields 
  2. Mandatory and dependent fields handled 
  3. Clean data formatting 
3. Business Rules 
  1. Deduplication logic 
  2. Lead assignment logic 
  3. Stage movement conditions 
  4. Workflow triggers
4. Error Handling
  1. API failure identification 
  2. Retry or alert mechanisms 
  3. Monitoring and logs
5. Testing & Validation 
  1. UAT using real-life scenarios 
  2. Volume and edge-case testing 
  3. Controlled production rollout 
If any of the above is missing, the integration is incomplete. 

Developer Portal vs Proper Integration (Simplified Comparison)

Aspect 
Developer Portal 
Proper Integration
Purpose 
Technical access 
Business correctness
Focus 
APIs 
Workflows
Business logic 
Not handled 
Fully defined
Testing 
Basic 
Structured (UAT)
Reporting reliability 
Not guaranteed 
Validated
Production readiness 
No 
Yes

Common Support Scenarios Explained

Scenario 1: Leads Are Coming but Allocation Is Wrong 

  1. APIs are working 
  2. Integration design is missing 
  3. Business rules are not applied inside Meritto 
Scenario 2: Reports Don’t Match Expectations 
  1. Data exists 
  2. But required workflows were bypassed
  3. Reporting logic was not considered during integration
Scenario 3: Client Says “Product Is Not Working” 
  1. Often not a product defect 
  2. Usually an integration design gap 

What Is Product Cannibalization? 

Simple Explanation 
Product cannibalization happens when: 
External systems start doing work that Meritto is designed to do natively. As a result: 
  1. Meritto is used mainly as a data store 
  2. Core product value is underutilized 
Examples of Cannibalization 
  1. Lead assignment handled fully outside Meritto 
  2. Stage movement triggered externally 
  3. Follow-ups managed in third-party tools 
  4. Custom dashboards replacing Meritto reports 
Why Cannibalization Is a Risk 
When Meritto is bypassed: 
  1. Reporting becomes unreliable 
  2. Support complexity increases 
  3. Upgrades become risky 
  4. Long-term maintenance cost increases 
This is not a technical issue, it is a design and governance issue.

Internal Guiding Principle for Integrations

A good integration should extend Meritto, not replace it. 
Internal teams should: 
  1. Prefer native Meritto features wherever possible like MIO AI 
  2. Introduce external logic only when it adds clear value 
  3. Flag over-customization risks early 

Final Internal Takeaway 

APIs make systems talk. 
Proper integration makes systems work. 
Clear understanding of this distinction reduces escalations, improves delivery quality, and protects long-term product value.