Expand my Community achievements bar.

Order Conversions in A4T

Avatar

Level 2

Hi Folks,

 

We are running a drop-off use case on our website home page by using experience targeting. In a personalized experience user will get a resume link to resume the buying journey. 

As of now, we are using A4T as a reporting source in our Experience targeting activities, and we have configured analytics event on the click of resume link. While checking the report in the Analytics workspace we can see the event as a metric against the experience in the target activity.

 

Our requirement over here is to check, how many are the unique visitor in the experience(1) -> how many clicked on resume link from those unique visitors(2) -> how many have placed the orders from those who have clicked on resume link(3).

 

as of now, we are able to see 1->2 and 1->3.

How can we see the report for 1->2->3 or 2->3?

 

Any help is highly appreciated for this. thanks in advance.

 

Regards,

Nitesh 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Reply

Avatar

Level 4

I had this same question. We set up a bunch of banners as an XT; the activity conversion metric is CTA clicks. Every visitor who loads one of the pages sees a banner, and some clicked a CTA. So the A4T report shows visitors, conversions, and a conversion %. You can compare visitors in the experience to overall visitors, but there's no control or A/B, so no lift. And there's no way to segment the experience visitors who saw the banner AND clicked a CTA from those who just saw the banner.

To address that last issue, we added Custom Link tracking to the CTA, like so:

 

 

$(".banner_button").click(function () {
window.s.tl(this, "o", bannerName);})

 


So now in AA Workspace, we can see clicks by banner name, and segment users by those who clicked on all banners or those with matching names. We could narrow that down to individual banner names, but it's a bit tedious.

What we now decided to do is add tracking tags to the target URLs of the CTA buttons. That way, the users who clicked on a button or group of buttons will fall into a campaign visitor segment. You can use the internal campaign variable designated for this purpose (icid=) but we just use our regular campaign tag, where all the metadata lives in SFDC and is ported into AA as Campaign classifications, and we set the vendor field to Internal.