Adobe Analytics

jiayingPa1 · 1/23/25

I am currently updating our Adobe Analytics dashboards for 2025 and notice something incorrect in one of our dashboards(screenshot below).

I find this a bit odd, as no gated content form is offered on the first, third, or eighth pages. Could you explain why these are counted as gated content form conversions in Adobe Analytics.

Harveer_SinghGi1 · 1/23/25

Hi @jiayingPa1 ,

One reason that I could think of is if there are some gated content form conversions that you are tracking but Page ID is not populated in those hits, in this case the Page ID that visitor saw before the gated content form conversions will take credit if Page ID is persisting, assuming that Page ID is an eVar.

If you have any means of verifying on which exact page the conversion happened (using page URL etc.) then you can perform a breakdown with relevant dimension to see if these conversion actually happened on those pages or are they taking credit because of persistence. Another thing you can test is using Page ID eVar's instances metric in the same report which will tell you if that Page ID was tracked on the same hit as the conversion or it persisted from earlier.

Cheers!

View solution in original post

Harveer_SinghGi1 · 1/23/25

Hi @jiayingPa1 ,

One reason that I could think of is if there are some gated content form conversions that you are tracking but Page ID is not populated in those hits, in this case the Page ID that visitor saw before the gated content form conversions will take credit if Page ID is persisting, assuming that Page ID is an eVar.

If you have any means of verifying on which exact page the conversion happened (using page URL etc.) then you can perform a breakdown with relevant dimension to see if these conversion actually happened on those pages or are they taking credit because of persistence. Another thing you can test is using Page ID eVar's instances metric in the same report which will tell you if that Page ID was tracked on the same hit as the conversion or it persisted from earlier.

Cheers!

MandyGeorge · 1/23/25

I agree with @Harveer_SinghGi1, it is very likely due to evar persistence in the Page ID.

One way that I would go about testing this is to take the evar instances metric and put it in a hit level segment, then apply that segment to your column. This will limit the resulting form ends to only those that actually passed a page ID.

I wouldn't use this to count your total form ends, but if you're trying to do it based on page ID, this can be a great way of making sure it isn't a persisted value.

jiayingPa1 · 1/23/25

@Harveer_SinghGi1 @MandyGeorge

Yes,I tried with the' Page URL ' dimension and it worked!

Thank you so much for your help and have a nice day

Cheers!:)

jiayingPa1 · 1/28/25

Hello @Harveer_SinghGi1 @MandyGeorge

I am sorry to bother again but today when using paid campaigns, I included the page URL as well.Then it displays each page url with a different utm code as a separate page url (even if the page url itself is the same).

Do you know if there is a way to fix this?Thank you so much for the help.

Best Regards:)

Harveer_SinghGi1 · 1/28/25

Hi @jiayingPa1 ,

You can create classification reports on top of your URL variable to clean it up where you can use regex type rule in Classification Rule builder to keep the part before "?" which is the URL of the page. Doing this will club the different URL variables caused for QSPs under single URL value for you to report.

Cheers!