Adobe Call not happening | Community
Skip to main content
JyotiSharmaV
Community Advisor
JyotiSharmaVCommunity Advisor
Community Advisor
June 4, 2021
Solved

Adobe Call not happening

  • June 4, 2021
  • 5 replies
  • 4461 views

Hello, 

 

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 ?

Best

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by irama987596

That's correct. You need to add Send Beacon action. Choose s.t() if it's page view, otherwise choose s.tl() for CTA interactions.

5 replies

H
Adobe Employee
HemanginiAdobe Employee
Adobe Employee
June 4, 2021

Hi @jyotisharmav ,

If you want to trigger an Analytics beacon when this rule fires then you need to add sendbeacon action in this rule.

JyotiSharmaV
Community Advisor
JyotiSharmaVCommunity AdvisorAuthor
Community Advisor
June 4, 2021
Thanks @hemangini for your response. Is this being the reason why Adobe Analytics call is not happening? Because as I mentioned this is the DOM Ready rule which is bringing a "Button" on every page load. And, in my first screenshot I showed that, under Actions in “Core-Custom Code” we just put our JS snippet to load the button but have not set the “Adobe Analytics – Send Beacon” action after that? So, should we try adding that?
I
Adobe Employee
irama987596Adobe EmployeeAccepted solution
Adobe Employee
June 4, 2021

That's correct. You need to add Send Beacon action. Choose s.t() if it's page view, otherwise choose s.tl() for CTA interactions.

JyotiSharmaV
Community Advisor
JyotiSharmaVCommunity AdvisorAuthor
Community Advisor
June 4, 2021

@hemangini and @irama987596 Thanks, maybe I need to be more elaborative. Even after setting the s.tl() my purpose is not getting solved.

I don’t see the Analytics call getting triggered in the developer console window when a user clicks
that Feedback Button (which means the feedback is opened) on my page.
This is how I set it up now. I guess from this setting adobe call is happening for page load, not for click on the
feedback button. Any help on that?

I want to adobe call to happen when the user will click that Feedback Button on my web page

Thanks

 

 

I
Adobe Employee
irama987596Adobe Employee
Adobe Employee
June 5, 2021

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.

Andrey_Osadchuk
Andrey_Osadchuk
Level 10
June 6, 2021

Hi @jyotisharmav ,

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.

 
JyotiSharmaV
Community Advisor
JyotiSharmaVCommunity AdvisorAuthor
Community Advisor
June 7, 2021

@andrey_osadchuk @irama987596 

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?

 

Terms & ConditionsAccessibility statement

Loading footer...