Nowadays businesses use many automations and integrations across many systems. Given Respond already provides outbound HTTP requests within workflows, we need access to all data that may come from triggers like Click to Chat for use within our external automations and processes.

Right now this lead/click id is hidden completely and only used within Respond itself and its Conversaions API integration, limiting business processes in cases where conversions do not happen within Respond.