Initialize SDKs

Prerequisites

• To use the Visitor ID/API Service, your company must be enabled for the Adobe Experience Cloud and have an Organization ID. For more information, see Experience Cloud Requirements: Organization ID in the Identity Service Help guide.
• You need the VisitorAPI.js file. You should already have this file if you have Adobe Analytics implemented. This file can also be added through the Adobe Experience Platform tags extension or can be downloaded from the Adobe Analytics Code Manager.

Configure and refer VisitorAPI.js

For more information, see Implement the Experience Cloud Service for Target.

Readings

• Experience Cloud Identity Service overview
• About the ID Service
• Cookies and the Experience Cloud Identity Service
• How the Experience Cloud Identity Service requests and sets IDs
• Understanding ID synchronization and match rates

Actions

• Embed the VisitorAPI.js file on your webpages.
• Read about the available configurations for the Visitor ID/API Service.
• After the VisitorAPI.js file is loaded, use the Visitor.getInstance method to initialize using the necessary configurations you need.
• Familiarize yourself with the available methods.

Prerequisites

• The visitors’ known ID should be available in the data layer.

Set Customer ID
For more information, see setCustomerIDs.

Readings

• Real-time profile syncing for mbox3rdPartyId

Actions

• Use visitor.setCustomerIDs to set the visitor known ID.

Prerequisites

• Not all data in the data layer must be sent to Target. Consult with your business team (digital marketing team) to determine which data is valuable for experimentation, optimization, and personalization. Only this data should be sent to Target.
• Ensure that you do not send any Personally Identifiable Information (PII) data to Target.

Configure automatic page load request

For more information, see targetGlobalSettings().

Readings

Learn about the pageLoadEnabled setting in targetGlobalSettings().

Actions

• Modify the window.targetGlobalSettings object to enable automatic page-load requests.

Prerequisites

• Have a discussion with the team responsible for web page performance regarding the pros and cons of controlling flicker using the default method used by at.js. You can search for design patterns that let you use custom flicker handling solution, such as loader animation. If you do not find a pattern, you can request a new pattern.

Configure flicker handling

For more information, see targetGlobalSettings().

Setting bodyHidingEnabled to true hides the entire page body while the page-load request is in progress. If you have not enabled the automatic page-load request for any reason (data later not ready, for example), it is best to set this setting to false.

If you have disabled bodyHidingEnabled because you do not want to fire APLR and want to fire the page request later, or you do not need flicker handling, you must implement your own flicker handling. You can handle flicker two ways: hiding the sections under test or by showing a throbber on the sections under test.

Readings

• How at.js manages flicker
• Learn about the bodyHiddenStyle and bodyHidingEnabled objects in targetGlobalSettings().

Actions

• Modify the window.targetGlobalSettings object to set bodyHiddenStyle and bodyHidingEnabled.

Prerequisites

• The data layer should be ready with all the data that must be sent to Target.

• Recommendations: enrich profile.

  • Pass entity.id to capture data for recently viewed criteria and items based on criteria based on last viewed product.
  • Pass entity.id to capture data for popularity criteria based on favorite category.
  • Pass the profile attribute if custom criteria is based on it or used in inclusion rule filtering in any criteria.

• Recommendations: ingest product data.

  • Other entity parameters (reserved and custom) can be passed to ingest or update the product catalog in Recommendations.
  • The product catalog can also be updated by using entity feeds using the Target UI or API.

Map data to Target

For more information, see targetPageParams().

Readings

• targetPageParams()
• Plan and implement Recommendations
• Set up your Recommendations catalog

Actions

• Use the targetPageParams() function to set all the required data that must be sent to Target.

Available options

• Promote by IDs
• Promote by collection
• Promote by attribute

Entity parameters required

• Item attribute in promotion must be passed when using the “promote by attribute” option.

Available criteria

• People Who Viewed These, Viewed Those
• People Who Viewed These, Bought Those
• People Who Bought These, Bought Those

Entity parameters required

• cartIds

Readings

• Cart-based

Available criteria

• Most Viewed Across the Site
• Most Viewed by Category
• Most Viewed by Item Attribute
• Top Sellers Across the Site
• Top Sellers by Category
• Top Sellers by Item Attribute
• Top by Analytics Metric

Entity parameters required

• entity.categoryId or the item attribute for popularity based if the criteria is based on the current item or the item attribute.
• Nothing must be passed for Most Viewed/Top sold across the site.

Readings

• Popularity-based

Available criteria

• People Who Viewed This, Viewed That
• People Who Viewed This, Bought That
• People Who Bought This, Bought That
• Items with Similar Attributes

Entity parameters required

• entity.id or any profile attribute used as a key

Readings

• Item based

Available criteria

• Recently Viewed Items
• Recommended for You

Entity parameters required

• entity.id

Readings

• User-based

Available criteria

• Custom algorithm

Entity parameters required

entity.id or the attribute used as a key for the custom algorithm

Readings

• Custom criteria

Readings

• Use dynamic and static inclusion rules