Adobe Dynamic Tag Management (DTM) allows you to quickly manage and deploy tags and distribute data. It’s part of the Adobe Marketing Cloud. DTM provides an interface to quickly and easily manage an unlimited number of Adobe Analytics and third-party tags.
Implementing GetFeedback Digital with DTM
The ability of DTM to manage, edit and deploy third-party tags enables its users to also install the Feedback button. One the numerous ways of implementing GetFeedback Digital is explained down below:
Step 1
Create a feedback button in the GetFeedback Digital tool. You will receive a JavaScript code snippet. This JavaScript code will be used to implement the button through DTM.
Step 2
If you are a Marketing Cloud user and have successfully linked your accounts, you should be able to access DTM from your marketing.adobe.com or dtm.adobe.com URLs. From these links, users should log in with the credentials they set up through the email invitation sent from the DTM system upon the creation of their DTM account.
Step 3
On the DTM home screen, select the designated web property where you want to install the button on.
Step 4
On the overview screen, select the 'Rules' section, since the implementation of GetFeedback Digital will be bind to a newly created rule.
Step 5
On the rules menu, select page load rules and click on "create new rule" to create a new page load rule
Step 6
On the page load rule creation menu, indicate the name of the rule and designate the conditions of the rule. The conditions of the rule will be the 'if' of your rule.
Step 7
Scroll down to the 'Javascript / Third Party Tags section to input the GetFeedback Digital code snippet. When on the 'sequential HTML' tab, click on the 'add new script' button. The section will designate the 'then' of your rule.
Step 8
On the 'Edit Javascript / Third Party Script' screen, the GetFeedback Digital snippet code of the previously created button can be inputted.
Step 9
Finally, on the GetFeedback Digital rule screen, the rule can be saved. Hereafter, the rule will be available for deployment through the multi-step approval process.
Once approved by an Approver, Approver & Publisher, or Admin level user, the change goes into the publishing queue (‘History’ tab) where the change will need to be actively published by an Admin, Publisher, or Approver & Publisher level user before being live on the site.
In the example above, the page load rule method of firing the GetFeedback Digital script has been explained. Next, to this best practice, there are other variations and custom ways to implement the button. Other general firing conditions are depicted in the picture below:
