We have configured a button that is populating via Adobe Launch for every page load rule as below:
The button is populating on all pages exactly the way we wanted it to be however there is no call happening to Adobe Analytics when we are clicking on the button. I have checked it in the Network of the developer console window, which ideally I guess it should.
So at this node, I wanted to confirm, Do we have to do set up a "Send Beacon" here like that ?
I want to adobe call to happen when the user will click that Feedback Button on my web page
Are you able to see if rule is getting fired in developer console. To check that, type _satellite.setDebug(true) and see if the rule is firing or condition is passing. If not, you might need to change the event type from DOM ready to click based event.
Hi @jsvasu ,
The rule you shared in the screenshot adds a button. You are looking for a way to send an AA beacon on button click. Add another rule with the Mouse Click event targeted to the added button, and trigger an AA beacon in the Actions.
The integrated button on the website actually has a configuration that says we just have to create "success events" in analytics and map them into Feedback Tool's Web Account as below. We are not supposed to build any click event rules to capture as per the button's configuration.
Success Events Created in Analytics:
This is how they are mapped in Feedback Tool's Web account:
We are bringing this Feedback button as a page load rule via Launch so that it appears on every page. As per the tool when if a feedback button will get clicked the counter-event will automatically capture the count, and similarly when user will complete the feedback, the counter-event will capture the count. However, we are not seeing any Adobe calls"b/ss/" happening, which usually happens to get in like below:
This is something the Feedback Tool vendor has tested in their test environment and they are successfully getting the events triggered at their end for every feedback start/success. Can there be any issue with the Staging Environment where we are testing? What could be the best possible solution to it? Any suggesstions?