Expand my Community achievements bar.

SOLVED

How to track clicks within Web Applications

Avatar

Level 2

We use our Web Application pages primarily for legal pages, and was wondering if there is a customized report or workflow we can enable that would allow us to track the total number of clicks on each web application for the month. We want to ensure that we are below our Engine Call volume but not entirely sure what the process would be for this.

Any help would be great!

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@mditullio :

In your case, I believe web-tracking tags are implemented into a web-site that is not located in the same domain as ACC.

How it works -

  • ACC sends the mail to the Recipient with a link inside.
  • The recipient opens the email.
  • When the email link is clicked, the request goes to the Tracking server URL which drops a cookie on Tracking URL domain(ie. adobe.com), and then redirects to the web-site.
  • After this, you will get hit in the tracking log, 0x000.log, but you don't get hit by the web-tracking tag.

Redirection and web tracking use cookies, and it is essential that the web server performing the synchronous HTTP call be in the same domain as the redirection server. The various HTTP exchanges must convey the ‘id’, ‘uuid’, and ‘uuid230’ cookies.

All tracking, web apps, and mirror pages should be served from same domains( on different sub-domains ), which does not need to same-site change.

View solution in original post

3 Replies

Avatar

Correct answer by
Employee Advisor

@mditullio :

In your case, I believe web-tracking tags are implemented into a web-site that is not located in the same domain as ACC.

How it works -

  • ACC sends the mail to the Recipient with a link inside.
  • The recipient opens the email.
  • When the email link is clicked, the request goes to the Tracking server URL which drops a cookie on Tracking URL domain(ie. adobe.com), and then redirects to the web-site.
  • After this, you will get hit in the tracking log, 0x000.log, but you don't get hit by the web-tracking tag.

Redirection and web tracking use cookies, and it is essential that the web server performing the synchronous HTTP call be in the same domain as the redirection server. The various HTTP exchanges must convey the ‘id’, ‘uuid’, and ‘uuid230’ cookies.

All tracking, web apps, and mirror pages should be served from same domains( on different sub-domains ), which does not need to same-site change.

Avatar

Administrator

Hi @mditullio,

Were you able to resolve this query with the help of the given solutions or do you still need more help here? Do let us know. In case the given solutions were helpful, then kindly choose the one that helped you the most as the 'Correct Reply'.
Thanks!



Sukrity Wadhwa