[Content]: Appcues Destination Requirement Conflicts #8163
Description
What article on segment.com/docs is affected?
https://segment.com/docs/connections/destinations/catalog/appcues
What part(s) of the article would you like to see updated?
In the Getting Started section, item #3, it says the AccountID and API key are an and/or configuration however both are required to set Appcues as a destination. This is unclear as Appcues should be a configurable server-side only destination which should only need the API key and/or a client-side which uses the AccountID.
At the end of the doc is says both API key and AccountID are required, which conflicts with item #3 in Getting Started, as well as conflicts with the overall destination expectations.
Per a support interaction, they provided the following:
**Unfortunately, the Appcues integration in Segment currently only supports server-side implementations for use with server or mobile sources. Analytics.js sources default to device-mode and are not compatible with a fully cloud-mode connection at this time.
As a workaround, the customer could set up a Repeater destination with their web source. The Repeater would send events to a new server source, such as an HTTP API, and from there, the events can be forwarded to the Appcues destination, allowing them to be processed in cloud-mode. The flow would look like this:
analytics.js source → Repeater destination → server source → Appcues destination
Alternatively, they could leverage Destination Functions to send web events to Appcues from Segment's servers via APIs. However, this approach would require some development work on their end.**
It would be really helpful to clarify this in the docs and provide the documentation regarding repeater destinations within this doc
Additional information
No response