We are happy to announce the release of our first major version of the Adobe Target Node.js SDK. With this release, we are excited to help you focus on business logic rather than waste time understanding the technicalities of integrating with our APIs. Our Node.js SDK is not merely an API wrapper, but rather a sophisticated software development kit (SDK) that removes the complexities of managing cookies, sessions, and integrating with Experience Cloud products such as Analytics, Experience Cloud Visitor ID service, and Audience Manager. By removing the need for you to understand our ecosystem, we imagine that you will realize increased development velocity as well as improved KPIs that matter most to your business.
New features in the Node.js SDK v1.0
Now with this first-ever major version comes amazing features that we know you will be excited about.
- An integration with Adobe Target’s newest delivery API — Our newest delivery API has better native support for Single Page Applications (SPA) and mobile applications.
- Support for prefetch and notifications that allow you to optimize for performance via caching — You can now use the Node.js SDK to retrieve experiences and cache them locally on your Node.js server with the purpose of minimizing server calls to Target and enhancing your application performance.
- Ability to retrieve VEC-created activities — You can now retrieve VEC-created activities on the server-side. The response that contains VEC-created activities will have selectors that can be used to only pre-hide portions of your page that need to be personalized. This will help optimize your page’s First Contentful Paint metric, which is an important KPI for the Google PageRank system.
To learn more, feel free to check out the Node.js SDK Github repo where you will find extensive documentation and examples.
Node.js SDK is now open sourced
Historically, we wanted marketers, within our customers’ organizations, to be enabled with our best-in-class and extremely easy-to-use products to deliver personalization for their businesses. Now that every business is undergoing a digital transformation, we are seeing developers (yes, you) play a crucial role. Therefore, we are making commitments to heavily invest in the right technology and tools so that you are well equipped to help your organizations deliver personalization programmatically, at scale, and at neck-breaking speed. That means giving you complete control over your implementation and the autonomy to make decisions that are aligned with your organization’s unique use cases and goals. Therefore, in the spirit of transparency, and to promote contribution, we have decided to open source the Node.js SDK. This move will help the Node.js SDK to mature organically, evolve at the pace of innovation, and support unique personalization use cases. Some other benefits of open sourcing the Node.js SDK that we would like to pursue are the following:
- Community: We want to foster a thriving and engaging developer community that can collaborate, share innovative ideas, and commit to improving the SDK.
- Transparency: We want to build trust with our developer community and provide full visibility into our code so that we eliminate any surprises or GOTCHAs for our developers.
- Quality: We believe that by having more developers contribute to our SDK, the code will become more robust, reliable, and highly tested. This will guarantee that our customers are using high-quality code in their technology stacks.
- Velocity: We acknowledge the fact that we sometimes don’t release software as quickly as our customers expect us to. If there are features that our customers want or bugs that need to be fixed, the developer community can develop those features and fix those bugs without heavily relying on our development cycle.
How can you contribute?
Now, I know this is all exciting stuff. And what’s more exciting is that you can contribute today! But, before contributing to the Node.js SDK, we highly encourage you to familiarize yourself with the documentation and code. We also provided sample apps and demos that you can explore, which will in turn help expedite the familiarization process. If you feel comfortable with the code and you already see opportunities for improvement, follow our contribution guidelines outlined in the CONTRIBUTION.md file. Next, submit a pull request through GitHub. Congratulations! You now have the bragging rights to being an open source contributor!