how do i merge http and https pages as one ?



Hi Folks,

I am seeing 2 separate pages for http and https and would like to know how to merge this into one single page in my AA Report. Do I need to set up a processing rule, Classification or some sort of conditions?

 What do i need to do please?

Accepted Solutions (1)

Accepted Solutions (1)



Classification would make you a report where historical data are merged, and that may seems like the least bad option. However, I would consider to fix the data collection (either on-site/TMS or via processing rule) so you do not store the protocol (http/https) as part of your dimension...


Answers (11)

Answers (11)




If you're willing to update your implementation, you can omit the protocol altogether. I find this valuable, as it also allows me to scrub query strings and anchor tags. This is what I use in an implementation I manage:

s.eVar1 = + window.location.pathname;

This drastically reduces the number of unique values, and I don't have to worry about the hassle of creating or using classifications.



KeeMac wrote...

how do i go about doing this?


Step 1 - Add the Classification using following navigation path

Admin -> Report Suites -> Edit Settings (for selected report suite) -> Traffic -> Traffic Classifications

Note - Assuming you are capturing page URL in an in-built traffic (Page, Channel, Server) or a custom traffic variable
Otherwise, navigate to Conversion -> Conversion Classification

Step 2 - Set-up the Classification Rule

Admin -> Classification Rule Builder -> Add Rule Set -> Create Rule Set

Access the rule set (from the table) just created.

Select Report Suite & the key (parent) variable

Add the rule with Regular Expression as Rule Type. Screenshot below: 



Saurabh Kumar.




     Classification does not alter parent (key) variable data, but only the associated classified variable. Can you re-check or re-run your report and add a screenshot of the issue?


Saurabh Kumar.



Thank you JordanAbbott for your response!

I am using the Page dimension and I'm still having the http/https issue as well as the case sensitivity problem. I think it's because our mobile/desktop implementation is different. Ideally, we should fix the implementation but I'm wondering if there's a quick fix using Launch or processing rules.

Here's an example of the top ten pages pulled through the Page report through Adobe workspace. It's annoying that Homepage/homepage are listed separately.

  1. Homepage
  2. homepage
  3. Search Results
  5. search results
  6. checkout:basket
  7. sales:all-sale
  8. Checkout: Universal Cart

Customer support suggested to either create a classification report or SAINT based upload which I'm trying to figure out. So currently I'm trying to go through the classification route.

We just migrated from DTM to Launch and I do believe it's a lot better. We hired a consultant to help us with the migration. I actually never used DTM but I heard it was hard to use.

Here are some links they sent me. Hope this helps you too!



Hi Suzannen,

We're also hoping to implement Launch, but had trouble getting assistance from ACSS (adobe customer success services) or from our Sales Rep (who never got back to us to this day). I found an easy remedy which may help! Swap out the "Page URL" dimension with just the "Page" dimension and this will ignore http/https protocols (and I'm assuming the Homepage/homepage issue).

Regarding Launch: here is the myriad of links we received from ACSS (Thankfully we had a really caring and helpful customer success manager helping us!):

"Sorry for the late response.

I was able to gather some information for you.

The good thing is that It's pretty easy to migrate from DTM to Launch. It pretty much walks you through how to do it step by step within DTM.

You started pretty well however, you can also go through the links below, I am not sure, if this is specific to DTM to Launch Migration, but these should be a good starting point

Adobe Launch Blogs:
Adobe Launch Videos :
Adobe Launch Information:
Upcoming Demos & Forum :
Activation Insider Newsletter :
Adobe Launch Reference Implementation Guides:
Adobe Web Browser Technology Performance:
Adobe Auditor:

Incase you get stuck you can always reach out to ( the support team and they can help you with any red flags you will raise."

Let me know if you make any headway - I'd love to collaborate/learn. Our issue is that we're not migrating from DTM (Dynamic tag manager) to Launch. DTM was a nightmare for us so we just stuck with the legacy implementation, but we've heard that Launch is a lot better.



If I wanted to go through Launch or through processing rules, how do I set that up? I'm also having issues where page names with different case capitalizations are being separated into different lines in the same page report due inconsistent implementation between mobile and desktop. Example: "Homepage", "homepage", "", and "". This may be a different topic but I'm wondering if I can solve them using the same method?



Thank you, Saurabh!

We think it had something to do with our importer - our web director ran the uploaded manually this morning and didn't get any errors. All of the parent data for our name reports were restored to their former titles.

Thanks again for your quick response!




Hi Saurabh,

I'm New to adobe analytics. I was using the Classification Rule Builder today to try and combine our http and https data today as you layed out and activated the rule. Checked to see if it worked after lunch on workspaces and the URLs didn't change. BUT all of the labels changed to numbers as the name for the metric: "name (programs)". I deleted the classification rule builder but it didn't restore the "name (programs)" to appropriate labels/names programs.

How would I go about restoring these names to their former title name rather than their number title?

Thank you for your help!



Rule based classification using regular expression may work out best if you already have page URL report and just want to combine http and https version of the page into one  (that is stripping out URL protocol). This will take care of the history data as well.