Cloudflare dropping the referrer info | Community
Skip to main content
A
AbhijithRa1
Level 3
May 15, 2026
Question

Cloudflare dropping the referrer info

  • May 15, 2026
  • 2 replies
  • 70 views

 

​@Jennifer_Dungan ​@sandip_surse ​@alchan ​@Property Suggest 

Can we load Analytics JS from my domain(to avoid as external call during CloudFlare challenge), while retaining Adobe hosted/managed on all other screens, would visitor ID be affected, what other possible implications I should be aware of?

 

I’m sure this quite common issue across industries and likely discussed/fixed in this community, any other workarounds would be much appreciated. Thank you

 

2 replies

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 15, 2026

Hi, 

I just want to clarify what you are asking….

 

When you say “Can we load Analytics JS from my domain” you mean, not use Adobe Launch’s default “assets.adobedtm.com” domain for the appmeasurement.js + all the resources files?

 

 

Then yes! This is something we do on all our sites.

 

This is called “Self-Hosting”

 

In the Hosts setting, you need to create a new host:

 

There are only two options available:

Managed by Adobe

and

SFTP

 

You will need to have an SFTP server set up on your side, and make sure it’s whitelisted to accept Adobe IPs:

 

 

In our case, our SFTP doesn’t go directly to our web server, we have a Jenkins job that copies updated files from our SFTP to our WebServer, and Clears the cache for the updated files. You may need a slightly different setup, but you will need to discuss that with your DevOps team.

 

 

Next, you will have to create or update your Environments:

Pay close attention to the “self-hosted path”… this is where you will need to make sure all your files reside… this impacts both the appmeasurement.js file, as well as all the resource files that are referenced.

 

For our needs, I leave our Dev environment as “Adobe Hosted” as this speeds up development work (no need to sync using Jenkins), but Staging and Prod go to our Self-Hosted solution.

 

Once you switch your environment to your SFTP Host and set the correct path, the install code snippet will reflect the path you specified.

 

Now, just test to make sure everything is working.

 

There is one little “gotcha” though…  In your Publishing Flow, you will lose access to the “Republish” option to roll back Production Builds to previous versions…

 

For the official documentation, please see: https://experienceleague.adobe.com/en/docs/experience-platform/tags/publish/self-hosting-libraries

    A
    AbhijithRa1Author
    Level 3
    May 18, 2026

    hi ​@Jennifer_Dungan 

    I had stated if we could have “self host”(new launch property) approach on CloudFlare screen alone as to avoid externa; domain during captca/challenge BUT retaining the existing “Adobe managed” approach on the subsequent screen(existing launch container). So an hybrid approach, then would there be any implications(?) as entry page(following the challenge page) would call the existing launch property(thus loads the extensions specifically ID services & Adobe Analytics again) OR would the cookies dropped on the very first challenge page would remain through session? If remains then that might rules out the session split doubt.

    Note that, during cloudFlare challenge page too, the domain remains the same, I meant www.abc.com would remain from Captcha page as well as all the siteSections pages.

    I hope now the ask is clearer. Thanks a ton 

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    May 18, 2026

    There should be no implications of a mixed approach… your ECID would be set based on your Adobe Cloud Account, regardless of what is setting it… 

     

    However, you probably will need two Launch properties, one for the CloudFlare challenge screen, and one for the rest of the site… since you can only have 1 Prod Environment in your Launch Property. 

    Our sites are a network of our sites, plus “external” subdomains… I have separate Launch properties for each code base, but they all send data into the same reporting suite…  We have one additional complication in our current set up… to allow our sites to share content, we had to set up a “hub” that supports the Single Sign On and Subscriptions… the hub is based on the same code base, but with some slight differences (i.e. I can’t use the domain to determine the site.. there is some extra logic to have a “selected site” to show the correct logo and ensure the return URLs go to the correct site…. So, it’s part of the main site flow, but I created a separate Hub property in launch… It can be a bit of a pain to make sure both properties are updated with some of the core analytics changes, but is doable…   this is probably the closest example of a scenario that matches yours… 

    But, I did early on with our external sites, use Adobe Hosted until we updated them… I never had any issues following the user and visit between the core sites and the externals. You should be okay...

     

    But like everything… TEST! lol

      manpreetkaur27
      Adobe Support
      manpreetkaur27Adobe Support
      Adobe Support
      May 17, 2026

      Hi ​@AbhijithRa1 
      I’m following up to see if ​@Jennifer_Dungan ’s answer has helped you. If so, please mark it as the best answer. Otherwise, feel free to share if you have any additional concerns or questions regarding this.

      A
      AbhijithRa1Author
      Level 3
      May 18, 2026

      I just saw Jenni’s response and sent a follow up. The question is still open. Thanks on the follow up.

        Terms & ConditionsAccessibility statement

        Loading footer...