Hitting a snag with the Genesys Cloud Web Messaging SDK. I’m trying to push a CRM customer ID into the conversation context using startChat(), but the metadata never shows up on the Genesys side. The chat connects fine, but the custom attributes are missing from the initial message payload.
Here’s the client-side code:
const client = await createWebMessagingClient({
organizationUuid: 'my-org-id',
applicationUuid: 'my-app-id',
deploymentUuid: 'my-deploy-id',
});
await client.startChat({
customData: {
crmCustomerId: 'CUST-998877',
sourceSystem: 'legacy-crm'
}
});
I checked the network tab. The POST to /api/v2/webmessaging/clients/conversations includes the customData object in the JSON body. The response is a 201 Created with a valid conversation ID. However, when I query the conversation details via the REST API (GET /api/v2/conversations/messaging/{conversationId}), the customAttributes array is empty. I also checked the webhook payload sent to our backend, and the customAttributes field is null there too.
I’ve verified that the deployment settings allow custom data. The customData field isn’t blocked by any policy. Is there a specific flag I’m missing in the startChat options? Or maybe the SDK is stripping it out before sending? The TypeScript definitions show customData as an optional field in StartChatParams, so it should be supported. Any ideas on why it’s getting dropped?