Leiste mit Community-Erfolgen erweitern.

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.

Mark Solution

Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.

GELÖST

Migration DTM to Adobe Launch

Avatar

Level 9

Hello everyone,

 

I am working on the migration from DTM to Launch. I noticed that a new rules was created with this name Migrated from DTM: Adobe Analytics - Send Beacon on every page. Anyone can give me some information about this rule and shall I adjust this?

 
 

 

 
 

 

 

1 Akzeptierte Lösung

Avatar

Korrekte Antwort von
Employee Advisor

Hi @Luca_Lattarini ,

In DTM, an Analytics beacon is fired on every page when App Measurement loads (Analytics library), even if no rules have been defined. In Launch, this beacon call is controlled by a rule and does not happen automatically. The upgrade process creates this rule for you unless you use the Page code is already present option in DTM. This rule is called "Migrated from DTM: Adobe Analytics - Send beacon on every page".

The Upgrade Assistant creates this rule in Launch, as long as an Analytics tool is installed in DTM. If you used a return false inside custom code in DTM to suppress the initial beacon call, then you should leave the Launch rule out of your library (or delete it) after the upgrade is complete.
Thanks!
 

Lösung in ursprünglichem Beitrag anzeigen

1 Antwort

Avatar

Korrekte Antwort von
Employee Advisor

Hi @Luca_Lattarini ,

In DTM, an Analytics beacon is fired on every page when App Measurement loads (Analytics library), even if no rules have been defined. In Launch, this beacon call is controlled by a rule and does not happen automatically. The upgrade process creates this rule for you unless you use the Page code is already present option in DTM. This rule is called "Migrated from DTM: Adobe Analytics - Send beacon on every page".

The Upgrade Assistant creates this rule in Launch, as long as an Analytics tool is installed in DTM. If you used a return false inside custom code in DTM to suppress the initial beacon call, then you should leave the Launch rule out of your library (or delete it) after the upgrade is complete.
Thanks!