Frequently Asked Questions FAQ
What environments and situations are SDK integration and API integration suitable for?
Generally, SDK integration is a method adopted when processing information that can be obtained from the client (in-app login, purchase, etc.). In this case, since basic terminal information, etc. are automatically collected through the SDK, more information can be easily obtained.
The API method can be used for all data points including clients. It is generally adopted to collect external data (POS data, automatic payment data, subscription cancellation event data through customer center, etc.) whose changes are difficult to detect on the client.
Is there any difference in the setting method whether I use SDK integration or API integration?
No, there is none. Since the basic method is to register the keys of events, event properties, and user properties and then collect data, there is no difference in using and configuring the DFINERY Console.
What is the effect on reports and campaigns if I change the basic information of an event or attribute (ex. display name, description)?
If you change the basic information, it will be changed in bulk everywhere that uses that basic information (e.g. the attribute description area in the audience filter, etc.).
Can I add custom event properties to events?
Of course. If you add a custom property, the property will be added to the use case that utilizes that event and can be used.
Can an error occur if I disable the collection status of events and properties being used in audiences, reports, campaigns, etc.? So what errors can occur?
Yes, there may be issues with audiences and campaigns created using the event. If the event and attribute collection status is disabled, data will no longer be collected. It will be difficult to update the exact audience parameters, and the resulting data may differ when checking the report. In addition, the campaign cannot be triggered to the desired target.
To avoid these issues, you should check how the data will be used before disabling the collection status.
Can I change the integration method (app, web or API) set when creating the service later?
It is possible in a limited way.
The previously selected and applied linkage method cannot be canceled, and the unselected items can be additionally selected later.
Is there any limit to the number of events that can be linked?
Yes, there is no limit to the number of events. However, there is a limit to the number of attribute data, such as event attributes and user profile attributes.
Can data analysis vary depending on when an event is called?
Yes, that's right.
For example, if you call the 'Purchase' event when the purchase button is clicked, the purchase event will be processed as occurring even if the purchase fails. However, if you call the purchase event on the 'Purchase Complete' page, this problem will not occur. Linking events at appropriate and clear times or pages like this helps you analyze and utilize accurate data.
Can I modify an event or property once created?
It is possible to modify the display name and description on the console, and also add custom properties.
If the nature or concept of the data changes, re-linking may be required by the development team as needed.
Can I use DFINERY only after all integrations, including SDK, user identification information, user profile attribute information, and S2S API, are completed?
If the session execution event is confirmed, is SDK integration completed?
If the SDK is installed and executed (initialized) normally, the SDK will automatically call the session execution event when you execute the app or access the web. If the session execution event is confirmed, you can determine that it is connected normally.
What is the difference between user identification information and user profile attribute information?
At DFINERY, we are building consistent customer profiles through unified IDs that collect data from various devices and channels.
The integrated ID is created based on user identification information, and user identification information includes external ID (user ID), email, phone number, Kakao ID, Line ID, etc.
※ For external ID (user ID), please link a unique number used for internal management purposes for security purposes. (Ex. Even if the external ID is dfinery123, data linking is required, such as 1230102301.)
User profile information is attribute information about the user, such as name, date of birth, and gender.
Last updated