Today, the Redirect URL after completion setting appears to be static. It would be extremely valuable if this redirect could be dynamically customized per document/session via integrations (e.g., Make / Zapier) or via variables, so customers can redirect signers to different landing pages and pass custom query parameters.

Why this matters (use case):

We run multiple campaigns and need to send signers to different LPs depending on:

document template / campaign

recipient / segment

region / language

deal owner / pipeline stage

We also want to pass tracking parameters such as:

utmsource, utmcampaign, utm_content

internal IDs like docid, recipientid, deal_id

This would unlock cleaner attribution and better post-sign flows (e.g., showing different onboarding steps).

Proposed solution:
Enable the redirect URL to be set programmatically (API + Make/Zapier) and/or with merge fields / variables, for example:

https://example.com/thank-you?doc={{document.id}}&email={{recipient.email}}&campaign={{custom.campaign}}

Acceptance criteria:

Redirect URL can be set/overwritten when creating a document from a template (API / integration step).

Redirect URL supports variables/merge fields and/or payload-based parameters.

Redirect URL can be different per recipient (optional but ideal).

Secure handling of parameters (e.g., allowlist / encoding) to avoid injection issues.

Works for completed signing events consistently (web + mobile).

Expected impact:

Better conversion tracking and attribution

More flexible campaign routing

Stronger automation use cases with Make/Zapier