Skip to main content
RuttalaLi
Level 1
September 25, 2026
Question

Author Environment URLs Appearing in Adobe Analytics Production Report Suite Despite Custom Tracking Server Configuration

  • September 25, 2026
  • 1 reply
  • 11 views

I am investigating an Adobe Analytics implementation issue and would appreciate guidance on understanding the root cause.

Current Setup

We are using:

  • Adobe Analytics Extension (AppMeasurement)
  • Custom Tracking Server configured in the Adobe Analytics Extension
  • AEM as a Cloud Service Author and Publish environments

The Adobe Analytics Extension is configured with:
 

Tracking Server:

smetrics.company.com

SSL Tracking Server:

smetrics.company.com
Based on Adobe documentation for trackingServerSecure, my understanding is that Analytics hits generated by this implementation should be sent through the configured tracking server rather than Adobe's default collection domains.
Observation #1
While testing an AEM Author URL similar to:
https://author-pxxxxx-exxxxxx.adobeaemcloud.com/content/site/page.html
I inspected Network requests and found Analytics calls being sent to:
amcglobal.sc.omtrdc.net
with report suite information resembling:
amc.global.prod
instead of using the configured tracking server:
smetrics.company.com
 

Question

Is this expected behavior because Adobe Experience Cloud / AEM Author itself uses a separate Adobe-managed Analytics implementation?

Or should all Analytics requests on the page be routed through the configured trackingServerSecure value?

 

Observation #2

When reviewing data in Adobe Analytics Workspace, I found Author environment URLs appearing inside our Production report suite.

Examples:
 

https://author-pxxxxx-exxxxxx.adobeaemcloud.com/content/site/page1.html

https://author-pxxxxx-exxxxxx.adobeaemcloud.com/content/site/page2.html

These URLs appear as values in the Page URL dimension of the Production report suite.

Concern

Author URLs should not ideally be collected in our Production reporting because:

  • Internal authoring activity is not customer traffic
  • Content editing and review activity can inflate metrics
  • Page views and engagement reporting may become inaccurate
     

    Network Analysis

    On the Author environment I can currently identify Analytics requests such as:
    amcglobal.sc.omtrdc.net/b/ss/amc.global.prod/...

    However, I am unable to identify requests such as:
    smetrics.company.com/b/ss/production_rsid/…
     

    which I would normally expect if our Analytics implementation were actively firing on Author.

    This creates confusion because:

  • Author URLs are visible in the Production report suite.
  • Network inspection only clearly shows Adobe-owned Analytics requests.
  • I cannot currently identify which request is responsible for sending Author URLs into our report suite.
     

    Question 1

    Can Adobe Experience Cloud / AEM Author generate Analytics requests to Adobe-owned report suites such as:
    amc.global.prod
    independently of the site's Analytics implementation?
     

    Question 2

    If Author URLs are appearing in a Production report suite, what is the best way to determine which Analytics request or implementation is responsible?

    Question 3

    Are there recommended debugging techniques to trace a specific Page URL value found in Workspace back to:

  • the originating report suite hit,
  • AppMeasurement instance,
  • Launch property,

  • Question 4

    If a custom trackingServerSecure is configured, under what scenarios would Analytics requests still appear against:
    *.sc.omtrdc.net
    rather than the configured tracking server?

1 reply

Jennifer_Dungan
Adobe Champion and Community Advisor
Jennifer_DunganAdobe Champion and Community Advisor
Adobe Champion and Community Advisor
September 25, 2026

Hi ​@RuttalaLi ,

 

I have a similar set up to you:

  • Adobe Analytics Extension (AppMeasurement)
  • Custom Tracking Server configured in the Adobe Analytics Extension

I do not have AEM, but that shouldn’t make a difference….

 

Is this expected behavior because Adobe Experience Cloud / AEM Author itself uses a separate Adobe-managed Analytics implementation?

Or should all Analytics requests on the page be routed through the configured trackingServerSecure value?

 

No, this is definitely not expected… you should be seeing your own declared tracking server.

 

 

Concern

Author URLs should not ideally be collected in our Production reporting because...

 

I completely agree with you. It looks like the “AEM Author environment” must be loading your production config (either because it’s been set up incorrectly in the environment, or there is something wrong in your Launch setup…  

 

 

 

I will try and condense your questions here:

  1. I don’t know enough about the AEM setup to know, but I know enough out-of-the-box techniques to ensure clean data. In my setup, I have a QA/DEV Suite, and I have a Prod Suite… all our QA and Dev environments point there, but also, IF someone loads a “preview” from our backend, I added code to my implementation to force that to the QA Suite… sounds like you could use something similar.
  2. Depending on what dimensions you are collecting, you should be able to use segmentation to determine real prod URLs from your back-end URLs… but the ideal scenario is to fix the implementation so that… but you will need both solutions as you fix the implementation AND try to report on clean data in the meantime, and for the foreseeable future (i.e. YoY and MoM reporting)
  3. Debugging techniques will vary depending on what data you are collecting… you might be able to get some of that from the Raw Data, but if you don’t have specific dimensions you won’t be able to use segments on it for cleanup….
  4. You should never see anything other than your specified tracking server….  (unless AEM is doing something incredibly weird…. )

 

I am going to reach out to you directly, I would be happy to jump on a call with you and try to help sort out these issues with you.

Terms & ConditionsAccessibility statement

Loading footer...