Issue in sending analytics data to Adobe analytics for URL containing # (fragment) in the URL | Community
Skip to main content
sharma_nik
sharma_nik
Level 2
September 15, 2021
Question

Issue in sending analytics data to Adobe analytics for URL containing # (fragment) in the URL

  • September 15, 2021
  • 2 replies
  • 1451 views

Hi

We are having issues in receiving analytics data from ACC email campaigns. This issue seems to coming for our single page application for purchasing products.

 

For example: Here is the link we use in our email campaigns: 

https://abc.com/#/external/purchase/xyz

 

for this, adobe campaign is creating following link to send data to analytics:

https://abc.com/?cmpid=xxxx&bid=yyyyy&did=zzzz#/external/purchase/home (adding cmpid, did, bid in between the url before #)

 

and following is the link ACC should create in our analytics to properly receive the data: https://abc.com/#/external/purchase/home?cmpid=xxxx&bid=yyyy&did=zzzzz

 

 

Most probably, this is due to the fragment (#) we are using in our spa page link.
As we are getting correct data for other purchase links which does not (#) in between the URL.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Manoj_Kumar
Community Advisor
Manoj_KumarCommunity Advisor
Community Advisor
September 15, 2021

Hello @sharma_nik 

Yes, you are correct. This is because of the # being use by your application routing. You will have to change the routing of your react/angular/vue app to remove the # from the URLs.

 

It is not a huge change from a developers perspectiv.

Manoj     Find me on LinkedIn
    sharma_nik
    sharma_nikAuthor
    Level 2
    September 16, 2021

    Hi Manoj 

    Thanks for your response.
    We have multiple pages like that and it will be a big change for us.
    Is there anything we can do from Campaign side that will work on this URL?

     

    Manoj_Kumar
    Community Advisor
    Manoj_KumarCommunity Advisor
    Community Advisor
    September 16, 2021

    Hello @sharma_nik 

    The other way also require web developers help. Whenin they will create a logic to fix the URL when ever they see it not aligned properly.

     

    If the web developers are using route names/alias to navigate then changing the route file would be a good idea. If they are using relevant paths to navigate then it is a huge change. 

     

    Manoj     Find me on LinkedIn
      sharma_nik
      sharma_nikAuthor
      Level 2
      September 24, 2021

      @vraghav 
      @davidkangni 
      @adhiyan 

      Terms & ConditionsAccessibility statement

      Loading footer...