I think your issue is somewhat related. The template is a special kind of AW project that allows you to build other projects with the same visualisations and layouts. But the panels in that new project are still specific to that project, so the TOC that is in the template and that uses the template's panels' links can't be replicated into that project.

@NitinCT What happens when you use Visits as your metric, instead of Unique Visitors?

@philipk92120636 It might also be interesting to find out why the numbers aligned very well in February. That seems like the anomaly to me.

It depends. Changing from Hit to Visit means that a user must follow the journeys like the examples that I had provided. But if the user would actually have Cart Views and Orders in the same visit, then you'd want to nest those 2 steps in one Visit container.

@Knowledgeseeker98 what are the Attribution and Expiration settings for your eVars in the report suites' admin settings?

Unique Visitors, as the metric implies, counts the number of visitors, which for all intents and purposes is the number of people.It is entirely possible for the same person to be tracked with different operating systems, and people could be updating their OSes regularly (e.g. through automatic updates).Try including the Visits metric in your table. Do the rows' Visits add up to the total? It is unlikely that a person's OS could update midway while browsing your website.

I assume that you know the basics of attribution modelling, i.e. common models like first touch, last touch, linear, etc., and also why attribution modelling is used.AA's attribution modelling works differently from GA's in that there isn't a dedicated Attribution report. Instead, you can set an attribution model per metric within a freeform table.I suggest that you start with these:Attribution overview | Adobe AnalyticsAttribution models and lookback windows | Adobe AnalyticsMetrics | Adobe Ana...

Regarding your "tes" value in 1depth, it's because of your RegEx. I believe 1depth is getting the content of the $2 group.So, with some colouring to help to explain:Your regular expression for 1depth: ^(gnb: )(.[a-zA-Z0-9 ]+)[^_$%^&]Your value and its matches: gnb: test_company_allThe red expression is preventing the last character from being included in your green expression. So instead of "test", you're getting "tes", i.e. without the last "t".Likewise with "gnb: test2_company_all" and "gnb: t...

@Matt_Freestone , my idea builds on field-based stitching.There are 2 aspects of CDA that are not immediately apparent (to me):If a user is using a client's mobile app, and within that app, he causes an in-app browser to open with the client's website. Let's say CDA is already in use. Will AA know how to stitch the hits from the app and in-app browser together? My idea intends for that to happen.While CDA results in a "People" metric, I don't recall reading anything about how it affects the exis...

@cam_213 what is your Tracking Code variable's Expiration setting? Is it the default "Week" or something else? And what is the date range of the report that you're running?

@e30powar Perhaps you can move your form submission tracking to the next page. So if it's a valid Thank You page, then you can track your form submission there.

@Gianluca is the variable set when the page is loaded or later on, e.g. through a script that gets executed after page load? Alternatively, are you able to provide a link to the web page for us to see?

@e30powar isn't that the correct behaviour, though? The form was submitted after all.

Panel links work within the panels' AW project only. So if you use project B's panel links in project A, you should expect to open project A first, and the browser window then jumps to the linked panel.

Just to confirm: inside Adobe Launch, you have setup a Data Element from Core > JavaScript Variable, and you've specified the name of your JavaScript variable in that data element's configuration, right?

My understanding is that ECID can't be set "externally". It is set purely from callbacks with Adobe's own API calls.

@jeff_bloomer Yes, that is how I'm expecting my Classification Rules to work. But they don't. So every time there is a new Product, then even though I have valid Classification Rules to assign values to the nested classifications, those nested classifications never get set, even several days after the Product has been tracked. So I end up having to use Classification Importer to get the classifications in place.

Yes, that's correct.

@CarbonCopyCC What "traffic source" are you referring to? I guess you're coming from Google Analytics. Adobe Analytics has various kinds of traffic source reports, e.g. Referrer, Referring Domain, Referring Type, though I think you meant Marketing Channel. Is that correct?

If you're using Adobe Launch as your tag manager:Open the Adobe Analytics extension.Expand the "Global variables" section.Under "Additional settings", look for the "Campaign" subsection. It might look like this:

I've seen this work sometimes.If you have a shared link to one of those old versions (i.e. a "an.adobe.com" link), open it. It might open up that old version of the dashboard.

Here's a non-obvious way to create your segment: use the Fallout visualisation to help you. Click "Create segment from touchpoint" from the contextual menu. Then edit the segment as desired, e.g.

@vijithar4145255 if you don't want to add custom code, install the "SDI Toolkit" extension from Search Discovery. You can then create a data element that returns the Launch build info.

I think Option 1 is the "most correct" approach.Launch's Core extension has several Event types that can respond to browser events. Mouse clicks are one of them, under the "Click" Event type. Furthermore, this Click Event type is not limited to regular elements, so it can be used to detect clicks anywhere. When configuring the Event, you can set any valid CSS selector. In your example, the selector can be as simple as ".adobelaunchtest". You can also comma-separate selectors to include more than one with the same Event type, then you don't need to create multiple Rules if they all share the same Conditions and Actions.If you're worried about having too many Rules to manage, you can go with a hybrid approach, e.g.Use your jQuery method for clicks within pages' content.Use the Click Event type for "common" elements, e.g. header and footer links, menu navigation.But I would personally use the Click Event types only, even if it results in more Rules being created. I think that approach is more in line with how Launch has been designed to be used, and might also make sense to future maintainers of your Launch property.