[Content]: Add context about supported libraries to Actions GA4

[lizkane222]

What article on segment.com/docs is affected?

https://segment.com/docs/connections/destinations/catalog/actions-google-analytics-4/

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

Please add the connection mode information listed under the destination info box at the top of this doc.

Additional information

No response

[markzegarelli]

Hi @lizkane222, I'm not sure what you mean here. Actions destinations, as far as I'm aware, do not have connection modes in the same way that Classic destinations do. Also, the documentation cannot compute connection modes for these destinations since they do not have any components listed.

[spencerattick]

Hey @markzegarelli ! I just wanted to jump in to say that we do get customers who are sometimes confused about which libraries certain integrations can connect with and what will load on their websites versus what will be sent server-side. I've had at least one customer ask about FullStory Actions expecting that they could use it server-side when it can only be used (like the classic version) in what has historically been considered Device Mode (it only works with a.js). I don't believe our documentation for it addresses that. I've also had customers confused about what loads for integrations like Amplitude Actions and GA4. I think it might be helpful (if possible) to have a blip at the beginning of individual Actions docs that clarifies what libraries they can each be used with and what components will load client-side versus server-side. I don't think this needs to look exactly like the Connection Mode table for classic destinations as Actions destinations are a bit different in that some are hybrid but I do think it would be useful. Let us know what you think!

[markzegarelli]

Hey @spencerattick. I agree, this would be great information to have. Unfortunately though, we don't have this available to us by default, and it's not something that we can maintain manually going forward.

I'll open up a thread with the destination actions team about how to get this surfaced in the API.

Thanks for the context though, it's super helpful!