Decoupling Target and Analytics rules in Web SDK

4 replies
34 views
Translate All

Using Web SDK. In Adobe Data Collection, we have a rule for collecting analytics called - Analytics - Page View, and a separate rule for loading Target called - Adobe Target - Page Load. These rules both fire on every page.

We’re experiencing an issue. Normally, the Target rule fires first, and the Analytics rule fires after it. Everything works when this is the sequence. However, recently, without explanation, the sequence which used to be consistent (Target first, Analytics second) has become inconsistent. Sometimes the sequence flips so that the Analytics fires first and the Target fires second. Whenever this happens, Target doesn’t render personalizations.

changed both rules so that Target personalizations render regardless of the sequence the rules fire. To do this, I “decoupled” Target and Analytics from the rules. My goal is to only collect Analytics (excluding Target data/impressions/etc) when the Analytics rule fires, and only show Target personalizations and collect (Target) impression data when the Target rule fires. Use guided events were checked on the rules previously. It needs to be unchecked to have more control of what happens when each of the rules fire. Changing the trigger is not an option because it causes more issues. Only the Send event for each rule was tweaked.

Does the new configuration for both rules accomplish my goal? It’s been tested and appears to work consistently.

johnsi11

Level 2

Is data layer event for your page view triggering and firing even before page top proposition fetch fires? Not sure how else those rules, given your chart here, would fire out of order. If so, that's interesting, but without knowing all the nuances of your setup, it's okay to be pragmatic here.

It doesn't really matter what order do things happen in, but important consideration here is collecting display metrics for target activities. Just doing proposition fetch and rendering does not automatically count impression data. Typically, a setup would be a 1. proposition fetch at page top, which requests and renders propositions then 2.Then a page view event soon after, which includes the propositions that were displayed in the decisioning propositions field in XDM. This is handled automatically by the "Include Rendered Propositions" checkbox and basically saves you a network call. By unchecking "Include Rendered Propositions" in your Analytics event and checking the “automatically send display event” Checkbox in your target rule you are adding another network call to track what target rendered. So given your new setup you should see in your network calls propositionFetch, propositionDisplay, Pageview.

If you still have some funky behavior going on, I would consider changing the Request default personalization from automatic to explicit on your target call.

Translate

m_alcantaraAuthor

Level 4

Thank you. For the longest time, the Target (Page top) was firing first, then the Analytics (using EEDL custom event as trigger) fired after. This aligns with what you said should be happening. Out of nowhere, the EEDL started firing before the Target Page top. No changes were made to the EEDL event and nothing changed in any of the rules. The order does flip flop, it’s unpredictable, very weird.

I do see a proposition fetch and a proposition display call. Now every page view has three calls, those two plus the analytics call.

Another potential solution is-restore the original Send event settings for both. Instead of a separate Target and Analytics call, add both Send events to one rule. For example, disable Target rule. In Analytics rule add Send event action for Target (can use guided events again) THEN the Analytics Update variables action, THEN the Send event for AA data collection. This will force Target to fire first. Trigger will be the EEDL. I’m concerned about flicker potentially even with the anti-flicker script in p[ace. This will go back to the two calls but Target trigger will now be the EEDL event and not Page Top as it normally is. What do you think of this?

Translate

johnsi11

Level 2

I believe that would technically work, although it would make me raise an eyebrow. I would be curious to see that setup if the analytics call includes the rendered propositions automatically or if things happen too fast for that to take effect. You could also have the 2 rules use the same trigger (dl event, page top, etc) and use rule seqiencing to force them into a specific order

Translate

m_alcantaraAuthor

Level 4

You could also have the 2 rules use the same trigger (dl event, page top, etc) and use rule seqiencing to force them into a specific order > true, I can use the EEDL event and prioritize Target first.

I reverted back to the original Use guided events settings for both and it’s working. But the Target is once again firing first, and the Analytics after it. This was how it was for a long time before the sequence flip started. What makes it difficult is that the issue is intermittent. Ugh.

Translate

Sign up

Login with SSO

Login to the community

Login with SSO