Unknown appMeasurement sending traffic to my reportsuite | Community
Skip to main content
A
AbhijithRa1
Level 3
March 6, 2026
Question

Unknown appMeasurement sending traffic to my reportsuite

  • March 6, 2026
  • 5 replies
  • 41 views

We discontinued supporting one of the website and even disabled the launch property build. But still some other unexpected(uncovered from collected data) websites sending the traffic to that report suite. As the other websites/current scripts it’s beyond our reach, we have no option to control the scripts itself. So is there a way to make the payloads fail at browser level for specific report suite from Admin or from Adobe, on report suite basis? Appreciate your inputs.

 

Again, VISTA, BOTS, aborting the calls, invalidating s object doesn’t helps as we can’t access the scripts nor just exclude hits, we completely want to stop ANY/ALL calls to that report suite ID to avoid cost.

​

5 replies

A
AbhijithRa1Author
Level 3
March 6, 2026

​@Jennifer_Dungan ​@amitvishvakarma ​@VishalKa5 ​@NicholeVargas ​@Darshil_Shah1 I see you have been very active lately, I’d really appreciate if you could look into this thread when possible. Thanks 

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
March 6, 2026

Hi ​@AbhijithRa1 

No – there is no Admin or Adobe-side setting that will make hits to a specific Adobe Analytics report suite "fail" at the browser or be rejected server‑side.

If a hit is sent with a valid rsid and tracking server, Adobe will accept and process it.

What you can do:

  1. Only true pre-collection block is in the code
    • The only supported way to stop hits before they reach Adobe is the abort flag in AppMeasurement / Web SDK (it prevents the request from being sent at all). This must be set client-side in the implementation and cannot be configured from Admin or by Adobe for a given report suite. See "Exclude data pre-data collection – use the abort variable" in https://experienceleague.adobe.com/en/docs/analytics/technotes/exclude-data
  2. Post-collection "hiding" options (do not stop billing or requests)
    • If you can't touch the scripts, your only levers are after data arrives:
      • Exclude by IP / Bot Rules / VISTA rules to keep those hits out of reports. They still count as server calls and the browser still sees a successful response.
      • Hide the report suite in the UI if it's truly retired; this makes it invisible but does not stop data collection or billing:
  3. Practical pattern
    • Create a new report suite for the sites you control and update only those implementations.
    • Leave the old suite hidden + filtered (IP/Bot/VISTA) so stray legacy traffic no longer pollutes your "real" reporting, accepting that you cannot hard-fail those requests.

