Overview
This guide is aimed to help configure your Adobe Launch environment to implement the Wunderkind Smart Tag and Conversion Pixel on your website. This guide utilizes a rule-based system, which is similar to Tools in Adobe’s Dynamic Tag Management (DTM) product, as Wunderkind does not yet have a native extension with Adobe Launch.
Both the tag and pixel are code snippets that are specific to a website. The tag is placed on all pages of a site, while the pixel is only placed on pages that represent a successful order and/or user conversion. Both files can be found accompanying the initial integration email you received from your Wunderkind point of contact.
Table of Contents
- Create a Rule for the Wunderkind Tag
- Configure the event trigger
- Configure an action for the tag rule
- Configure the conversion pixel
- Add a condition to the pixel rule
- Create 2 actions for the pixel rule
- Testing and deployment
1. Create a Rule for the Wunderkind Tag
Name the Rule, then add an Event Trigger.
2. Configure the Event
Adobe defines their Event Types according to these descriptions. Wunderkind recommends selecting the Library Loaded event since it allows our tag to begin executing as soon as the Launch library is loaded.
It is possible to use event triggers other than Library Loaded, but there are considerations to take into account before making this decision. Most notably, other event triggers may not execute the tag soon enough and thus tracking data may be lost if end-users navigate away from a page prior to tag load. Your Wunderkind point of contact can talk through the advantages and disadvantages of the different event triggers.
The tag is loaded asynchronously and should not block other tags, scripts, or elements from loading. Below is an example of a custom event trigger that executes as soon as the page beings to render:
3. Configure an Action for the Tag Rule
Make sure that “HTML” and “Execute globally” are selected, then click “Open Editor”.
In the code editor, copy/paste the Tag code provided by your Wunderkind contact. Note that the blurred section of the tag is your website-specific id.
Click Save, and then “Keep Changes” to save the Action. At this point, the Wunderkind Smart Tag placement has been completed and the Rule can be saved.
4. Create a second Rule to execute the Conversion Pixel
Repeat Steps 1 - 3, but make the following changes:
- Name the Rule “Wunderkind_Conversion”
- When configuring the event, set the rule order to be higher than that of the Smart Tag. This ensures that the Smart Tag loads before the Conversion Pixel.
5. Add a Condition to the Pixel Rule
This step is unique to your website’s configuration. You will need to create a condition that ensures only order confirmation pages are targeted with this Rule.
In the below example, we are using a Condition that states that the rule can only fire on raw page types that have the value “Order”. Once this has been configured, save changes.
6. Create two Actions for the pixel Rule
The pixel is comprised of two code snippets, each of which is unique to your website. It’s important to use these as they specifically map to the data elements on your website.
7. Testing and Deployment
Once complete, you can save the Rule and deploy to a staging environment to test. If preferred, a screenshare can be scheduled to troubleshoot in real-time. Please reach out to your Wunderkind contact to schedule if desired.
Adobe Launch allows you to deploy to staging environments prior to launch in production. This is done in the “Publishing” tab.
If implemented correctly, the Wunderkind tag can be seen loading in your browser console on all website pages.
The conversion pixel should only load on order confirmation pages. All fields should map to the correct data elements in your data layer. While you should ensure that all fields are properly mapped, it’s most important for Wunderkind to receive the following: order_id, amount, and email.
Once tested in a staging environment, please let your Wunderkind point of contact know and we can begin validation prior to deploying to production.