Registration page migration impact on reporting

[Maheswar_Reddy]

Hello Everyone, 

We have 2 adobe properties for Parent Brand and it's child brand
those adobe configuration is completely different each other.

Now management want one registration page for both parent and child brand so they are redirecting users
from child brand to Parent brand when they are clicking registration button in child brand site. in this senreio what are reports will effect .
because users are completely going out from child brand launch scope and coming back after registration.

Is below report will effect or not? any other also

1. Is Campaign Reports & Marketing Channel Reports will effect
2. Duplicate data as refereeing traffic will increase

any thoughts on it . how can we do this with out effecting any of child brand adobe analytics reports

any thoughts will be great help

[VaniBhemarasetty · Accepted solution]

@Maheswar_Reddy If both domains belong to the same organization, you can use cross-domain tracking implementation if both the domains are different.

In this way, you can ensure that your visitors are identified uniformly across both domains, in case third-party cookies are not allowed

https://experienceleague.adobe.com/docs/id-service/using/id-service-api/methods/appendvisitorid.html...

1. Is Campaign Reports & Marketing Channel Reports will affect: It depends on how you are treating the child brand, if you are adding the child domain as internal, then I do not think there should not be a problem
2. Duplicate data as refereeing traffic will increase: If the visitor is tracked the same, again there should not be any issues

[Jennifer_Dungan]

In addition to using the visitor ID service / cross domain tracking as suggested above.

I would suggest changing your implementation to track both the parent and child brands in a "global suite", then create virtual suites for the parent and child separately...

This will allow you to see ALL data together, and easily see the pathing between parent and child (campaign data between the two sites would be shared as the user moves between the domains/sub-domains, traffic won't be duplicated, etc)... but also still have the ability to see the parent in isolation, and the child in isolation.