Action usage examples
Examples give users ideas on actual usage. We use automation to generate, test, and run these actions, so names and combinations may be odd or repetitive . In many cases, other actions or environmental setup is required for the action to run, so you will need to adjust the action parameters and setup appropriate for your environment.
Command line environments can be different, especially between Windows and non-Windows systems. This page talks about command line escaping differences and there are differences with respect to environment variable references ($ for non-Windows and %...% for Windows). These differences can impact examples, so recognize and adjust for your platform. In particular, all examples here are run with the standard bash shell on Linux.
--action identifyUser --token "***" --userId "cli_1@appfire.com" --afterSql "insert into test01 (a1) values('segment')" --database "@database-test" --properties "{\"email\":\"cli_1@appfire.com\", \"organization\":\"appfire\"}" --properties2 "{\"region\":\"Americas\", \"empty\":null, \"organization\":\"appfire\"}"
|
--action identifyUser --token "***" --userId "cli_1@appfire.com" --properties "{\"email\":\"cli_1@appfire.com\", \"organization\":\"appfire\"}" --properties2 "{\"region\":\"Americas\", \"empty\":null, \"organization\":\"appfire\"}"
|
--action identifyUser --token "***" --userId "cli_1@appfire.com" --sendNullProperties --properties "{\"email\":\"cli_1@appfire.com\", \"organization\":\"appfire\"}" --properties2 "{\"region\":\"Americas\", \"empty\":null, \"organization\":\"appfire\"}"
|
--action runFromList --list "userId" --token "***" --common "-a identifyUser --userId @entry@"
|
--action trackEvent --token "***" --userId "cli_1@appfire.com" --event "My event" --properties "{\"email\":\"cli_1@appfire.com\", \"organization\":\"appfire\"}" --properties2 "{\"region\":\"Americas\", \"empty\":null, \"organization\":\"appfire\"}"
|
