Rule is fired but beacon isn't sent

Question

Hi Community,

For a specific page template on my website, I have 2 rules sending beacon (s.t()).

The first rule is the generic one (rule name : "BOTTOM") which sends a pageview event on every page of my website.

I'm struggling with my second rule dedicated to this specific page template (rule name : "Product-dt").

It's a basic rule as it's waiting "Page BOTTOM" event with a condition on a specific page template of my website.

I added 2 actions : Adobe Analytics - Set Variables wait, then Adobe Analytics - Send Beacon (s.t())

The problem is that when I'm testing my rule, I can see only one beacon fired (I assume it's the one coming from my BOTTOM generic rule) :

My rule product-dt is fired but it seems that it doesn't send a beacon.

Has anyone come across a similar case?

Thanks

Jennifer_Dungan · Accepted Answer

Yes it's part of my product-dt rule.

I juste made the change and tested it, but it doesn't seem to help...

I am seeing beacon fired in my JS Console, but when I want to check in Adobe Platform Debugger, it's like nothing happened...

Ok, let's try the "heavy handed" approach...

Remove the Send Beacon action completely

Go into your Set Variables action, open Custom Code (if you have any custom code here, you need to add this to the end), and add:

s.t();

Basically, we are trying to ensure that everything in your Set Variables is finished before the beacon is set.. if this works, I suggest renaming you action to something like "Adobe Analytics - Set Variables and Send Beacon" so that you remember why you don't have a "Send Beacon" in the rule...

I had to do this on some of my implementations due to timing issues.

Jennifer_Dungan · Answer

No, generally the issue is trying to prevent multiple s.t calls from being made for the same page... but given your description, you are expecting to track the same page twice?

This is bad... you don't want to artificially inflate your Page Views by tracking the same page twice.

If the rule "fires" then unless you have a JS error happening in your rule, the full rule will run. So if you aren't seeing the beacon, I assume that your rule triggers (which is why the debug shows it) then something is failing inside it resulting in not getting the beacon...

But again, I cannot stress enough how bad for your overall analytic health firing two s.tl calls is....

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded