Skip to main content
m_alcantara
m_alcantara
Level 4
Oct 16, 2026 6:33 PM UTC
Question

Data Collection - separate rules for Target page and Analytics or combine multiple actions into a single rule

In Data Collection, I have (the usual) Target Page Load Rule, configured like this for reference-

Extension: Adobe Experience Platform Web SDK

Action Type: Send event

Use guided events: checked

Request personalization: checked

This will load Target and render any matching personalizations.

 

For Analytics (for every page load) I have a separate Rule with two actions; the Update variable action to set variables, and the Send event action, configured like this for reference-

Extension: Adobe Experience Platform Web SDK

Action Type: Send event

Use guided events: checked

Collect analytics: checked

 

Question: Is it advisable or good practice to combine the Target send event, the Analytics Update variable, and Analytics Send event all into one Rule? The Target send event action would be fired first, then the Analytics Update vars, then the Analytics send event.

 

I have an issue where I’m using two separate Rules, one for Target and one for Analytics. However, the Analytics rule is firing first and the Target is firing second. Target is not rendering personalizations. In troubleshooting, when I combined them all into one Rule, Target works fine. So, is combining considered good practice or should I keep them separate and find an alternate way to solve the issue?

1 reply

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity Advisor
Community Advisor
Oct 20, 2026 10:35 PM UTC

HI ​@m_alcantara 

As per your use case,  I think yes, combining the actions into one rule is a good approach in this scenario, especially since there is a dependency on the personalization request happening before the Analytics collection.

Adobe actually documents a top-of-page / bottom-of-page Web SDK pattern for implementations using personalization and Analytics:

  • At the top of the page, send a Web SDK event using Request personalization. This fetches personalization decisions and can render the experience, while the special decisioning.propositionFetch event is ignored by Adobe Analytics.
  • At the bottom of the page, send another Web SDK event using Collect analytics. This records the page-view event and can include the propositions that were rendered. 

If keeping Target and Analytics in separate rules causes the Analytics rule to execute first, but combining the actions gives you the correct sequence and resolves the personalization issue, I think keeping them together is a good solution.

However, I wouldn't say that Adobe specifically recommends"put all three actions into one rule." The documentation supports the top-of-page personalization + bottom-of-page Analytics pattern, but doesn't explicitly require those actions to be in the same Tags rule

So I would focus more on ensuring the correct execution sequence rather than separating the rules simply for organizational purposes. 

 

References - https://experienceleague.adobe.com/en/docs/experience-platform/collection/use-cases/personalization/top-bottom-page-events 

Hops this helps. 

Translate
Thanks, Gokul
Terms & ConditionsAccessibility statement

Loading footer...