Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Migration DTM to Adobe Launch

1982luca
Level 8
Level 8

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 Accepted Solution
ishans52004352
Correct answer by
Employee
Employee

Hi @1982luca ,

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!
 

View solution in original post

1 Reply
ishans52004352
Correct answer by
Employee
Employee

Hi @1982luca ,

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!
 

View solution in original post