Make integration proxy paths configurable per customer

[cmdvuy]

User story

Context

Several integrations currently use fixed, predictable proxy paths:

• /integrations/didomi/consent (Didomi integration)
• /integrations/addingwell/* (Addingwell integration)

Using shared, hardcoded paths increases the risk of ad blockers adding them to their block lists, which would defeat the purpose of first-party proxying.

Proposal

Allow the proxy path to be configurable per customer for each integration, for example:

[integrations.didomi]
proxy_path = "my-custom-consent-path" # default: "integrations/didomi"

[integrations.addingwell]
proxy_path = "my-custom-addingwell-path" # default: "integrations/addingwell"

Trade-offs to discuss

• A randomized or customer-specific path is harder for ad blockers to target
• It adds configuration complexity for the customer setup
• All script serving snippets and redirects must reflect the configured path at render time