we see no outgoing calls to Floodlight but rule fired in console | Community
Skip to main content
J
jerlinlourds
February 4, 2022
Solved

we see no outgoing calls to Floodlight but rule fired in console

  • February 4, 2022
  • 1 reply
  • 4005 views

For floodlight we were having the issue that we could see in our console that the rule is fired (so launch setup works fine), however in our debugging tool we see no outgoing calls to Floodlight.

For Google Ads everything seemed to work fine.

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 Gokul_Agiwal

And if i deploy using custom code then floodlight tags are firing in network tabs


Hey @jerlinlourds  

Please check the links send through DM. 

1 reply

yuhuisg
Community Advisor
yuhuisgCommunity Advisor
Community Advisor
February 4, 2022

How have you implemented your Floodlight tag? There could be a misconfiguration or an error somewhere.

Also, have you checked your browser's console to see if there were any JavaScript errors when trying to run your Floodlight tag?

J
jerlinlourdsAuthor
February 4, 2022

it was working fine a week back. I dont see any javascript errors on browsers console and i see sent a gtag event in browser console along with rule fired

 

J
jerlinlourdsAuthor
February 7, 2022

302 request is a redirect. Usually, that occurs when the original network request is an insecure HTTP, so the Floodlight server redirects to a secure HTTPS. Although that results in 2 network requests, only one Floodlight hit should be tracked and reported.


would like to understand why 2 302 request in network tab but i see fired a event in browser console from adobe launch. This was actually working fine during december

Terms & ConditionsAccessibility statement

Loading footer...