Custom Redirect URLs After Document Signing

Redirect recipients to custom pages after they complete signing documents. This guide covers setting redirect URLs, use cases, customizing redirect destinations per document, passing context data, and troubleshooting redirect issues.

Prerequisites

  • Account: Active BreezeDoc account
  • Plan: Pro or Agency plan (redirect URLs require paid plan)
  • Document: Created document ready for configuration
  • Access: Document owner or editor role
  • Redirect Destination: URL where you want to redirect recipients

What are Custom Redirect URLs?

Custom redirect URLs allow you to send recipients to a specific webpage after they complete signing a document, instead of showing BreezeDoc's default confirmation page. This feature enables seamless integration with your own websites, apps, or workflows. Key features:

  • Plan Requirement – Available on Pro and Agency plans (not Free plan)
  • Per-Document Configuration – Set different redirect URLs for each document
  • Automatic Redirect – Recipient automatically redirected after signing
  • Custom Experience – Control post-signature user experience
  • URL Parameters – Pass document context to your redirect destination
  • Any Valid URL – Redirect to any webpage you control

Why Use Custom Redirect URLs?

Seamless Integration with Your Workflow

  • Keep Users in Your App – Redirect back to your application after signing
  • Consistent Branding – Show your own confirmation page instead of BreezeDoc's
  • Next Steps Guidance – Direct users to next actions in your process
  • Eliminate Context Switching – Users stay within your ecosystem

Enhanced User Experience

  • Custom Thank You Pages – Show personalized confirmation messages
  • Onboarding Flow – Continue customer onboarding after contract signing
  • Upsell Opportunities – Redirect to product pages or additional services
  • Survey Collection – Gather feedback immediately after signing
  • Payment Processing – Direct to payment page after contract execution

Tracking and Analytics

  • Conversion Tracking – Track document completions in your analytics
  • Goal Completion – Trigger analytics events when redirects occur
  • Attribution – Pass document context to understand which contracts convert
  • A/B Testing – Test different post-signature experiences

Automation and Integration

  • Webhook Alternative – Redirect to a webhook endpoint that captures completion
  • API Triggers – Hit your own API endpoint after signing to trigger workflows
  • CRM Updates – Redirect to page that updates CRM status
  • Database Logging – Capture completion events in your database

Setting Custom Redirect URLs

