Skip to main content

Using the Artifacts

Integrating​

Once a code is generated, client like Android, IOS, Web or Backend. Based on their tech stack and language choosen. Can pick up the generated code and directly place it in their existing codebase.

How a sample DataEvent looks like?​

{
  "event_name" : "user_sign_up",
  "user_id" : "12345abcd-abcd1234",
  "signup_time" : "2025-05-29T15:40:48Z",
  "referrer" : "ad_campaign_1",
  "client" : "web-mobile",
  "consent_given" : true,
  "paid_up_amount" : 123.50
}

Filling up the data​

At runtime based on the requirement, client code needs to create the event object and fill data to it via available setter methods. Generated event classes are using builder pattern. That will help create the object easily. Following sample is based on the sample event defined above

UserSignUp event = new UserSignUp.Builder()
  .setUserId("12345abcd-abcd1234")
  .setSignupTime("2025-05-29T15:40:48Z")
  .setReferrer("ad_campaign_1")
  .setClient("web-mobile")
  .setConsentGiven(true)
  .setPaidUpAmount(123.50)
  .build();

Validation​

Condee dashboard allows adding validation rules that can be applied and checked at runtime for the event whenever build() is called. This helps setup rules like non null values or a specific value only kind of validation. Like sending only an email which is in valid email format. This is one of the most important value that condee brings up while defining analytics specs.

Sending the data​

If all validation is in place, Build method will simply return the json created or will throw exception. Generated json will carry the event name and its properties name exactly consistent to what was defined in the dashboard.

This generated json can be sent to your existing system the way it is already being sent. Condee has helped making it consistent and as per expectation.