Edge Data Collection Concepts: Migrating Adobe Target

[#1]

By @amandadeasy  and @chrismdavis 

Migrating Adobe Analytics and Target implementations to Edge Data Collection simultaneously is key to streamlining your setup and ensuring consistency across your Experience Cloud solutions. In previous blogs, we discussed the value of using the data object when implementing Edge Data Collection for Experience Cloud solutions, including Adobe Analytics. In this post, we’ll dive into using the data object to migrate mbox parameters for Adobe Target. For a complete step-by-step guide, check out this Web SDK migration tutorial for Target. 

Recall that the data object allows you to implement Web SDK without using an XDM schema. For Target, this approach also provides a flexible way to configure and pass mbox parameters without additional mapping, making implementation and validation even easier! 

Creating the Data Object 

Before you begin, ensure that your datastream is enabled for Target. If you haven’t already set up a data object variable in your Adobe Tags property, you can do so by following these steps:  

1. Install the Adobe Experience Platform Web SDK extension in your Tags property and configure your Datastream IDs.
2. Create a data element using the AEP Web SDK extension with the “Variable” type and enable the Adobe Target solution.  

If you’ve already created a data object variable created from your Analytics implementation, simply update the data element and enable Adobe Target as an additional solution. 

Adding mbox Parameters

Once your data object is enabled for Target, you can begin populating the Target object in your Web SDK rules:  

1. In your “Update variables” action, choose your data object data element. 
2. Populate the Target object within the data element by adding mbox parameters. These parameters will automatically map to Adobe Target without manual mapping. 
3. Ensure that the data object variable is included in the subsequent “Send event” action to send the populated data to Edge. 

Validating Target

Validation is a critical step in ensuring that your mbox parameters are correctly passed to Target. Here’s how you can validate your implementation using the browser’s developer tools: 

1. Open the developer tools and navigate to the network tab.  
2. Locate your Web SDK calls be filtering network calls for /ee  
3. Inspect the payload of your network request and validate your Target parameters. 

Inspecting these server calls ensures that your parameters are correctly passed to Target. You can also use the AEP Debugger Extension or Adobe Assurance to do the same. 

Conclusion

Migrating Adobe Target to Edge Data Collection using the data object offers an efficient and consistent way to manage your implementation. With this approach, you can streamline the process of passing mbox parameters and maintain alignment across Experience Cloud solutions, future-proofing your implementation.  

In an upcoming post, we’ll round out our Experience Cloud migration with Adobe Audience Manager! 

[#2]

So valuable, Thanks