Hi there,
Seeking your expertise to address some inquiries regarding tracking sales associated with content clicks.
Currently, I am tracking sales metric based on two key dimensions:
Approach:
To validate this approach, I've created a segment (see Picture A) that includes both dimensions and conditions such as card additions, landing on the confirmation page, and orders. I've limited these conditions to actions that occurred after the initial content click.
My Questions:
Solved! Go to Solution.
Views
Replies
Total Likes
Honestly, if I were you, I would consider using a "Conversion Variable Syntax" merchandising eVar (bound to the purchase event).
I am not sure how familiar you are with Products and Merchandising eVars, but normally when you set this up, you use "Product Syntax" and set the Merchandising eVars right in your Products notation...
But "Conversion Variable Syntax" allows for a stitching effect between an earlier page/action and the products later in the journey.
So for example:
Now you don't have to do any fancy segments, you can just correlate eVarx and eVarY to your Orders metric.
Views
Replies
Total Likes
Let me take a stab at the first question. The "then" parts do care what happened between the check points. So the first criteria looks for c17- shop AND c47=<something>. If that condition is met, the next condition is that there is there is there is a cart addition. If the cart condition is met, the rule moves on. It does not matter if there were other calls between the two checkpoints as long as there was a cart addition after the shop + click condition.
Note there is the ability to time limit the "then" conditions. E.g. next hit or within 1 page etc.
Honestly, if I were you, I would consider using a "Conversion Variable Syntax" merchandising eVar (bound to the purchase event).
I am not sure how familiar you are with Products and Merchandising eVars, but normally when you set this up, you use "Product Syntax" and set the Merchandising eVars right in your Products notation...
But "Conversion Variable Syntax" allows for a stitching effect between an earlier page/action and the products later in the journey.
So for example:
Now you don't have to do any fancy segments, you can just correlate eVarx and eVarY to your Orders metric.
Views
Replies
Total Likes
unfortunately, at this stage I cannot build any new rules (i.e. adding new merch eVar, due to some technical reasons and devop capacities) so my option is limited to building segments : /. is there a way to build a generic segment as "sales condition" as shown in Pic B and then apply page and component type as filter?
Let me try a few things on my end, see if I can find a segment that will work.. You may not be far off on your attempts, but I sequential segments can sometimes be tricky.
So far I;m still having some issues, my numbers seem slightly inflated over what they should be...
Views
Replies
Total Likes
@Jennifer_Dungan I was able to fix this issue. this is how I resolved it:
- the filtering segment ( component type & previous page name) had to be at the visit level.
- for the condition segment, I changed the cart addition at hit level, and kept both the page & orders exist at visit level.
...and now numbers are aligned, viola!
Thank you so much for your constant support, I've made a lot of progress based on your feedbacks here, cheers!
Glad you got it working
Views
Likes
Replies
Views
Likes
Replies