Like the event filter, forwarding rules let you filter out events from being sent to an Output. But where the event filter is based on event and attribute names, forwarding rules look at values, which lets you build more complex conditions.
To learn more about forwarding rules, please visit our docs.
The 3 "core" SDKs are the only SDKs that support kits (not including "wrapper" SDKs, described below):
|User Attribute Conditional Forwarding||NO||NO||YES|
|Event Attribute Conditional Forwarding||YES||YES||YES|
|Event and user attribute filters||YES||YES||YES|
Any "wrapper" SDKs that use the above SDKs under the hood will follow the table above, based on the runtime platform (e.g., when you use flutter w/ Android or Xamarin with iOS, etc.).
Wrapper SDKs and the underlying "core" SDKs that they use/support:
Other Client Side SDKs
These SDKs are stateful and are meant to function on end-user devices. But they do not support kits at all - so only server-side forwarding and forwarding rules:
These SDKs are stateless and are purely HTTP clients for our server-to-server API, and so naturally do not support kits - so only server-side forwarding and forwarding rules: