<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bharatkongari on Medium]]></title>
        <description><![CDATA[Stories by Bharatkongari on Medium]]></description>
        <link>https://medium.com/@bharatkongari1101?source=rss-a001ac17f191------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*unQFvBRHByPDjRRa</url>
            <title>Stories by Bharatkongari on Medium</title>
            <link>https://medium.com/@bharatkongari1101?source=rss-a001ac17f191------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:40:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bharatkongari1101/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[3. Set up Adobe Target with the platform web SDK]]></title>
            <link>https://medium.com/@bharatkongari1101/3-set-up-adobe-target-with-the-platform-web-sdk-80c124db2459?source=rss-a001ac17f191------2</link>
            <guid isPermaLink="false">https://medium.com/p/80c124db2459</guid>
            <dc:creator><![CDATA[Bharatkongari]]></dc:creator>
            <pubDate>Fri, 16 Jun 2023 18:58:17 GMT</pubDate>
            <atom:updated>2023-06-16T18:58:47.671Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the final step of our blog series on Implementing Adobe Target with Adobe Experience Platform Web SDK. In Part 2, we explored the <a href="https://medium.com/@bharatkongari1101/2-tag-configuration-8c91b4abfc95">Tag Configuration</a>, providing you with the knowledge to optimize your Adobe Target implementation. Now, in Part 3, we’ll explore Application Setup — the crucial phase where Adobe Target and Adobe Experience Platform merge to create exceptional user experiences. Let’s dive in and take your implementation to the next level!</p><p>You must need:</p><p>· Complete all steps for the initial configuration of the Platform Web SDK, including setting up data elements and rules.</p><p>· Ensure you have an Editor or Approver role.</p><p>· Install the Visual Experience Composer helper extension if you are using the Google Chrome browser.</p><p>· Know how to set up activities in Target.</p><p>Setting up Adobe Target with the Platform Web SDK can be done in two primary ways:</p><p>1. Asynchronous Implementation</p><p>2. synchronous Implementationuses the <a href="https://luma.enablementadobe.com/content/luma/us/en.html">Luma site</a> which has an asynchronous implementation of tags and flicker mitigation in place</p><p>We uses the <a href="https://luma.enablementadobe.com/content/luma/us/en.html">Luma site</a> which has an asynchronous implementation of tags and flicker mitigation in place. More detail <a href="https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-target.html?lang=en#">https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-target.html?lang=en#</a></p><p><strong>Configure the DataStream</strong></p><p>Target must be enabled in the DataStream configuration before any Target activities can be delivered by Platform Web SDK.</p><p>To configure Target in the data stream:</p><p>1. Go to the Data Collection interface</p><p>2. On the left navigation, select Data streams</p><p>3. Select the previously created Luma Web SDK data stream</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WiRw6ZQSVwVL3HrkmJO4w.png" /></figure><p>4. Select Add Service</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ahya-AaktL8NH16xZ_vtbA.png" /></figure><p>5. Select Adobe Target as the Service</p><p>6. Enter the optional details about your Target implementation, if desired, following the guidance below.</p><p>7. Select Save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1VN7IOUZgT-0Zr1iORJRbQ.png" /></figure><p><strong>Property token</strong></p><p>To set up or find property tokens, navigate to Adobe Target &gt; Administration &gt; Properties. The &lt;/&gt; icon displays the implementation code. The at-property value is the property token you would use in your data stream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3F75p9coZyh3O8DmQkYupA.png" /></figure><p><strong>Target environment ID</strong></p><p>Environments in Target help you manage your implementation through all stages of development.</p><p>To set up or find Environment IDs, navigate to Adobe Target &gt; Administration &gt; Environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aU-JxU9LuiaAe531J9dA9w.png" /></figure><p><strong>Target third-party ID namespace</strong></p><p>This optional setting allows you to specify which Identity Symbol to use for the Target Third Party ID.</p><p>The Identity Symbols are found in the identities list under Data Collection &gt; Customer &gt; Identities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HhD6kHuVMHGPjoMZCTCH2A.png" /></figure><p><strong>Update the page load rule</strong></p><p>When Target is enabled in the DataStream configuration, the Platform Web SDK is responsible for delivering visual personalization decisions. However, these decisions are not automatically rendered on the page. To enable automatic rendering, you need to make modifications to the global page load rule.</p><ol><li>In the <a href="https://experience.adobe.com/#/data-collection">Data Collection</a> interface, open the tag property you are using for this tutorial</li></ol><p>2. Open the all pages - library load - AA &amp; AT rule</p><p>3. Select the Adobe Experience Platform Web SDK - Send event action</p><p>4. Enable <strong>Render visual personalization decisions</strong> with the checkbox</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*axZ_08cG6IpIKwVXd5IQhA.png" /></figure><p>5. Save your changes then build to your library</p><p>Enabling the “render visual personalization decisions” setting in the Platform Web SDK allows Target’s personalized modifications to be automatically applied on the web page.</p><p><strong>Set up a Target activity with the Visual Experience Composer</strong></p><p>Now that the basic implementation portion is complete, create an Experience Targeting (XT) activity in Target to validate that everything is working correctly.</p><p>1. Navigate to Target</p><p>2. Create an Experience Targeting (XT) activity using the Luma homepage for the activity URL</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*od-1vyDZ-lr2u4IbOa5GeA.png" /></figure><p>3. Modify the page, for example, change the text on the homepage banner</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NA9wgegOuMZqnLG2FgU5eA.png" /></figure><p>4. Choose Adobe Analytics as the reporting source with the appropriate report suite and the Orders metric as the goal</p><p>5. Save the activity</p><p>6. If you are comfortable with your changes, then you can activate your activity. Otherwise, if you would like to preview the experience without activating you can copy the QA Preview URL.</p><p>7. Load the Luma homepage and you should see your changes applied</p><p>8. After a few hours, you should be able to see Target activity data and conversions in Adobe Analytics</p><p><strong>Validate with the Debugger</strong></p><p>Once you have set up an activity, you can verify if Target is configured correctly by checking the Send Event network call. Even if no activities are currently live, examining the Send Event call can confirm the proper configuration of Target.</p><p>1. Open the Adobe Experience Platform debugger browser extension</p><p>2. Go to the Luma demo site and use the debugger to switch the tag property on the site to your own development property</p><p>3. Reload the page</p><p>4. Select the Network tool in the debugger</p><p>5. Filter by Adobe Experience Platform Web SDK</p><p>6. Select the value in the event’s row for the first call</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CvU3gmyZW2uVgLPDCs4RgQ.png" /></figure><p>7. Notice that there are keys under query &gt; personalization and decisionScopes has a value of __view__. This scope is equivalent to Target’s “global mbox”. This Platform Web SDK call requested decisions from Target.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ubgNEWjvt_xD62RcoT7Jyg.png" /></figure><p>8 Close the overlay and select the event details for the second network call. This call is only present if Target returned an activity.</p><p>9 Close the overlay and select the event details for the second network call. This call is only present if Target returned an activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IgBV-GA1pvpMhSzdjE7yhQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j8SofCxpqon8BUqiekLROQ.png" /></figure><p><strong>Add a scope to the page load rule</strong></p><p>Modify your page load rule to add a custom decision scope:</p><p>1 Open the all pages — library load — AA &amp; AT rule</p><p>2 Select the Adobe Experience Platform Web SDK — Send Event action</p><p>3 Add one or more scopes you would like to use. For this example, use homepage-hero</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w35jFSZcnk7xL3lVg2F7Kg.png" /></figure><p>4 Save your changes and build to your library</p><p><strong>Process the response from Target</strong></p><p>After configuring the Platform Web SDK to request content for the homepage-hero scope, you need to handle the response appropriately. To accomplish this, the Platform Web SDK tag extension offers a Send Event Complete event that can be utilized to trigger a new rule immediately upon receiving a response from a Send Event action.</p><p>1 create a rule called homepage — send event completely — render homepage-hero.</p><p>2 Add an event to the rule. Use the Adobe Experience Platform Web SDK extension and the Send event complete event type.</p><p>3 Add a condition to restrict the rule to the Luma homepage (path without query string equals /content/luma/us/en.html).</p><p>4 Add an action to the rule. Use the Core extension and Custom Code action type.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cz3jPpRWNEq5l1TiAv_1fw.png" /></figure><p>5 Enter custom code to read and act on the propositions returned from the Platform Web SDK response. The custom code in this example uses the approach outlined in the guide for manually rendering personalized content. The code was adapted for the homepage-hero example scope using a tag rule action.</p><p><strong><em>For Code image refer this link : </em></strong><a href="https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-target.html?lang=en#">https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-target.html?lang=en#</a></p><p>6 Save your changes and build to your library</p><p><strong><em>7</em></strong> Load the Luma homepage a few times, which should be enough to make the new homepage-hero decision scope register in the Target interface<strong><em>.</em></strong></p><p><strong>Set up a Target activity with the Form-based Experience Composer</strong></p><p>Now that you have set up a rule to manually render a custom decision scope, you can proceed to create another Experience Targeting (XT) activity in Target. For this activity, you will utilize the Form-Based Experience Composer, which allows you to design personalized experiences using form inputs<strong>.</strong></p><p>1 Open Adobe Target</p><p>2 Deactivate the activity used for the previous lesson</p><p>3 Create an Experience Targeting (XT) activity using the Form-based Experience Composer option</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B6jLhUDQwa85b6pyb0wJZw.png" /></figure><p>4 Select the homepage-hero location from the location dropdown and Create HTML Offer from the content dropdown. If the location is not available, you can type it in. Target periodically populates new location names after receiving requests for that location or scope</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tSrjAnvdgxZcyFZh_o5lhw.png" /></figure><p>5 Paste the following code in the content box. This code is a basic hero banner with a different background image</p><p><strong><em>For Code image refer this link : </em></strong><a href="https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-target.html?lang=en#">https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-target.html?lang=en#</a></p><p>6 On the Goals &amp; Settings step, choose Adobe Target as the reporting source and Engagement &gt; Page Views as the goal</p><p>7 Save the activity</p><p><strong>8</strong> if you are comfortable with your changes, then you can activate your activity. Otherwise, if you would like to preview the experience without activating you can copy the QA Preview URL<strong>.</strong></p><p>9 Load the Luma homepage and you should see your changes applied</p><p><strong>Validate with the Debugger</strong></p><p>Follow the same debugger steps that were used in the previous VEC implementation.</p><p>Congratulations on completing our blog series on Implementing Adobe Target with Adobe Experience Platform Web SDK. We’ve explored the <a href="https://medium.com/@bharatkongari1101/implementing-adobe-target-with-adobe-experience-platform-web-sdk-f11e93699cb5">Initial Configuration</a>, <a href="https://medium.com/@bharatkongari1101/2-tag-configuration-8c91b4abfc95">Tag Configuration</a>, and <a href="https://medium.com/@bharatkongari1101/3-set-up-adobe-target-with-the-platform-web-sdk-80c124db2459">Application Setup</a>, allowing you to seamlessly integrate Adobe Target into your web application. Thank you for joining us on this insightful adventure…</p><p>We value your feedback, so please share your thoughts and suggestions with us to help us improve and provide more valuable content.</p><p>Once again, thank you for being a part of our community. Stay tuned for more informative content, and we look forward to connecting with you soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80c124db2459" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2. Tag Configuration]]></title>
            <link>https://medium.com/@bharatkongari1101/2-tag-configuration-8c91b4abfc95?source=rss-a001ac17f191------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c91b4abfc95</guid>
            <dc:creator><![CDATA[Bharatkongari]]></dc:creator>
            <pubDate>Wed, 14 Jun 2023 18:35:42 GMT</pubDate>
            <atom:updated>2023-06-15T08:20:26.088Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome back to Part 2 of our blog series on Implementing Adobe Target with Adobe Experience Platform Web SDK. In this implementation, we’ll dive into Tag Configuration.</p><p>Tag configuration is a crucial aspect of implementing Adobe Target. It allows you to track user activities and target specific experiences to different segments of your audience. According to the Adobe documentation, follow these steps to configure tags for Adobe Target using the Adobe Experience Platform Web SDK</p><p>Learn how to install and configure the Platform Web SDK tag extension in the Data Collection interface.</p><p><strong>Requirements</strong></p><p>You must have completed the following step</p><p>· Configure permission</p><p>· Configure an XDM schema</p><p>· Configure an identity namespace</p><p>· Configure a data stream</p><p><strong>Install Experience Platform Web SDK Extension</strong></p><p><strong>Add Property</strong></p><p>To begin, you need to have a tag property. A tag property serves as a container for JavaScript, rules, and other necessary components that collect information from a web page and transmit it to different destinations.</p><p>New property creation</p><p>1. Open the data collection interface</p><p>2. Select Tags in the left navigation</p><p>3. elect the New Property button</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_UrK-_upBZENzREqykW83A.png" /></figure><p>1. As the Name, enter Web SDK Course (add your name to the end, if multiple people from your company are taking this tutorial)</p><p>2. As the Domains, enter enablementadobe.com</p><p>3. Select Save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvKcDZZ1diH_4ZHD5JnEoA.png" /></figure><p><strong>Add the Web SDK extension</strong></p><p>1. Open your new tag property</p><p>2. Go to Extensions &gt; catalog</p><p>3. Search for Adobe Experience Platform Web SDK</p><p>4. Select Install</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DUqOLrFzyG48sxgCTgD9wg.png" /></figure><p>Link Platform Web SDK to your data stream</p><p>1. Under <strong>DataStream</strong>, select the <strong>Choose from list</strong> input method</p><p>2. select the DataStream you created earlier, Luma Web SDK</p><p>3. Select Save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cRy9QLsuQ9TP_MNQUBp3XQ.png" /></figure><p>Now that you have installed Platform Web SDK and associated it to the data stream, you are ready to start mapping data elements to an XDM object with the schema you created.</p><p><strong>Create a data element</strong></p><p>To create the essential data elements needed to capture data with Experience Platform Web SDK. Capture both content and identity data on the Luma demo site</p><p><strong>Requirement</strong></p><p>· Configure permission</p><p>· Configure an XDM schema</p><p>· Configure an identity namespace</p><p>· Configure data stream</p><p>· Web SDK extension installed in tag property</p><p><strong>Create data elements to capture the data layer</strong></p><p>Step for data elements mapping to the Luma demo site data layer</p><p>1. Go to Data Elements and select Add Data Element</p><p>2. Name the data element page.pageInfo.pageName</p><p>3. Use the JavaScript Variable Data Element type to point to a value in Luma’s data layer: digitalData.page.pageInfo.pageName</p><p>4. Check the boxes for Force lowercase value and clean text to standardize the case and remove extraneous spaces</p><p>5. Leave None as the Storage Duration setting since this value is different on every page</p><p>6. Select Save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ejArqaYBLc5htnLx8ACg9A.png" /></figure><p>Follow the same steps to create these four additional data elements:</p><p>page.pageInfo.server mapped to</p><p>digitalData.page.pageInfo.server</p><p>page.pageInfo.hierarchie1 mapped to</p><p>digitalData.page.pageInfo.hierarchie1</p><p>user.profile.attributes.username mapped to</p><p>digitalData.user.0.profile.0.attributes.username</p><p>user.profile.attributes.loggedIn mapped to</p><p>digitalData.user.0.profile.0.attributes.loggedIn</p><p>cart.orderId mapped to digitalData.cart.orderId</p><p><strong>Create Identity Map Data Element</strong></p><p>create the Identity Map data element</p><p>1. Go to Data Elements and select Add Data Element</p><p>2. Name the Data Element identityMap.loginID</p><p>3. As the Extension, select Adobe Experience Platform Web SDK</p><p>4. As the Data Element Type, select Identity map</p><p>5. As the Namespace, select the Luma CRM Id namespace that you previously created in the Configure Identities lesson</p><p>6. After the Namespace is selected, an ID must be set. Select the user.profile.attributes.username data element created earlier in this lesson, which captures an ID when users are logged into the Luma site.</p><p>7. As the Authenticated state, select Authenticated</p><p>8. Select Save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0PyWZ3TX65n_T-0Awa5H_g.png" /></figure><p><strong>Map data elements to XDM objects</strong></p><p>Every data element you generate needs to be associated with an XDM object. This object should align with the XDM schema you established in the Configure a schema lesson.</p><p>Create an XDM object to capture content data:</p><p>1. In the left navigation, select Data Elements</p><p>2. Select Add Data Element</p><p>3. Name the data element xdm.content</p><p>4. As the Extension select Adobe Experience Platform Web SDK</p><p>5. As the Data Element Type select XDM object</p><p>6. Select the Platform Sandbox in which you created the XDM schema in during the Configure an XDM Schema lesson, in this example DEVELOPMENT Mobile and Web SDK Courses</p><p>7. As the Schema, select your Luma Web Event Data schema</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VwsaMZGjy7JHvfqGhOPgEA.png" /></figure><p>8. Scroll down until you reach the web object</p><p>9. Select to open it</p><p>10. Map the following web XDM variables to data elements</p><p>· web.webPageDetials.name to %page.pageInfo.pageName%</p><p>· web.webPageDetials.server to %page.pageInfo.server%</p><p>· web.webPageDetials.siteSection to %page.pageInfo.hierarchie1%</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VAhBJrvh6UpvNXi0siLxGw.png" /></figure><p>11. Next, find the identityMap object in the schema and select it</p><p>12. Map to the identityMap.loginID data element</p><p>13. Select <strong>Save</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YxqPWvSt5bgbeTR2k084Rw.png" /></figure><p><strong>Create tag rule</strong></p><p>Discover the process of transmitting an event to the Platform Edge Network utilizing your XDM object through a tag rule. A tag rule is a combination of events, conditions, and actions that instructs the tag property on what actions to perform</p><p>To create a tag rule:</p><ol><li>Open the tag property you are using for this tutorial</li><li>Go to Rules in the left navigation</li><li>Select the Create New Rule button</li><li>Name the rule all pages - library load - AA &amp; AT</li><li>In the Events section, select Add</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ftb6wJKafzjYLFGIm11p2w.png" /></figure><p>6. Use the Core Extension and select Library Loaded (Page Top) as the Event Type.</p><p>7. Select Keep Changes to return to the main rule screen</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DePL22kTlAjA8AjSf86VHg.png" /></figure><p>8. In the Conditions section, select the Add button</p><p>9. Select Logic Type Exception, Extension Core, and Condition Type Path Without Query String</p><p>10. Enter the URL path /content/luma/us/en/user/cart.html in the path equals field, and name it Core — cart page</p><p>11. Select Keep Changes</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_aLfXKM2UblJCbuCBsGOBQ.png" /></figure><p>12. Add three more exceptions for the following URL paths</p><p>· Core — checkout page for /content/luma/us/en/user/checkout.html</p><p>· Core — thankyou page for /content/luma/us/en/user/checkout/order/thank-you.html</p><p>· Core — product page for /products/ <strong>with the Regex switch turned ON</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zkcERobE3CuQ9mjfrjaI4A.png" /></figure><p>13. In the Actions section, select Add</p><p>14. Select Adobe Experience Platform Web SDK as the Extension</p><p>15. Select Send Event as the Action Type</p><p>16. Select web.webpagedetails.pageViews as the Type.</p><p>17. As the XDM data, select the xdm.content data element created in the previous lesson</p><p>18. Select Keep Changes to return to the main rule screen</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w-E3o-wMXSlJ32z2m2qNeQ.png" /></figure><p>19. Select Save to save the rule</p><p><strong>Publish the rule in a library</strong></p><p>To create a library:</p><p>1. Go to Publishing Flow in the left navigation</p><p>2. Select Add Library</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-mNZgC5oqneHrVRaeciDg.png" /></figure><p>3. or the Name, enter Luma Web SDK Tutorial</p><p>4. For the Environment, select Development</p><p>5. Select Add All Changed Resources</p><p>6. Select Save &amp; Build for Development</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mFKR1HeaXN5bqc93QYQT7A.png" /></figure><p><strong>Validate Web SDK implementations with Experience Platform Debugger</strong></p><p>The Experience Platform Debugger is a browser extension that can be installed on Chrome and Firefox. It provides visibility into the Adobe technology integrated within your web pages.</p><p>The Experience Platform Debugger allows you to easily replace an existing tag library with a different one, saving time and simplifying the validation process.</p><p>Steps:</p><p>1. Make sure you have the Luma site open and select the Experience Platform Debugger extension icon</p><p>2. The Debugger will open and show some details of the hardcoded implementation, which is unrelated to this tutorial</p><p>3. Confirm that the Debugger is “Connected to Luma” as pictured below and then select the “lock” icon to lock the Debugger to the Luma site.</p><p>4. Select the Sign In button and sign into Adobe Experience Cloud using your Adobe Id.</p><p>5. Now go to Experience Platform Tags in the left navigation</p><p>6. Select the Configuration tab</p><p>7. To the right of where it shows you the Page Embed Codes, open the Actions dropdown, and select Replace</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-VIcsXwIvotkWrQDQyDObw.png" /></figure><p>8. Since you are authenticated, the Debugger is going to pull in your available tag properties and environments. Select your Web SDK Course property automatically</p><p>9. Select the Apply button</p><p>The Luma website will now reload with your tag property</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FPAOwrAB0U_vtL3cCDyhdA.png" /></figure><p><strong>Validate your implementation in Experience Platform Debugger</strong></p><p>1. Go to Summary in the left navigation, to see the details of your tag property</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2lbqycGfSi4V520DEXFzIA.png" /></figure><p>2. Now go to Experience Platform Web SDK in the left navigation to see the Network Requests</p><p>3. Open the event’s row</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NOvVT-Qi_WwJKsBjbCtA4g.png" /></figure><p>4. Note how we can see the web.webpagedetails.pageView event type we specified in our Send Event action, and other, out-of-the-box variables adhering to the AEP Web SDK ExperienceEvent Mixin format</p><p>5. Scroll down to the web object, select to open it and inspect the webPageDetails.name, webPageDetails.server, and webPageDetails.siteSection. They should match the corresponding digitalData data layer variables on the homepage</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kyGSKunEtDKjEOHhAhxAcQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c91b4abfc95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing Adobe Target with Adobe Experience Platform Web SDK]]></title>
            <link>https://medium.com/@bharatkongari1101/implementing-adobe-target-with-adobe-experience-platform-web-sdk-f11e93699cb5?source=rss-a001ac17f191------2</link>
            <guid isPermaLink="false">https://medium.com/p/f11e93699cb5</guid>
            <dc:creator><![CDATA[Bharatkongari]]></dc:creator>
            <pubDate>Wed, 14 Jun 2023 12:05:23 GMT</pubDate>
            <atom:updated>2023-06-16T18:57:34.024Z</atom:updated>
            <content:encoded><![CDATA[<p>Experience Platform Web SDK is a client-side JavaScript library that allows customers of Adobe Experience Cloud to interact with both Adobe applications and third-party services through the Adobe Experience Platform Edge Network.</p><p>There are 3 main Steps needed for implementing Adobe Target with AEP Web SDK:</p><p>1. Initial Configuration</p><p>2. Tag Configuration</p><p>3. Application Setup</p><p>We will dive deep into the first part, which focuses on the <strong>Initial Configuration</strong>. Stay tuned for the upcoming sections where we’ll explore the <a href="https://medium.com/@bharatkongari1101/2-tag-configuration-8c91b4abfc95"><strong>Tag Configuration</strong></a> and <strong>Application Setup</strong> to complete your understanding of this powerful integration.</p><p><strong>1. Initial Configuration:</strong></p><p>There are a few steps in the initial configuration</p><p><strong>A. Configuration permissions:</strong></p><p>To implement the Experience Platform Web SDK using tags in the Data Collection interface, it is important to have the necessary user permissions set up in the Admin Console</p><p>Also have permission to Develop, Edit, Approve, Publish, Manage Extensions, Manage Environments, and Manage Properties.</p><p>Experience Platform: These features are accessible to all Adobe Experience Cloud customers, irrespective of their usage of Platform-based applications like Real-Time CDP.</p><p>We need to access all these things</p><p>i. Default production i.e. <strong>prod</strong>.</p><p>ii. Manage <strong>Schemas</strong> and <strong>View Schemas</strong> under <strong>Data Modelling</strong></p><p>iii. Manage <strong>Identity Namespaces</strong> and <strong>View Identity Namespaces</strong> under <strong>Identity Management</strong></p><p>iv. Manage <strong>DataStream</strong> and <strong>View DataStream </strong>under<strong> Data Collection</strong></p><p>v. If you are a customer of a Platform-based application:</p><p>Access to a development sandbox</p><p>All permission items under Data Management, and Profile management</p><p><strong>For Adobe target configure permission we need the editor or approver access</strong></p><p><strong>B. Configure XDM schema</strong></p><p>Learn how to create an XDM schema for web data in the Data Collection interface.</p><p>Experience Data Model (XDM) schemas are the building blocks, principles, and best practices for composing schemas in Adobe Experience Platform.</p><p>By utilizing the Platform Web SDK and your schema, you can effectively manage and streamline the flow of web event data within the Adobe Experience Cloud ecosystem.</p><p><strong>Requirements</strong></p><p>All necessary provisioning and user permissions for Data Collection and Adobe Experience Platform.</p><p><strong>C. Create an XDM schema</strong></p><p>XDM schemas provide a universal and conflict-free way to describe data in the Experience Platform. They allow data structures to be easily shared and reused across organizations, ensuring compatibility and consistency in data management.</p><p>Step to create a schema for the Luma website</p><p>1. Open the Data Collection interface</p><p>2. Make sure that you are in the correct sandbox</p><p>3. Go to Schemas in the left navigation</p><p>4. Select the Create Schema button on the top right</p><p>5. From the dropdown menu, select XDM Experience Event</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MSL5FDO1GIB-4npqbzrfmg.png" /></figure><p><strong>Add fields group</strong></p><p>As noted earlier, XDM is the core framework that standardizes customer experience data by providing common structures and definitions for use in downstream Adobe Experience Platform services. By adhering to XDM standards, all customer experience data can be incorporated into a common representation</p><p>1. In the Field Groups section, select Add</p><p>2. Search for AEP Web SDK Experience Event</p><p>3. Check the box</p><p>4. Search for Consumer Experience Event</p><p>5. Select Add field groups</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VRlQ6RdKhZwg_1iporCtqg.png" /></figure><p>Once you have selected the appropriate field groups, it’s time to give your schema a name. A widely used naming convention for XDM schemas is to name them after the source of the data they represent.</p><p>1. In the Composition panel, select the Untitled schema name</p><p>2. In the Schema properties panel, enter the Display Name Luma Web Event Data</p><p>3. Select anything outside of the Display Name field to activate the Save option</p><p>4. Select Save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GYqPOnuOX_irB4HO0zXfUg.png" /></figure><p>When examining both field groups, you will observe that they provide access to the commonly used key-value pairs essential for web data collection. These pairs contain important information that marketers can utilize in the segment builder interface of Platform-based applications.</p><p>you can change the display name of standard fields to suit your needs. You can also remove fields you don’t want. When you click on either field group name, the interface highlights what key-value pair groupings belong to it. In the below example, you see what groups belong to Consumer Experience Event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_JrGwDzC0PWJGrqQnITKlQ.png" /></figure><p>Creating your web events schema requires exploring and documenting your business requirements, like crafting a Business Requirements Document. This process involves understanding your organization’s needs and objectives to guide the schema development.</p><p><strong>The identity Map object</strong></p><p>To accurately identify web users, a specific data set known as an “identity map” is necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iMYxWhOezB2-amPGyDn4NQ.png" /></figure><p><strong>D. Configure Identity Namespace</strong></p><p>Discover how to set up identity namespaces for utilization with Adobe Experience Platform Web SDK<strong>.</strong></p><p>The Adobe Experience Platform Identity Service establishes a unified visitor ID that seamlessly operates across all Adobe solutions. This empowers Experience Cloud functionalities, including audience-sharing across solutions. Additionally, you can transmit your own customer IDs to the Service to facilitate cross-device targeting and integrations with external systems, such as your Customer Relationship Management (CRM) platform.</p><p><strong>Requirement</strong></p><p>· Configure permissions</p><p>· Configure schema</p><p>Steps to create an identity namespace for luma CRM ID</p><p>1. Open the data collection interface</p><p>2. Select the sandbox you are using for the tutorial</p><p>3. Select Identities in the left navigation</p><p>4. Select Browse</p><p>5. Select Create Identity namespace</p><p>6. Provide details as follows and select Create</p><p>Field Value Display name- Luma CRM ID, Identity symbol- lumaCrmId, Type Cross-Device ID.</p><p>The Identity namespace populates in the Identities screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j2OpHR76Y8IiIY3ZsD9qdw.png" /></figure><p>To overcome a limitation in the Web SDK extension, it is necessary to create identity namespaces in the production sandbox as well, even if you have been using a development sandbox for this tutorial. Specifically, you need to create the Luma CRM ID namespace in your production sandbox.</p><p><strong>E. Configure DataStream</strong></p><p>Data streams are responsible for directing the data collected by the Platform Web SDK to the Adobe Experience Platform Edge Network. Through the data stream configuration, you can enable your Experience Cloud applications, connect to your Experience Platform account, and set up event forwarding.</p><p><strong>Requirements</strong></p><p>Before you configure your DataStream, you must have already completed the following steps</p><p>· Configure permissions</p><p>· Configure schema</p><p>· Configure identity namespace</p><p>Steps to create a DataStream :</p><p>1. Open the data collection interface</p><p>2. Make sure that you are in the correct sandbox</p><p>3. Go to Data Streams in the left navigation</p><p>4. Select New DataStream on the right-hand side of the screen.</p><p>5. Enter Luma Web SDK as the Name. This name is referenced later when you configure the Web SDK extension in your tag property.</p><p>6. Select your Luma Web Event Data as the Event Schema</p><p>7. Select Save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S0xh-E4f7ADWJZgETuPP4g.png" /></figure><p>Congratulations on completing the first part of our blog series on Implementing Adobe Target with Adobe Experience Platform Web SDK! In the next part, we’ll dive into Tag Configuration. Stay tuned for Part 2: Tag Configuration and level up your Adobe Experience Platform skills.</p><p><a href="https://medium.com/@bharatkongari1101/2-tag-configuration-8c91b4abfc95"><strong>Click here</strong></a><strong> to access Part 2 :- </strong><a href="https://medium.com/@bharatkongari1101/2-tag-configuration-8c91b4abfc95"><strong>https://medium.com/@bharatkongari1101/2-tag-configuration-8c91b4abfc95</strong></a></p><p>and continue your journey towards adobe Target Implementation. Happy reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f11e93699cb5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>