Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Content]: Update the Kustomer destination's Engage section in docs #5880

Open
MStephen024 opened this issue Jan 12, 2024 · 1 comment
Open
Assignees
Labels
content When the bug is about content that needs to get fixed triaged

Comments

@MStephen024
Copy link
Contributor

What article on segment.com/docs is affected?

https://segment.com/docs/connections/destinations/catalog/kustomer/#engage

What part(s) of the article would you like to see updated?

The Kustomer destination is maintained by Kustomer.

Per a past Zendesk ticket, it seems the Kustomer destination does not accept custom properties, only standard properties (name, phone, email, etc.). This prevents any traits Engage generated events from being added to a user's profile downstream, since the Audience's/Computed Trait's names will be considered custom traits (e.g. my_computed_trait_name).

Therefore, the template Engage section in the Kustomer destination docs are not accurate. Once the Kustomer integration is able to send/receive custom properties, the Engage section in the docs would apply to the destination.

Additional information

No response

@MStephen024 MStephen024 added content When the bug is about content that needs to get fixed triage labels Jan 12, 2024
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content When the bug is about content that needs to get fixed triaged
Projects
None yet
Development

No branches or pull requests

2 participants