Yes. Other testing and visual tools do this. You should add this as an
idea. Adobe is actually behind on this. A marketer should be able to
just navigate to the event they want to track and identify the css
selector
Can you add the ability to know what segments I use all the time and
keep them in a special tab? I hate having to search every time I need to
apply an audience. I use like 10 segments all the time, but I gotta
search every time.
This great. Can you move the collisions tab into the actual edit area?
You have to save the campaign and then go to the overview to see
collisions. In classic you could check collisions on the mbox level
Target can't interact with the DOM to determine what HTML selector is
present. You'd have to pass a parameter through the mbox to be able to
Target. You could use a simple javascript function to check the DOM if
the class exists and if it does pass a parameter into the mbox. Then you
could build and audience with the class value. Another option would be
to insert the javascript in your offer that would look at the DOM, once
loaded, and then call another mbox in the offer. If you have more
detail...
Here's one we use, if you never coded one beforename: testgroupif
(!user.get('testgroup')) {var ran_number=Math.floor((Math.random() *
100) + 1);return ran_number;}This one is 1=100
This is a classic clickTracking problem. The page is being forwarded on
too quickly for the response to be sent out. The browser can't send it
out in time and aborts it. I bet you see this being pretty sporadic
depending on how quick the next page is loading. I've used a delay
anchor with the clickTracking. Try something like this$('element').click(function (e) {
e.preventDefault(); var goingHere = this.getAttribute("href"); /// track
events adobe.target.trackEvent({"mbox": "clicked-cta","params": {
"param1": "value1"}}); setTimeout(function(){ window.location =
goingHere; },500); }); This is using JQuery. Your developers
may not use JQuery so they'd have to do something with Javascript. I
hope this helps. Let me know if you have any questions. Russ
You can totally use it without having Recommendations. It is an out of
the box feature of Target Standard. If you aren't seeing what you'd
expect for "Category Affinity" targeting check out this doc on how it
populates Category Affinity I've used it on all types of mboxes from
global, regional, and raw boxes and it has worked as I've expected. The
algorthm that it uses to define favorite can be confusing, so if it
isn't making sense you could reach out to CC.
Can you provide more details about how this is setup? Are you using
at.js? Are you using a global mbox or regional? Did you use a redirect
offer in Target or code your own redirect?
Hi Chris - I should've provided a little more detail. eVars are Adobe
Analytics variables that you would have to implement in your Target
offers. They would make a request to Adobe Analytics and the data would
appear there. We use a simple onClick with javascript or jquery to
populate and call the eVar. I can't really provide you with a code
sample because or implementation is so custom it wouldn't make sense.
Your developers should be able to call the eVar when visitors engage. it
would be simi...
Chris - We just fire and eVar with click actions since we are using A4T.
So for example....If the user clicked on the new nav you could fire
"eVar99=newnav" and they click an option you would fire
"eVar99-newnav_element1" This would give you the ability to look in AA
to see what the visitors for each cell are engaging with by test cell
and you'd be able to add any segment including mobile, desktop, etc.
This limits you to reporting in AA. Another option is to have 2
campaigns in Target. One that...
Nope. These are to only 3 fields that you can pass data to the Target
DB, audit tables. Here is a couple hacks/work-arounds we used.1. Pass
more than one parameter in orderId and productPurchasedID. We've passed
strings like this "12345677|abcsedee|dfdf123uejjs" into the orderId and
then parsed them out on the DW end. ProductPurchaseId can be comma
delimited and you could do the same thing once you pull them with an API
you can parse them out on the backend. 2. Use A4T. If you are using
Analytic...
This is basic statistics. If you flip a coin 100 times you could
potentially get lopsided heads or lopsided tails. If you continue to
flip a coin a million times you should experience a close 50/50
percentage of time and the more times you flip. You can tell when an a/b
test has normalized and the noise of adding a new experience has leveled
out when your experiences come back to an even split. This is the
principal behind A/A tests as well. If you run an A/A/B Test you know
you can call it when...
The majority of the time I do an equal split, but here are some cases
when I do 90/10 or 80/20. There are a bunch of confidence calculators
that will tell you how long something should be tested with an unequal
split. 1. 90/10 - Called a "Hold-out" Where I plan on rolling a new
feature or creative out with full on a/b testing it. These would be
things that have to happen due to technology upgrades or site standards
pushes. They basically provide a baseline for how the new feature is
performing a...
This is a regular occurrence for us. Sometimes we have to copy the
Activity that is running a hamster wheel sync and save and sync the new
campaign. Every time I report to CC, they are like "It appears to be
working now"Not very helpful I know, but that's our current state of
this issue.Russ
From the details you provided this seems like there shouldn't be any
issue with what you are trying to do. You might want to run this by CC
and see if they can help you troubelshoot
GrantWe have to use the multiple audience feature to generate a "force"
campaign for the experiences. Like this I agree that Target should
provide a way to preview the experience without this
work-aroundSiddharth.J Other A/B testing tools have the ability to
preview the experience with a test link, and it usually doesn't matter
how many cells or locations the test has. In Target as soon as we have a
multiple mboxes in a setup we lose the ability to use out of the box QA
parameters
Some follow up questions1. Are both locations in the variant B in the
test? Are you using the visual editor or the form based setup?2. Are
both locations on the same domain? 3. How does the visitor appear in the
data?4. Have you verified that your mbox cookie value persists from Cart
Page to the Product Display page?These things can lead to Target
thinking you haven't entered the campaign and gives you a new
experience. Give me the details and I might be able to help fix the
issue.
When Target reports are refreshed the additional metrics that I have
added are removed. Is this expected behavior for me to have to add them
back in manually every time I want the data to refresh? Can I get the
option to save my setup with key metics? Is this a bug I should submit
through CC?
I can copy an offer and I can copy an Activity why can't I copy a
Success Metric? It would be much more efficient to not have to select
"viewed an mbox" every success metric I create
Not very intuitive right? Even though you selected Analytics as the data
source you would have to have an Analytics event implemented for that
action. This would look at the Analytics event 23. If you choose Target
as the data source you would have to have an mbox implemented to fire
when the event occurs. It just depends on what you have implemented when
determining what data source.
I didn't activate it. I think it comes out of the box once you have A4T.
You can check your classification structure hereAdmin > Report Suites >
Select a report suite > Edit Settings > Conversion > Conversion
Classifications > once there you would select tntActive Dates appearsWe
then go into Workspace and see it hereWe'd choose the one that says
"(Analytics for Target)"If you aren't seeing this structure you might
want to reach out to CC.
You defined the conversion in Target? It won't be ported over as an
event to Analytics. You would have to create an Analytics event and
implement it on the click action. We created an eVar specifically for
this purpose. To send click actions to Analytics. Let me know if you
have any questions and I can show what we did. Russ
The special variable has a classification report called "Active
Dates"You can create excluding segments for the end date. So nothing
greater than whatever your end date is. Pretty handy and it is an epoch
format so it is always easy to exclude. Hope this helps
