Clix Event Tracking FAQs

Question 1

Which platforms does this skill support?

Accepted Answer

The skill provides platform-correct implementation patterns and SDK signatures for iOS, Android, React Native, and Flutter.

Question 2

What is the purpose of the event-plan.json file?

Accepted Answer

It serves as a committable planning document that defines event names, properties, and locations. This allows the agent to validate your tracking logic against best practices before any code is actually written.

Question 3

Can this skill help with marketing campaign setup?

Accepted Answer

Yes. It specifically designs events to be 'campaign-ready' by ensuring event names and property keys match your Clix console configurations exactly, which is required for triggering automated campaigns.

Question 4

How does it handle data privacy and PII?

Accepted Answer

The workflow includes a specific PII policy step to define what data must never be sent, and provides validation tools to ensure sensitive information like emails or names are excluded from tracking payloads.

Question 5

How does property normalization work?

Accepted Answer

The skill ensures that booleans, numbers, and strings map directly, while date-like values are serialized to ISO 8601 and unsupported objects are converted to strings to prevent tracking failures.

Clix Event Tracking

主要功能

使用场景

Clix Event Tracking

主要功能

使用场景