Solved

Does Amplitude Actions benefit from the Amplitude client side SDK implementation or is it redundant?

  • 16 November 2021
  • 1 reply
  • 150 views
A

Hi all,

Long time Amplitude user, super excited to be implementing it again and seeing what’s new. 

One question, we’re using Segment and your documentation recommends implementing the client side SDKs for a couple benefits (https://help.amplitude.com/hc/en-us/articles/217934128-Segment-Amplitude-Integration#pros-cons-of-client-side-bundled-integration).

However reading the Amplitude Actions documentation, it sounds like the core benefit (session tracking) of implementing the client side SDK is “auto-magically” handled by Segment and passed via Cloud mode for Amplitude Actions.  Does that mean implementing the client side SDKs for mobile devices are completely redundant?  What would we be missing if we’re using Cloud mode?  Just want to be clear about this.

Kind regards,

icon

Best answer by ning.chang 19 November 2021, 10:46

View original

1 reply

ning.chang
Rank
Userlevel 4
Badge +7

Hi @andrews! Glad to see you sticking around the Amplitude-verse :)

As pointed out in the article you’ve linked, the other benefit of implementing the Amplitude SDK (aside from session tracking) is that the SDKs will automatically record several user properties such as device type, operating system, and user agent. Here is a list of the user properties tracked automatically by our SDKs. 

Reply


Terms & ConditionsCookie settings