Multiple page name sent from a single react component not tracked | Community
Skip to main content
H
harshapr
August 28, 2025
Solved

Multiple page name sent from a single react component not tracked

  • August 28, 2025
  • 3 replies
  • 961 views

Hello,
I 'm sending the adobe page name , one on page load and another on a success api call, in the same page.
But in the adobe tracking tool i only see a single page name under Report Suite(s) column, [xyz-TAG-1].
but under the network section i see  2 columns where i see the 2nd TAG in Page Name coumn -[xyz-TAG-2].
but under the Adobe analytics i do not see the [xyz-TAG-2].
is this. a known issue or is this the expected behaviour , 
also are both the page names are received in the tracker?

Best answer by AnkitJasani29

Hi @harshapr ,

If you want the second event to count as a separate page in Adobe Analytics reports, it needs to be tracked as a full page view. In SPAs, you typically need to manually trigger a page view call for each distinct view you want to appear in the reports.

Thanks,

Ankit

3 replies

AnkitJasani29
AnkitJasani29
Level 6
August 28, 2025

Hi @harshapr ,

This is expected behavior most of the time.

Both values can reach Adobe, you can see the second tag in the browser network request, so the tracker did receive it.

But Adobe’s Pages report only counts page view hits. If the second hit was sent as a link/event (or you only changed pageName without actually calling a pageview), it will show in the network but won’t show up as a page in the Pages report.

Thanks,

Ankit

    H
    harshaprAuthor
    September 9, 2025

    Hello ,
    sorry for the late reply,
    as you mentioned ,
    i can see the 2nd tag

    but i the adobe analytics part i can see only the first page-


    So in my react app, i have both the events that i trigger in a single page, 
    one on page load and one on sucessfull posting , 

    so do you mean that the  2nd event will be shown like this only in the netwrok request ?

     

    Sukrity_Wadhwa
    Community Manager
    Sukrity_WadhwaCommunity Manager
    Community Manager
    September 22, 2025

    Hi @ankitjasani29,

    Could you please help @harshapr further with their query?

    Thanks!

    Sukrity Wadhwa
      bjoern__koth
      Community Advisor and Adobe Champion
      bjoern__kothCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      August 30, 2025

      Hi @harshapr 

      Just one question, is the second request you are sending another page view call or is it a custom link tracking call? Because the "Page" dimension is only available within a page view event, and not custom link tracking. You can set the pageName, and you will see it in your network request, but Adobe will ignore the value during processing.

       

      if you want to have the page name accessible within custom link tracking calls, then make sure to send the pageName value within a separate prop or eVar in the custom link tracking call. I would recommend a Hit-scoped eVar to benefit from the longer value it can hold (255 Bytes vs 100 on a prop)

      Cheers from Switzerland!
        H
        harshaprAuthor
        September 9, 2025

        Sorry but what is custom link tracking ,
        From my application i m sending  the page name
        prop41 : Review: Toukou_complete
        cs.js:63 prop42 : No Referrer:Review: Toukou_complete
        cs.js:63 prop43 : Review: Toukou_complete
        like this 
        . I would recommend a Hit-scoped eVar to benefit from the longer value it can hold  - let me check on this ,

          Sukrity_Wadhwa
          Community Manager
          Sukrity_WadhwaCommunity Manager
          Community Manager
          September 8, 2025

          Hi @harshapr,

          Were you able to resolve this query with the help of the provided solutions, or do you still need further assistance? Please let us know. If any of the answers were helpful in moving you closer to a resolution, even partially, we encourage you to mark the one that helped the most as the 'Correct Reply.'

          Thank you!

          Sukrity Wadhwa
            Terms & ConditionsAccessibility statement

            Loading footer...