Step-by-Step: Configure Redirect URL

  1. Log in to your BreezeDoc account (Pro or Agency plan required).
  2. Go to Documents and open the document (or create new one).
  3. Look for Document Settings or Advanced Settings section.
  4. Find the Redirect URL or Completion Redirect field.
  5. Enter the complete URL where recipients should be redirected (e.g., https://example.com/thank-you).
  6. Ensure the URL is valid and starts with https:// (or http://).
  7. Click Save to apply the redirect URL.
  8. Send the document to recipients.
  9. After recipients sign, they're automatically redirected to your specified URL.

Important: Always use complete, fully-qualified URLs including protocol (https://).

URL Format Requirements

  • Complete URL: Must include protocol (https://example.com, not just example.com)
  • Valid Domain: Must be accessible publicly (localhost URLs won't work for recipients)
  • URL Length: Practical limit around 2000 characters
  • Encoding: Special characters should be URL-encoded
  • HTTPS Preferred: Use https:// for security best practices

Testing Redirect URLs

  1. Set up redirect URL on a test document.
  2. Send document to yourself (use your own email).
  3. Complete signing the document as a recipient.
  4. Verify you're redirected to the correct page.
  5. Check that the page loads correctly and shows expected content.
  6. Test on both desktop and mobile browsers.

Common Use Cases

Custom Thank You Page

Scenario: Show branded confirmation after contract signing

Redirect URL: https://yourcompany.com/thank-you/contract-signed

Page Content: Thank you message, next steps, contact information

Benefit: Maintains brand consistency throughout signing experience

Customer Onboarding Flow

Scenario: Continue onboarding after service agreement

Redirect URL: https://yourapp.com/onboarding/step-2

Page Content: Next onboarding step (account setup, payment, training)

Benefit: Seamless transition from contract to activation

Payment Collection

Scenario: Collect payment after contract execution

Redirect URL: https://yoursite.com/checkout?contract=signed

Page Content: Payment form with contract context

Benefit: Immediate payment collection while momentum is high

Post-Signature Survey

Scenario: Gather feedback on signing experience

Redirect URL: https://survey.example.com/signature-feedback

Page Content: Short survey about ease of signing

Benefit: Collect feedback while experience is fresh

Upsell/Cross-Sell Opportunity

Scenario: Promote additional products after purchase

Redirect URL: https://yourstore.com/recommended-products

Page Content: Personalized product recommendations

Benefit: Capture additional revenue from engaged customers

Webhook Endpoint Integration

Scenario: Trigger backend workflow after signing

Redirect URL: https://api.yourservice.com/webhooks/document-complete

Page Content: Simple confirmation or redirect again to final page

Benefit: Alternative to webhooks for triggering automations

Advanced Configuration

Dynamic Redirect URLs (With Parameters)

Pass document context to your redirect page using URL parameters:

Example with Static Parameters:

https://yoursite.com/confirm?source=breezedoc&type=contract

Example with Document Context:

https://yoursite.com/confirm?document_id={document_id}&recipient={email}

Note: BreezeDoc currently passes the redirect URL as-is. For dynamic context, you may need to generate unique redirect URLs per recipient via API, or use server-side logic to capture context from query parameters.

Different Redirects for Different Recipients

BreezeDoc uses one redirect URL per document (not per recipient). To redirect different recipients to different pages:

  • Option 1: Create separate documents for each recipient with different redirect URLs
  • Option 2: Redirect to a router page that determines destination based on recipient email
  • Option 3: Use query parameters and server-side logic to route appropriately

Adding Tracking Parameters

Include analytics tracking in redirect URLs:

Google Analytics:

https://yoursite.com/thank-you?utm_source=breezedoc&utm_medium=esignature&utm_campaign=contracts

Custom Parameters:

https://yoursite.com/confirm?signed=true×tamp={current_time}

Redirect Chaining

Redirect to an intermediate page that then redirects to final destination:

  1. BreezeDoc redirects to: https://yoursite.com/capture?document=xyz
  2. Your capture page logs completion, then redirects to: https://yoursite.com/thank-you
  3. Benefit: Capture completion event server-side before final page

Handling Redirects on Your Server

Server-Side Redirect Logic Example

Capture completion event when recipient lands on your redirect page:

// Pseudo-code for redirect handling
app.get('/contract-complete', function(req, res) {
  // Log the completion
  logDocumentCompletion({
    source: 'breezedoc',
    timestamp: Date.now(),
    userAgent: req.headers['user-agent']
  });
  
  // Update CRM or database
  updateCustomerStatus('contract_signed');
  
  // Show thank you page or redirect again
  res.render('thank-you', { message: 'Contract signed!' });
});

Mobile Browser Considerations

  • Deep Links: You can redirect to app deep links (myapp://success) but user must have app installed
  • Responsive Pages: Ensure redirect destination is mobile-friendly
  • Load Time: Fast-loading pages improve user experience
  • Back Button: Users may hit back and see BreezeDoc confirmation page

Redirect URL Best Practices

URL Reliability

  • Test Before Sending: Always test redirect URLs before sending documents
  • Monitor Uptime: Ensure redirect destination has high uptime (99.9%+)
  • Error Handling: Configure redirect page to handle errors gracefully
  • Valid SSL: Use https:// with valid SSL certificates
  • Avoid Redirects to Redirects: Minimize redirect chains for better UX

User Experience

  • Fast Loading: Optimize redirect destination for quick load times
  • Clear Messaging: Show confirmation that signing was successful
  • Mobile-Friendly: Ensure redirect pages work on all devices
  • Avoid Pop-ups: Don't use redirects that trigger pop-up blockers
  • Back Navigation: Consider what happens if user hits back button

Security Considerations

  • HTTPS Only: Always use https:// for redirect URLs
  • Validate Referrers: Check that redirects come from BreezeDoc domain
  • No Sensitive Data: Don't pass sensitive info in URL parameters (use server-side lookups)
  • Rate Limiting: Protect redirect endpoints from abuse

Analytics and Tracking

  • Track Completions: Log all redirect hits as completion events
  • Conversion Funnels: Map document signing to conversion funnels
  • User Journey: Track full user path from document send to post-signature actions
  • A/B Testing: Test different redirect pages to optimize conversions

Troubleshooting

Issue: Redirect URL field is not visible in document settings

Fix: Redirect URLs require Pro or Agency plan. Verify your plan at Settings ➜ Account ➜ Plan. Free plan users must upgrade to Pro ($19/month) or Agency ($49/month) to access this feature. If you have a paid plan and still don't see the field, try refreshing the page or clearing browser cache. The field is typically in Document Settings or Advanced Settings section.

Issue: Recipient is not redirected after signing

Fix: Verify redirect URL is saved correctly in document settings (check for typos). Ensure URL is complete with protocol (https://example.com, not example.com). Test the URL directly in a browser to confirm it loads. Check if the page has redirect restrictions or requires authentication. Try sending a test document to yourself to verify redirect works. If URL is correct but redirect fails, check browser console for JavaScript errors on the redirect page.

Issue: Redirect URL shows 404 or error page

Fix: Verify the redirect URL is correct and the page exists. Check that your web server is running and accessible. Test the URL in multiple browsers to rule out browser-specific issues. Ensure the page doesn't require login or special permissions. Check your web server logs for error details. If using a reverse proxy or CDN, verify configuration is correct.

Issue: Need to change redirect URL after document is already sent

Fix: You can update the redirect URL even after sending the document. Open the document ➜ Document Settings ➜ update Redirect URL ➜ Save. The change takes effect immediately for recipients who haven't completed signing yet. Recipients who already signed will not be redirected retroactively (they saw the old confirmation page).

Issue: Redirect works on desktop but not mobile

Fix: Test redirect URL on mobile browser to identify the issue. Ensure redirect destination is mobile-responsive. Check if mobile browser blocks redirects (some browsers have anti-redirect features). Avoid app deep links unless you detect app installation first. Use responsive web pages instead of app-specific URLs for universal compatibility. Test on multiple mobile browsers (Safari iOS, Chrome Android).

Issue: Want to pass document ID or recipient email to redirect page

Fix: BreezeDoc does not currently support dynamic variables in redirect URLs. Workarounds: 1) Generate unique redirect URLs per document via API (include context in URL), 2) Use server-side logic to capture and look up document context based on timestamp, 3) Implement a router page that identifies context from session/cookies, 4) Contact BreezeDoc support to request dynamic variable support in future updates.

FAQ

Q: Is custom redirect URL available on the Free plan?

A: No, custom redirect URLs require a Pro or Agency plan. Free plan users see the default BreezeDoc confirmation page after signing.

Q: Can I redirect to different URLs for different recipients?

A: BreezeDoc uses one redirect URL per document (shared by all recipients). To redirect different recipients to different pages, create separate documents or use server-side routing logic.

Q: Can I redirect to a mobile app using deep links?

A: Yes, you can use app deep links (e.g., myapp://success), but this only works if the recipient has your app installed. Otherwise, the redirect may fail or show an error. For universal compatibility, use web URLs.

Q: Does BreezeDoc support dynamic variables in redirect URLs?

A: Not currently. Redirect URLs are static per document. For dynamic context, generate unique URLs via API or use server-side logic to identify context.

Q: What happens if the redirect URL is broken or returns an error?

A: The recipient may see an error page or browser error message. Always test redirect URLs before sending documents. Monitor redirect destination uptime to prevent issues.

Q: Can I redirect to localhost for testing?

A: Localhost URLs work for the document owner testing on their own machine, but won't work for remote recipients. Use a publicly accessible staging server for testing with real recipients.


Need more help? Contact our support team – we are here to help!

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Related Articles