Deep Linking Platform RFP Template

An RFP (Request for Proposal) standardizes how you evaluate deep linking platforms. Instead of comparing marketing pages, you ask every vendor the same questions and compare their answers. This template covers the questions that matter for deep linking.

For a scoring-based evaluation, see deep linking platform selection checklist. For enterprise-specific requirements, see enterprise deep linking platforms.

How to Use This Template

1. Copy the questions relevant to your requirements.
2. Send to each vendor you are evaluating.
3. Set a response deadline (2 weeks is standard).
4. Score responses on a consistent scale (0-3).
5. Weight sections by importance to your team.
6. Compare total weighted scores.

Not every section will apply to your evaluation. Skip sections that are not relevant.

Section 1: Company and Product

1. Describe your company, founding year, and funding status.
2. How many customers use your deep linking product?
3. What is your product roadmap for the next 12 months?
4. What is your annual recurring revenue or revenue range? (Optional, but indicates stability.)
5. Have you deprecated or shut down any products in the past 3 years? If yes, what was the migration path for affected customers?

Section 2: Core Deep Linking Features

1. Do you support Apple Universal Links? Describe your AASA file management approach.
2. Do you support Android App Links? Describe your assetlinks.json management approach.
3. Do you support deferred deep linking? Describe the mechanism for each platform (iOS, Android).
4. What is your deferred deep linking match accuracy rate?
5. Do you support custom link domains? How many domains can be configured per account?
6. Do you support route patterns with dynamic path parameters (e.g., /products/:id)?
7. How do you handle web fallback for users who do not have the app installed?
8. Do you provide smart banners for web-to-app promotion? Describe customization options.
9. Do you generate QR codes? Describe styling and analytics capabilities.
10. How do you handle in-app browsers (Instagram, Facebook, Twitter/X, LinkedIn)?

Section 3: SDKs and Integration

1. List all available SDKs (iOS, Android, React Native, Flutter, web, etc.).
2. What is the SDK size for each platform (binary size increase to the app)?
3. What is the SDK initialization time on cold start?
4. What is the minimum supported OS version for each SDK?
5. How are SDK updates distributed? What is your deprecation policy?
6. Provide a time estimate for basic integration (Universal Links + App Links + deferred deep linking).
7. Provide API documentation for your REST API.
8. Do you support webhooks? Describe the payload format and retry policy.

Section 4: Analytics and Reporting

1. What analytics do you provide for deep links? (Clicks, opens, conversions, geographic data, device data.)
2. What is the analytics data retention period for each pricing tier?
3. Can analytics data be exported? In what formats? (CSV, API, data warehouse connectors.)
4. Do you provide real-time analytics or is there a processing delay?
5. Do you support webhooks for real-time event delivery?
6. Can analytics be segmented by link, route, campaign, or custom parameter?

Section 5: Pricing

1. Provide your complete pricing structure, including all tiers and overage charges.
2. What metric drives pricing? (Clicks, conversions, links created, MAU.)
3. Is there a free tier? What are its limitations?
4. Is self-serve signup available, or is a sales conversation required?
5. What happens when usage exceeds the plan limit? (Auto-upgrade, overage charges, service throttling.)
6. Are there minimum contract lengths? Can the contract be terminated monthly?
7. What is included in each tier? Provide a feature breakdown per tier.
8. Are there any hidden costs? (Setup fees, migration fees, support fees, API access fees.)

Section 6: Reliability and Support

1. What is your published uptime SLA?
2. Provide a link to your status page and recent incident history.
3. Describe your infrastructure. (CDN, cloud provider, geographic distribution, redundancy.)
4. What support channels are available? (Email, chat, phone, dedicated CSM.)
5. What are your support response time SLAs by severity level?
6. Provide 2-3 customer references we can contact.
7. Describe your incident response process. Do you publish post-mortems?

Section 7: Security and Compliance

1. Do you have SOC 2 Type II certification? If not, what security certifications do you hold?
2. Is data encrypted at rest and in transit?
3. Where is customer data stored? Do you offer data residency options?
4. Do you provide a Data Processing Agreement (DPA) for GDPR compliance?
5. Does your SDK collect any data that requires user consent under GDPR?
6. Does your SDK require Apple's App Tracking Transparency (ATT) permission?
7. Does your SDK include an iOS privacy manifest?
8. Do you use device fingerprinting? If yes, for what purpose?
9. Do you share customer data with third parties (ad networks, data brokers)?
10. Do you support data deletion requests?
11. Describe your access control model. (Role-based access, SSO support, audit logging.)

Section 8: Migration and Portability

1. Do you provide migration guides from other platforms? Which platforms?
2. Can existing links from another platform be redirected to your platform?
3. Can we export all link configurations and route patterns?
4. Can we export all analytics data?
5. What is the estimated migration time from our current platform?
6. Is there a parallel running period where both old and new links work?
7. If we decide to leave your platform, what is the data export process?

Section 9: Technical Evaluation

In addition to the written RFP responses, request:

1. Sandbox or trial account. Evaluate the dashboard, create test links, and verify they work.
2. Integration prototype. Have a developer integrate the SDK into a test app and measure the experience.
3. Support test. Submit a technical question and evaluate response time and quality.
4. Load test results. Request data on how the platform performs under high traffic.

Evaluation Scoring

Score each response on a 0-3 scale:

Score	Meaning
0	Not supported or no response
1	Partially supported with significant limitations
2	Fully supported
3	Exceeds requirements

Weight each section based on your priorities:

Section	Weight (Example)
Core features	3x
SDKs and integration	3x
Pricing	2x
Analytics	2x
Security and compliance	2x
Reliability and support	2x
Migration	1x
Company and product	1x

Tolinku RFP Response

Tolinku welcomes RFP evaluations. The platform provides Universal Links, App Links, deferred deep linking, smart banners, QR codes, and analytics with transparent pricing and lightweight SDKs. Contact the team or sign up for a free account to evaluate.

For the selection checklist, see deep linking platform selection checklist. For the full comparison, see deep linking platform comparison.