Welcome to Dynamic Yield! The Dynamic Yield platform allows you to serve your visitors with more relevant content and promotions, instead of serving a one-size-fit-all to all visitors. This can be done with advanced behavioral targeting capabilities, targeted messages, and product recommendations.
While Dynamic Yield is most commonly used to power websites, you can also leverage Dynamic Yield in emails, native mobile apps, or you can use the eXPerience API to power any digital asset (call center, Kiosk, Alexa Skill, etc.).
Want more details? Visit Dynamic Yield Inspiration Library to see what you can do, or watch this overview:
Where to Start
The Dynamic Yield Academy includes several beginner courses to get you started:
- Dynamic Yield 101 - the basic beginners guide to get an overview of the platform.
- Intro to Behavioral Targeting - to learn a bit more about the user data you can use to create personalized experiences.
You can implement Dynamic Yield on your site in one of the following ways:
- Web implementation: By implementing the Dynamic Yield script in the <head> tag, you allow Dynamic Yield to track your users’ behavior, and serve campaigns on your site. The campaigns are executed via JS code, which manipulates the page upon page load (e.g. replace a page element for a specific segment) or any other trigger (e.g. trigger an overlay when the user attempts to leave the site).
- API implementation: With this approach, you don't implement the JS based script of Dynamic Yield in your <head> tag. This means that your application will need to manage the user and session IDs, and rendering is fully in your hands. This is the most secure, efficient, and integrated method of implementation, but it means that every campaign will require a code deployment of your app, and you will not be able to use the Dynamic Yield templates that allow marketers to create campaigns more quickly. To learn more about the eXPerience API, visit dy.dev.
- Mobile app implementation: for iOS and Android apps, Dynamic Yield offers a dedicated SDK you can implement in your app. The SDK allows you to run segmented experiences, tests, product recommendations and power push notification.
Additional Implementation Procedures
The implementation process also includes:
- Tracking meaningful events: Tracking the meaningful events (similarly to how you track Google Analytics events) allows you to measure how campaigns affect your different KPIs. For example, how much revenue is generated by users who were served with a campaign; or if you run a test on the product page, which variation contributed to more Add to Cart events. This will also allow you to segment your traffic by engagement. For example, users who added an item to the cart 5 times, or users who subscribed to your newsletter. There’s a set of commonly used events that are recommended, but you can also track any interaction that is unique to your business with custom events. Learn more about implementing events in Web, API, and Mobile implementations.
- Product Feed onboarding: By onboarding your product catalog, you unlock many powerful features of Dynamic Yield such as product recommendations, building an affinity profile that analyzes your visitors’ preferences (e.g. user X favorite category is running shoes), social proof messaging, and much more. If your business does not have a product catalog, this is not mandatory.
Before You Create a Project
In Dynamic Yield, all campaigns, audiences, and assets are managed inside a Project. Many times, you have multiple entities: A website and mobile apps, or a website for each country, etc. You might manage these entities in one or more projects, we recommend reading up about how to determine if you want to use a single or multiple projects before getting started.
We also recommend that you read about Dynamic Yield's multilingual support, as this may affect the way you decide to implement your projects.
Dynamic Yield for Developers
Your development team is an integral part of working with Dynamic Yield. Dynamic Yield is an open platform that integrates with your technology stack in many ways. Even though there are many marketer-friendly features that do not require development resources, there are also many personalization opportunities that require custom development. If you're a developer, you might want to check out:
- The Academy course for "Developer Essentials" to learn about the role of developers in web implementation.
- Developer documentation for the eXPerience API.