Demandbase api causing double pageview issue | Community
Skip to main content
V
Adobe Employee
VidhyaAk1Adobe Employee
Adobe Employee
June 18, 2024
Question

Demandbase api causing double pageview issue

  • June 18, 2024
  • 2 replies
  • 1562 views

Hi ,
We have "Global all pages" rules firing on al page to track a pageload
and This rule has a demandbase event .
When ECID is present then only this rule is firing.

In current situation we are getting double pageview call? I search it on google on demandbase api.
I assumed that because of this demand base api is causing this issue.
Anyone  knows how this demand base api's are working ?



 



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

2 replies

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
June 18, 2024

Hi @vidhyaak1 

have you validated by looking at the executed rules / logs that the rule executed more than once?

Is there a chance to figure out what type of demandbase event (success/fail/timeout) triggered the rule e.g., through a separate data element?

 

Alternatively, what do you see if you add a custom code action that only prints out the current event?

_satellite.logger.debug(">>> demandbase event", event);
Cheers from Switzerland!
    V
    Adobe Employee
    VidhyaAk1Adobe EmployeeAuthor
    Adobe Employee
    June 19, 2024

    Hi @bjoern__koth 

    Yes i validated using setDebug(true) i can see that "global all pages" rules fires twice.

    i tried executing the above line of code on console it gives me "undefine" value

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    June 18, 2024

    I agree with @bjoern__koth, it looks like Demandbase is likely triggering multiple events, and each one is triggering the rule.

     

    You could add a second condition for Max Frequency (assuming the events are very close together even something like a Max Frequency of: "Return true no more than once every 1 seconds"

     

    V
    Adobe Employee
    VidhyaAk1Adobe EmployeeAuthor
    Adobe Employee
    June 19, 2024

    Hi @jennifer_dungan 

    where i need to add "max frequency" condition ? before  "custom code" condition or after "custom code" condition in the rule ?
    why we need to set unit as seconds why not as pageview?

    I tried putting max frequency condition before and after custom code still i am getting multiple pageview calls.

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    June 19, 2024

    Hi @vidhyaak1,

     

    it shouldn't matter, since both conditions must pass in order to proceed (and I think they are run in parallel (they say "AND" not "THEN" or "WAIT, THEN" like the Actions).

     

    Technically you can use Page Views, however, I wasn't sure if your website was an SPA (which technically would only have one "page view" condition - these aren't based on the Adobe "Page Views" but actual page loads). I am also not familiar with your site, and whether or not you might get failure or timeouts from demandbase within the "page view". Ultimately, you can play with the settings and fine a condition that works for you. Once per page view may be exactly what you need.

     

    Now, as for still getting multiple page view calls, have you confirmed (using the satellite debugger) that this rule is the one that is firing multiple times, or is it possible this rule and another rule are both triggering (or maybe the calls are more than a second apart if you have only tried my 1 second suggestion, your could try increasing that, or try page view as per above discussion)?

     

    To enable Satellite Debugging, run the commands in your browser's console:

    // Turn on Satellite Debugging _satellite.setDebug(true); // Turn off Satellite Debugging _satellite.setDebug(false);

     

    This will tell you what rules are firing, and in what order... 

    Terms & ConditionsAccessibility statement

    Loading footer...