The Non-site action card is mainly used to finish experience branches where you are not changing the user experience, but it also creates a nonSite JavaScript event that you can listen for and perform some action in response to. Here's the event listener code for the nonSite event:
tp.push(["addHandler", "nonSite",
function(eventParams, cardParams, contextParams) { ...
}
]);
If you add this code to your website, the event listener code will be executed when a nonSite event is triggered. The nonSite event will be triggered regardless of name given on the non-site action card. If you wanted to know exactly which non-site action was executed, you could use the cardParams parameter in the event listener.
If you are not using Piano’s Management + Billing then you might use the non-site action event to trigger a third-party checkout process, send data to a third-party analytics system, or activate some other logic already implemented within the scope of your site. Since the non-site action JavaScript event does nothing unless a you capture the event and take some action in response, this card is frequently used for control groups during A/B tests.