So: you cannot make the payloads fail at browser or collection level per report suite from Admin or via an Adobe switch; only client-side abort or infrastructure controls (CSP, firewall, DNS, etc.) can truly stop the calls.

Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
    P
    patrik60579
    Level 2
    March 6, 2026

    Hi ​@AbhijithRa1 

    No – there is no Admin or Adobe-side setting that will make hits to a specific Adobe Analytics report suite "fail" at the browser or be rejected server‑side.

    If a hit is sent with a valid rsid and tracking server, Adobe will accept and process it.

    What you can do:

    1. Only true pre-collection block is in the code
      • The only supported way to stop hits before they reach Adobe is the abort flag in AppMeasurement / Web SDK (it prevents the request from being sent at all). This must be set client-side in the implementation and cannot be configured from Admin or by Adobe for a given report suite. See "Exclude data pre-data collection – use the abort variable" in https://experienceleague.adobe.com/en/docs/analytics/technotes/exclude-data
    2. Post-collection "hiding" options (do not stop billing or requests)
      • If you can't touch the scripts, your only levers are after data arrives:
        • Exclude by IP / Bot Rules / VISTA rules to keep those hits out of reports. They still count as server calls and the browser still sees a successful response.
        • Hide the report suite in the UI if it's truly retired; this makes it invisible but does not stop data collection or billing:
    3. Practical pattern
      • Create a new report suite for the sites you control and update only those implementations.
      • Leave the old suite hidden + filtered (IP/Bot/VISTA) so stray legacy traffic no longer pollutes your "real" reporting, accepting that you cannot hard-fail those requests.

    So: you cannot make the payloads fail at browser or collection level per report suite from Admin or via an Adobe switch; only client-side abort or infrastructure controls (CSP, firewall, DNS, etc.) can truly stop the calls.

    https://experienceleaguecommunities.adobe.com/adobe-journey-optimizer-15/choosing-between-adobe-target-and-adobe-journey-optimizer-for-web-based-personalization-115806?postid=400321#post400321

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    March 6, 2026

    Hi ​@AbhijithRa1,

     

    So just making sure I have this straight…  You have a site, let’s call it websiteA.com, and you have other websites in your network (websiteB.com, websiteC.com, etc).

     

    WebsiteA.com is no longer under your support, but still has tracking associated to your Organization on it (so you are paying for the server calls) and collecting data for a site that is no longer yours?

     

    WebsiteA.com is a Launch Property? Despite being “disabled” at this time? How did you disable it?

     

    Did you actually go and disable all the rules, and push those changes live? Or did you just delete the property from your Launch?

     

    As far as I know, there is no way to disavow a tracking suite (even though there should be). 

     

    If you didn’t push actual changes up to “turn off tracking” that is probably the main issue here.. and it you deleted the property from your Launch, that will make it difficult if not impossible to do so now (You can try contacting Client Care to restore the deleted property so that you can make the needed changes).

     

    The best option would be to contact whoever is in control of WebsiteA.com now, and ask them to remove the Launch script from their website (this is for both of your benefits… yours so you aren’t paying for it, and theirs so you aren’t still collecting data about their site that you shouldn’t be seeing any longer).

     

    This won’t stop a trickle of data from coming through, from people viewing old cached versions of the site… I still have a handful of traffic each month to old suites that haven’t been used for years (pre-Launch), but its small enough that it’s not a major issue.

     

    Good Luck!

      Jennifer_Dungan
      Community Advisor and Adobe Champion
      Jennifer_DunganCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      March 6, 2026

      In my org, I don’t typically delete Launch properties, I just rename them with a prefix of “ZZZ - “ so that they go to the end of my list, but IF I need to make adjustments (cause something goes crazy), I still have access to them.

       

      However, I am also dealing with a manageable number of properties… this may not be the case for you, and I understand wanting to clean stuff up.

       

      I would hold onto old properties for at least a few months to ensure that nothing “wonky” is happening when a property is transferred.

        A
        AbhijithRa1Author
        Level 3
        March 6, 2026

        hi ​@Jennifer_Dungan  As always big thanks for your contribution to this community. I had mentioned “discontinued”(I used to support websiteA.com and they started using GTM/GA , later I disabled(all rules and published, I supposed no leak here as no more hits from websiteA.com) launch. 

        All the traffic now is from other than websiteA.com(say xyz.com and abc.com), and no control from code front. Hoping if Adobe could fail calls..looking ​Amit’s response, less chances!

          P
          patrik60579
          Level 2
          March 6, 2026

          about-u

          P
          patrik60579
          Level 2
          March 6, 2026

          about-u

          https://experienceleaguecommunities.adobe.com/adobe-journey-optimizer-15/choosing-between-adobe-target-and-adobe-journey-optimizer-for-web-based-personalization-115806?postid=115806#post115806

          VishalKa5
          VishalKa5
          Level 5
          March 7, 2026

          Hi ​@AbhijithRa1,

           

          You cannot fully block AppMeasurement requests to a Report Suite from the browser or from the admin side if external websites are still sending hits with that RSID. As long as the request contains a valid report suite ID, Adobe Analytics will accept the hit.

          Possible options:

          • Contact Adobe Support: Raise a ticket with Adobe Customer Care and request them to disable or decommission the report suite so it stops processing hits.

          • Retire the Report Suite: If it’s no longer needed, ask Adobe to fully deactivate or delete it.

          • Move to a New RSID: Create a new report suite and update your valid implementations, then stop using the old RSID.

          • Filtering won’t stop costs: Options like VISTA rules, bot rules, or processing rules only filter data after collection and do not prevent hits from being counted.

          Summary: The only practical way to stop all traffic is to work with Adobe Support to deactivate the report suite or migrate to a new RSID.

          Thanks & Regards,
          Vishal

          Terms & ConditionsAccessibility statement

          Loading footer...