UTM parameters appear in the Meeting Activity dashboard when they are added to router links or mapped through form submissions, but not when they are passed via the JS API as part of the lead object. Admins using the JS API integration have no way to see UTM data in Meeting Activity, even though the same data is visible when using other supported methods. The inconsistency is confusing and undermines attribution reporting for teams that use the JS API.

Chili Piper should surface UTM values in Meeting Activity regardless of how the lead was submitted, including when passed via the JS API.

Attribution reporting depends on consistent UTM capture across all entry points. When one supported integration method silently drops UTM data from the activity dashboard, teams cannot trust their meeting attribution data or accurately measure campaign performance.