Software development kit driven features and events
A method includes providing, to a third-party content provider, code identifying a feature associated with digital content of the third-party content provider, wherein the identification comprises a feature variable placeholder associated with the feature. The method further includes receiving, by an experimentation platform, an indication of a first event type associated with the digital content, wherein the first event type identifies a first trackable action associated with the feature. The method further includes determining, by a processing device of the experimentation platform, that the first event type does not exist in a configuration associated with the feature; The method further includes, in response to the determining, generating the first event type in the configuration, generating and providing a graphical representation of the first event type for display in a user interface of the experimentation platform, and tracking the first event type on the experimentation platform.
1. An apparatus, comprising:
a memory;
a processing device operatively coupled to the memory, the processing device to:
receive, by an experimentation platform, an identification of a feature and an indication of a first event type associated with digital content of a content provider, wherein the first event type identifies a first trackable action performed by a user with respect to one of a plurality of variations of the digital content;
responsive to a determination that the feature associated with the first event type does not exist in a configuration, generate the feature in the configuration based on the identification of the feature; and
log instances in which the first event type is received with respect to the feature of the digital content.
2. The apparatus of claim 1 , wherein the identification of the feature comprises a name and type of the feature.
3. The apparatus of claim 1 , wherein, to determine that the feature associated with the first event type does not exist in the configuration, the processing device is to determine that the feature does not exist in a cache associated with the configuration.
4. The apparatus of claim 1 , the processing device further to:
generate a graphical user interface (GUI) for configuration of the feature; and
responsive to a user interaction with the GUI, configure an experiment associated with the feature that provides additional variations of the digital content that are associated with the feature.
5. The apparatus of claim 1 , wherein the processing device is further to select a version of the feature to implement based on the logging of the instances in which the first event type is received with respect to the feature of the digital content of the content provider.
6. The apparatus of claim 1 , wherein generating the feature in the configuration is further based on a comparison of a number of features that have been generated to a threshold.
7. The apparatus of claim 1 , wherein, to generate the feature in the configuration, the processing device is further to access a representational state transfer (REST) application program interface (API) to create a request to generate the feature on the experimentation platform.
8. A method comprising:
receiving, by an experimentation platform, an identification of a feature and an indication of a first event type associated with digital content of a content provider, wherein the first event type identifies a first trackable action performed by a user with respect to one of a plurality of variations of the digital content;
responsive to a determination that the feature associated with the first event type does not exist in a configuration, generating, by a processing device, the feature in the configuration based on the identification of the feature; and
logging instances in which the first event type is received with respect to the feature of the digital content.
9. The method of claim 8 , wherein the identification of the feature comprises a name and type of the feature.
10. The method of claim 8 , wherein determining that the feature associated with the first event type does not exist in the configuration comprises that the feature does not exist in a cache associated with the configuration.
11. The method of claim 8 , further comprising:
generating a graphical user interface (GUI) for configuration of the feature; and
responsive to a user interaction with the GUI, configuring an experiment associated with the feature that provides additional variations of the digital content that are associated with the feature.
12. The method of claim 8 , further comprising selecting a version of the feature to implement based on the logging of the instances in which the first event type is received with respect to the feature of the digital content of the content provider.
13. The method of claim 8 , wherein generating the feature in the configuration is further based on a comparison of a number of features that have been generated to a threshold.
14. The method of claim 8 , wherein generating the feature in the configuration comprises accessing a representational state transfer (REST) application program interface (API) to create a request to generate the feature on the experimentation platform.
15. A non-transitory computer-readable storage medium storing instructions that, when executed by a processing device, cause the processing device to:
receive, by an experimentation platform, an identification of a feature and an indication of a first event type associated with digital content of a content provider, wherein the first event type identifies a first trackable action performed by a user with respect to one of a plurality of variations of the digital content;
responsive to a determination that the feature associated with the first event type does not exist in a configuration, generate the feature in the configuration based on the identification of the feature; and
log instances in which the first event type is received with respect to the feature of the digital content.
16. The non-transitory computer-readable storage medium of claim 15 , wherein the identification of the feature comprises a name and type of the feature.
17. The non-transitory computer-readable storage medium of claim 15 , wherein, to determine that the feature associated with the first event type does not exist in the configuration, the processing device is to determine that the feature does not exist in a cache associated with the configuration.
18. The non-transitory computer-readable storage medium of claim 9 , the processing device further to:
generate a graphical user interface (GUI) for configuration of the feature; and
responsive to a user interaction with the GUI, configure an experiment associated with the feature that provides additional variations of the digital content that are associated with the feature.
19. The non-transitory computer-readable storage medium of claim 15 , wherein the processing device is further to select a version of the feature to implement based on the logging of the instances in which the first event type is received with respect to the feature of the digital content of the content provider.
20. The non-transitory computer-readable storage medium of claim 15 , wherein generating the feature in the configuration is further based on a comparison of a number of features that have been generated to a threshold.