Your implementation can be via a client-side script that runs on your website, server-side APIs, or a combination of both. Whichever method you choose to serve your campaign variations, include the following components in your implementation to get the full value of Dynamic Yield on your websites and apps. You'll have a discussion with your Dynamic Yield account team during your onboarding to make these initial decisions.
Create your sections
One of the first things you’ll do in terms of implementation is create a section. The section is an entity representing your website or mobile app, for which you’ll be creating your personalization campaigns. All campaigns, audiences, and assets are managed in the section entity.
Each section has a defined type, or platform: Website, Mobile, or API. The Website type can use the script, APIs, or both, and also includes mobile web. The Mobile type is for mobile apps, and the API type is for use with APIs only. It can't be converted to use with scripts, so we recommend choosing Website.
You can have multiple section entities, say, for different countries or brands.
Before you create your sections, learn more about the following:
- Using a single section or multiple sections.
- Multi-language support. This can affect how you decide to implement your sections.
Onboard a Product feed
Every section defined in the OS must have either a product feed or a content feed, containing your product or content catalog. The feed unlocks many powerful capabilities, such as serving personalized recommendations, building an affinity profile based on analysis of your visitors’ preferences, social proof messaging, and much more. The feed can be created and updated by uploading a CSV file or using a server-side API.
Track meaningful events
Track events to measure how campaigns affect your KPIs. For example, see 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. Tracking also enables you to segment your traffic by engagement. For example, users who added 5 items to the cart, or users who subscribed to your newsletter. We have a set of recommended, commonly used events, and you can also create custom events to track any interaction that is unique to your business.
Learn more about implementing events using client-side scripts (for websites only) or via server-side API (for both web and app).
Manage page contexts and pageviews
On websites with the script implemented, Dynamic Yield tracks user engagement with various products and categories using the context defined for each page on your site. The context also enables you to target campaigns that are specific to a page type, or filter recommendations according to the product or category that the user interacts with. Every page on a website that includes the client-side script automatically reports a pageview with the context set in the client.
For apps and for web pages without the script, make sure to report pageviews via server-side API and set the context every time you request campaign variations.